bodyspace.com.mx - dns.ninja

bodyspace.com.mx

DNSSEC⚠️ Not signed
A3.33.139.32πŸ‡ΊπŸ‡Έ Amazon3.33.128.0/20
PTRaeedc42b70c898c66.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
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
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
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 2016-03-07 #3

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=1782300173
WOT: NOT_SAFE (44/100)

Same first word

Similar names

DNS History

14 records (6 active, 8 former)

20162017201820192020202120222023202420252026NSns1.markmonitor.comns2.markmonitor.comns3.markmonitor.comns4.markmonitor.comns5.markmonitor.comns1.netnames.netns2.netnames.netns5.netnames.netns6.netnames.netMXrelay1.netnames.netrelay2.netnames.netA3.33.139.32185.26.230.12972.52.10.14
●NSns1.markmonitor.com2016-07-26 β†’ 2026-06-24 Β· 3 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2026-06-24 11:33:14
β—‹NSns1.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
●NSns2.markmonitor.com2016-07-26 β†’ 2026-06-24 Β· 3 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2026-06-24 11:33:14
β—‹NSns2.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
●NSns3.markmonitor.com2016-07-26 β†’ 2026-06-24 Β· 3 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2026-06-24 11:33:14
●NSns4.markmonitor.com2016-07-26 β†’ 2026-06-24 Β· 3 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2026-06-24 11:33:14
●NSns5.markmonitor.com2016-07-26 β†’ 2026-06-24 Β· 3 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2026-06-24 11:33:14
β—‹NSns5.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
β—‹NSns6.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
β—‹MXrelay1.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
β—‹MXrelay2.netnames.net2015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
β—‹A185.26.230.1292015-08-12 β†’ 2016-03-13 Β· 4 obs
● 2015-08-12 00:07:32
● 2016-03-13 15:54:50
β—‹ 2016-07-26 05:00:22
β—‹ 2026-06-24 11:33:14
●A3.33.139.322026-03-29 β†’ 2026-06-24 Β· 3 obs
β—‹ 2020-03-26 16:46:24
● 2026-03-29 02:15:04
● 2026-06-24 11:33:14
β—‹A72.52.10.142016-07-26 β†’ 2020-03-26 Β· 5 obs
β—‹ 2016-03-13 15:54:50
● 2016-07-26 05:00:22
● 2020-03-26 16:46:24
β—‹ 2026-03-29 02:15:04
β—‹ 2026-06-24 11:33:14

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
mxc.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...-
bodyspace.com.mxns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com...-

βœ… Authoritative Response

Server:149.112.160.2

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 678ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A13.33.139.32
NS5ns1.markmonitor.com, ns2.markmonitor.com...
SOA1ns1.markmonitor.com hostmaster.markmonit

Analysis

IP Addresses

bodyspace.com.mx resolves to just one IP address, 3.33.139.32.

Two other host names, along with fingerman.com, mofa.de and americanhealth.us, also share IP numbers with bodyspace.com.mx.

Name Servers

bodyspace.com.mx delegates to five name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and two others.

The name servers of bodyspace.com.mx overlap at least partially with those of other domains β€” among them altinvest.com, lubrizol.jobs, spiritofservice365.com and two more.

These name servers commonly co-occur with the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Host names that have two IP addresses:

ns1.markmonitor.com directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.