`metaversestable.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`verification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net serial=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=1774613327

Same first word

metaversestable.com

DNS History

5 records (5 active, 0 former)

●NSns1.afternic.com2026-03-02 → 2026-03-27 · 2 obs

● 2026-03-02 15:02:22
● 2026-03-27 12:13:32

●NSns2.afternic.com2026-03-02 → 2026-03-27 · 2 obs

● 2026-03-02 15:02:22
● 2026-03-27 12:13:32

●NSverification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn2026-03-02 → 2026-03-27 · 2 obs

● 2026-03-02 15:02:22
● 2026-03-27 12:13:32

●A13.248.169.482026-03-02 → 2026-03-27 · 2 obs

● 2026-03-02 15:02:22
● 2026-03-27 12:13:32

●A76.223.54.1462026-03-02 → 2026-03-27 · 2 obs

● 2026-03-02 15:02:22
● 2026-03-27 12:13:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
metaversestable.com	ns1.afternic.com, ns2.afternic.com, verification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for metaversestable.com (unsigned zone)

⏱️ Timing

Total: 3169ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

metaversestable.com resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.

other host names including mail.arezen.com, portal-cdn.microsoftonline.dogcratecover.com, cfja.net, clubinter.com and tinrao.com share IP numbers with metaversestable.com.

Name Servers

metaversestable.com is delegated to three name servers ns1.afternic.com, ns2.afternic.com and verification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn.

metaversestable.com at least partially shares name servers with other domains, for instance dstravel.com, jachaibachai.com, rodeo.cn, lilysblog.com and furnitureinstallationservice.com.

These name servers are commonly used with verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn.

Host names with two IP numbers:

ns1.afternic.com points to: 2603:5:2126::45 and 97.74.98.69.

ns2.afternic.com points to: 2603:5:2226::45 and 173.201.66.69.

verification-o2mhvysikbewdvuypk9kmp.ns101.verify.hn points to: 13.248.169.48 and 76.223.54.146.

metaversestable.com - robtex.com