chrome - robtex.com
chrome
(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-05-31 #0 | ||||||
Subdomains
Same first word
Similar names
DNS History
7 records (5 active, 2 former)
●NSns-tld1.charlestonroadregistry.com2015-08-23 → 2026-05-31 · 2 obs
● 2026-05-31 10:47:40
●NSns-tld2.charlestonroadregistry.com2015-08-23 → 2026-05-31 · 2 obs
● 2026-05-31 10:47:40
●NSns-tld3.charlestonroadregistry.com2015-08-23 → 2026-05-31 · 2 obs
● 2026-05-31 10:47:40
●NSns-tld4.charlestonroadregistry.com2015-08-23 → 2026-05-31 · 2 obs
● 2026-05-31 10:47:40
●NSns-tld5.charlestonroadregistry.com2015-08-23 → 2026-05-31 · 2 obs
● 2026-05-31 10:47:40
○MXyour-dns-needs-immediate-attention.chrome2015-08-23 → 2018-02-11 · 4 obs
● 2018-02-11 09:09:34
○ 2019-04-12 18:11:10
○ 2026-05-31 10:47:40
○A127.0.53.532015-08-23 → 2018-02-11 · 4 obs
● 2018-02-11 09:09:34
○ 2019-04-12 18:11:10
○ 2026-05-31 10:47:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| chrome | ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com... | 10 records |
✅ Authoritative Response
Server:216.239.34.105
NS records: ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 323ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 5 | ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com... |
| SOA | 1 | ns-tld1.charlestonroadregistry.com cloud |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld4.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
Hierarchy
apps.chrome and nic.chrome each fall under chrome as their parent domain.
Name Servers
The zone chrome is authoritative on 5 name servers: ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com and two additional ones.
At least some of chrome's name servers are shared with other domains, for example ing, hangout, ads and two more.
These name servers tend to be deployed in combination with the name servers ns-tld4.charlestonroadregistry.com and ns-tld5.charlestonroadregistry.com.
Host names that have two IP addresses:
ns-tld1.charlestonroadregistry.com resolves to 216.239.32.105 and 2001:4860:4802:32::69.
ns-tld2.charlestonroadregistry.com resolves to 216.239.34.105 and 2001:4860:4802:34::69.
ns-tld3.charlestonroadregistry.com resolves to 216.239.36.105 and 2001:4860:4802:36::69.
ns-tld4.charlestonroadregistry.com resolves to 216.239.38.105 and 2001:4860:4802:38::69.
ns-tld5.charlestonroadregistry.com resolves to 216.239.60.105 and 2001:4860:4805::69.