dialo.mx - dns.ninja
dialo.mx
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1785747096 | ||||||
Same first word
dialo.de |
dialo.ch |
dialo.com.br |
dialo.net |
dialo.at |
dialo.mx |
dialo.chat |
dialo.org |
dialo.pl |
dialo.ga |
dialo.jp |
dialo.co |
dialo.com |
dialo.nl |
dialo.gg |
dialo.in |
Similar names
DNS History
10 records (10 active, 0 former)
●NSns35.domaincontrol.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●NSns36.domaincontrol.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●MXalt1.aspmx.l.google.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●MXalt2.aspmx.l.google.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●MXalt3.aspmx.l.google.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●MXalt4.aspmx.l.google.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●MXaspmx.l.google.com2026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●A3.167.112.1292026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●A3.167.112.702026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
●A3.167.112.952026-02-15 → 2026-08-03 · 2 obs
● 2026-08-03 09:01:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | i.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, c.mx-ns.mx... | - |
| dialo.mx | ns35.domaincontrol.com, ns36.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.75.18
NS records: ns35.domaincontrol.com, ns36.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dialo.mx (unsigned zone)
⏱️ Timing
Total: 481ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 3.167.112.70, 3.167.112.95... |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | amazonses:KCGtSNoFeC234FX9y0JENSda2++yTX, google-site-verification=uc1WWCXnlz-NWYc... |
| SOA | 1 | ns35.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
dialo.mx directs to three IP numbers: 3.167.112.70, 3.167.112.95 and 3.167.112.129.
Additional host names — doctorkrawitz.com, d12eggbk0mjncn.cloudfront.net, once.se and two others — share IP numbers with dialo.mx.
Name Servers
dialo.mx uses two name servers for its delegation: ns35.domaincontrol.com and ns36.domaincontrol.com.
dialo.mx shares its name server setup with other domains, including trojanheattreat.com, idealhost.co.uk, yerfdog.com and two others.
At least some of dialo.mx's name servers are also used by other domains, among them infilabs.com.
The two host names ns35.domaincontrol.com and ns36.domaincontrol.com each have a pair of IP addresses: ns35.domaincontrol.com has 97.74.107.18 and 2603:5:21b1::12, and ns36.domaincontrol.com has 173.201.75.18 and 2603:5:22b1::12.
Mail Servers
Five mail servers handle dialo.mx: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
dialo.mx shares mail servers — at least in part — with other domains, including happycar.es, ns500742.ns500731.ns500742.ns500731.ns500742.ns500742.ns500731.ns500731.ns500704.ns500705.ns500291.ns500671.ns500649.ns500666.ns500291.ns500131.lustychickser.com, ns500731.ns500731.ns500671.ns500731.ns500704.ns500742.ns500688.ns500671.ns500688.ns500671.ns500666.ns500666.ns500291.ns500131.lustychickser.com and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com directs traffic to 142.251.163.26 and 2607:f8b0:4004:c06::1a.
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.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.