admcstesting.dev - dns.ninja
admcstesting.dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.googledomains.com ⭐ | ||||||
| A | 2001:4860:4802:32::63🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns1.googledomains.com | ||||||
| A | 216.239.32.99🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns1.googledomains.com | ||||||
| NS | ns2.googledomains.com | ||||||
| A | 2001:4860:4802:34::63🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns2.googledomains.com | ||||||
| A | 216.239.34.99🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns2.googledomains.com | ||||||
| NS | ns3.googledomains.com | ||||||
| A | 2001:4860:4802:36::63🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns3.googledomains.com | ||||||
| A | 216.239.36.99🇺🇸 Google216.239.36.0/24 | ||||||
| PTR | ns3.googledomains.com | ||||||
| NS | ns4.googledomains.com | ||||||
| A | 2001:4860:4802:38::63🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns4.googledomains.com | ||||||
| A | 216.239.38.99🇺🇸 Google216.239.38.0/24 | ||||||
| PTR | ns4.googledomains.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.googledomains.comcloud-dns-hostmaster@google.com serial=1 | ||||||
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
admcstesting.dev |
DNS History
4 records (4 active, 0 former)
●NSns1.googledomains.com2026-02-18 → 2026-06-04 · 2 obs
● 2026-06-04 14:18:36
●NSns2.googledomains.com2026-02-18 → 2026-06-04 · 2 obs
● 2026-06-04 14:18:36
●NSns3.googledomains.com2026-02-18 → 2026-06-04 · 2 obs
● 2026-06-04 14:18:36
●NSns4.googledomains.com2026-02-18 → 2026-06-04 · 2 obs
● 2026-06-04 14:18:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| admcstesting.dev | ns3.googledomains.com, ns4.googledomains.com, ns2.googledomains.com, ns1.googledomains.com | - |
✅ Authoritative Response
Server:216.239.32.99
NS records: ns3.googledomains.com, ns4.googledomains.com, ns2.googledomains.com, ns1.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for admcstesting.dev (unsigned zone)
⏱️ Timing
Total: 2492ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns3.googledomains.com, ns1.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.googledomains.com cloud-dns-hostmast |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
admcstesting.dev carries NS records pointing to 4 name servers: ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com and ns4.googledomains.com.
There is at least partial name server overlap between admcstesting.dev and other domains — blogger.cam, eooglemail.com, googlesoli.com and two more among them.
All four hostnames — ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com and ns4.googledomains.com — resolve to two IP numbers apiece: ns1.googledomains.com to 216.239.32.99 and 2001:4860:4802:32::63; ns2.googledomains.com to 216.239.34.99 and 2001:4860:4802:34::63; ns3.googledomains.com to 216.239.36.99 and 2001:4860:4802:36::63; ns4.googledomains.com to 216.239.38.99 and 2001:4860:4802:38::63.