niantic.dev - dns.ninja

`niantic.dev`

DNSSEC	⚠️ Not signed
A	35.227.218.156^{🇺🇸 Google35.227.0.0/16}
		PTR	`156.218.227.35.bc.googleusercontent.com`
NS	`ns-cloud-e1.googledomains.com` ⭐
		A	2001:4860:4802:32::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e1.googledomains.com`
		A	216.239.32.110^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-e1.googledomains.com`
NS	`ns-cloud-e2.googledomains.com`
		A	2001:4860:4802:34::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e2.googledomains.com`
		A	216.239.34.110^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-e2.googledomains.com`
NS	`ns-cloud-e3.googledomains.com`
		A	2001:4860:4802:36::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e3.googledomains.com`
		A	216.239.36.110^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-e3.googledomains.com`
NS	`ns-cloud-e4.googledomains.com`
		A	2001:4860:4802:38::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e4.googledomains.com`
		A	216.239.38.110^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-e4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=CMok-4Mvyb3CNKqJHOwsWXPeJsKeETl7GTLg0VVRoak`
SOA	`ns-cloud-e1.googledomains.com`cloud-dns-hostmaster@google.com serial=1

`dev`

	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

niantic.fail

niantic.wtf

niantic.com

niantic.cn

niantic.net

niantic.dev

niantic.team

niantic.biz.id

niantic.wiki

Similar names

cantini.com

cantini.cn

cintian.com

natiinc.com

cainint.com

incinta.net

cantini.fr

tancini.it

incanti.ro

incanti.ru

innatic.com

tinainc.com

antinic.com

tiicann.org

incinta.ro

nicanti.com

inintca.com

cantini.it

DNS History

22 records (10 active, 12 former)

○NSns-cloud-d1.googledomains.com2019-03-12 → 2019-03-12 · 3 obs

● 2019-03-12 09:59:20
○ 2026-02-15 23:29:32
○ 2026-07-24 03:52:46

○NSns-cloud-d2.googledomains.com2019-03-12 → 2019-03-12 · 3 obs

● 2019-03-12 09:59:20
○ 2026-02-15 23:29:32
○ 2026-07-24 03:52:46

○NSns-cloud-d3.googledomains.com2019-03-12 → 2019-03-12 · 3 obs

● 2019-03-12 09:59:20
○ 2026-02-15 23:29:32
○ 2026-07-24 03:52:46

○NSns-cloud-d4.googledomains.com2019-03-12 → 2019-03-12 · 3 obs

● 2019-03-12 09:59:20
○ 2026-02-15 23:29:32
○ 2026-07-24 03:52:46

●NSns-cloud-e1.googledomains.com2026-02-15 → 2026-07-24 · 3 obs

○ 2019-03-12 09:59:20
● 2026-02-15 23:29:32
● 2026-07-24 03:52:46

●NSns-cloud-e2.googledomains.com2026-02-15 → 2026-07-24 · 3 obs

○ 2019-03-12 09:59:20
● 2026-02-15 23:29:32
● 2026-07-24 03:52:46

●NSns-cloud-e3.googledomains.com2026-02-15 → 2026-07-24 · 3 obs

○ 2019-03-12 09:59:20
● 2026-02-15 23:29:32
● 2026-07-24 03:52:46

●NSns-cloud-e4.googledomains.com2026-02-15 → 2026-07-24 · 3 obs

○ 2019-03-12 09:59:20
● 2026-02-15 23:29:32
● 2026-07-24 03:52:46

●MXalt1.aspmx.l.google.com2026-02-15 → 2026-07-24 · 4 obs

● 2026-02-15 23:29:32
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

●MXalt2.aspmx.l.google.com2026-02-15 → 2026-07-24 · 4 obs

● 2026-02-15 23:29:32
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

●MXalt3.aspmx.l.google.com2026-02-15 → 2026-07-24 · 4 obs

● 2026-02-15 23:29:32
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

●MXalt4.aspmx.l.google.com2026-02-15 → 2026-07-24 · 4 obs

● 2026-02-15 23:29:32
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

●MXaspmx.l.google.com2026-02-15 → 2026-07-24 · 4 obs

● 2026-02-15 23:29:32
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

○A2001:4860:4802:32::152019-03-12 → 2026-04-06 · 4 obs

● 2019-03-12 09:59:20
● 2026-04-06 14:28:38
○ 2026-04-08 13:37:56
○ 2026-07-24 03:52:46

○A2001:4860:4802:34::152019-03-12 → 2026-04-06 · 4 obs

● 2019-03-12 09:59:20
● 2026-04-06 14:28:38
○ 2026-04-08 13:37:56
○ 2026-07-24 03:52:46

○A2001:4860:4802:36::152019-03-12 → 2026-04-06 · 4 obs

● 2019-03-12 09:59:20
● 2026-04-06 14:28:38
○ 2026-04-08 13:37:56
○ 2026-07-24 03:52:46

○A2001:4860:4802:38::152019-03-12 → 2026-04-06 · 4 obs

● 2019-03-12 09:59:20
● 2026-04-06 14:28:38
○ 2026-04-08 13:37:56
○ 2026-07-24 03:52:46

○A216.239.32.212019-03-12 → 2026-03-23 · 4 obs

● 2019-03-12 09:59:20
● 2026-03-23 22:13:40
○ 2026-03-27 21:48:20
○ 2026-07-24 03:52:46

○A216.239.34.212019-03-12 → 2026-03-23 · 4 obs

● 2019-03-12 09:59:20
● 2026-03-23 22:13:40
○ 2026-03-27 21:48:20
○ 2026-07-24 03:52:46

○A216.239.36.212019-03-12 → 2026-03-23 · 4 obs

● 2019-03-12 09:59:20
● 2026-03-23 22:13:40
○ 2026-03-27 21:48:20
○ 2026-07-24 03:52:46

○A216.239.38.212019-03-12 → 2026-03-23 · 4 obs

● 2019-03-12 09:59:20
● 2026-03-23 22:13:40
○ 2026-03-27 21:48:20
○ 2026-07-24 03:52:46

●A35.227.218.1562026-03-27 → 2026-07-24 · 5 obs

○ 2026-03-23 22:13:40
● 2026-03-27 21:48:20
○ 2026-07-03 11:26:12
● 2026-07-08 21:35:00
● 2026-07-24 03:52:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
niantic.dev	ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com	-

✅ Authoritative Response

Server:216.239.36.110

NS records: ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for niantic.dev (unsigned zone)

⏱️ Timing

Total: 1211ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.227.218.156`
NS	4	`ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 40), alt4.aspmx.l.google.com (pri: 50)...`
TXT	1	`google-site-verification=CMok-4Mvyb3CNKq`
SOA	1	`ns-cloud-e1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 10

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

Analysis

IP Addresses

niantic.dev resolves to just one IP address, 35.227.218.156.

Among others, 156.218.227.35.bc.googleusercontent.com, lightship.dev, ar.dev and www.lightship.dev resolve to the same IP numbers as niantic.dev.

Name Servers

The NS records for niantic.dev point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

niantic.dev partially shares its NS delegation with several other domains, including lotfancy.net, work-locally.com, sharpcopytranscription.com and two others.

ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com each carry two IP addresses. ns-cloud-e1.googledomains.com has 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com has 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com has 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com has 216.239.38.110 and 2001:4860:4802:38::6e.

Mail Servers

niantic.dev 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 niantic.dev and other domains, including thecollectiveshoppe.com, gilbarsela.com, dagostinpneus.com.br 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 directs traffic to 192.178.155.27 and 2607:f8b0:4004:c19::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

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

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.