`propertymanagement.com.mx`

DNSSEC	⚠️ Not signed
NS	`ns1.dynadot.com` ⚠️ Not in zone NS records
		A	162.159.26.83^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.147^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dynadot.com` ⚠️ Not in zone NS records
		A	162.159.26.170^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.11^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}

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

WOT: NOT_SAFE (44/100)

Same first word

DNS History

10 records (2 active, 8 former)

●NSns1.dynadot.com2018-10-23 → 2026-03-24 · 3 obs

○ 2017-02-05 16:59:14
● 2018-10-23 13:29:12
● 2026-03-24 20:31:48

○NSns1.jimdo.com2015-11-08 → 2016-06-19 · 4 obs

● 2015-11-08 18:29:50
● 2016-06-19 03:56:46
○ 2017-02-05 16:59:14
○ 2026-03-24 20:31:48

●NSns2.dynadot.com2018-10-23 → 2026-03-24 · 3 obs

○ 2017-02-05 16:59:14
● 2018-10-23 13:29:12
● 2026-03-24 20:31:48

○NSns2.jimdo.com2015-11-08 → 2016-06-19 · 4 obs

● 2015-11-08 18:29:50
● 2016-06-19 03:56:46
○ 2017-02-05 16:59:14
○ 2026-03-24 20:31:48

○MXmx1.jimdo.com2015-11-08 → 2016-06-19 · 4 obs

● 2015-11-08 18:29:50
● 2016-06-19 03:56:46
○ 2017-02-05 16:59:14
○ 2026-03-24 20:31:48

○MXmx2.jimdo.com2015-11-08 → 2016-06-19 · 4 obs

● 2015-11-08 18:29:50
● 2016-06-19 03:56:46
○ 2017-02-05 16:59:14
○ 2026-03-24 20:31:48

○A52.0.217.442018-10-23 → 2018-10-23 · 3 obs

○ 2017-02-05 16:59:14
● 2018-10-23 13:29:12
○ 2026-03-24 20:31:48

○A52.18.10.762015-11-08 → 2015-11-08 · 3 obs

● 2015-11-08 18:29:50
○ 2016-02-07 16:15:38
○ 2026-03-24 20:31:48

○A52.18.89.542016-02-07 → 2016-02-07 · 4 obs

○ 2015-11-08 18:29:50
● 2016-02-07 16:15:38
○ 2016-06-19 03:56:46
○ 2026-03-24 20:31:48

○A52.48.208.322016-06-19 → 2016-06-19 · 4 obs

○ 2016-02-07 16:15:38
● 2016-06-19 03:56:46
○ 2017-02-05 16:59:14
○ 2026-03-24 20:31:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	12 records
propertymanagement.com.mx	ns1.dynadot.com, ns2.dynadot.com	-

✅ Authoritative Response

Server:162.159.26.170

NS records: ns1.dynadot.com, ns2.dynadot.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 312ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (c.mx-ns.mx, c.mx-ns.mx, e.mx-ns.mx...)

Analysis

Name Servers

Two name servers ns1.dynadot.com and ns2.dynadot.com handle the delegation for propertymanagement.com.mx.

propertymanagement.com.mx shares the same name server setup as other domains, for instance showdot.com, amputeligi.com, gpstrackingcollar.com, shoppingpatiopaulista.com and eoloft.com.

propertymanagement.com.mx shares name servers with other domains at least partially, for example onlinecasinohire.com.

Host names with two IP numbers:

ns1.dynadot.com points to 162.159.26.83 and 162.159.27.147.

ns2.dynadot.com points to 162.159.26.170 and 162.159.27.11.

propertymanagement.com.mx - robtex.com