detectederror.com - dns.ninja
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=1784848337 | ||||||
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-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
○NSns1.qualitynodedns.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-23 23:21:22
●NSns1kpv.name.com2026-07-01 → 2026-07-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
○NSns2.qualitynodedns.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-23 23:21:22
●NSns2bls.name.com2026-07-01 → 2026-07-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
●NSns3qtx.name.com2026-07-01 → 2026-07-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
●NSns4lny.name.com2026-07-01 → 2026-07-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
○MXdetectederror.com2015-06-14 → 2017-05-22 · 4 obs
● 2017-05-22 01:00:42
○ 2026-07-01 02:37:18
○ 2026-07-23 23:21:22
●A167.114.155.922026-07-01 → 2026-07-23 · 3 obs
● 2026-07-01 02:37:18
● 2026-07-23 23:21:22
○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-23 23:21:22
🔍 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.216.17
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: 203ms | 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 resolves to one IP address: 167.114.155.92.
vps-34b45080.vps.ovh.ca is an example of another host name that shares IP numbers with detectederror.com.
Name Servers
detectederror.com has five name servers, which are ns1.name.com, ns1kpv.name.com, ns2bls.name.com and two others.
detectederror.com partially shares its NS delegation with several other domains, including kyjace.com, christinemariebaker.com, atlantis-server.site and two others.
In DNS configurations, these name servers often share authority with ns4lny.name.com, ns3qtx.name.com, ns1cnb.name.com and 7 other name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns2bls.name.com resolves to 163.114.216.49 and 2402:cf80:107::1.
ns3qtx.name.com resolves to 163.114.217.17 and 2a00:edc0:107::49.
ns4lny.name.com resolves to 163.114.217.49 and 2402:cf80:107::49.
The host names ns1.name.com and ns1kpv.name.com both resolve to 2a00:edc0:107::1 IP addresses.
The host names ns1.name.com and ns1kpv.name.com both resolve to 163.114.216.17 IP addresses.