`congressforce.com`

DNSSEC	⚠️ Not signed
A	168.62.186.126^{🇺🇸 Microsoft168.62.0.0/15 MICROSOFT}
NS	`ns33.worldnic.com` ⭐
		A	162.159.26.212^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns34.worldnic.com`
		A	162.159.27.146^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 -all`
SOA	`NS33.WORLDNIC.com`namehost@WORLDNIC.com serial=125120908

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

Same first word

congressforce.com

DNS History

7 records (3 active, 4 former)

○NSdns10.ai.net2015-05-12 → 2017-08-17 · 4 obs

● 2015-05-12 22:31:36
● 2017-08-17 17:06:42
○ 2026-04-12 09:09:58
○ 2026-04-12 09:10:00

○NSdns6.ai.net2015-05-12 → 2017-08-17 · 4 obs

● 2015-05-12 22:31:36
● 2017-08-17 17:06:42
○ 2026-04-12 09:09:58
○ 2026-04-12 09:10:00

○NSdns9.ai.net2015-05-12 → 2017-08-17 · 4 obs

● 2015-05-12 22:31:36
● 2017-08-17 17:06:42
○ 2026-04-12 09:09:58
○ 2026-04-12 09:10:00

●NSns33.worldnic.com2026-04-12 → 2026-04-12 · 3 obs

○ 2017-08-17 17:06:42
● 2026-04-12 09:09:58
● 2026-04-12 09:10:00

●NSns34.worldnic.com2026-04-12 → 2026-04-12 · 3 obs

○ 2017-08-17 17:06:42
● 2026-04-12 09:09:58
● 2026-04-12 09:10:00

●A168.62.186.1262026-04-12 → 2026-04-12 · 3 obs

○ 2017-08-17 17:06:42
● 2026-04-12 09:09:58
● 2026-04-12 09:10:00

○A205.134.170.1892015-05-12 → 2017-08-17 · 4 obs

● 2015-05-12 22:31:36
● 2017-08-17 17:06:42
○ 2026-04-12 09:09:58
○ 2026-04-12 09:10:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net...	-
congressforce.com	ns33.worldnic.com, ns34.worldnic.com	2 records

✅ Authoritative Response

Server:162.159.26.212

NS records: ns33.worldnic.com, ns34.worldnic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for congressforce.com (unsigned zone)

⏱️ Timing

Total: 222ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`168.62.186.126`
NS	2	`ns33.worldnic.com, ns34.worldnic.com`
TXT	1	`v=spf1 -all`
SOA	1	`NS33.WORLDNIC.com namehost.WORLDNIC.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns33.worldnic.com, ns34.worldnic.com)

Analysis

IP Addresses

congressforce.com resolves to one IP number: 168.62.186.126.

Other host names for instance kw3.knowwho.com and knowwho.com share IP numbers with congressforce.com.

Name Servers

congressforce.com's delegation uses two name servers: ns33.worldnic.com and ns34.worldnic.com.

congressforce.com uses the same name server setup as other domains, such as shelbytwp.org, plano-b.com, eurocork.com, vfquniversity.com and neurosurgery-texas.com.

Host names with a single IP address: ns33.worldnic.com points to 162.159.26.212; ns34.worldnic.com points to 162.159.27.146.

congressforce.com - robtex.com