localhost3000.dev - robtex.com
localhost3000.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
Previous names
Next names
DNS History
5 records (5 active, 0 former)
βNSns1hnx.name.com2026-08-28 β 2026-09-09 Β· 2 obs
β 2026-09-09 23:54:14
βNSns2dky.name.com2026-08-28 β 2026-09-09 Β· 2 obs
β 2026-09-09 23:54:14
π 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 |
| localhost3000.dev | ns1hnx.name.com, ns4bfy.name.com, ns3bfm.name.com, ns2dky.name.com | - |
β Authoritative Response
Server:163.114.216.49
NS records: ns1hnx.name.com, ns4bfy.name.com, ns3bfm.name.com, ns2dky.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for localhost3000.dev (unsigned zone)
β±οΈ Timing
Total: 1567ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1hnx.name.com, ns2dky.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 localhost3000.dev: ns1.name.com, ns1hnx.name.com, ns2dky.name.com and two others.
At least some of localhost3000.dev's name servers are shared with other domains, for example pristap.com, 4nahda.com, starbuilder.pro and two more.
These name servers tend to co-occur with ns4bfy.name.com, ns3bfm.name.com, ns2fln.name.com and 7 other name servers in the same DNS delegations.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1hnx.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dky.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3bfm.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4bfy.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1hnx.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1hnx.name.com resolve to 163.114.216.17 IP addresses each.