`mysecurehealthdata.com`

DNSSEC	⚠️ Not signed
A	54.187.235.136^{🇺🇸 Amazon54.186.0.0/15 EC2 PDX prefix}
		PTR	`ec2-54-187-235-136.us-west-2.compute.amazonaws.com`
NS	`ns37.domaincontrol.com` ⭐
		A	2603:5:21c1::13^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns37.domaincontrol.com`
		A	97.74.108.19^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns37.domaincontrol.com`
NS	`ns38.domaincontrol.com`
		A	2603:5:22c1::13^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns38.domaincontrol.com`
		A	173.201.76.19^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns38.domaincontrol.com`
MX	`mysecurehealthdata-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch1pr04cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr03cu00403.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr21cu00100.inbound.protection.outlook.com`
		A	52.101.11.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr03cu00102.inbound.protection.outlook.com`
		A	52.101.40.1^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy4pr03cu00101.inbound.protection.outlook.com`
		A	52.101.41.28^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	52.101.194.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00504.inbound.protection.outlook.com`
TXT	`202602181938413gle23nd8489odflrjnz0pvoebmhrhsil18owao1k8tue1h0py`
TXT	`202602181944281dvuocq8g9amj1mtn66gdxh7k1uhe5so8x9qzg3088i4wj44yn`
TXT	`v=spf1 include:spf.protection.outlook.com include:spfa.cpmails.com include:sp...`
TXT	`D2868672`
SOA	`ns37.domaincontrol.com`dns@jomax.net 2026-02-18 #2

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

Same first word

mysecurehealthdata.com

DNS History

7 records (4 active, 3 former)

●NSns37.domaincontrol.com2015-08-10 → 2026-07-28 · 2 obs

● 2015-08-10 13:21:50
● 2026-07-28 20:46:44

●NSns38.domaincontrol.com2015-08-10 → 2026-07-28 · 2 obs

● 2015-08-10 13:21:50
● 2026-07-28 20:46:44

○MXmailstore1.secureserver.net2015-08-10 → 2017-11-11 · 4 obs

● 2015-08-10 13:21:50
● 2017-11-11 03:29:40
○ 2026-07-28 20:46:42
○ 2026-07-28 20:46:44

●MXmysecurehealthdata-com.mail.protection.outlook.com2026-07-28 → 2026-07-28 · 3 obs

○ 2017-11-11 03:29:40
● 2026-07-28 20:46:42
● 2026-07-28 20:46:44

○MXsmtp.secureserver.net2015-08-10 → 2017-11-11 · 4 obs

● 2015-08-10 13:21:50
● 2017-11-11 03:29:40
○ 2026-07-28 20:46:42
○ 2026-07-28 20:46:44

○A108.47.79.682015-08-10 → 2017-11-11 · 4 obs

● 2015-08-10 13:21:50
● 2017-11-11 03:29:40
○ 2026-07-28 20:46:42
○ 2026-07-28 20:46:44

●A54.187.235.1362026-07-28 → 2026-07-28 · 3 obs

○ 2017-11-11 03:29:40
● 2026-07-28 20:46:42
● 2026-07-28 20:46:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, a.gtld-servers.net...	-
mysecurehealthdata.com	ns37.domaincontrol.com, ns38.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.76.19

NS records: ns37.domaincontrol.com, ns38.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mysecurehealthdata.com (unsigned zone)

⏱️ Timing

Total: 166ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.187.235.136`
NS	2	`ns37.domaincontrol.com, ns38.domaincontrol.com`
MX	1	`mysecurehealthdata-com.mail.protection.o`
TXT	4	`202602181938413gle23nd8489odflrjnz0pvoeb, 202602181944281dvuocq8g9amj1mtn66gdxh7k1...`
SOA	1	`ns37.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns37.domaincontrol.com, ns37.domaincontrol.com, ns38.domaincontrol.com...)

Analysis

IP Addresses

mysecurehealthdata.com resolves to one IP address: 54.187.235.136.

Other host names share IP numbers with mysecurehealthdata.com; ec2-54-187-235-136.us-west-2.compute.amazonaws.com is one such example.

Name Servers

mysecurehealthdata.com is served by two delegated name servers, ns37.domaincontrol.com and ns38.domaincontrol.com.

mysecurehealthdata.com uses the same name servers as several other domains — among them art19.co.uk, lakemary.org, pixelmania.co.uk and two more.

Each of the two host names carries two IP addresses: ns37.domaincontrol.com points to 97.74.108.19 and 2603:5:21c1::13, and ns38.domaincontrol.com points to 173.201.76.19 and 2603:5:22c1::13.

Mail Servers

Mail for mysecurehealthdata.com is handled by a single mail server, mysecurehealthdata-com.mail.protection.outlook.com.

mysecurehealthdata-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.11.2, 52.101.40.1, 52.101.41.28 and 5 others.

mysecurehealthdata.com - robtex.com