successfullyunsuccessfull.com - robtex.com
successfullyunsuccessfull.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 | ns25.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2161::d🇺🇸 GODADDY-DNS2603:5:2160::/44 | ||||||
| PTR | ns25.domaincontrol.com | ||||||
| A | 97.74.102.13🇺🇸 GODADDY-DNS97.74.102.0/23 | ||||||
| PTR | ns25.domaincontrol.com | ||||||
| NS | ns26.domaincontrol.com | ||||||
| A | 2603:5:2261::d🇺🇸 GODADDY-DNS2603:5:2260::/44 | ||||||
| PTR | ns26.domaincontrol.com | ||||||
| A | 173.201.70.13🇺🇸 GODADDY-DNS173.201.70.0/23 | ||||||
| PTR | ns26.domaincontrol.com | ||||||
| SOA | ns25.domaincontrol.comdns@jomax.net 2023-09-20 #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.netnstld@verisign-grs.com serial=1786095189 | ||||||
Same first word
successfullyunsuccessfull.com |
DNS History
4 records (4 active, 0 former)
●NSns25.domaincontrol.com2026-03-31 → 2026-08-07 · 2 obs
● 2026-08-07 09:38:56
●NSns26.domaincontrol.com2026-03-31 → 2026-08-07 · 2 obs
● 2026-08-07 09:38:56
●A15.197.148.332026-03-31 → 2026-08-07 · 2 obs
● 2026-08-07 09:38:56
●A3.33.130.1902026-03-31 → 2026-08-07 · 2 obs
● 2026-08-07 09:38:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net... | - |
| successfullyunsuccessfull.com | ns25.domaincontrol.com, ns26.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.102.13
NS records: ns25.domaincontrol.com, ns26.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for successfullyunsuccessfull.com (unsigned zone)
⏱️ Timing
Total: 138ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns25.domaincontrol.com, ns26.domaincontrol.com |
| SOA | 1 | ns25.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns25.domaincontrol.com, ns25.domaincontrol.com, ns26.domaincontrol.com...)
Analysis
IP Addresses
successfullyunsuccessfull.com directs to two IP numbers, 3.33.130.190 and 15.197.148.33
Among the host names that share IP numbers with successfullyunsuccessfull.com are serviceperfectsoftware.com, crm.healthcare, fitfamily.ca and two others.
Name Servers
successfullyunsuccessfull.com has two authoritative name servers — ns25.domaincontrol.com and ns26.domaincontrol.com.
successfullyunsuccessfull.com has the same name server delegation as a number of other domains, such as adeltd.co.uk, newmexicohighschool.com, paddock-house.com and two more.
Both ns25.domaincontrol.com and ns26.domaincontrol.com have two IP addresses each. ns25.domaincontrol.com resolves to 97.74.102.13 and 2603:5:2161::d; ns26.domaincontrol.com resolves to 173.201.70.13 and 2603:5:2261::d.