`domaindiligence.com`

DNSSEC	⚠️ Not signed
A	35.85.70.222^{🇺🇸 Amazon35.80.0.0/12 EC2 PDX prefix}
		PTR	`ec2-35-85-70-222.us-west-2.compute.amazonaws.com`
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`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com`
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com`
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
TXT	`v=spf1 -all`
SOA	`ns1.markmonitor.com`joseph\@jenkins.markmonitor.com 2025-06-11 #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=1785944429

Same first word

domaindiligence.com

DNS History

15 records (8 active, 7 former)

●NSns1.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

○NSns1.sedoparking.com2015-08-02 → 2017-03-22 · 4 obs

● 2015-08-02 01:08:10
● 2017-03-22 16:35:52
○ 2020-03-02 17:48:26
○ 2026-08-05 15:52:48

●NSns2.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

○NSns2.sedoparking.com2015-08-02 → 2017-03-22 · 4 obs

● 2015-08-02 01:08:10
● 2017-03-22 16:35:52
○ 2020-03-02 17:48:26
○ 2026-08-05 15:52:48

●NSns3.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

●NSns4.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

●NSns5.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

●NSns6.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

●NSns7.markmonitor.com2020-03-02 → 2026-08-05 · 3 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
● 2026-08-05 15:52:48

○MXbh.markmonitor.com2020-03-02 → 2020-03-02 · 4 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
○ 2026-05-22 23:52:30
○ 2026-08-05 15:52:48

○MXlocalhost2017-03-22 → 2017-03-22 · 4 obs

○ 2016-07-11 21:02:38
● 2017-03-22 16:35:52
○ 2020-03-02 17:48:26
○ 2026-08-05 15:52:48

○MXmail.nickstel.com2015-08-02 → 2016-07-11 · 4 obs

● 2015-08-02 01:08:10
● 2016-07-11 21:02:38
○ 2017-03-22 16:35:52
○ 2026-08-05 15:52:48

●A35.85.70.2222026-05-22 → 2026-08-05 · 3 obs

○ 2020-03-02 17:48:26
● 2026-05-22 23:52:30
● 2026-08-05 15:52:48

○A72.52.4.1192015-08-02 → 2017-03-22 · 4 obs

● 2015-08-02 01:08:10
● 2017-03-22 16:35:52
○ 2020-03-02 17:48:26
○ 2026-08-05 15:52:48

○A93.191.168.522020-03-02 → 2020-03-02 · 4 obs

○ 2017-03-22 16:35:52
● 2020-03-02 17:48:26
○ 2026-05-22 23:52:30
○ 2026-08-05 15:52:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
domaindiligence.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com...	14 records

✅ Authoritative Response

Server:176.97.158.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for domaindiligence.com (unsigned zone)

⏱️ Timing

Total: 290ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.85.70.222`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.markmonitor.com joseph\.jenkins.mark`

📌 Glue Records Collected

Total: 14

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

Analysis

IP Addresses

domaindiligence.com resolves to just one IP address, 35.85.70.222.

Among others, tmguard.com, elawmonitor.com, marksecure.com and ec2-35-85-70-222.us-west-2.compute.amazonaws.com resolve to the same IP numbers as domaindiligence.com.

Name Servers

domaindiligence.com delegates authority to 7 name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com plus 4 other.

There is at least partial name server overlap between domaindiligence.com and other domains — oktane.info, wwwskyanytimetv.com, fontainebleaugaming.net and two more among them.

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

Host names that have two IP addresses:

ns1.markmonitor.com directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com directs traffic to 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com directs traffic to 149.112.161.2 and 2620:10a:80a9::2.