`districtdaily.com`

DNSSEC	⚠️ Not signed
NS	`ns1.digitalocean.com` ⚠️ Not in zone NS records
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com` ⚠️ Not in zone NS records
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`

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

Same first word

districtdaily.com

districtdaily.co.uk

DNS History

8 records (2 active, 6 former)

○NSns.phx1.nearlyfreespeech.net2015-05-20 → 2016-07-28 · 4 obs

● 2015-05-20 19:30:46
● 2016-07-28 05:06:00
○ 2017-04-08 09:37:04
○ 2026-04-16 01:31:34

○NSns.phx5.nearlyfreespeech.net2015-05-20 → 2016-07-28 · 4 obs

● 2015-05-20 19:30:46
● 2016-07-28 05:06:00
○ 2017-04-08 09:37:04
○ 2026-04-16 01:31:34

○NSns.phx6.nearlyfreespeech.net2015-05-20 → 2016-07-28 · 4 obs

● 2015-05-20 19:30:46
● 2016-07-28 05:06:00
○ 2017-04-08 09:37:04
○ 2026-04-16 01:31:34

●NSns1.digitalocean.com2017-04-08 → 2026-04-16 · 3 obs

○ 2016-07-28 05:06:00
● 2017-04-08 09:37:04
● 2026-04-16 01:31:34

●NSns2.digitalocean.com2017-04-08 → 2026-04-16 · 3 obs

○ 2016-07-28 05:06:00
● 2017-04-08 09:37:04
● 2026-04-16 01:31:34

○NSns3.digitalocean.com2017-04-08 → 2017-04-08 · 4 obs

○ 2016-07-28 05:06:00
● 2017-04-08 09:37:04
○ 2026-04-10 21:22:38
○ 2026-04-16 01:31:34

○A138.197.118.852017-04-08 → 2017-04-08 · 4 obs

○ 2016-07-28 05:06:00
● 2017-04-08 09:37:04
○ 2026-04-10 21:22:38
○ 2026-04-16 01:31:34

○A208.94.116.1522015-05-20 → 2016-07-28 · 4 obs

● 2015-05-20 19:30:46
● 2016-07-28 05:06:00
○ 2017-04-08 09:37:04
○ 2026-04-16 01:31:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, f.gtld-servers.net, l.gtld-servers.net, d.gtld-servers.net...	-
districtdaily.com	ns1.digitalocean.com, ns2.digitalocean.com	2 records

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for districtdaily.com (unsigned zone)

⏱️ Timing

Total: 171ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.digitalocean.com, ns2.digitalocean.com)

Analysis

Name Servers

districtdaily.com is delegated to two name servers: ns1.digitalocean.com and ns2.digitalocean.com.

districtdaily.com uses the same name server setup as other domains, for instance stupidhistory.com, merchantop.com, xn--72c5aah8b0d8b0e.com, hengsrenghong.com.kh and kashwp7.com.

districtdaily.com shares name servers with other domains at least partially, for instance zoomda.uz, 205.236.104.in-addr.arpa, 1.0.0.4.8.2.1.2.0.0.0.0.0.0.0.0.0.d.0.0.2.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa, mariya-club.com and stibon.nl.

these name servers are often used together with the name servers ns3.digitalocean.com.

Host names with two IP numbers:

The host ns1.digitalocean.com points to 2606:4700:52::ac40:34d2 and 172.64.52.210.

The host ns2.digitalocean.com points to 2606:4700:5a::ac40:3515 and 172.64.53.21.

districtdaily.com - robtex.com