`remotelyrelevant.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.dan.com` ⭐
		A	2603:5:2125::43^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.dan.com`
		A	97.74.98.67^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.dan.com`
NS	`ns2.dan.com`
		A	2603:5:2225::43^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.dan.com`
		A	173.201.66.67^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.dan.com`
SOA	`ns1.dan.com`dns@jomax.net 2025-10-01 #0

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

Same first word

remotelyrelevant.com

DNS History

9 records (4 active, 5 former)

○NSns03.domaincontrol.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 10:05:36
○ 2015-11-01 15:07:40
○ 2026-03-23 12:21:44

○NSns04.domaincontrol.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 10:05:36
○ 2015-11-01 15:07:40
○ 2026-03-23 12:21:44

●NSns1.dan.com2026-03-23 → 2026-03-23 · 2 obs

○ 2015-11-01 15:07:40
● 2026-03-23 12:21:44

●NSns2.dan.com2026-03-23 → 2026-03-23 · 2 obs

○ 2015-11-01 15:07:40
● 2026-03-23 12:21:44

○MXmailstore1.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 10:05:36
○ 2015-11-01 15:07:40
○ 2026-03-23 12:21:44

○MXsmtp.secureserver.net2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 10:05:36
○ 2015-11-01 15:07:40
○ 2026-03-23 12:21:44

●A13.248.169.482026-03-23 → 2026-03-23 · 2 obs

○ 2015-11-01 15:07:40
● 2026-03-23 12:21:44

○A64.202.189.1702008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 10:05:36
○ 2015-11-01 15:07:40
○ 2026-03-23 12:21:44

●A76.223.54.1462026-03-23 → 2026-03-23 · 2 obs

○ 2015-11-01 15:07:40
● 2026-03-23 12:21:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
remotelyrelevant.com	ns1.dan.com, ns2.dan.com	4 records

✅ Authoritative Response

Server:173.201.66.67

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for remotelyrelevant.com (unsigned zone)

⏱️ Timing

Total: 589ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.248.169.48, 76.223.54.146`
NS	2	`ns1.dan.com, ns2.dan.com`
SOA	1	`ns1.dan.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

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

Analysis

IP Addresses

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

Other host names, for instance altinihalesi.com, verifydefender.xyz, www.musclebuildingsupplementsd15.publicsets.com, saaq.org and anarsizm.com share IP numbers with remotelyrelevant.com.

Name Servers

Two name servers ns1.dan.com and ns2.dan.com handle delegation for remotelyrelevant.com.

remotelyrelevant.com uses the same name server setup as other domains, for example pet-animal.com, oneclickupgrade.com, swiss-exchange.com, trueop.com and 0500london.com.

remotelyrelevant.com partially shares name servers with other domains; examples include overbruv.com, roxy.ee, elitestrip.com, strugglestory.com and ukk.fr.

These name servers are often used with the name servers ns1.undeveloped.com and ns2.undeveloped.com.

Host names with two IP numbers:

ns1.dan.com points to: 2603:5:2125::43 and 97.74.98.67

ns2.dan.com points to: 2603:5:2225::43 and 173.201.66.67

remotelyrelevant.com - robtex.com