🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`structopolis.com`

DNSSEC	⚠️ Not signed
A	216.239.32.21^{🇺🇸 Google216.239.32.0/24}
		PTR	`any-in-2015.1e100.net`
A	216.239.34.21^{🇺🇸 Google216.239.34.0/24}
A	216.239.36.21^{🇺🇸 Google216.239.36.0/24}
A	216.239.38.21^{🇺🇸 Google216.239.38.0/24}
NS	`ns1.netfirms.com` ⭐
		A	162.159.24.252^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.netfirms.com`
		A	162.159.25.208^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4013:c20::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqvu-in-f27.1e100.net`
		A	172.253.153.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yugrqfv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4010:c22::1a^{🇫🇮 Google2a00:1450:4010::/48}
			PTR	`yulpptr-in-f26.1e100.net`
		A	172.253.152.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yulpptr-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.26^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f26.1e100.net`
TXT	`v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all`
SOA	`ns1.netfirms.com`dnsadmin@netfirms.com 2012-11-30 #7

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1794730713

Same first word

structopolis.com

Previous names

Next names

structopora.com

structopt.com

structoptima.com

DNS History

15 records (11 active, 4 former)

○NSdns.site5.com2015-07-18 → 2018-11-01 · 4 obs

● 2015-07-18 17:44:42
● 2018-11-01 03:20:02
○ 2026-09-03 09:45:58
○ 2026-11-15 08:43:42

○NSdns2.site5.com2015-07-18 → 2018-11-01 · 4 obs

● 2015-07-18 17:44:42
● 2018-11-01 03:20:02
○ 2026-09-03 09:45:58
○ 2026-11-15 08:43:42

●NSns1.netfirms.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●NSns2.netfirms.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●MXalt1.aspmx.l.google.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●MXalt2.aspmx.l.google.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●MXalt3.aspmx.l.google.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●MXalt4.aspmx.l.google.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●MXaspmx.l.google.com2026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

○MXmail.structopolis.com2015-07-18 → 2018-11-01 · 4 obs

● 2015-07-18 17:44:42
● 2018-11-01 03:20:02
○ 2026-09-03 09:45:58
○ 2026-11-15 08:43:42

○A146.101.249.1072015-07-18 → 2018-11-01 · 4 obs

● 2015-07-18 17:44:42
● 2018-11-01 03:20:02
○ 2026-09-03 09:45:58
○ 2026-11-15 08:43:42

●A216.239.32.212026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●A216.239.34.212026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●A216.239.36.212026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

●A216.239.38.212026-09-03 → 2026-11-15 · 3 obs

○ 2018-11-01 03:20:02
● 2026-09-03 09:45:58
● 2026-11-15 08:43:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
structopolis.com	ns1.netfirms.com, ns2.netfirms.com	2 records

✅ Authoritative Response

Server:162.159.25.208

NS records: ns1.netfirms.com, ns2.netfirms.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for structopolis.com (unsigned zone)

⏱️ Timing

Total: 1459ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`216.239.38.21, 216.239.34.21...`
NS	2	`ns2.netfirms.com, ns1.netfirms.com`
MX	5	`ALT2.ASPMX.L.GOOGLE.com (pri: 5), ALT4.ASPMX.L.GOOGLE.com (pri: 10)...`
TXT	1	`v=spf1 ip4:66.96.128.0/18 include:websit`
SOA	1	`ns1.netfirms.com dnsadmin.netfirms.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.netfirms.com, ns2.netfirms.com)

Analysis

IP Addresses

structopolis.com points to the four IP addresses 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.

Name Servers

structopolis.com uses two name servers for its delegation: ns1.netfirms.com and ns2.netfirms.com.

Both ns1.netfirms.com and ns2.netfirms.com have a single IP address each — ns1.netfirms.com resolves to 162.159.24.252 while ns2.netfirms.com resolves to 162.159.25.208.

Mail Servers

structopolis.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 172.253.153.27 and 2a00:1450:4013:c20::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.135.27 and 2607:f8b0:4023:1015::1b.

alt3.aspmx.l.google.com directs traffic to 172.253.152.27 and 2a00:1450:4010:c22::1a.

alt4.aspmx.l.google.com directs traffic to 142.251.96.26 and 2607:f8b0:4003:c4a::1a.

structopolis.com - robtex.com