find.foo - dns.ninja
find.foo
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2001:4860:4802:32::1d🇺🇸 Google2001:4860::/32 | ||||||
| PTR | any-in-2001-4860-4802-32--1d.1e100.net | ||||||
| A | 216.239.32.29🇺🇸 Google216.239.32.0/24 | ||||||
| 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.comdns-admin@google.com 2013-03-30 #1 | ||||||
foo
| 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
Similar names
DNS History
19 records (6 active, 13 former)
●NSns1.googledomains.com2016-12-09 → 2026-07-11 · 2 obs
● 2026-07-11 16:00:50
●NSns2.googledomains.com2016-12-09 → 2026-07-11 · 2 obs
● 2026-07-11 16:00:50
●NSns3.googledomains.com2016-12-09 → 2026-07-11 · 2 obs
● 2026-07-11 16:00:50
●NSns4.googledomains.com2016-12-09 → 2026-07-11 · 2 obs
● 2026-07-11 16:00:50
○MXalt1.aspmx.l.google.com2016-12-09 → 2016-12-09 · 3 obs
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○MXalt2.aspmx.l.google.com2016-12-09 → 2016-12-09 · 3 obs
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○MXalt3.aspmx.l.google.com2016-12-09 → 2016-12-09 · 3 obs
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○MXalt4.aspmx.l.google.com2016-12-09 → 2016-12-09 · 3 obs
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○MXaspmx.l.google.com2016-12-09 → 2016-12-09 · 3 obs
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A2001:4860:4802:32::152016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
●A2001:4860:4802:32::1d2026-03-18 → 2026-07-11 · 3 obs
● 2026-03-18 03:20:34
● 2026-07-11 16:00:50
○A2001:4860:4802:34::152016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A2001:4860:4802:36::152016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A2001:4860:4802:38::152016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A216.239.32.212016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
●A216.239.32.292026-03-18 → 2026-07-11 · 3 obs
● 2026-03-18 03:20:34
● 2026-07-11 16:00:50
○A216.239.34.212016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A216.239.36.212016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
○A216.239.38.212016-12-09 → 2018-08-07 · 4 obs
● 2018-08-07 17:23:48
○ 2026-03-18 03:20:34
○ 2026-07-11 16:00:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| foo | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| find.foo | ns1.googledomains.com, ns3.googledomains.com, ns2.googledomains.com, ns4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.32.99
NS records: ns1.googledomains.com, ns3.googledomains.com, ns2.googledomains.com, ns4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for find.foo (unsigned zone)
⏱️ Timing
Total: 2459ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.239.32.29 |
| AAAA | 1 | 2001:4860:4802:32::1d |
| NS | 4 | ns1.googledomains.com, ns3.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.googledomains.com dns-admin.google.c |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
find.foo has two IP addresses: 216.239.32.29 and 2001:4860:4802:32::1d
Additional host names — googlemaps.berlin, fundo.town, mandiant.cg and two others — share IP numbers with find.foo.
Name Servers
find.foo has four authoritative name servers: ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com and ns4.googledomains.com.
There is at least partial name server overlap between find.foo and other domains — testappeng20.com, earthgloogle.com, tastybourbon-pci.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.