3rdhonk.com - dns.ninja
3rdhonk.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=1783709957 | ||||||
Same first word
3rdhonk.com |
DNS History
6 records (6 active, 0 former)
●A75.126.104.2432026-02-14 → 2026-07-10 · 2 obs
● 2026-07-10 19:06:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| 3rdhonk.com | ns1dhl.name.com, ns2dhj.name.com, ns3fqs.name.com, ns4dls.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.49
NS records: ns1dhl.name.com, ns2dhj.name.com, ns3fqs.name.com, ns4dls.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 3rdhonk.com (unsigned zone)
⏱️ Timing
Total: 199ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.104.243 |
| NS | 4 | ns1dhl.name.com, ns2dhj.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1dhl.name.com, ns1dhl.name.com, ns2dhj.name.com...)
Analysis
IP Addresses
3rdhonk.com has exactly one IP address — 75.126.104.243.
1.mqsto.org, ns2.inoveris.com, winsanled.net plus two other host names have IP numbers in common with 3rdhonk.com.
Name Servers
Five name servers handle delegation for 3rdhonk.com: ns1.name.com, ns1dhl.name.com, ns2dhj.name.com and two others.
At least some of 3rdhonk.com's name servers are shared with other domains, for example fourple.com, elementsholisticwellness.com, latd.co.uk and two more.
These name servers tend to co-occur with ns3fqs.name.com, ns4dls.name.com, ns4jnz.name.com and 7 other name servers in the same DNS delegations.
Host names pointing to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1dhl.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2dhj.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4dls.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1dhl.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1dhl.name.com each resolve to 163.114.216.17 IP addresses.