firext.com.mx - robtex.com
firext.com.mx
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.mxhostmaster@nic.mx serial=1781683312 | ||||||
Same first word
Similar names
DNS History
8 records (8 active, 0 former)
●NSns1-sukra.hosting-mexico.net2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●NSns2-sukra.hosting-mexico.net2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●MXalt1.aspmx.l.google.com2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●MXalt2.aspmx.l.google.com2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●MXaspmx.l.google.com2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●MXaspmx2.googlemail.com2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●MXaspmx3.googlemail.com2026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
●A68.70.164.132026-06-10 → 2026-06-17 · 2 obs
● 2026-06-17 08:37:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| firext.com.mx | ns1-sukra.hosting-mexico.net, ns2-sukra.hosting-mexico.net | - |
✅ Authoritative Response
Server:68.70.164.14
NS records: ns1-sukra.hosting-mexico.net, ns2-sukra.hosting-mexico.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for firext.com.mx (unsigned zone)
⏱️ Timing
Total: 413ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 68.70.164.13 |
| NS | 2 | ns1-sukra.hosting-mexico.net, ns2-sukra.hosting-mexico.net |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | ns1-sukra.hosting-mexico.net notificatio |
Analysis
IP Addresses
firext.com.mx resolves to one IP address: 68.70.164.13.
mailsavapartner.com.mx, cpcontacts.innovamed.com.mx, jwals.net and two other host names share IP numbers with firext.com.mx.
Name Servers
firext.com.mx uses two name servers for its delegation: ns1-sukra.hosting-mexico.net and ns2-sukra.hosting-mexico.net.
firext.com.mx uses the same name servers as several other domains — among them grupokosmossecurity.com.mx, insys.com.mx, maspharma.mx and two more.
At least some of firext.com.mx's name servers are also used by other domains, among them suma.gob.mx.
ns1-sukra.hosting-mexico.net directs to 68.70.164.13 and ns2-sukra.hosting-mexico.net directs to 68.70.164.14; each host name points to exactly one IP number.
Mail Servers
Mail for firext.com.mx is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
firext.com.mx has at least partial mail server overlap with other domains such as tc4b.net, yazzihands.com, ns500821.ns500794.ns500841.ns500795.ns500794.ns500794.ns500794.ns500821.ns500790.ns500795.lustypartnersfinder.com and two more.
These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 192.178.155.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.