congresstitle.com - dns.ninja

`congresstitle.com`

DNSSEC	⚠️ Not signed
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2026-05-21 #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=1782863386

Previously MX for

congresstitle.com

Same first word

congresstitle.com

Similar names

scoresettling.com

closingstreet.com

DNS History

16 records (4 active, 12 former)

○NSbdiia01.fnfis.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

○NSns0.directnic.com2019-01-15 → 2019-01-15 · 4 obs

○ 2017-01-23 11:19:48
● 2019-01-15 00:55:00
○ 2026-02-17 09:36:34
○ 2026-07-01 00:03:52

○NSns1.directnic.com2019-01-15 → 2019-01-15 · 4 obs

○ 2017-01-23 11:19:48
● 2019-01-15 00:55:00
○ 2026-02-17 09:36:34
○ 2026-07-01 00:03:52

○NSns1.fisglobal.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

●NSns1.markmonitor.com2026-02-17 → 2026-07-01 · 3 obs

○ 2019-01-15 00:55:00
● 2026-02-17 09:36:34
● 2026-07-01 00:03:52

○NSns2.fisglobal.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

●NSns2.markmonitor.com2026-02-17 → 2026-07-01 · 3 obs

○ 2019-01-15 00:55:00
● 2026-02-17 09:36:34
● 2026-07-01 00:03:52

○NSns3.fisglobal.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

●NSns3.markmonitor.com2026-02-17 → 2026-07-01 · 3 obs

○ 2019-01-15 00:55:00
● 2026-02-17 09:36:34
● 2026-07-01 00:03:52

●NSns4.markmonitor.com2026-02-17 → 2026-07-01 · 3 obs

○ 2019-01-15 00:55:00
● 2026-02-17 09:36:34
● 2026-07-01 00:03:52

○MXcongresstitle.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

○MXsmtp.congresstitle.com2015-08-11 → 2017-01-23 · 4 obs

● 2015-08-11 01:25:22
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

○A206.211.106.442017-01-23 → 2017-01-23 · 4 obs

○ 2016-03-25 03:10:38
● 2017-01-23 11:19:48
○ 2019-01-15 00:55:00
○ 2026-07-01 00:03:52

○A206.211.96.92015-08-11 → 2016-03-25 · 4 obs

● 2015-08-11 01:25:22
● 2016-03-25 03:10:38
○ 2017-01-23 11:19:48
○ 2026-07-01 00:03:52

○A74.117.221.212019-01-15 → 2019-01-15 · 4 obs

○ 2017-01-23 11:19:48
● 2019-01-15 00:55:00
○ 2026-02-17 09:36:34
○ 2026-07-01 00:03:52

○A74.117.221.222019-01-15 → 2019-01-15 · 4 obs

○ 2017-01-23 11:19:48
● 2019-01-15 00:55:00
○ 2026-02-17 09:36:34
○ 2026-07-01 00:03:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net...	-
congresstitle.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com	8 records

✅ Authoritative Response

Server:149.112.160.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for congresstitle.com (unsigned zone)

⏱️ Timing

Total: 218ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.markmonitor.com, ns2.markmonitor.com...`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)

Analysis

Name Servers

The authoritative name servers for congresstitle.com are ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com.

congresstitle.com has at least partial name server overlap with other domains, such as wootcoupon.com, stoneisland.kr, megabloc.com and two others.

These name servers tend to appear together with the name servers ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com all point to exactly two IP numbers each: ns1.markmonitor.com → 149.112.160.1 and 2620:10a:80a8::1; ns2.markmonitor.com → 176.97.158.1 and 2001:67c:10b8::1; ns3.markmonitor.com → 149.112.161.1 and 2620:10a:80a9::1; ns4.markmonitor.com → 192.174.68.1 and 2001:67c:1bc::1.