problematic.mx - dns.ninja
problematic.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=1791500197 | ||||||
Same first word
Similar names
Previous names
Next names
probono.mx |
probosque.mx |
probounce.mx |
probro.mx |
probrokers.mx |
probscore.mx |
probst-handling.mx |
probus.mx |
probuscanin.mx |
probusinessapps.mx |
proc.mx |
procab.mx |
procables.mx |
procac.mx |
procad.mx |
procades.mx |
DNS History
8 records (8 active, 0 former)
●NSns37.domaincontrol.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●NSns38.domaincontrol.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●MXalt1.aspmx.l.google.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●MXalt2.aspmx.l.google.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●MXalt3.aspmx.l.google.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●MXalt4.aspmx.l.google.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●MXaspmx.l.google.com2026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
●A23.227.38.322026-08-30 → 2026-10-08 · 2 obs
● 2026-10-08 23:32:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | i.mx-ns.mx, x.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | 12 records |
| problematic.mx | ns37.domaincontrol.com, ns38.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.76.19
NS records: ns37.domaincontrol.com, ns38.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for problematic.mx (unsigned zone)
⏱️ Timing
Total: 561ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.32 |
| NS | 2 | ns37.domaincontrol.com, ns38.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | google-site-verification=9_VGsqOd39e6JRA, google-site-verification=tp09_OzIDM8YSp4... |
| SOA | 1 | ns37.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx...)
Analysis
IP Addresses
problematic.mx points to a single IP number: 23.227.38.32.
Additional host names — blueshellcollectibles.com, hardinfarms.com, lastwardrobesg.com and two others — share IP numbers with problematic.mx.
Name Servers
problematic.mx has two authoritative name servers — ns37.domaincontrol.com and ns38.domaincontrol.com.
problematic.mx shares its name server setup with other domains, including copiersdfw.com, drivefertitta.com, concretesinkingpro.com and two others.
Both ns37.domaincontrol.com and ns38.domaincontrol.com have two IP addresses each. ns37.domaincontrol.com resolves to 97.74.108.19 and 2603:5:21c1::13; ns38.domaincontrol.com resolves to 173.201.76.19 and 2603:5:22c1::13.
Mail Servers
Five mail servers handle problematic.mx: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
problematic.mx shares mail servers — at least in part — with other domains, including europemagicwand.dk, deepico.ch, clipsnip.co 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 resolves to 64.233.180.26 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.