nullifiednetwork.dev - robtex.com
nullifiednetwork.dev
dev
| DNSSEC | π Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com β | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
nullifiednetwork.dev |
Previous names
Next names
DNS History
5 records (5 active, 0 former)
βNSns1kwy.name.com2026-08-18 β 2026-08-29 Β· 2 obs
β 2026-08-29 16:58:20
βNSns2hkt.name.com2026-08-18 β 2026-08-29 Β· 2 obs
β 2026-08-29 16:58:20
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| nullifiednetwork.dev | ns4qxz.name.com, ns2hkt.name.com, ns1kwy.name.com, ns3ghw.name.com | - |
β Authoritative Response
Server:163.114.217.17
NS records: ns4qxz.name.com, ns2hkt.name.com, ns1kwy.name.com, ns3ghw.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for nullifiednetwork.dev (unsigned zone)
β±οΈ Timing
Total: 666ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1kwy.name.com, ns2hkt.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
Name Servers
The authoritative name servers for nullifiednetwork.dev are ns1.name.com, ns1kwy.name.com, ns2hkt.name.com and two others.
nullifiednetwork.dev has at least partial name server overlap with other domains, such as qm282.com, sluggergang.com, sachwert-rente.com and two others.
ns4qxz.name.com, ns3ghw.name.com and ns1cnb.name.com β plus 7 other name servers β are commonly paired with these name servers.
Hosts with two IP numbers each:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1kwy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2hkt.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3ghw.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4qxz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1kwy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1kwy.name.com resolve to 163.114.216.17 IP addresses each.