`mysuccessfulfailures.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	`ns51.domaincontrol.com` ⭐
		A	2603:5:2192::1a^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns51.domaincontrol.com`
		A	97.74.105.26^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns51.domaincontrol.com`
NS	`ns52.domaincontrol.com`
		A	2603:5:2292::1a^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns52.domaincontrol.com`
		A	173.201.73.26^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns52.domaincontrol.com`
SOA	`ns51.domaincontrol.com`dns@jomax.net 2025-09-27 #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=1774687907

Previously MX for

mysuccessfulfailures.com

Same first word

mysuccessfulfailures.com

DNS History

9 records (4 active, 5 former)

○NSns1.bluehost.com2016-02-07 → 2016-05-01 · 4 obs

● 2016-02-07 04:14:48
● 2016-05-01 05:13:28
○ 2017-01-08 07:36:28
○ 2026-03-28 09:19:24

○NSns2.bluehost.com2016-02-07 → 2016-05-01 · 4 obs

● 2016-02-07 04:14:48
● 2016-05-01 05:13:28
○ 2017-01-08 07:36:28
○ 2026-03-28 09:19:24

●NSns51.domaincontrol.com2026-03-02 → 2026-03-28 · 3 obs

○ 2017-01-08 07:36:28
● 2026-03-02 03:06:54
● 2026-03-28 09:19:24

●NSns52.domaincontrol.com2026-03-02 → 2026-03-28 · 3 obs

○ 2017-01-08 07:36:28
● 2026-03-02 03:06:54
● 2026-03-28 09:19:24

○MXmail.mysuccessfulfailures.com2016-02-07 → 2016-02-07 · 3 obs

● 2016-02-07 04:14:48
○ 2016-05-01 05:13:28
○ 2026-03-28 09:19:24

○MXmysuccessfulfailures.com2016-05-01 → 2016-05-01 · 4 obs

○ 2016-02-07 04:14:48
● 2016-05-01 05:13:28
○ 2017-01-08 07:36:28
○ 2026-03-28 09:19:24

●A15.197.148.332026-03-02 → 2026-03-28 · 3 obs

○ 2017-01-08 07:36:28
● 2026-03-02 03:06:54
● 2026-03-28 09:19:24

●A3.33.130.1902026-03-02 → 2026-03-28 · 3 obs

○ 2017-01-08 07:36:28
● 2026-03-02 03:06:54
● 2026-03-28 09:19:24

○A74.220.219.1492016-02-07 → 2016-05-01 · 4 obs

● 2016-02-07 04:14:48
● 2016-05-01 05:13:28
○ 2017-01-08 07:36:28
○ 2026-03-28 09:19:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, k.gtld-servers.net, g.gtld-servers.net, c.gtld-servers.net...	-
mysuccessfulfailures.com	ns51.domaincontrol.com, ns52.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.73.26

NS records: ns51.domaincontrol.com, ns52.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mysuccessfulfailures.com (unsigned zone)

⏱️ Timing

Total: 1567ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns51.domaincontrol.com, ns51.domaincontrol.com, ns52.domaincontrol.com...)

Analysis

IP Addresses

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

Other host names such as ghbkk.com, springassisted.com, solentventure.com, stack-pc.com and savantacademy.org share IPs with mysuccessfulfailures.com.

Name Servers

mysuccessfulfailures.com is delegated to two name servers: ns51.domaincontrol.com and ns52.domaincontrol.com.

mysuccessfulfailures.com shares the same name server setup as altapure.org, halehealing.com, polytechnicscorp.com, longbeachhouseforsale.com and workplace-safety.net.

mysuccessfulfailures.com shares some name servers with other domains, for instance dsteel.net.

Host names with two IP numbers: ns51.domaincontrol.com points to: 2603:5:2192::1a and 97.74.105.26; ns52.domaincontrol.com points to: 2603:5:2292::1a and 173.201.73.26.

mysuccessfulfailures.com - robtex.com