zeroco.dev - robtex.com
zeroco.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
zeroco.cn |
zeroco.rocks |
zeroco.dev |
zeroco.de |
zeroco.ai |
zeroco.co |
zeroco.in |
zeroco.my |
zeroco.com.au |
zeroco.se |
zeroco.com |
Similar names
Previous names
Next names
DNS History
5 records (5 active, 0 former)
βNSns1.name.com2026-09-01 β 2026-09-04 Β· 4 obs
β 2026-09-03 02:04:38
β 2026-09-03 16:53:40
β 2026-09-04 11:47:42
βNSns1dnx.name.com2026-09-01 β 2026-09-04 Β· 2 obs
β 2026-09-04 11:47:42
βNSns2fjz.name.com2026-09-01 β 2026-09-04 Β· 2 obs
β 2026-09-04 11:47:42
π 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 |
| zeroco.dev | ns1dnx.name.com, ns4bht.name.com, ns3ghw.name.com, ns2fjz.name.com | - |
β Authoritative Response
Server:163.114.216.49
NS records: ns1dnx.name.com, ns4bht.name.com, ns3ghw.name.com, ns2fjz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for zeroco.dev (unsigned zone)
β±οΈ Timing
Total: 725ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1dnx.name.com, ns2fjz.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
Five name servers handle delegation for zeroco.dev: ns1.name.com, ns1dnx.name.com, ns2fjz.name.com and two others.
zeroco.dev partially shares its NS delegation with several other domains, including ahilan.me, movietrip.com, redneckeng.com and two others.
In DNS configurations, these name servers often share authority with ns4bht.name.com, ns3ghw.name.com, ns4ghm.name.com and 7 other name servers.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1dnx.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fjz.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.
ns4bht.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1dnx.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1dnx.name.com resolve to 163.114.216.17 IP addresses each.