`washingtonpost.net`

DNSSEC	⚠️ Not signed
A	198.72.14.16
NS	`dns1.cscdns.net` ⭐
		A	2610:a1:1022::100^{🇺🇸 MAINT-ID-120082610:a1:1022::/48 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
		A	156.154.130.100^{🇺🇸 MAINT-ID-12008156.154.130.0/24 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`ns5.bac.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`g.ns-bac.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
NS	`dns2.cscdns.net`
		A	2610:a1:1023::100^{🇺🇸 MAINT-ID-120082610:a1:1023::/48 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
		A	156.154.131.100^{🇺🇸 MAINT-ID-12008156.154.131.0/24 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`ns9.bac.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
			PTR	`h.ns-bac.org`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2013-03-01 #4

`net`

	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=1785341802

WOT: SAFE (97/100)

Same first word

Similar names

DNS History

3 records (3 active, 0 former)

●NSdns1.cscdns.net2015-08-23 → 2026-07-29 · 2 obs

● 2015-08-23 13:31:58
● 2026-07-29 16:29:58

●NSdns2.cscdns.net2015-08-23 → 2026-07-29 · 2 obs

● 2015-08-23 13:31:58
● 2026-07-29 16:29:58

●A198.72.14.162015-08-23 → 2026-07-29 · 2 obs

● 2015-08-23 13:31:58
● 2026-07-29 16:29:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
washingtonpost.net	dns1.cscdns.net, dns2.cscdns.net	4 records

✅ Authoritative Response

Server:156.154.130.100

NS records: dns1.cscdns.net, dns2.cscdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for washingtonpost.net (unsigned zone)

⏱️ Timing

Total: 162ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.72.14.16`
NS	2	`dns1.cscdns.net, dns2.cscdns.net`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.cscdns.net, dns1.cscdns.net, dns2.cscdns.net...)

Analysis

IP Addresses

washingtonpost.net points to a single IP number: 198.72.14.16.

Additional host names — fuelforactiveminds.mobi, cap(0x736578)tra.com, washingtonpost.me and two others — share IP numbers with washingtonpost.net.

Name Servers

Two name servers handle the delegation for washingtonpost.net: dns1.cscdns.net and dns2.cscdns.net.

washingtonpost.net shares its name server setup with other domains, including conexusmobile.com, skyhighnetworks.jp, bienvenueaucanadagm.ca and two others.

washingtonpost.net is at least partially co-delegated on name servers with other domains, such as stressless.dk.

dns1.cscdns.net and dns2.cscdns.net both carry two IP addresses. The A records for dns1.cscdns.net are 156.154.130.100 and 2610:a1:1022::100; the A records for dns2.cscdns.net are 156.154.131.100 and 2610:a1:1023::100.

washingtonpost.net - robtex.com