isolaz.com.mx - dns.ninja

isolaz.com.mx

DNSSEC⚠️ Not signed
A99.83.176.46πŸ‡ΊπŸ‡Έ Amazon99.83.176.0/20
PTRa44fc39dcd01d2028.awsglobalaccelerator.com
NSns1.markmonitor.com ⭐
A2620:10a:80a8::1πŸ‡¨πŸ‡¦ CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
A149.112.160.1πŸ‡¨πŸ‡¦ CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
NSns2.markmonitor.com ⚠️ Not in zone NS records
A2001:67c:10b8::1πŸ‡¨πŸ‡­ RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net
PTRns2.markmonitor.com
A176.97.158.1πŸ‡¦πŸ‡Ή RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net
PTRns2.markmonitor.com
NSns3.markmonitor.com
A2620:10a:80a9::1πŸ‡¨πŸ‡¦ CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
A149.112.161.1πŸ‡¨πŸ‡¦ CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
NSns4.markmonitor.com ⚠️ Not in zone NS records
A2001:67c:1bc::1πŸ‡¦πŸ‡Ή RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast
PTRns1.markmonitor.com
A192.174.68.1πŸ‡¦πŸ‡Ή RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net
PTRns1.markmonitor.com
NSns5.markmonitor.com ⚠️ Not in zone NS records
A2620:10a:80a8::2πŸ‡¨πŸ‡¦ CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
A149.112.160.2πŸ‡¨πŸ‡¦ CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada
SOAns1.markmonitor.comhostmaster@markmonitor.com 2015-07-31 #6

com.mx

DNSSEC⚠️ Not signed
NSm.mx-ns.mx ⭐ ⚠️ Not in parent delegation
NSc.mx-ns.mx ⚠️ Not in parent delegation
NSe.mx-ns.mx ⚠️ Not in parent delegation
NSi.mx-ns.mx ⚠️ Not in parent delegation
NSo.mx-ns.mx ⚠️ Not in parent delegation
NSx.mx-ns.mx ⚠️ Not in parent delegation
TXTv=spf1 -all
SOAm.mx-ns.mxhostmaster@nic.mx serial=1781952593
WOT: NOT_SAFE (44/100)

Same first word

Similar names

DNS History

13 records (6 active, 7 former)

20162017201820192020202120222023202420252026NSns1.markmonitor.comns2.markmonitor.comns3.markmonitor.comns4.markmonitor.comns5.markmonitor.comns1.netnames.netns2.netnames.netns5.netnames.netns6.netnames.netMXrelay1.netnames.netrelay2.netnames.netA99.83.176.46185.26.230.129
●NSns1.markmonitor.com2026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04
β—‹NSns1.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
●NSns2.markmonitor.com2026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04
β—‹NSns2.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
●NSns3.markmonitor.com2026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04
●NSns4.markmonitor.com2026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04
●NSns5.markmonitor.com2026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04
β—‹NSns5.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
β—‹NSns6.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
β—‹MXrelay1.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
β—‹MXrelay2.netnames.net2015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
β—‹A185.26.230.1292015-06-20 β†’ 2016-04-16 Β· 4 obs
● 2015-06-20 14:12:02
● 2016-04-16 22:13:00
β—‹ 2026-03-28 13:06:22
β—‹ 2026-06-20 10:56:04
●A99.83.176.462026-03-28 β†’ 2026-06-20 Β· 3 obs
β—‹ 2016-04-16 22:13:00
● 2026-03-28 13:06:22
● 2026-06-20 10:56:04

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
mxc.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx...-
isolaz.com.mxns5.markmonitor.com, ns3.markmonitor.com, ns2.markmonitor.com, ns1.markmonitor.com...-

βœ… Authoritative Response

Server:192.174.68.1

NS records: ns5.markmonitor.com, ns3.markmonitor.com, ns2.markmonitor.com, ns1.markmonitor.com, ns4.markmonitor.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 455ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A199.83.176.46
NS2ns1.markmonitor.com, ns3.markmonitor.com
SOA1ns1.markmonitor.com hostmaster.markmonit

Analysis

IP Addresses

isolaz.com.mx resolves to one IP address: 99.83.176.46.

flupertine.org, telegraphpanel.uk, quickbooks.fans and two other host names share IP numbers with isolaz.com.mx.

Name Servers

isolaz.com.mx has five name servers, which are ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and two others.

isolaz.com.mx shares at least some of its name servers with other domains, including statefarmsbank.com, paypalselectcashback.com, amazonec2.com and two others.

These name servers are frequently seen alongside the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Hostnames that resolve to two IP addresses:

ns1.markmonitor.com maps to two IP addresses β€” 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com maps to two IP addresses β€” 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com maps to two IP addresses β€” 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com maps to two IP addresses β€” 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com maps to two IP addresses β€” 149.112.160.2 and 2620:10a:80a8::2.