`m-comunicacion.com.mx`

DNSSEC	⚠️ Not signed
NS	`ns1.systemdns.com` ⚠️ Not in zone NS records
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com` ⚠️ Not in zone NS records
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com` ⚠️ Not in zone NS records
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`

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

WOT: NOT_SAFE (44/100)

Same first word

m-comunicacion.com.mx

DNS History

12 records (3 active, 9 former)

○NSjakub.ns.cloudflare.com2026-05-10 → 2026-05-10 · 4 obs

○ 2026-04-24 04:58:58
● 2026-05-10 12:56:10
○ 2026-05-12 10:34:54
○ 2026-08-01 18:23:34

○NSkristina.ns.cloudflare.com2026-05-10 → 2026-05-10 · 4 obs

○ 2026-04-24 04:58:58
● 2026-05-10 12:56:10
○ 2026-05-12 10:34:54
○ 2026-08-01 18:23:34

○NSns1.m-comunicacion.com.mx2015-08-19 → 2018-05-24 · 4 obs

● 2015-08-19 22:59:40
● 2018-05-24 03:41:08
○ 2026-04-24 04:58:58
○ 2026-08-01 18:23:34

●NSns1.systemdns.com2026-05-12 → 2026-08-01 · 3 obs

○ 2026-05-10 12:56:10
● 2026-05-12 10:34:54
● 2026-08-01 18:23:34

○NSns2.m-comunicacion.com.mx2015-08-19 → 2018-05-24 · 4 obs

● 2015-08-19 22:59:40
● 2018-05-24 03:41:08
○ 2026-04-24 04:58:58
○ 2026-08-01 18:23:34

●NSns2.systemdns.com2026-05-12 → 2026-08-01 · 3 obs

○ 2026-05-10 12:56:10
● 2026-05-12 10:34:54
● 2026-08-01 18:23:34

●NSns3.systemdns.com2026-05-12 → 2026-08-01 · 3 obs

○ 2026-05-10 12:56:10
● 2026-05-12 10:34:54
● 2026-08-01 18:23:34

○MXmail.m-comunicacion.com.mx2015-08-19 → 2018-05-24 · 4 obs

● 2015-08-19 22:59:40
● 2018-05-24 03:41:08
○ 2026-04-24 04:58:58
○ 2026-08-01 18:23:34

○MXmx.betterbeingcoach.com2026-05-10 → 2026-05-10 · 4 obs

○ 2026-04-24 04:58:58
● 2026-05-10 12:56:10
○ 2026-05-12 10:34:54
○ 2026-08-01 18:23:34

○A54.183.102.222026-05-10 → 2026-05-10 · 4 obs

○ 2026-04-24 04:58:58
● 2026-05-10 12:56:10
○ 2026-05-12 10:34:54
○ 2026-08-01 18:23:34

○A65.99.205.1772015-08-19 → 2015-08-19 · 3 obs

● 2015-08-19 22:59:40
○ 2015-12-06 23:02:02
○ 2026-08-01 18:23:34

○A65.99.205.1792015-12-06 → 2018-05-24 · 5 obs

○ 2015-08-19 22:59:40
● 2015-12-06 23:02:02
● 2018-05-24 03:41:08
○ 2026-04-24 04:58:58
○ 2026-08-01 18:23:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
m-comunicacion.com.mx	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	-

✅ Authoritative Response

Server:64.99.96.36

NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for m-comunicacion.com.mx (unsigned zone)

⏱️ Timing

Total: 624ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

Three name servers are authoritative for m-comunicacion.com.mx: ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

m-comunicacion.com.mx shares at least some of its name servers with other domains, including oti.cz, ragbos.com, pacificoastfarming.com and two others.

ns1.systemdns.com resolves to 216.40.47.90 and 2604:4000:0:d:216:40:47:90. ns2.systemdns.com resolves to 64.98.148.16 and 2604:4000:2800:d:64:99:148:16. ns3.systemdns.com resolves to 64.99.96.36 and 2604:4000:0:d:64:99:96:36. All three hostnames point to two IP numbers each.

m-comunicacion.com.mx - robtex.com