`washingtonstatement.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns63.domaincontrol.com` ⭐
		A	2603:5:2154::2a^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns63.domaincontrol.com`
		A	97.74.101.42^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns63.domaincontrol.com`
NS	`ns64.domaincontrol.com`
		A	2603:5:2254::2a^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns64.domaincontrol.com`
		A	173.201.69.42^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns64.domaincontrol.com`
MX	`washingtonstatement-com.mail.protection.outlook.com` ⭐
TXT	`v=spf1 include:secureserver.net -all`
TXT	`NETORGFT9584432.onmicrosoft.com`
SOA	`ns63.domaincontrol.com`dns@jomax.net 2024-02-01 #8

`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

Same first word

washingtonstatement.com

DNS History

9 records (5 active, 4 former)

●NSns63.domaincontrol.com2015-08-21 → 2026-02-25 · 2 obs

● 2015-08-21 03:01:54
● 2026-02-25 09:07:46

●NSns64.domaincontrol.com2015-08-21 → 2026-02-25 · 2 obs

● 2015-08-21 03:01:54
● 2026-02-25 09:07:46

○MXmailstore1.secureserver.net2015-08-21 → 2017-04-20 · 3 obs

● 2015-08-21 03:01:54
● 2017-04-20 07:15:38
○ 2026-02-25 09:07:46

○MXsmtp.secureserver.net2015-08-21 → 2017-04-20 · 3 obs

● 2015-08-21 03:01:54
● 2017-04-20 07:15:38
○ 2026-02-25 09:07:46

●MXwashingtonstatement-com.mail.protection.outlook.com2026-02-25 → 2026-02-25 · 2 obs

○ 2017-04-20 07:15:38
● 2026-02-25 09:07:46

●A15.197.148.332026-02-25 → 2026-02-25 · 2 obs

○ 2017-04-20 07:15:38
● 2026-02-25 09:07:46

○A184.168.221.882017-04-20 → 2017-04-20 · 3 obs

○ 2016-09-19 04:32:20
● 2017-04-20 07:15:38
○ 2026-02-25 09:07:46

●A3.33.130.1902026-02-25 → 2026-02-25 · 2 obs

○ 2017-04-20 07:15:38
● 2026-02-25 09:07:46

○A50.63.90.12015-08-21 → 2016-09-19 · 4 obs

● 2015-08-21 03:01:54
● 2016-09-19 04:32:20
○ 2017-04-20 07:15:38
○ 2026-02-25 09:07:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
washingtonstatement.com	ns63.domaincontrol.com, ns64.domaincontrol.com	-

✅ Authoritative Response

Server: 173.201.69.42

NS records: ns63.domaincontrol.com, ns64.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for washingtonstatement.com (unsigned zone)

⏱️ Timing

Total: 46ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns63.domaincontrol.com, ns64.domaincontrol.com`
MX	1	`washingtonstatement-com.mail.protection.`
TXT	2	`v=spf1 include:secureserver.net -all, NETORGFT9584432.onmicrosoft.com`
SOA	1	`ns63.domaincontrol.com dns.jomax.net`

AI analysis

washingtonstatement.com resolves to two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names, for instance kura.tech, contactadoctor.com, hubville.com, doubletap-tactical.com and shatterland.net share IP numbers with washingtonstatement.com.

washingtonstatement.com has two name servers: ns63.domaincontrol.com and ns64.domaincontrol.com.

washingtonstatement.com shares the same name server setup as other domains, for example legatom.com, therailingshop.co, amcfairmont.com, sustainablegardensdirect.com and lovelandtown.com.

Host names with two IP numbers:

ns63.domaincontrol.com points to: 2603:5:2154::2a and 97.74.101.42; ns64.domaincontrol.com points to: 2603:5:2254::2a and 173.201.69.42.

washingtonstatement.com is handled by a single mail server, washingtonstatement-com.mail.protection.outlook.com.

washingtonstatement.com - robtex.com