`jhancocklaw.com`

DNSSEC	⚠️ Not signed
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`jhancocklaw-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c927::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:c927::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn8pr05cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f90a::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr02cu00300.inbound.protection.outlook.com`
		A	52.101.8.42^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr03cu00402.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.9.14^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr03cu00206.inbound.protection.outlook.com`
		A	52.101.11.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
TXT	`mscid=EPAY45LmWfI/+tQ15KQI/vHXgDY8AWrqEgGK8GDA0cZZQgOZRrXIQ2OvxWDhhhg9W7zYft9...`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=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=1776447062

Same first word

jhancocklaw.com

DNS History

11 records (5 active, 6 former)

●NSns1.bdm.microsoftonline.com2018-06-03 → 2026-04-17 · 3 obs

○ 2017-01-06 22:34:48
● 2018-06-03 03:34:26
● 2026-04-17 17:55:18

○NSns1.stratanet.com2015-06-07 → 2017-01-06 · 4 obs

● 2015-06-07 19:29:30
● 2017-01-06 22:34:48
○ 2018-06-03 03:34:26
○ 2026-04-17 17:55:18

●NSns2.bdm.microsoftonline.com2018-06-03 → 2026-04-17 · 3 obs

○ 2017-01-06 22:34:48
● 2018-06-03 03:34:26
● 2026-04-17 17:55:18

○NSns2.stratanet.com2015-06-07 → 2017-01-06 · 4 obs

● 2015-06-07 19:29:30
● 2017-01-06 22:34:48
○ 2018-06-03 03:34:26
○ 2026-04-17 17:55:18

●NSns3.bdm.microsoftonline.com2018-06-03 → 2026-04-17 · 3 obs

○ 2017-01-06 22:34:48
● 2018-06-03 03:34:26
● 2026-04-17 17:55:18

●NSns4.bdm.microsoftonline.com2018-06-03 → 2026-04-17 · 3 obs

○ 2017-01-06 22:34:48
● 2018-06-03 03:34:26
● 2026-04-17 17:55:18

●MXjhancocklaw-com.mail.protection.outlook.com2018-06-03 → 2026-04-17 · 3 obs

○ 2017-01-06 22:34:48
● 2018-06-03 03:34:26
● 2026-04-17 17:55:18

○MXmx1.stratanet.com2015-06-07 → 2017-01-06 · 4 obs

● 2015-06-07 19:29:30
● 2017-01-06 22:34:48
○ 2018-06-03 03:34:26
○ 2026-04-17 17:55:18

○MXmx2.stratanet.com2015-06-07 → 2017-01-06 · 4 obs

● 2015-06-07 19:29:30
● 2017-01-06 22:34:48
○ 2018-06-03 03:34:26
○ 2026-04-17 17:55:18

○A199.47.189.402017-01-06 → 2017-01-06 · 4 obs

○ 2016-03-31 22:55:42
● 2017-01-06 22:34:48
○ 2018-06-03 03:34:26
○ 2026-04-17 17:55:18

○A67.213.225.502015-06-07 → 2016-03-31 · 4 obs

● 2015-06-07 19:29:30
● 2016-03-31 22:55:42
○ 2017-01-06 22:34:48
○ 2026-04-17 17:55:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net...	-
jhancocklaw.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com	4 records

✅ Authoritative Response

Server:150.171.21.208

NS records: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jhancocklaw.com (unsigned zone)

⏱️ Timing

Total: 223ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`jhancocklaw-com.mail.protection.outlook.`
TXT	2	`mscid=EPAY45LmWfI/+tQ15KQI/vHXgDY8AWrqEg, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...)

Analysis

Name Servers

jhancocklaw.com is delegated to four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

At least part of the name servers for jhancocklaw.com are shared with other domains, for instance maxim-associates.com, grupomds.com, apexaustralia.com, rexon.com.br and mrmessenger.com.