`washingtonreporting.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

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

Previously MX for

washingtonreporting.com

Same first word

washingtonreporting.com

DNS History

8 records (4 active, 4 former)

●NSns1.afternic.com2026-03-03 → 2026-03-23 · 3 obs

○ 2017-04-04 17:59:00
● 2026-03-03 07:45:38
● 2026-03-23 16:08:20

○NSns1.nextleveldns.net2015-08-20 → 2017-04-04 · 4 obs

● 2015-08-20 02:26:58
● 2017-04-04 17:59:00
○ 2026-03-03 07:45:38
○ 2026-03-23 16:08:20

●NSns2.afternic.com2026-03-03 → 2026-03-23 · 3 obs

○ 2017-04-04 17:59:00
● 2026-03-03 07:45:38
● 2026-03-23 16:08:20

○NSns2.nextleveldns.net2015-08-20 → 2017-04-04 · 4 obs

● 2015-08-20 02:26:58
● 2017-04-04 17:59:00
○ 2026-03-03 07:45:38
○ 2026-03-23 16:08:20

○MXwashingtonreporting.com2015-08-20 → 2017-04-04 · 4 obs

● 2015-08-20 02:26:58
● 2017-04-04 17:59:00
○ 2026-03-03 07:45:38
○ 2026-03-23 16:08:20

●A13.248.169.482026-03-03 → 2026-03-23 · 3 obs

○ 2017-04-04 17:59:00
● 2026-03-03 07:45:38
● 2026-03-23 16:08:20

○A64.64.14.2282015-08-20 → 2017-04-04 · 4 obs

● 2015-08-20 02:26:58
● 2017-04-04 17:59:00
○ 2026-03-03 07:45:38
○ 2026-03-23 16:08:20

●A76.223.54.1462026-03-03 → 2026-03-23 · 3 obs

○ 2017-04-04 17:59:00
● 2026-03-03 07:45:38
● 2026-03-23 16:08:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net...	-
washingtonreporting.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:97.74.98.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for washingtonreporting.com (unsigned zone)

⏱️ Timing

Total: 169ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

washingtonreporting.com resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.

Other host names, for instance smartworkspaces.com, callmidwife.com, singaporeedu.com, itugo.com and withyourbrand.com share IP numbers with washingtonreporting.com.

Name Servers

Two name servers ns1.afternic.com and ns2.afternic.com handle delegation for washingtonreporting.com.

washingtonreporting.com uses the same name server setup as other domains, for example www.adultrealm.com, winsub.com, mrsnyc.com, slimsparen.com and cacuti.com.

washingtonreporting.com partially shares name servers with other domains; examples include ecofier.com, schonborg.com, westwoodwedding.com, azd.io and logane.com.

these name servers are commonly used with the name servers verification-q2yfbmuxrvnsdnaogqtqft.ns101.verify.hn.

Host names with two IP numbers:

ns1.afternic.com points to: 2603:5:2126::45 and 97.74.98.69

ns2.afternic.com points to: 2603:5:2226::45 and 173.201.66.69

washingtonreporting.com - robtex.com