`reddistrict.com`

DNSSEC	⚠️ Not signed
NS	`ns1.vercel-dns.com` ⭐ ⚠️ Not in zone NS records
		A	2620:4d:4000:6259:7:13:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p13.nsone.net`
		A	198.51.44.13^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p13.nsone.net`
NS	`ns-cloud-e1.googledomains.com` ⚠️ Not in zone NS records
		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` ⚠️ Not in zone NS records
		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` ⚠️ Not in zone NS records
		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` ⚠️ Not in zone NS records
		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`
NS	`ns2.vercel-dns.com` ⚠️ Not in zone NS records
		A	2a00:edc0:6259:7:13::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p13.nsone.net`
		A	198.51.45.13^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns2.p13.nsone.net`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1763053224

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

Same first word

reddistrict.com

reddistrict.net

DNS History

11 records (6 active, 5 former)

●NSns-cloud-e1.googledomains.com2015-10-28 → 2026-07-24 · 3 obs

○ 2015-06-18 21:58:00
● 2015-10-28 01:19:20
● 2026-07-24 13:26:26

●NSns-cloud-e2.googledomains.com2015-10-28 → 2026-07-24 · 3 obs

○ 2015-06-18 21:58:00
● 2015-10-28 01:19:20
● 2026-07-24 13:26:26

●NSns-cloud-e3.googledomains.com2015-10-28 → 2026-07-24 · 3 obs

○ 2015-06-18 21:58:00
● 2015-10-28 01:19:20
● 2026-07-24 13:26:26

●NSns-cloud-e4.googledomains.com2015-10-28 → 2026-07-24 · 3 obs

○ 2015-06-18 21:58:00
● 2015-10-28 01:19:20
● 2026-07-24 13:26:26

○NSns.yohost.com2015-06-18 → 2015-06-18 · 3 obs

● 2015-06-18 21:58:00
○ 2015-10-28 01:19:20
○ 2026-07-24 13:26:26

●NSns1.vercel-dns.com2026-06-29 → 2026-07-24 · 3 obs

○ 2015-10-28 01:19:20
● 2026-06-29 16:40:50
● 2026-07-24 13:26:26

●NSns2.vercel-dns.com2026-06-29 → 2026-07-24 · 3 obs

○ 2015-10-28 01:19:20
● 2026-06-29 16:40:50
● 2026-07-24 13:26:26

○NSns2.yohost.com2015-06-18 → 2015-06-18 · 3 obs

● 2015-06-18 21:58:00
○ 2015-10-28 01:19:20
○ 2026-07-24 13:26:26

○MXmx1.yodns.com2015-06-18 → 2017-04-24 · 4 obs

● 2015-06-18 21:58:00
● 2017-04-24 01:54:54
○ 2026-06-29 16:40:50
○ 2026-07-24 13:26:26

○MXmx2.yodns.com2015-06-18 → 2017-04-24 · 4 obs

● 2015-06-18 21:58:00
● 2017-04-24 01:54:54
○ 2026-06-29 16:40:50
○ 2026-07-24 13:26:26

○A72.13.85.102015-06-18 → 2017-04-24 · 4 obs

● 2015-06-18 21:58:00
● 2017-04-24 01:54:54
○ 2026-06-29 16:40:50
○ 2026-07-24 13:26:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
reddistrict.com	ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com...	12 records

✅ Authoritative Response

Server:198.51.44.13

NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns1.vercel-dns.com, ns2.vercel-dns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for reddistrict.com (unsigned zone)

⏱️ Timing

Total: 2583ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)

Analysis

Name Servers

reddistrict.com delegates authority to 6 name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com plus 3 other.

The name servers of reddistrict.com overlap at least partially with those of other domains — among them leaversgear.com, mrt-shyinoho-viddilu-khrebta.online, tramite.art and two more.

The name servers ns-cloud-e4.googledomains.com, ns1.vercel-dns.com and ns2.vercel-dns.com are commonly seen alongside these name servers.

Host names with two IP numbers:

ns-cloud-e1.googledomains.com directs traffic to 216.239.32.110 and 2001:4860:4802:32::6e.

ns-cloud-e2.googledomains.com directs traffic to 216.239.34.110 and 2001:4860:4802:34::6e.

ns-cloud-e3.googledomains.com directs traffic to 216.239.36.110 and 2001:4860:4802:36::6e.

ns-cloud-e4.googledomains.com directs traffic to 216.239.38.110 and 2001:4860:4802:38::6e.

ns1.vercel-dns.com directs traffic to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1.

ns2.vercel-dns.com directs traffic to 198.51.45.13 and 2a00:edc0:6259:7:13::2.