managedservicesseattle.com - dns.ninja
managedservicesseattle.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-cloud-b1.googledomains.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:32::6b🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns-cloud-b1.googledomains.com | ||||||
| A | 216.239.32.107🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns-cloud-b1.googledomains.com | ||||||
| NS | ns-cloud-b2.googledomains.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:34::6b🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns-cloud-b2.googledomains.com | ||||||
| A | 216.239.34.107🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns-cloud-b2.googledomains.com | ||||||
| NS | ns-cloud-b3.googledomains.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:36::6b🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns-cloud-b3.googledomains.com | ||||||
| A | 216.239.36.107🇺🇸 Google216.239.36.0/24 | ||||||
| PTR | ns-cloud-b3.googledomains.com | ||||||
| NS | ns-cloud-b4.googledomains.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:38::6b🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns-cloud-b4.googledomains.com | ||||||
| A | 216.239.38.107🇺🇸 Google216.239.38.0/24 | ||||||
| PTR | ns-cloud-b4.googledomains.com | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1780706991 | ||||||
Same first word
managedservicesseattle.com |
DNS History
4 records (4 active, 0 former)
●NSns-cloud-b1.googledomains.com2026-02-25 → 2026-06-06 · 2 obs
● 2026-06-06 01:20:12
●NSns-cloud-b2.googledomains.com2026-02-25 → 2026-06-06 · 2 obs
● 2026-06-06 01:20:12
●NSns-cloud-b3.googledomains.com2026-02-25 → 2026-06-06 · 2 obs
● 2026-06-06 01:20:12
●NSns-cloud-b4.googledomains.com2026-02-25 → 2026-06-06 · 2 obs
● 2026-06-06 01:20:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net... | - |
| managedservicesseattle.com | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.36.107
NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
Validation error at com: Error: DNS query timeout: 192.54.112.30 for DNSKEY com
⏱️ Timing
Total: 5851ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)
Analysis
Name Servers
managedservicesseattle.com delegates DNS authority to 4 name servers — ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com all point to exactly two IP numbers each: ns-cloud-b1.googledomains.com → 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com → 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com → 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com → 216.239.38.107 and 2001:4860:4802:38::6b.