detectederror.com - robtex.com
detectederror.com
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=1784173732 | ||||||
Previously MX for
detectederror.com |
Same first word
detectederror.com |
DNS History
10 records (6 active, 4 former)
●NSns1.name.com2026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
○NSns1.qualitynodedns.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-16 04:09:56
●NSns1kpv.name.com2026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
○NSns2.qualitynodedns.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-16 04:09:56
●NSns2bls.name.com2026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
●NSns3qtx.name.com2026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
●NSns4lny.name.com2026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
○MXdetectederror.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-16 04:09:56
●A167.114.155.922026-07-01 → 2026-07-16 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-16 04:09:56
○A198.27.68.682015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-16 04:09:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| detectederror.com | ns1kpv.name.com, ns2bls.name.com, ns3qtx.name.com, ns4lny.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1kpv.name.com, ns2bls.name.com, ns3qtx.name.com, ns4lny.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for detectederror.com (unsigned zone)
⏱️ Timing
Total: 112ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 167.114.155.92 |
| NS | 4 | ns1kpv.name.com, ns2bls.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1kpv.name.com, ns1kpv.name.com, ns2bls.name.com...)
Analysis
IP Addresses
detectederror.com directs to one IP number, which is 167.114.155.92.
vps-34b45080.vps.ovh.ca, for instance, is one of the other host names sharing IP numbers with detectederror.com.
Name Servers
The authoritative name servers for detectederror.com are ns1.name.com, ns1kpv.name.com, ns2bls.name.com and two others.
detectederror.com shares at least some of its name servers with other domains, including kyjace.com, christinemariebaker.com, atlantis-server.site and two others.
These name servers are frequently seen alongside ns4lny.name.com, ns3qtx.name.com, ns1cnb.name.com and 7 other name servers.
Hosts with two IP numbers each:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2bls.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3qtx.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4lny.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1kpv.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1kpv.name.com resolve to 163.114.216.17 IP addresses each.