welo.mx - dns.ninja
welo.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=1786223736 | ||||||
Same first word
welo.us |
welo.online |
welo.agency |
welo.be |
welo.ru |
welo.cn |
welo.group |
welo.world |
welo.fr |
welo.de |
welo.email |
welo.mx |
welo.health |
welo.kr |
welo.nl |
welo.co.in |
welo.at |
welo.ca |
welo.net |
welo.co |
welo.com |
welo.tv |
welo.cg |
welo.ch |
Similar names
DNS History
12 records (8 active, 4 former)
●NSns11.domaincontrol.com2026-04-07 → 2026-08-08 · 3 obs
● 2026-04-07 06:18:56
● 2026-08-08 21:17:22
●NSns12.domaincontrol.com2026-04-07 → 2026-08-08 · 3 obs
● 2026-04-07 06:18:56
● 2026-08-08 21:17:22
○NSns17.domaincontrol.com2019-12-27 → 2019-12-27 · 3 obs
○ 2026-04-07 06:18:56
○ 2026-08-08 21:17:22
○NSns18.domaincontrol.com2019-12-27 → 2019-12-27 · 3 obs
○ 2026-04-07 06:18:56
○ 2026-08-08 21:17:22
●MXalt1.aspmx.l.google.com2019-12-27 → 2026-08-08 · 2 obs
● 2026-08-08 21:17:22
●MXalt2.aspmx.l.google.com2019-12-27 → 2026-08-08 · 2 obs
● 2026-08-08 21:17:22
●MXaspmx.l.google.com2019-12-27 → 2026-08-08 · 2 obs
● 2026-08-08 21:17:22
●MXaspmx2.googlemail.com2019-12-27 → 2026-08-08 · 2 obs
● 2026-08-08 21:17:22
●MXaspmx3.googlemail.com2019-12-27 → 2026-08-08 · 2 obs
● 2026-08-08 21:17:22
●A13.88.24.862026-04-07 → 2026-08-08 · 3 obs
● 2026-04-07 06:18:56
● 2026-08-08 21:17:22
○A13.91.225.1512026-04-07 → 2026-08-08 · 2 obs
○ 2026-08-08 21:17:22
○A192.241.201.1412019-12-27 → 2019-12-27 · 3 obs
○ 2026-04-07 06:18:56
○ 2026-08-08 21:17:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, o.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| welo.mx | ns11.domaincontrol.com, ns12.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.73.6
NS records: ns11.domaincontrol.com, ns12.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for welo.mx (unsigned zone)
⏱️ Timing
Total: 375ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.88.24.86 |
| NS | 2 | ns11.domaincontrol.com, ns12.domaincontrol.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 3 | MS=525B93831B6919CEA0F3FBA3D1726E10B4C4F, v=spf1 include:_spf.google.com ~all... |
| SOA | 1 | ns11.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
welo.mx directs to one IP number, which is 13.88.24.86.
gonload.com, for instance, is one of the other host names sharing IP numbers with welo.mx.
Name Servers
welo.mx uses two name servers for its delegation: ns11.domaincontrol.com and ns12.domaincontrol.com.
welo.mx has the same name server delegation as a number of other domains, such as luralimousin.com, in-ctrl.com, rtooffice.in and two more.
The two host names ns11.domaincontrol.com and ns12.domaincontrol.com each have a pair of IP addresses: ns11.domaincontrol.com has 97.74.105.6 and 2603:5:2190::6, and ns12.domaincontrol.com has 173.201.73.6 and 2603:5:2290::6.
Mail Servers
Five mail servers handle welo.mx: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
welo.mx shares at least some of its mail servers with other domains — for example ns500759.ns500758.ns500698.ns500758.ns500698.ns500735.ns500698.ns500735.ns500735.ns500698.ns500708.ns500708.ns500576.ns500576.ns500652.ns500619.ns500576.trackreceptor.com, ns500734.ns500693.ns500693.ns500693.ns500734.ns500699.ns500734.ns500699.ns500699.ns500699.ns500699.ns500693.ns500588.ns500612.ns500588.ns500110.dtrkdll.com, ns500742.ns500754.ns500671.ns500742.ns500742.ns500671.ns500671.ns500742.ns500731.ns500705.ns500731.ns500671.ns500705.ns500678.ns500649.ns500291.ns500142.lusty(0x736c7574)z.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
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 192.178.155.26 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
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 108.177.123.26 IP addresses each.