able - dns.ninja
able
(root)
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.root-servers.net ⭐ ⚠️ Not in parent delegation | ||||||
| NS | b.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | c.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | d.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | e.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | f.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | g.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | h.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | i.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | j.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | k.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | l.root-servers.net ⚠️ Not in parent delegation | ||||||
| NS | m.root-servers.net ⚠️ Not in parent delegation | ||||||
| SOA | a.root-servers.netnstld@verisign-grs.com 2026-07-22 #3 | ||||||
Subdomains
nic.able |
saitama.able |
maison.able |
test-saitama.able |
Same first word
Similar names
DNS History
11 records (6 active, 5 former)
●NSa.nic.able2026-02-15 → 2026-07-22 · 3 obs
● 2026-02-15 16:31:24
● 2026-07-22 22:06:18
●NSb.nic.able2026-02-15 → 2026-07-22 · 3 obs
● 2026-02-15 16:31:24
● 2026-07-22 22:06:18
●NSc.nic.able2026-02-15 → 2026-07-22 · 3 obs
● 2026-02-15 16:31:24
● 2026-07-22 22:06:18
●NSns1.dns.nic.able2016-08-01 → 2026-07-22 · 2 obs
● 2026-07-22 22:06:18
●NSns2.dns.nic.able2016-08-01 → 2026-07-22 · 2 obs
● 2026-07-22 22:06:18
●NSns3.dns.nic.able2016-08-01 → 2026-07-22 · 2 obs
● 2026-07-22 22:06:18
○NSns4.dns.nic.able2016-08-01 → 2020-12-14 · 4 obs
● 2020-12-14 09:20:08
○ 2026-02-15 16:31:24
○ 2026-07-22 22:06:18
○NSns5.dns.nic.able2016-08-01 → 2020-12-14 · 4 obs
● 2020-12-14 09:20:08
○ 2026-02-15 16:31:24
○ 2026-07-22 22:06:18
○NSns6.dns.nic.able2016-08-01 → 2020-12-14 · 4 obs
● 2020-12-14 09:20:08
○ 2026-02-15 16:31:24
○ 2026-07-22 22:06:18
○MXyour-dns-needs-immediate-attention.able2016-08-01 → 2016-08-27 · 4 obs
● 2016-08-27 07:20:02
○ 2016-10-13 22:46:16
○ 2026-07-22 22:06:18
○A127.0.53.532016-08-01 → 2016-08-27 · 4 obs
● 2016-08-27 07:20:02
○ 2016-10-13 22:46:16
○ 2026-07-22 22:06:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| able | ns3.dns.nic.able, ns2.dns.nic.able, ns1.dns.nic.able, a.nic.able... | 12 records |
✅ Authoritative Response
Server:37.209.192.10
NS records: ns3.dns.nic.able, ns2.dns.nic.able, ns1.dns.nic.able, a.nic.able, c.nic.able, b.nic.able
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 264ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 6 | a.nic.able, b.nic.able... |
| SOA | 1 | ns1.dns.nic.able admin.tldns.godaddy |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (a.nic.able, b.nic.able, c.nic.able...)
Analysis
Hierarchy
The domain able is a parent of nic.able, saitama.able, maison.able and test-saitama.able.
Name Servers
able has 6 name servers — a.nic.able, b.nic.able, c.nic.able and 3 others.
The name servers for able overlap at least partially with those of other domains — for example nic.able.
It is common for these name servers to be used in conjunction with the name servers ns1.dns.nic.able, ns2.dns.nic.able and ns3.dns.nic.able.
Host names that have two IP addresses:
a.nic.able resolves to 37.209.192.10 and 2001:dcd:1::10.
b.nic.able resolves to 37.209.194.10 and 2001:dcd:2::10.
c.nic.able resolves to 37.209.196.10 and 2001:dcd:3::10.
ns1.dns.nic.able resolves to 156.154.144.3 and 2610:a1:1071::3.
ns2.dns.nic.able resolves to 156.154.145.3 and 2610:a1:1072::3.
ns3.dns.nic.able resolves to 156.154.159.3 and 2610:a1:1073::3.