`yearinsearch.google`

DNSSEC	🔒 Signed (DS record present)
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.zdns.google` ⭐
		A	2001:4860:4802:32::72^{🇺🇸 Google2001:4860::/32}
			PTR	`ns1.zdns.google`
		A	216.239.32.114^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns1.zdns.google`
NS	`ns2.zdns.google`
		A	2001:4860:4802:34::72^{🇺🇸 Google2001:4860::/32}
			PTR	`ns2.zdns.google`
		A	216.239.34.114^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns2.zdns.google`
NS	`ns3.zdns.google`
		A	2001:4860:4802:36::72^{🇺🇸 Google2001:4860::/32}
			PTR	`ns3.zdns.google`
		A	216.239.36.114^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns3.zdns.google`
NS	`ns4.zdns.google`
		A	2001:4860:4802:38::72^{🇺🇸 Google2001:4860::/32}
			PTR	`ns4.zdns.google`
		A	216.239.38.114^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns4.zdns.google`
TXT	`v=spf1 -all`
SOA	`ns1.zdns.google`cloud-dns-hostmaster@google.com serial=1

`google`

	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.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

yearinsearch.google

DNS History

6 records (6 active, 0 former)

●NSns1.zdns.google2026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

●NSns2.zdns.google2026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

●NSns3.zdns.google2026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

●NSns4.zdns.google2026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

●A2001:4860:4802:32::1d2026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

●A216.239.32.292026-04-14 → 2026-05-10 · 2 obs

● 2026-04-14 18:52:28
● 2026-05-10 09:56:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
google	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
yearinsearch.google	ns2.zdns.google, ns4.zdns.google, ns1.zdns.google, ns3.zdns.google	8 records

✅ Authoritative Response

Server:216.239.34.114

NS records: ns2.zdns.google, ns4.zdns.google, ns1.zdns.google, ns3.zdns.google

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 584ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.239.32.29`
AAAA	1	`2001:4860:4802:32::1d`
NS	4	`ns4.zdns.google, ns2.zdns.google...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.zdns.google cloud-dns-hostmaster.goo`

📌 Glue Records Collected

Total: 18

Out-of-bailiwick: 18 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)

Analysis

IP Addresses

yearinsearch.google resolves to two IP numbers: 2001:4860:4802:32::1d and 216.239.32.29.

Other host names, for instance iad23s40-in-f29.1e100.net, mandiant.pt, grow.google.com, gradient.google.com and chromevox.com share IP numbers with yearinsearch.google.

Name Servers

yearinsearch.google is delegated to four name servers: ns1.zdns.google, ns2.zdns.google, ns3.zdns.google and ns4.zdns.google.

yearinsearch.google shares some name servers with other domains, for example lers.google, cloudconnect.goog, accounts.google, ticket.new and sustainability.google.

These name servers are commonly used with the name servers ns1.googledomains.com.

Host names with two IP numbers

Two IPs per host:

ns1.zdns.google points to 2001:4860:4802:32::72 and 216.239.32.114

ns2.zdns.google points to 2001:4860:4802:34::72 and 216.239.34.114

ns3.zdns.google points to 2001:4860:4802:36::72 and 216.239.36.114

ns4.zdns.google points to 2001:4860:4802:38::72 and 216.239.38.114

yearinsearch.google - robtex.com