`congressdistrict.org`

DNSSEC	🔒 Signed (DS record present)
NS	`ns-cloud-d1.googledomains.com` ⭐
		A	2001:4860:4802:32::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-d4.googledomains.com`
MX	`congressdistrict-org.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01703.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch0pr04cu00504.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr02cu00402.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr05cu00101.inbound.protection.outlook.com`
		A	52.101.9.20^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00604.inbound.protection.outlook.com`
		A	52.101.10.5^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr04cu00105.inbound.protection.outlook.com`
		A	52.101.41.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00305.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns-cloud-d1.googledomains.com`cloud-dns-hostmaster@google.com serial=23

`org`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.org.afilias-nst.info` ⭐ ⚠️ Not in parent delegation
	NS	`a2.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`c0.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`d0.org.afilias-nst.org`
	SOA	`a0.org.afilias-nst.info`hostmaster@donuts.email serial=1774496779

Same first word

congressdistrict.org

DNS History

10 records (5 active, 5 former)

○NSdns1.name-services.com2015-08-02 → 2017-03-27 · 3 obs

● 2015-08-02 17:06:58
● 2017-03-27 23:08:14
○ 2026-03-26 04:11:16

○NSdns2.name-services.com2015-08-02 → 2017-03-27 · 3 obs

● 2015-08-02 17:06:58
● 2017-03-27 23:08:14
○ 2026-03-26 04:11:16

○NSdns3.name-services.com2015-08-02 → 2017-03-27 · 3 obs

● 2015-08-02 17:06:58
● 2017-03-27 23:08:14
○ 2026-03-26 04:11:16

○NSdns4.name-services.com2015-08-02 → 2017-03-27 · 3 obs

● 2015-08-02 17:06:58
● 2017-03-27 23:08:14
○ 2026-03-26 04:11:16

○NSdns5.name-services.com2015-08-02 → 2017-03-27 · 3 obs

● 2015-08-02 17:06:58
● 2017-03-27 23:08:14
○ 2026-03-26 04:11:16

●NSns-cloud-d1.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 23:08:14
● 2026-03-26 04:11:16

●NSns-cloud-d2.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 23:08:14
● 2026-03-26 04:11:16

●NSns-cloud-d3.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 23:08:14
● 2026-03-26 04:11:16

●NSns-cloud-d4.googledomains.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 23:08:14
● 2026-03-26 04:11:16

●MXcongressdistrict-org.mail.protection.outlook.com2015-08-02 → 2026-03-26 · 2 obs

● 2015-08-02 17:06:58
● 2026-03-26 04:11:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
org	b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org	-
congressdistrict.org	ns-cloud-d1.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com	-

✅ Authoritative Response

Server:216.239.32.109

NS records: ns-cloud-d1.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 711ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com...`
MX	1	`congressdistrict-org.mail.protection.out`
TXT	1	`v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns-cloud-d1.googledomains.com cloud-dns-`

Analysis

Name Servers

congressdistrict.org is delegated to four name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.

congressdistrict.org at least partially shares its name servers with other domains, for instance cefonstudio.com, westernattorneyservices.com, itverse.com, finleylawfirm.net and kwoberlin.com.

Host names with two IPs: ns-cloud-d1.googledomains.com points to 2001:4860:4802:32::6d and 216.239.32.109; ns-cloud-d2.googledomains.com points to 2001:4860:4802:34::6d and 216.239.34.109; ns-cloud-d3.googledomains.com points to 2001:4860:4802:36::6d and 216.239.36.109; ns-cloud-d4.googledomains.com points to 2001:4860:4802:38::6d and 216.239.38.109.

Mail Servers

congressdistrict.org is served by a single mail server, congressdistrict-org.mail.protection.outlook.com.

The host name congressdistrict-org.mail.protection.outlook.com resolves to eight IP numbers: 2a01:111:f403:c902::3, 2a01:111:f403:c946::4, 2a01:111:f403:f901::2, 2a01:111:f403:f913::1, 52.101.9.20, 52.101.10.5, 52.101.41.21 and 52.101.41.24.

congressdistrict.org - robtex.com