eemsa.com.mx - dns.ninja
eemsa.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=1782699711 | ||||||
Same first word
Similar names
DNS History
13 records (11 active, 2 former)
โNSfelipe.ns.cloudflare.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โNSirma.ns.cloudflare.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โMXalt1.aspmx.l.google.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โMXalt2.aspmx.l.google.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โMXalt3.aspmx.l.google.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โMXalt4.aspmx.l.google.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โMXaspmx.l.google.com2026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โA104.21.35.2142026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โA172.67.179.2292026-06-09 โ 2026-06-29 ยท 2 obs
โ 2026-06-29 02:38:32
โA2606:4700:3031::6815:23d62026-06-29 โ 2026-06-29 ยท 3 obs
โ 2026-06-29 02:38:26
โ 2026-06-29 02:38:32
โA2606:4700:3033::6815:23d62026-06-09 โ 2026-06-09 ยท 3 obs
โ 2026-06-29 02:38:26
โ 2026-06-29 02:38:32
โA2606:4700:3035::ac43:b3e52026-06-29 โ 2026-06-29 ยท 3 obs
โ 2026-06-29 02:38:26
โ 2026-06-29 02:38:32
โA2606:4700:3037::ac43:b3e52026-06-09 โ 2026-06-09 ยท 3 obs
โ 2026-06-29 02:38:26
โ 2026-06-29 02:38:32
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | - |
| eemsa.com.mx | irma.ns.cloudflare.com, felipe.ns.cloudflare.com | - |
โ Authoritative Response
Server:172.64.35.116
NS records: irma.ns.cloudflare.com, felipe.ns.cloudflare.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for eemsa.com.mx (unsigned zone)
โฑ๏ธ Timing
Total: 796ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.35.214, 172.67.179.229 |
| AAAA | 2 | 2606:4700:3035::ac43:b3e5, 2606:4700:3031::6815:23d6 |
| NS | 2 | felipe.ns.cloudflare.com, irma.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=b5PiW3tSXBqn54u, v=spf1 include:dc-aa8e722993._spfm.eemsa |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | felipe.ns.cloudflare.com dns.cloudflare. |
Analysis
IP Addresses
eemsa.com.mx directs to four IP numbers, which are 104.21.35.214, 172.67.179.229, 2606:4700:3031::6815:23d6 and 2606:4700:3035::ac43:b3e5.
Among the host names that share IP numbers with eemsa.com.mx are cafeinbet.net, northstudio.com, jira.commsult.de and two others.
Name Servers
Two name servers handle the delegation for eemsa.com.mx: felipe.ns.cloudflare.com and irma.ns.cloudflare.com.
eemsa.com.mx has the same name server delegation as a number of other domains, such as tlchealthcare.com.au, patagalana.com, tlcsunlight.com.au and two more.
There is at least partial name server overlap between eemsa.com.mx and other domains โ webalias.com, henrybelk.com, miiwin11.com and two more among them.
These name servers tend to appear in combination with the name servers gloria.ns.cloudflare.com, nitin.ns.cloudflare.com, carlane.ns.cloudflare.com and carioca.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
felipe.ns.cloudflare.com resolves to 108.162.195.116, 162.159.44.116 and 172.64.35.116 among others, with 3 other IP addresses in total.
irma.ns.cloudflare.com resolves to 108.162.192.166, 172.64.32.166 and 173.245.58.166 among others, with 3 other IP addresses in total.
Mail Servers
Five mail servers handle eemsa.com.mx: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
eemsa.com.mx shares at least some of its mail servers with other domains โ for example ns500724.ns500737.ns500599.ns500724.ns500599.ns500737.ns500737.ns500737.ns500599.ns500583.ns500697.ns500697.ns500682.ns500669.www.yummyflingsfinder.com, ns500754.ns500731.ns500742.ns500731.ns500731.ns500731.ns500671.ns500704.ns500291.ns500291.ns500649.ns500142.lusty(0x736c7574)z.com, ns500698.ns500758.ns500698.ns500758.ns500698.ns500735.ns500698.ns500698.ns500698.ns500698.ns500736.ns500576.ns500708.ns500698.ns500652.ns500619.ns500619.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to two addresses: 142.250.31.27 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.