`johnhancockcdc.com`

DNSSEC	⚠️ Not signed
NS	`dns1.hrtc.net` ⭐
		A	2602:ffe2:54::97^{🇺🇸 TUT-AS2602:ffe2:54::/48 REACH (Customer Route)}
			PTR	`ns1.hrtc.net`
		A	216.59.57.97^{🇺🇸 TUT-AS216.59.57.0/24 Total Uptime Technologies LLC}
			PTR	`ns1.hrtc.net`
NS	`dns2.hrtc.net`
		A	2602:ffe2:ffe::97^{🇺🇸 TUT-AS2602:ffe2:ffe::/48 REACH (Customer Route)}
			PTR	`ns2.hrtc.net`
		A	104.153.199.97^{🇺🇸 TUT-AS104.153.199.0/24 Total Uptime Technologies LLC}
			PTR	`ns2.hrtc.net`
MX	`johnhancockcdc-org.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr05cu00501.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f90a::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr02cu00300.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
		A	52.101.41.58^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr02cu00102.inbound.protection.outlook.com`
		A	52.101.50.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00502.inbound.protection.outlook.com`
TXT	`MS=ms98153798`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`dns1.hrtc.net`dzurner@johnhancockcdc.org 2023-03-27 #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=1781491950

Same first word

johnhancockcdc.net

johnhancockcdc.com

DNS History

3 records (3 active, 0 former)

●NSdns1.hrtc.net2026-05-17 → 2026-06-15 · 2 obs

● 2026-05-17 12:17:18
● 2026-06-15 02:56:38

●NSdns2.hrtc.net2026-05-17 → 2026-06-15 · 2 obs

● 2026-05-17 12:17:18
● 2026-06-15 02:56:38

●MXjohnhancockcdc-org.mail.protection.outlook.com2026-05-17 → 2026-06-15 · 2 obs

● 2026-05-17 12:17:18
● 2026-06-15 02:56:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
johnhancockcdc.com	dns1.hrtc.net, dns2.hrtc.net	-

✅ Authoritative Response

Server:104.153.199.97

NS records: dns1.hrtc.net, dns2.hrtc.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for johnhancockcdc.com (unsigned zone)

⏱️ Timing

Total: 1541ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.hrtc.net, dns2.hrtc.net`
MX	1	`johnhancockcdc-org.mail.protection.outlo`
TXT	2	`MS=ms98153798, v=spf1 include:spf.protection.outlook.co`
SOA	1	`dns1.hrtc.net dzurner.johnhancockcdc.org`

Analysis

Name Servers

johnhancockcdc.com is delegated to two name servers: dns1.hrtc.net and dns2.hrtc.net.

johnhancockcdc.com has the same name server delegation as a number of other domains, such as 9starconnections.net, 9startelevision.org, ninestarenergy.org and two more.

There is at least partial name server overlap between johnhancockcdc.com and other domains — 118.112.74.in-addr.arpa, cloudninestar.net, 15.184.64.in-addr.arpa and two more among them.

dns1.hrtc.net and dns2.hrtc.net each resolve to two IP addresses: dns1.hrtc.net points to 216.59.57.97 and 2602:ffe2:54::97, while dns2.hrtc.net points to 104.153.199.97 and 2602:ffe2:ffe::97.

Mail Servers

johnhancockcdc.com routes its mail through a single mail server, johnhancockcdc-org.mail.protection.outlook.com.

johnhancockcdc-org.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.11.15, 52.101.41.24 and 52.101.41.58, along with 5 other.

johnhancockcdc.com - robtex.com