`metaversedaf.com`

DNSSEC	⚠️ Not signed
A	99.83.176.46^{🇺🇸 Amazon99.83.176.0/20}
		PTR	`a44fc39dcd01d2028.awsglobalaccelerator.com`
NS	`ha1.markmonitor.zone` ⭐
		A	2001:67c:1bc::5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ha1.markmonitor.zone`
		A	192.174.68.5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ha1.markmonitor.zone`
NS	`ha2.markmonitor.zone`
		A	2620:10a:80eb::6b^{🇨🇦 CIRA-22620:10a:80eb::/48 D-Zone Anycast Cloud 1}
			PTR	`ha2.markmonitor.zone`
		A	162.219.54.170^{🇨🇦 CIRA-2162.219.54.0/24 D-Zone Anycast Cloud1}
			PTR	`ha2.markmonitor.zone`
NS	`ha3.markmonitor.zone`
		A	2001:67c:10b8::5^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ha3.markmonitor.zone`
		A	176.97.158.5^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ha3.markmonitor.zone`
NS	`ha4.markmonitor.zone`
		A	2620:10a:80ec::6b^{🇨🇦 CIRA-32620:10a:80ec::/48 D-Zone IPv6 Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
		A	162.219.55.170^{🇨🇦 CIRA-3162.219.55.0/24 D-Zone Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
TXT	`v=spf1 -all`
SOA	`ha1.markmonitor.zone`hostmaster@markmonitor.com 2024-07-26 #1

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

Same first word

metaversedaf.com

DNS History

5 records (5 active, 0 former)

●NSha1.markmonitor.zone2026-06-29 → 2026-07-27 · 2 obs

● 2026-06-29 22:09:06
● 2026-07-27 05:34:20

●NSha2.markmonitor.zone2026-06-29 → 2026-07-27 · 2 obs

● 2026-06-29 22:09:06
● 2026-07-27 05:34:20

●NSha3.markmonitor.zone2026-06-29 → 2026-07-27 · 2 obs

● 2026-06-29 22:09:06
● 2026-07-27 05:34:20

●NSha4.markmonitor.zone2026-06-29 → 2026-07-27 · 2 obs

● 2026-06-29 22:09:06
● 2026-07-27 05:34:20

●A99.83.176.462026-06-29 → 2026-07-27 · 2 obs

● 2026-06-29 22:09:06
● 2026-07-27 05:34:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
metaversedaf.com	ha4.markmonitor.zone, ha2.markmonitor.zone, ha1.markmonitor.zone, ha3.markmonitor.zone	-

✅ Authoritative Response

Server:176.97.158.5

NS records: ha4.markmonitor.zone, ha2.markmonitor.zone, ha1.markmonitor.zone, ha3.markmonitor.zone

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for metaversedaf.com (unsigned zone)

⏱️ Timing

Total: 319ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`99.83.176.46`
NS	4	`ha1.markmonitor.zone, ha2.markmonitor.zone...`
TXT	1	`v=spf1 -all`
SOA	1	`ha1.markmonitor.zone hostmaster.markmoni`

Analysis

IP Addresses

metaversedaf.com points to a single IP number: 99.83.176.46.

Additional host names — krystexa.net, gulfstream650.info, smallvillebank.com and two others — share IP numbers with metaversedaf.com.

Name Servers

metaversedaf.com has four authoritative name servers: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone.

metaversedaf.com has at least partial name server overlap with other domains, such as peterbilt.com.tw, regencov2.com, cpadomains.net and two others.

ns1.markmonitor.com, ns2.markmonitor.com and ns3.markmonitor.com — plus 4 other name servers — are commonly paired with these name servers.

ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone all point to exactly two IP numbers each: ha1.markmonitor.zone → 192.174.68.5 and 2001:67c:1bc::5; ha2.markmonitor.zone → 162.219.54.170 and 2620:10a:80eb::6b; ha3.markmonitor.zone → 176.97.158.5 and 2001:67c:10b8::5; ha4.markmonitor.zone → 162.219.55.170 and 2620:10a:80ec::6b.

metaversedaf.com - robtex.com