freiman.com.mx - robtex.com
freiman.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=1785430050 | ||||||
Same first word
freiman.com.br |
freiman.us |
freiman.com.mx |
freiman.info |
freiman.com |
freiman.ru |
freiman.de |
freiman.eu |
freiman.co.il |
Similar names
DNS History
8 records (8 active, 0 former)
●NSns53.domaincontrol.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●NSns54.domaincontrol.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●MXalt1.aspmx.l.google.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●MXalt2.aspmx.l.google.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●MXaspmx.l.google.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●MXaspmx2.googlemail.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●MXaspmx3.googlemail.com2026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01:18
●A198.202.211.12026-06-10 → 2026-07-30 · 2 obs
● 2026-07-30 17:01: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... | - |
| freiman.com.mx | ns53.domaincontrol.com, ns54.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.74.27
NS records: ns53.domaincontrol.com, ns54.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for freiman.com.mx (unsigned zone)
⏱️ Timing
Total: 450ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.202.211.1 |
| NS | 2 | ns53.domaincontrol.com, ns54.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | v=spf1 include:_spf.google.com ~all, google-site-verification=8DMKWnbcP8qVwjt... |
| SOA | 1 | ns53.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
freiman.com.mx resolves to one IP address: 198.202.211.1.
foodliner.de, ase.tech, pixelmachine.com.ar and two other host names share IP numbers with freiman.com.mx.
Name Servers
freiman.com.mx uses two name servers for its delegation: ns53.domaincontrol.com and ns54.domaincontrol.com.
freiman.com.mx uses the same name servers as several other domains — among them pceonline.org, latechengineering.com, thewaterdamageteam.com and two more.
The two host names ns53.domaincontrol.com and ns54.domaincontrol.com each have a pair of IP addresses: ns53.domaincontrol.com has 97.74.106.27 and 2603:5:21a2::1b, and ns54.domaincontrol.com has 173.201.74.27 and 2603:5:22a2::1b.
Mail Servers
Five mail servers handle freiman.com.mx: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
freiman.com.mx has at least partial mail server overlap with other domains such as allnetit.com, ns500671.ns500671.ns500742.ns500742.ns500742.ns500704.ns500705.ns500688.ns500649.ns500671.ns500666.tenderladiesbz.com, ns500698.ns500759.ns500759.ns500759.ns500735.ns500735.ns500698.ns500698.ns500576.ns500698.ns500576.ns500686.ns500619.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.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.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.63.26 and 2607:f8b0:4004:c17::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::1a.
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::1a IP addresses each.