chainshot.com - dns.ninja
chainshot.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=1786553259 | ||||||
Same first word
chainshot.net |
chainshot.com |
Similar names
DNS History
18 records (10 active, 8 former)
●NSns1.name.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●NSns1vwx.name.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●NSns2ckr.name.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
○NSns33.domaincontrol.com2015-08-20 → 2016-07-03 · 4 obs
● 2016-07-03 20:26:14
○ 2017-03-26 01:59:30
○ 2026-08-12 17:01:10
○NSns34.domaincontrol.com2015-08-20 → 2016-07-03 · 4 obs
● 2016-07-03 20:26:14
○ 2017-03-26 01:59:30
○ 2026-08-12 17:01:10
●NSns3hjx.name.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●NSns4bht.name.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
○NSns61.domaincontrol.com2017-03-26 → 2017-03-26 · 4 obs
● 2017-03-26 01:59:30
○ 2026-04-09 02:02:30
○ 2026-08-12 17:01:10
○NSns62.domaincontrol.com2017-03-26 → 2017-03-26 · 4 obs
● 2017-03-26 01:59:30
○ 2026-04-09 02:02:30
○ 2026-08-12 17:01:10
●MXalt1.aspmx.l.google.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●MXalt2.aspmx.l.google.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●MXalt3.aspmx.l.google.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●MXalt4.aspmx.l.google.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
●MXaspmx.l.google.com2026-04-09 → 2026-08-12 · 3 obs
● 2026-04-09 02:02:30
● 2026-08-12 17:01:10
○MXmailstore1.secureserver.net2015-08-20 → 2017-03-26 · 4 obs
● 2017-03-26 01:59:30
○ 2026-04-09 02:02:30
○ 2026-08-12 17:01:10
○MXsmtp.secureserver.net2015-08-20 → 2017-03-26 · 4 obs
● 2017-03-26 01:59:30
○ 2026-04-09 02:02:30
○ 2026-08-12 17:01:10
○A184.168.221.562017-03-26 → 2017-03-26 · 4 obs
● 2017-03-26 01:59:30
○ 2026-04-09 02:02:30
○ 2026-08-12 17:01:10
○A50.63.202.462015-08-20 → 2016-07-03 · 4 obs
● 2016-07-03 20:26:14
○ 2017-03-26 01:59:30
○ 2026-08-12 17:01:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| chainshot.com | ns1vwx.name.com, ns2ckr.name.com, ns3hjx.name.com, ns4bht.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1vwx.name.com, ns2ckr.name.com, ns3hjx.name.com, ns4bht.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chainshot.com (unsigned zone)
⏱️ Timing
Total: 352ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1vwx.name.com, ns2ckr.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 4 | google-site-verification=bNGqYyXiFU1cje5, brave-ledger-verification=bd6a483dbdbafd... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1vwx.name.com, ns1vwx.name.com, ns2ckr.name.com...)
Analysis
Name Servers
The authoritative name servers for chainshot.com are ns1.name.com, ns1vwx.name.com, ns2ckr.name.com and two others.
There is at least partial name server overlap between chainshot.com and other domains — 74843484.xyz, project-insomnia.com, zvaf.com and two more among them.
These name servers regularly appear alongside ns4bht.name.com, ns1cny.name.com, ns3hjx.name.com and 7 other name servers in NS record sets.
Hosts with two IP numbers each:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1vwx.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2ckr.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3hjx.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4bht.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1vwx.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1vwx.name.com each resolve to 163.114.216.17 IP addresses.
Mail Servers
chainshot.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
chainshot.com shares at least some of its mail servers with other domains — for example ns500794.ns500841.ns500821.ns500794.ns500795.ns500795.ns500794.ns500795.ns500794.ns500790.ns500795.lustypartnersfinder.com, ns500699.ns500693.ns500734.ns500693.ns500699.ns500734.ns500588.ns500588.ns500683.ns500683.ns500578.ns500110.dtrkdll.com, ns500693.ns500693.ns500699.ns500699.ns500693.ns500693.ns500734.ns500588.ns500693.ns500693.ns500699.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to two addresses: 142.251.16.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.