`securitydays.com.mx`

DNSSEC	⚠️ Not signed
A	20.70.246.20^{🇦🇺 Microsoft20.64.0.0/10}
A	20.76.201.171^{🇳🇱 Microsoft20.64.0.0/10}
A	20.112.250.133^{🇺🇸 Microsoft20.64.0.0/10}
A	20.231.239.246^{🇺🇸 Microsoft20.192.0.0/10}
A	20.236.44.162^{🇺🇸 Microsoft20.192.0.0/10}
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
SOA	`ns1-01.azure-dns.com`azuredns-hostmaster@microsoft.com serial=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=1773555550

WOT: NOT_SAFE (44/100)

Same first word

securitydays.com.mx

DNS History

18 records (9 active, 9 former)

●NSns1-01.azure-dns.com2026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

○NSns1.msft.net2015-05-23 → 2017-05-25 · 4 obs

● 2015-05-23 14:28:52
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

●NSns2-01.azure-dns.net2026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

○NSns2.msft.net2015-05-23 → 2017-05-25 · 4 obs

● 2015-05-23 14:28:52
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

●NSns3-01.azure-dns.org2026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

●NSns4-01.azure-dns.info2026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

○A104.40.191.2372015-10-15 → 2017-05-25 · 5 obs

○ 2015-05-23 14:28:52
● 2015-10-15 04:26:30
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

○A104.43.142.342015-10-15 → 2017-05-25 · 5 obs

○ 2015-05-23 14:28:52
● 2015-10-15 04:26:30
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

○A134.170.185.462015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 14:28:52
○ 2015-10-15 04:26:30
○ 2026-03-22 20:21:54

○A134.170.188.2212015-05-23 → 2015-05-23 · 3 obs

● 2015-05-23 14:28:52
○ 2015-10-15 04:26:30
○ 2026-03-22 20:21:54

○A191.235.218.1662015-10-15 → 2017-05-25 · 5 obs

○ 2015-05-23 14:28:52
● 2015-10-15 04:26:30
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

○A191.237.78.582015-10-15 → 2017-05-25 · 5 obs

○ 2015-05-23 14:28:52
● 2015-10-15 04:26:30
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

●A20.112.250.1332026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

●A20.231.239.2462026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

●A20.236.44.1622026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

●A20.70.246.202026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

●A20.76.201.1712026-02-28 → 2026-03-22 · 3 obs

○ 2017-05-25 09:35:10
● 2026-02-28 14:06:58
● 2026-03-22 20:21:54

○A23.101.184.2062015-10-15 → 2017-05-25 · 5 obs

○ 2015-05-23 14:28:52
● 2015-10-15 04:26:30
● 2017-05-25 09:35:10
○ 2026-02-28 14:06:58
○ 2026-03-22 20:21:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, o.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
securitydays.com.mx	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	-

✅ Authoritative Response

Server: 150.171.21.1

NS records: ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 278ms | Queries: -

📄 Records

Type	Count	Sample Data
A	5	`20.76.201.171, 20.112.250.133...`
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

Analysis

IP Addresses

securitydays.com.mx points to five IP numbers: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.

Other host names, for instance bingplaces.com.mx, hotmailmember.biz, officelive.net, reactormicrosoft.com and binggate.com share IP numbers with securitydays.com.mx.

Name Servers

securitydays.com.mx is delegated to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

securitydays.com.mx at least partially shares name servers with other domains such as inmationdev.com, aebtorneria.it, simplyelt.com, arapahoedrives.gov and propheseesolutions.com.

Host names with two IP numbers:

ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1

ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1

ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1

ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1

securitydays.com.mx - robtex.com