bitcode.com.mx - robtex.com

bitcode.com.mx

DNSSEC⚠️ Not signed
A65.99.248.153πŸ‡ΊπŸ‡Έ TierPoint65.99.192.0/18 LLC
PTRsvgel70.cloud-mx-ns.net
NSns401.controldns.mx ⭐
A174.136.53.245πŸ‡ΊπŸ‡Έ TierPoint174.136.0.0/18 LLC
PTRns401.controldns.mx
NSns402.controldns.mx
A65.99.248.132πŸ‡ΊπŸ‡Έ TierPoint65.99.192.0/18 LLC
PTRns402.controldns.mx
NSns403.controldns.mx
A72.249.55.3πŸ‡ΊπŸ‡Έ TierPoint72.249.48.0/20 LLC
PTRns403.controldns.mx
MXbitcode.com.mx ⭐
A65.99.248.153πŸ‡ΊπŸ‡Έ TierPoint65.99.192.0/18 LLC
PTRsvgel70.cloud-mx-ns.net
TXTv=spf1 +a +mx +ip4:65.99.248.153 include:spf.antispamcloud.com +include:relay...
SOAns401.controldns.mxroot@svgel140.cloud-mx-ns.net 2026-05-08 #1

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

MX for

Same first word

Similar names

DNS History

17 records (5 active, 12 former)

20162017201820192020202120222023202420252026NSns401.controldns.mxns402.controldns.mxns403.controldns.mxns2227.el.controladordns.comns2228.el.controladordns.comns35.domaincontrol.comns36.domaincontrol.comMXbitcode.com.mxalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA65.99.248.15350.62.108.150.63.202.7767.225.220.158
β—‹NSns2227.el.controladordns.com2017-04-04 β†’ 2017-04-04 Β· 4 obs
β—‹ 2016-09-14 03:05:02
● 2017-04-04 08:27:48
β—‹ 2026-02-23 12:43:26
β—‹ 2026-05-09 20:09:04
β—‹NSns2228.el.controladordns.com2017-04-04 β†’ 2017-04-04 Β· 4 obs
β—‹ 2016-09-14 03:05:02
● 2017-04-04 08:27:48
β—‹ 2026-02-23 12:43:26
β—‹ 2026-05-09 20:09:04
β—‹NSns35.domaincontrol.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
β—‹NSns36.domaincontrol.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
●NSns401.controldns.mx2026-02-23 β†’ 2026-05-09 Β· 3 obs
β—‹ 2017-04-04 08:27:48
● 2026-02-23 12:43:26
● 2026-05-09 20:09:04
●NSns402.controldns.mx2026-02-23 β†’ 2026-05-09 Β· 3 obs
β—‹ 2017-04-04 08:27:48
● 2026-02-23 12:43:26
● 2026-05-09 20:09:04
●NSns403.controldns.mx2026-02-23 β†’ 2026-05-09 Β· 3 obs
β—‹ 2017-04-04 08:27:48
● 2026-02-23 12:43:26
● 2026-05-09 20:09:04
β—‹MXalt1.aspmx.l.google.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
β—‹MXalt2.aspmx.l.google.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
β—‹MXaspmx.l.google.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
β—‹MXaspmx2.googlemail.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
β—‹MXaspmx3.googlemail.com2015-06-07 β†’ 2016-09-14 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
●MXbitcode.com.mx2017-04-04 β†’ 2026-05-09 Β· 3 obs
β—‹ 2016-09-14 03:05:02
● 2017-04-04 08:27:48
● 2026-05-09 20:09:04
β—‹A50.62.108.12015-06-07 β†’ 2016-04-07 Β· 4 obs
● 2015-06-07 21:28:22
● 2016-04-07 11:35:04
β—‹ 2016-09-14 03:05:02
β—‹ 2026-05-09 20:09:04
β—‹A50.63.202.772016-09-14 β†’ 2016-09-14 Β· 4 obs
β—‹ 2016-04-07 11:35:04
● 2016-09-14 03:05:02
β—‹ 2017-04-04 08:27:48
β—‹ 2026-05-09 20:09:04
●A65.99.248.1532026-02-23 β†’ 2026-05-09 Β· 3 obs
β—‹ 2017-04-04 08:27:48
● 2026-02-23 12:43:26
● 2026-05-09 20:09:04
β—‹A67.225.220.1582017-04-04 β†’ 2017-04-04 Β· 4 obs
β—‹ 2016-09-14 03:05:02
● 2017-04-04 08:27:48
β—‹ 2026-02-23 12:43:26
β—‹ 2026-05-09 20:09:04

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
mxc.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...-
bitcode.com.mxns401.controldns.mx, ns402.controldns.mx, ns403.controldns.mx-

βœ… Authoritative Response

Server:65.99.248.132

NS records: ns401.controldns.mx, ns402.controldns.mx, ns403.controldns.mx

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 477ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A165.99.248.153
NS3ns403.controldns.mx, ns401.controldns.mx...
MX1bitcode.com.mx (pri: 0)
TXT1v=spf1 +a +mx +ip4:65.99.248.153 include
SOA1ns401.controldns.mx root.svgel140.cloud-

Analysis

Mail Server Role

The mail server for bitcode.com.mx is bitcode.com.mx.

IP Addresses

bitcode.com.mx points to a single IP address: 65.99.248.153.

Other host names such as pucsa.com, mrdoc.com.mx, mabytov.net, grupoimex.com and encadena.tv share IPs with bitcode.com.mx.

Name Servers

bitcode.com.mx is delegated to three name servers: ns401.controldns.mx, ns402.controldns.mx and ns403.controldns.mx.

bitcode.com.mx at least partially shares name servers with other domains, for example publiadvisor.com, vallasmoviles.mx, notaria28.com.mx, grupoitcom.net and avanzasoluciones.com.mx.

Host names with a single IP address:

ns401.controldns.mx resolves to 174.136.53.245.

ns402.controldns.mx resolves to 65.99.248.132.

ns403.controldns.mx resolves to 72.249.55.3.

Mail Servers

One mail server handles bitcode.com.mx; that server is bitcode.com.mx.

bitcode.com.mx points to a single IP number: 65.99.248.153.