`famebitbygoogle.com`

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

`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.net`nstld@verisign-grs.com serial=1776964896

Same first word

famebitbygoogle.com

DNS History

7 records (4 active, 3 former)

●NSns1.googledomains.com2026-04-20 → 2026-04-23 · 3 obs

○ 2017-08-15 11:22:00
● 2026-04-20 20:02:34
● 2026-04-23 17:42:26

●NSns2.googledomains.com2026-04-20 → 2026-04-23 · 3 obs

○ 2017-08-15 11:22:00
● 2026-04-20 20:02:34
● 2026-04-23 17:42:26

○NSns27.domaincontrol.com2017-08-15 → 2017-08-15 · 3 obs

● 2017-08-15 11:22:00
○ 2026-04-20 20:02:34
○ 2026-04-23 17:42:26

○NSns28.domaincontrol.com2017-08-15 → 2017-08-15 · 3 obs

● 2017-08-15 11:22:00
○ 2026-04-20 20:02:34
○ 2026-04-23 17:42:26

●NSns3.googledomains.com2026-04-20 → 2026-04-23 · 3 obs

○ 2017-08-15 11:22:00
● 2026-04-20 20:02:34
● 2026-04-23 17:42:26

●NSns4.googledomains.com2026-04-20 → 2026-04-23 · 3 obs

○ 2017-08-15 11:22:00
● 2026-04-20 20:02:34
● 2026-04-23 17:42:26

○A50.63.202.442017-08-15 → 2017-08-15 · 3 obs

● 2017-08-15 11:22:00
○ 2026-04-20 20:02:34
○ 2026-04-23 17:42:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net...	-
famebitbygoogle.com	ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com, ns4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.34.99

NS records: ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com, ns4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for famebitbygoogle.com (unsigned zone)

⏱️ Timing

Total: 300ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns3.googledomains.com, ns4.googledomains.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.googledomains.com cloud-dns-hostmast`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.googledomains.com, ns1.googledomains.com, ns2.googledomains.com...)

Analysis

Name Servers

famebitbygoogle.com's delegation is handled by four name servers: ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com and ns4.googledomains.com.

famebitbygoogle.com partially shares name servers with other domains; examples include gogael.com, famebit.net, googleservicehosting.org, youtube.koeln and mndtgov.com.

Host names with two IPs:

ns1.googledomains.com points to 2001:4860:4802:32::63 and 216.239.32.99

ns2.googledomains.com points to 2001:4860:4802:34::63 and 216.239.34.99

ns3.googledomains.com points to 2001:4860:4802:36::63 and 216.239.36.99

ns4.googledomains.com points to 2001:4860:4802:38::63 and 216.239.38.99

famebitbygoogle.com - robtex.com