`medicaldistrict.com.mx`

DNSSEC	⚠️ Not signed
A	195.250.27.21^{🇬🇧 WHG-MEX195.250.27.0/24}
		PTR	`s3409.mex1.stableserver.net`
NS	`ns1.mysecurecloudhost.com` ⭐
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.mysecurecloudhost.com`
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.mysecurecloudhost.com`
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns4.mysecurecloudhost.com`
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c06::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f27.1e100.net`
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.1e100.net`
		A	2607:f8b0:4004:c0b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f27.1e100.net`
		A	142.250.31.26^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f26.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
		A	172.253.115.26^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f26.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
		A	172.253.122.27^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
TXT	`v=spf1 +a +mx +ip4:195.250.27.21 include:spf.mysecurecloudhost.com ~all`
SOA	`ns1.mysecurecloudhost.com`servers@mysecurecloudhost.com 2026-06-27 #1

`com.mx`

	DNSSEC	⚠️ Not signed
	NS	`m.mx-ns.mx` ⭐ ⚠️ Not in parent delegation
	NS	`c.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`e.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`i.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`o.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`x.mx-ns.mx` ⚠️ Not in parent delegation
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1785173617

WOT: NOT_SAFE (44/100)

Subdomains

cpanel.medicaldistrict.com.mx

autodiscover.medicaldistrict.com.mx

Same first word

medicaldistrict.com.mx

Similar names

districtmedical.ca

DNS History

9 records (9 active, 0 former)

●NSns1.mysecurecloudhost.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●NSns2.mysecurecloudhost.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●NSns3.mysecurecloudhost.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●NSns4.mysecurecloudhost.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●MXalt1.aspmx.l.google.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●MXalt2.aspmx.l.google.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●MXalt3.aspmx.l.google.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●MXsmtp.google.com2026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

●A195.250.27.212026-06-14 → 2026-07-27 · 2 obs

● 2026-06-14 12:04:14
● 2026-07-27 17:43:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx...	-
medicaldistrict.com.mx	ns1.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns4.mysecurecloudhost.com	-

✅ Authoritative Response

Server:13.248.158.180

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for medicaldistrict.com.mx (unsigned zone)

⏱️ Timing

Total: 622ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`195.250.27.21`
NS	4	`ns1.mysecurecloudhost.com, ns3.mysecurecloudhost.com...`
MX	4	`alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 +a +mx +ip4:195.250.27.21 include`
SOA	1	`ns1.mysecurecloudhost.com servers.mysecu`

Analysis

Hierarchy

cpanel.medicaldistrict.com.mx and autodiscover.medicaldistrict.com.mx each fall under medicaldistrict.com.mx as their parent domain.

IP Addresses

medicaldistrict.com.mx resolves to just one IP address, 195.250.27.21.

Two other host names, along with superlimpias.com, rninoxidables.com and cpanel.medicaldistrict.com.mx, also share IP numbers with medicaldistrict.com.mx.

Name Servers

The NS records for medicaldistrict.com.mx point to four name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.

medicaldistrict.com.mx partially shares its NS delegation with several other domains, including greentheoryandpraxisjournal.org, ralcomsa.mx, valesco.com.pe and two others.

These name servers are regularly seen alongside ns1000.mochahost.com and ns2000.mochahost.com as name servers.

The hosts ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com all resolve to exactly one IP address each: 13.248.158.180, 75.2.118.134, 76.223.26.245 and 99.83.147.209 respectively.