incidentcontrol.com - dns.ninja
incidentcontrol.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=1785706832 | ||||||
Same first word
incidentcontrol.com |
DNS History
10 records (5 active, 5 former)
●NSdns1.name-services.com2026-07-08 → 2026-08-02 · 3 obs
● 2026-07-08 16:36:04
● 2026-08-02 22:00:44
●NSdns2.name-services.com2026-07-08 → 2026-08-02 · 3 obs
● 2026-07-08 16:36:04
● 2026-08-02 22:00:44
●NSdns3.name-services.com2026-07-08 → 2026-08-02 · 3 obs
● 2026-07-08 16:36:04
● 2026-08-02 22:00:44
●NSdns4.name-services.com2026-07-08 → 2026-08-02 · 3 obs
● 2026-07-08 16:36:04
● 2026-08-02 22:00:44
●NSdns5.name-services.com2026-07-08 → 2026-08-02 · 3 obs
● 2026-07-08 16:36:04
● 2026-08-02 22:00:44
○NSns1.futurequest.net2015-06-25 → 2019-05-02 · 4 obs
● 2019-05-02 17:26:48
○ 2026-07-08 16:36:04
○ 2026-08-02 22:00:44
○NSns2.futurequest.net2015-06-25 → 2019-05-02 · 4 obs
● 2019-05-02 17:26:48
○ 2026-07-08 16:36:04
○ 2026-08-02 22:00:44
○NSns3.futurequest.net2015-06-25 → 2019-05-02 · 4 obs
● 2019-05-02 17:26:48
○ 2026-07-08 16:36:04
○ 2026-08-02 22:00:44
○MXmx.futurequest.net2015-06-25 → 2019-05-02 · 4 obs
● 2019-05-02 17:26:48
○ 2026-07-08 16:36:04
○ 2026-08-02 22:00:44
○A69.5.13.1822015-06-25 → 2019-05-02 · 4 obs
● 2019-05-02 17:26:48
○ 2026-07-08 16:36:04
○ 2026-08-02 22:00:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| incidentcontrol.com | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com... | 10 records |
✅ Authoritative Response
Server:64.98.148.137
NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for incidentcontrol.com (unsigned zone)
⏱️ Timing
Total: 240ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 5 | dns1.name-services.com, dns3.name-services.com... |
| SOA | 1 | dns1.name-services.com info.name-service |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)
Analysis
Name Servers
Delegation for incidentcontrol.com is to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.
incidentcontrol.com has at least partial name server overlap with other domains, such as autismseohio.org, baseball-card-price.com, 441animalhospital.com and two others.
It is common to see these name servers used together with name servers dns4.name-services.com and dns5.name-services.com.
Host names with two IP numbers:
dns1.name-services.com maps to two IP addresses — 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.
dns2.name-services.com maps to two IP addresses — 216.40.47.201 and 2604:4000:0:d:216:40:47:201.
dns3.name-services.com maps to two IP addresses — 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.
dns4.name-services.com maps to two IP addresses — 216.40.47.202 and 2604:4000:0:d:216:40:47:202.
dns5.name-services.com maps to two IP addresses — 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.