`failuretophoenix.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns29.domaincontrol.com` ⭐
		A	2603:5:2181::f^{🇺🇸 GODADDY-DNS2603:5:2180::/44}
			PTR	`ns29.domaincontrol.com`
		A	97.74.104.15^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns29.domaincontrol.com`
NS	`ns30.domaincontrol.com`
		A	2603:5:2281::f^{🇺🇸 GODADDY-DNS2603:5:2280::/44}
			PTR	`ns30.domaincontrol.com`
		A	173.201.72.15^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns30.domaincontrol.com`
SOA	`ns29.domaincontrol.com`dns@jomax.net 2023-09-19 #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=1778835846

Same first word

failuretophoenix.com

DNS History

5 records (4 active, 1 former)

●NSns29.domaincontrol.com2019-04-10 → 2026-05-15 · 2 obs

● 2019-04-10 06:56:22
● 2026-05-15 09:23:06

●NSns30.domaincontrol.com2019-04-10 → 2026-05-15 · 2 obs

● 2019-04-10 06:56:22
● 2026-05-15 09:23:06

●A15.197.148.332026-03-30 → 2026-05-15 · 3 obs

○ 2019-04-10 06:56:22
● 2026-03-30 06:45:32
● 2026-05-15 09:23:06

○A184.168.221.612019-04-10 → 2019-04-10 · 3 obs

● 2019-04-10 06:56:22
○ 2026-03-30 06:45:32
○ 2026-05-15 09:23:06

●A3.33.130.1902026-03-30 → 2026-05-15 · 3 obs

○ 2019-04-10 06:56:22
● 2026-03-30 06:45:32
● 2026-05-15 09:23:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
failuretophoenix.com	ns29.domaincontrol.com, ns30.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.72.15

NS records: ns29.domaincontrol.com, ns30.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for failuretophoenix.com (unsigned zone)

⏱️ Timing

Total: 194ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns29.domaincontrol.com, ns30.domaincontrol.com`
SOA	1	`ns29.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns29.domaincontrol.com, ns29.domaincontrol.com, ns30.domaincontrol.com...)

Analysis

IP Addresses

failuretophoenix.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names such as nesuru.com, libelexpert.com, ell2.com, male.tips and togel389fortune.com share IPs with failuretophoenix.com.

Name Servers

Two name servers ns29.domaincontrol.com and ns30.domaincontrol.com handle the delegation for failuretophoenix.com.

failuretophoenix.com shares the same name server setup as other domains, for example bytanfer.com, sonicsentinel.com, genesisprotectionplan.com, stoild.com and 30arealestate.com.

Host names with two IP numbers:

ns29.domaincontrol.com points to 2603:5:2181::f and 97.74.104.15.

ns30.domaincontrol.com points to 2603:5:2281::f and 173.201.72.15.

failuretophoenix.com - robtex.com