ngram.com - dns.ninja

`ngram.com`

DNSSEC	⚠️ Not signed
A	76.76.21.21^{🇺🇸 Amazon76.76.21.0/24 EC2 Prefix}
NS	`ns-cloud-c1.googledomains.com` ⭐
		A	2001:4860:4802:32::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	192.179.18.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ry-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`ps-cd-verification=4b7b967d-8430-42d0-a504-7f2cd335dd80`
TXT	`v=spf1 mx a include:_spf.google.com ~all`
SOA	`ns-cloud-c1.googledomains.com`cloud-dns-hostmaster@google.com serial=4

`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=1786764384

Previously NS for

ngram.com

Same first word

ngram.ru

ngram.de

ngram.ca

ngram.co.kr

ngram.me

ngram.it

ngram.org

ngram.com

Similar names

grman.eu

grman.org

nagmr.org

nagmr.com

gramn.com

gramn.ir

angrm.net

grman.at

mangr.online

mngar.com

magnr.com

grman.com

mrgan.co.il

mrgan.com

mgran.com

gnmar.com

agnmr.at

gmrna.com

argmn.com

angrm.org

nmgra.com

margn.com

amngr.ru

mrnga.com

nrmag.ch

granm.com

mrgan.de

nmgra.org

mrang.com

nmgar.com

rganm.org

mgran.ru

DNS History

19 records (10 active, 9 former)

○NSngram.com2017-03-20 → 2017-03-20 · 4 obs

○ 2016-07-10 15:20:10
● 2017-03-20 17:38:36
○ 2026-02-27 01:32:54
○ 2026-08-15 03:35:52

●NSns-cloud-c1.googledomains.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●NSns-cloud-c2.googledomains.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●NSns-cloud-c3.googledomains.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●NSns-cloud-c4.googledomains.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

○NSns1.ngram.com2016-07-10 → 2017-03-20 · 5 obs

○ 2016-03-07 06:30:20
● 2016-07-10 15:20:10
● 2017-03-20 17:38:36
○ 2026-02-27 01:32:54
○ 2026-08-15 03:35:52

○NSns2.ngram.com2016-07-10 → 2017-03-20 · 5 obs

○ 2016-03-07 06:30:20
● 2016-07-10 15:20:10
● 2017-03-20 17:38:36
○ 2026-02-27 01:32:54
○ 2026-08-15 03:35:52

○NSns39.domaincontrol.com2015-08-16 → 2016-03-07 · 5 obs

○ 2008-03-19 01:49:30
● 2015-08-16 01:33:56
● 2016-03-07 06:30:20
○ 2016-07-10 15:20:10
○ 2026-08-15 03:35:52

○NSns40.domaincontrol.com2015-08-16 → 2016-03-07 · 5 obs

○ 2008-03-19 01:49:30
● 2015-08-16 01:33:56
● 2016-03-07 06:30:20
○ 2016-07-10 15:20:10
○ 2026-08-15 03:35:52

●MXalt1.aspmx.l.google.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●MXalt2.aspmx.l.google.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●MXalt3.aspmx.l.google.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●MXalt4.aspmx.l.google.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

●MXaspmx.l.google.com2026-02-27 → 2026-08-15 · 3 obs

○ 2017-03-20 17:38:36
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

○MXmail.ngram.com2008-03-19 → 2017-03-20 · 6 obs

● 2008-03-19 01:49:30
○ 2015-08-16 01:33:56
● 2016-07-10 15:20:10
● 2017-03-20 17:38:36
○ 2026-02-27 01:32:54
○ 2026-08-15 03:35:52

○MXmailstore1.secureserver.net2015-08-16 → 2016-03-07 · 5 obs

○ 2008-03-19 01:49:30
● 2015-08-16 01:33:56
● 2016-03-07 06:30:20
○ 2016-07-10 15:20:10
○ 2026-08-15 03:35:52

○MXsmtp.secureserver.net2015-08-16 → 2016-03-07 · 5 obs

○ 2008-03-19 01:49:30
● 2015-08-16 01:33:56
● 2016-03-07 06:30:20
○ 2016-07-10 15:20:10
○ 2026-08-15 03:35:52

○A50.63.202.472015-08-16 → 2016-03-07 · 5 obs

○ 2008-03-19 01:49:30
● 2015-08-16 01:33:56
● 2016-03-07 06:30:20
○ 2016-07-10 15:20:10
○ 2026-08-15 03:35:52

●A76.76.21.212026-02-27 → 2026-08-15 · 3 obs

○ 2016-07-10 15:20:10
● 2026-02-27 01:32:54
● 2026-08-15 03:35:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ngram.com	ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.38.108

NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ngram.com (unsigned zone)

⏱️ Timing

Total: 329ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`76.76.21.21`
NS	4	`ns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`v=spf1 mx a include:_spf.google.com ~all, ps-cd-verification=4b7b967d-8430-42d0-a5`
SOA	1	`ns-cloud-c1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)

Analysis

IP Addresses

ngram.com resolves to just one IP address, 76.76.21.21.

Two other host names, along with freddiesflowers.com, recover.no and liuk3r.com, also share IP numbers with ngram.com.

Name Servers

The NS records for ngram.com point to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.

ngram.com has at least partial name server overlap with other domains, such as widowly.com, innerpeaceglobalimpact.com, jbirch.net and two others.

ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com all point to exactly two IP numbers each: ns-cloud-c1.googledomains.com → 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com → 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com → 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com → 216.239.38.108 and 2001:4860:4802:38::6c.

Mail Servers

ngram.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between ngram.com and other domains, including bindlebinaries.org, ns500699.ns500693.ns500693.ns500734.ns500699.ns500734.ns500734.ns500693.ns500588.ns500699.ns500699.ns500699.ns500612.ns500632.ns500612.dtrkdll.com, ns500759.ns500698.ns500759.ns500708.ns500576.ns500686.ns500652.ns500576.ns500576.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com resolves to 192.179.18.27 and 2607:f8b0:4004:c06::1b.

alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.