`hunkanalytics.mx`

DNSSEC	⚠️ Not signed
NS	`ha1.markmonitor.zone` ⭐
		A	2001:67c:1bc::5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ha1.markmonitor.zone`
		A	192.174.68.5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ha1.markmonitor.zone`
NS	`ha2.markmonitor.zone`
		A	2620:10a:80eb::6b^{🇨🇦 CIRA-22620:10a:80eb::/48 D-Zone Anycast Cloud 1}
			PTR	`ha2.markmonitor.zone`
		A	162.219.54.170^{🇨🇦 CIRA-2162.219.54.0/24 D-Zone Anycast Cloud1}
			PTR	`ha2.markmonitor.zone`
NS	`ha3.markmonitor.zone`
		A	2001:67c:10b8::5^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ha3.markmonitor.zone`
		A	176.97.158.5^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ha3.markmonitor.zone`
NS	`ha4.markmonitor.zone`
		A	2620:10a:80ec::6b^{🇨🇦 CIRA-32620:10a:80ec::/48 D-Zone IPv6 Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
		A	162.219.55.170^{🇨🇦 CIRA-3162.219.55.0/24 D-Zone Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
TXT	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all`
SOA	`ha1.markmonitor.zone`hostmaster@markmonitor.com 2025-10-23 #1

`mx`

	DNSSEC	🔒 Signed (DS record present)
	NS	`m.mx-ns.mx` ⭐
	NS	`c.mx-ns.mx`
	NS	`e.mx-ns.mx`
	NS	`i.mx-ns.mx`
	NS	`o.mx-ns.mx`
	NS	`x.mx-ns.mx`
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1784350475

Same first word

DNS History

13 records (4 active, 9 former)

●NSha1.markmonitor.zone2026-05-25 → 2026-07-18 · 3 obs

○ 2017-04-08 14:26:08
● 2026-05-25 06:35:04
● 2026-07-18 05:30:32

●NSha2.markmonitor.zone2026-05-25 → 2026-07-18 · 3 obs

○ 2017-04-08 14:26:08
● 2026-05-25 06:35:04
● 2026-07-18 05:30:32

●NSha3.markmonitor.zone2026-05-25 → 2026-07-18 · 3 obs

○ 2017-04-08 14:26:08
● 2026-05-25 06:35:04
● 2026-07-18 05:30:32

●NSha4.markmonitor.zone2026-05-25 → 2026-07-18 · 3 obs

○ 2017-04-08 14:26:08
● 2026-05-25 06:35:04
● 2026-07-18 05:30:32

○NSns1.markmonitor.com2015-08-10 → 2017-04-08 · 4 obs

● 2015-08-10 07:07:14
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns2.markmonitor.com2016-03-04 → 2017-04-08 · 5 obs

○ 2015-08-10 07:07:14
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns3.markmonitor.com2015-08-10 → 2017-04-08 · 4 obs

● 2015-08-10 07:07:14
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns4.markmonitor.com2016-03-04 → 2017-04-08 · 5 obs

○ 2015-08-10 07:07:14
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns5.markmonitor.com2016-03-04 → 2017-04-08 · 5 obs

○ 2015-08-10 07:07:14
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns6.markmonitor.com2016-03-04 → 2017-04-08 · 5 obs

○ 2015-08-10 07:07:14
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○NSns7.markmonitor.com2016-03-04 → 2017-04-08 · 5 obs

○ 2015-08-10 07:07:14
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○A72.52.10.142016-03-04 → 2017-04-08 · 5 obs

○ 2015-11-23 19:14:48
● 2016-03-04 11:41:16
● 2017-04-08 14:26:08
○ 2026-05-25 06:35:04
○ 2026-07-18 05:30:32

○A93.191.168.522015-08-10 → 2015-11-23 · 4 obs

● 2015-08-10 07:07:14
● 2015-11-23 19:14:48
○ 2016-03-04 11:41:16
○ 2026-07-18 05:30:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx...	12 records
hunkanalytics.mx	ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone	-

✅ Authoritative Response

Server:162.219.54.170

NS records: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hunkanalytics.mx (unsigned zone)

⏱️ Timing

Total: 801ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ha2.markmonitor.zone, ha4.markmonitor.zone...`
TXT	1	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}.`
SOA	1	`ha1.markmonitor.zone hostmaster.markmoni`

📌 Glue Records Collected

Total: 12

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

Analysis

Name Servers

The NS records for hunkanalytics.mx point to four name servers: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone.

There is at least partial name server overlap between hunkanalytics.mx and other domains — aquarea.ch, enduranceinsurance.eu, sandoz.ua and two more among them.

These name servers regularly appear alongside ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 other name servers in NS record sets.

All four hostnames — ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone — resolve to two IP numbers apiece: ha1.markmonitor.zone to 192.174.68.5 and 2001:67c:1bc::5; ha2.markmonitor.zone to 162.219.54.170 and 2620:10a:80eb::6b; ha3.markmonitor.zone to 176.97.158.5 and 2001:67c:10b8::5; ha4.markmonitor.zone to 162.219.55.170 and 2620:10a:80ec::6b.

hunkanalytics.mx - robtex.com