odm.com.mx checked at 2025-01-01T20:06:27.288Z 245ms 76/77/77 99% R:16
DNSTREE.COM - odm.com.mx
Search for IP or hostnames
odm.com.mx
MX | aspmx.l.google.com | ||||||
A | 2a00:1450:400c:c0c::1b 🇧🇪 Google | ||||||
PTR | wr-in-f27.1e100.net | ||||||
PTR | wr-in-x1b.1e100.net | ||||||
A | 64.233.184.26🇺🇸 Google | ||||||
PTR | wa-in-f26.1e100.net | ||||||
MX | alt1.aspmx.l.google.com | ||||||
A | 2a00:1450:4013:c16::1b 🇳🇱 Google | ||||||
PTR | ea-in-f27.1e100.net | ||||||
A | 142.250.153.26🇺🇸 Google | ||||||
PTR | ea-in-f26.1e100.net | ||||||
MX | alt2.aspmx.l.google.com | ||||||
A | 2a00:1450:4025:c03::1b 🇵🇱 Google | ||||||
PTR | rc-in-f27.1e100.net | ||||||
A | 142.251.9.27🇺🇸 Google | ||||||
PTR | rc-in-f27.1e100.net | ||||||
MX | alt3.aspmx.l.google.com | ||||||
A | 2a00:1450:4010:c1c::1a 🇫🇮 Google | ||||||
PTR | la-in-f26.1e100.net | ||||||
A | 142.250.150.26🇺🇸 Google | ||||||
PTR | la-in-f26.1e100.net | ||||||
MX | alt4.aspmx.l.google.com | ||||||
A | 2404:6800:4003:c00::1b 🇸🇬 Google | ||||||
PTR | sa-in-f27.1e100.net | ||||||
PTR | sa-in-x1b.1e100.net | ||||||
A | 74.125.200.26🇺🇸 Google | ||||||
PTR | sa-in-f26.1e100.net |
com.mx
NS | c.mx-ns.mx | ||||||
NS | e.mx-ns.mx | ||||||
NS | i.mx-ns.mx | ||||||
NS | m.mx-ns.mx | ||||||
NS | o.mx-ns.mx | ||||||
NS | x.mx-ns.mx |
AI analysis
Host names zeus.odm.com.mx, ares.odm.com.mx, webmail.odm.com.mx, odmsercorreo2.odm.com.mx, singapur.odm.com.mx and a few others, all have odm.com.mx as their parent.
Five mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, manage odm.com.mx.
Just like domains ns500759.ns500735.ns500736.ns500698.ns500698.ns500708.ns500576.ns500619.ns500652.ns500576.trackreceptor.com, ns500758.ns500758.ns500758.ns500758.ns500759.ns500735.ns500736.ns500698.ns500708.ns500576.ns500698.ns500576.ns500698.ns500698.ns500576.ns500619.ns500619.trackreceptor.com, ns500734.ns500699.ns500699.ns500693.ns500699.ns500693.ns500693.ns500693.ns500699.ns500588.ns500588.ns500699.ns500588.ns500683.ns500588.ns500699.ns500602.dtrkdll.com, ns500698.ns500758.ns500758.ns500759.ns500758.ns500736.ns500698.ns500698.ns500698.ns500708.ns500698.ns500698.ns500708.ns500619.ns500698.ns500619.tracksymphony.com, and ns500759.ns500698.ns500698.ns500698.ns500735.ns500698.ns500698.ns500736.ns500708.ns500708.ns500576.ns500698.ns500576.ns500652.ns500652.ns500619.trackreceptor.com, odm.com.mx also has the same mail server setup.
Some mail servers are at least partially shared between odm.com.mx and other domains, such as thomasforbesjohnson.com.
aspmx.l.google.com, 2a00:1450:400c:c0c::1b, and 64.233.184.26 are associated with each other.
alt1.aspmx.l.google.com, 2a00:1450:4013:c16::1b, and 142.250.153.26 are linked together.
alt2.aspmx.l.google.com, 2a00:1450:4025:c03::1b, and 142.251.9.27 are connected.
alt3.aspmx.l.google.com, 2a00:1450:4010:c1c::1a, and 142.250.150.26 are related.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1b, and 74.125.200.26 are all interlinked.