districtaccess.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`districtaccess.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b1.googledomains.com`
		A	216.239.32.107^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-b1.googledomains.com`
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b2.googledomains.com`
		A	216.239.34.107^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-b2.googledomains.com`
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b3.googledomains.com`
		A	216.239.36.107^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-b3.googledomains.com`
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b4.googledomains.com`
		A	216.239.38.107^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-b4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-cloud-b1.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=1786944834

Same first word

districtaccess.com

DNS History

18 records (9 active, 9 former)

●NSns-cloud-b1.googledomains.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●NSns-cloud-b2.googledomains.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●NSns-cloud-b3.googledomains.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●NSns-cloud-b4.googledomains.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

○NSns1.netfirms.com2016-07-09 → 2020-02-14 · 5 obs

○ 2015-11-25 15:59:46
● 2016-07-09 15:04:26
● 2020-02-14 08:47:06
○ 2026-05-14 09:46:54
○ 2026-08-17 05:50:58

○NSns2.netfirms.com2016-07-09 → 2020-02-14 · 5 obs

○ 2015-11-25 15:59:46
● 2016-07-09 15:04:26
● 2020-02-14 08:47:06
○ 2026-05-14 09:46:54
○ 2026-08-17 05:50:58

○NSns41.domaincontrol.com2015-06-22 → 2015-06-22 · 3 obs

● 2015-06-22 11:29:00
○ 2015-11-25 15:59:46
○ 2026-08-17 05:50:58

○NSns42.domaincontrol.com2015-06-22 → 2015-06-22 · 3 obs

● 2015-06-22 11:29:00
○ 2015-11-25 15:59:46
○ 2026-08-17 05:50:58

●MXalt1.aspmx.l.google.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●MXalt2.aspmx.l.google.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●MXalt3.aspmx.l.google.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●MXalt4.aspmx.l.google.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

●MXaspmx.l.google.com2026-05-14 → 2026-08-17 · 3 obs

○ 2020-02-14 08:47:06
● 2026-05-14 09:46:54
● 2026-08-17 05:50:58

○MXmailstore1.secureserver.net2015-06-22 → 2015-06-22 · 3 obs

● 2015-06-22 11:29:00
○ 2015-11-25 15:59:46
○ 2026-08-17 05:50:58

○MXmx.districtaccess.com2016-07-09 → 2020-02-14 · 5 obs

○ 2015-11-25 15:59:46
● 2016-07-09 15:04:26
● 2020-02-14 08:47:06
○ 2026-05-14 09:46:54
○ 2026-08-17 05:50:58

○MXsmtp.secureserver.net2015-06-22 → 2015-06-22 · 3 obs

● 2015-06-22 11:29:00
○ 2015-11-25 15:59:46
○ 2026-08-17 05:50:58

○A50.63.73.12015-06-22 → 2015-06-22 · 3 obs

● 2015-06-22 11:29:00
○ 2015-11-25 15:59:46
○ 2026-08-17 05:50:58

○A66.96.160.1342016-07-09 → 2020-02-14 · 5 obs

○ 2015-11-25 15:59:46
● 2016-07-09 15:04:26
● 2020-02-14 08:47:06
○ 2026-05-14 09:46:54
○ 2026-08-17 05:50:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
districtaccess.com	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.32.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 438ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)

Analysis

Name Servers

The domain districtaccess.com is delegated to these four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

At least some of districtaccess.com's name servers are shared with other domains, for example tswv.com, nzkt.net, tinfield.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-cloud-b1.googledomains.com directs to 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com directs to 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com directs to 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com directs to 216.239.38.107 and 2001:4860:4802:38::6b.

Mail Servers

Five mail servers handle districtaccess.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

districtaccess.com shares at least some of its mail servers with other domains — for example rrrforms.com, abennett.us, datadriveninvestor.com and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com maps to two IP addresses — 192.178.155.26 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1b.