`metropolisdata.com`

DNSSEC	⚠️ Not signed
A	192.0.78.24^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.25^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns1.wordpress.com` ⭐
		A	2a04:fa87:ffff::c6b5:7409^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns1.wordpress.com`
		A	198.181.116.9^{🇺🇸 Automattic198.181.116.0/24 Route Object}
			PTR	`ns1.wordpress.com`
NS	`ns2.wordpress.com`
		A	2a04:fa87:ffff::c6b5:7509^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns2.wordpress.com`
		A	198.181.117.9^{🇺🇸 Automattic198.181.117.0/24 Route Object}
			PTR	`ns2.wordpress.com`
NS	`ns3.wordpress.com`
		A	2620:115:c00f::c000:4a09^{🇺🇸 Automattic2620:115:c00f::/48 Route6 Object}
			PTR	`ns3.wordpress.com`
		A	192.0.74.9^{🇺🇸 Automattic192.0.74.0/24 Route Object}
			PTR	`ns3.wordpress.com`
MX	`metropolisdata-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:ca0b::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	2a01:111:f403:ca0b::2^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo0p265cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00601.inbound.protection.outlook.com`
		A	52.101.89.0^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	52.101.89.1^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo0p265cu00201.inbound.protection.outlook.com`
		A	52.101.89.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo3p265cu00302.inbound.protection.outlook.com`
		A	52.101.99.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00502.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com include:_spf.wpcloud.com -all`
TXT	`MS=ms39840814`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2025-02-18 #3

`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=1784282727

Same first word

metropolisdata.com

Similar names

datametropolis.com

DNS History

12 records (6 active, 6 former)

○NSa.dns.gandi.net2016-01-23 → 2017-02-16 · 4 obs

● 2016-01-23 19:19:20
● 2017-02-16 08:17:24
○ 2020-02-24 14:34:46
○ 2026-07-17 10:15:24

○NSb.dns.gandi.net2016-01-23 → 2017-02-16 · 4 obs

● 2016-01-23 19:19:20
● 2017-02-16 08:17:24
○ 2020-02-24 14:34:46
○ 2026-07-17 10:15:24

○NSc.dns.gandi.net2016-01-23 → 2017-02-16 · 4 obs

● 2016-01-23 19:19:20
● 2017-02-16 08:17:24
○ 2020-02-24 14:34:46
○ 2026-07-17 10:15:24

●NSns1.wordpress.com2026-02-20 → 2026-07-17 · 3 obs

○ 2020-02-24 14:34:46
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

●NSns2.wordpress.com2026-02-20 → 2026-07-17 · 3 obs

○ 2020-02-24 14:34:46
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

●NSns3.wordpress.com2026-02-20 → 2026-07-17 · 3 obs

○ 2020-02-24 14:34:46
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

○MXfb.mail.gandi.net2016-01-23 → 2017-02-16 · 4 obs

● 2016-01-23 19:19:20
● 2017-02-16 08:17:24
○ 2020-02-24 14:34:46
○ 2026-07-17 10:15:24

●MXmetropolisdata-com.mail.protection.outlook.com2026-02-20 → 2026-07-17 · 3 obs

○ 2020-02-24 14:34:46
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

○MXspool.mail.gandi.net2016-01-23 → 2017-02-16 · 4 obs

● 2016-01-23 19:19:20
● 2017-02-16 08:17:24
○ 2020-02-24 14:34:46
○ 2026-07-17 10:15:24

●A192.0.78.242026-02-20 → 2026-07-17 · 3 obs

○ 2017-02-16 08:17:24
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

●A192.0.78.252026-02-20 → 2026-07-17 · 3 obs

○ 2017-02-16 08:17:24
● 2026-02-20 20:22:34
● 2026-07-17 10:15:24

○A96.127.238.222016-01-23 → 2016-04-30 · 4 obs

● 2016-01-23 19:19:20
● 2016-04-30 08:48:58
○ 2017-02-16 08:17:24
○ 2026-07-17 10:15:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net...	-
metropolisdata.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:198.181.116.9

NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for metropolisdata.com (unsigned zone)

⏱️ Timing

Total: 141ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.24, 192.0.78.25`
NS	3	`ns1.wordpress.com, ns2.wordpress.com...`
MX	1	`metropolisdata-com.mail.protection.outlo`
TXT	2	`v=spf1 include:spf.protection.outlook.co, MS=ms39840814`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)

Analysis

IP Addresses

metropolisdata.com points to the IP addresses 192.0.78.24 and 192.0.78.25

Two other host names, along with hcac.ca, darac.com and actsgame.com, also share IP numbers with metropolisdata.com.

Name Servers

The authoritative name servers for metropolisdata.com are ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — three in total.

The name servers of metropolisdata.com overlap at least partially with those of other domains — among them sdkapartment.com, rwcom.org, mvadillo.com and two more.

ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com all resolve to exactly two IP numbers apiece: ns1.wordpress.com → 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409; ns2.wordpress.com → 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509; ns3.wordpress.com → 192.0.74.9 and 2620:115:c00f::c000:4a09.

Mail Servers

The sole mail server for metropolisdata.com is metropolisdata-com.mail.protection.outlook.com.

With 8 IP addresses total, metropolisdata-com.mail.protection.outlook.com resolves to 52.101.89.0, 52.101.89.1, 52.101.89.2 and 5 others.

metropolisdata.com - robtex.com