askmen.mx - dns.ninja
askmen.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=1786530276 | ||||||
Same first word
Similar names
DNS History
18 records (9 active, 9 former)
●NSns-1014.awsdns-62.net2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
●NSns-1330.awsdns-38.org2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
●NSns-1711.awsdns-21.co.uk2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
●NSns-430.awsdns-53.com2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
○NSns-cloud-b1.googledomains.com2026-02-20 → 2026-05-28 · 5 obs
● 2026-02-20 11:19:12
● 2026-05-28 05:33:56
○ 2026-06-10 17:23:28
○ 2026-08-12 11:21:38
○NSns-cloud-b2.googledomains.com2026-02-20 → 2026-05-28 · 5 obs
● 2026-02-20 11:19:12
● 2026-05-28 05:33:56
○ 2026-06-10 17:23:28
○ 2026-08-12 11:21:38
○NSns-cloud-b3.googledomains.com2026-02-20 → 2026-05-28 · 5 obs
● 2026-02-20 11:19:12
● 2026-05-28 05:33:56
○ 2026-06-10 17:23:28
○ 2026-08-12 11:21:38
○NSns-cloud-b4.googledomains.com2026-02-20 → 2026-05-28 · 5 obs
● 2026-02-20 11:19:12
● 2026-05-28 05:33:56
○ 2026-06-10 17:23:28
○ 2026-08-12 11:21:38
○NSns1.eurodns.com2015-07-14 → 2018-08-21 · 4 obs
● 2018-08-21 21:32:24
○ 2026-02-20 11:19:12
○ 2026-08-12 11:21:38
●NSns1.zd-dns.com2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
○NSns2.eurodns.com2015-07-14 → 2018-08-21 · 4 obs
● 2018-08-21 21:32:24
○ 2026-02-20 11:19:12
○ 2026-08-12 11:21:38
●NSns2.zd-dns.com2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
○NSns3.eurodns.com2015-07-14 → 2018-08-21 · 4 obs
● 2018-08-21 21:32:24
○ 2026-02-20 11:19:12
○ 2026-08-12 11:21:38
●NSns3.zd-dns.com2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
○NSns4.eurodns.com2015-07-14 → 2018-08-21 · 4 obs
● 2018-08-21 21:32:24
○ 2026-02-20 11:19:12
○ 2026-08-12 11:21:38
●NSns4.zd-dns.com2026-06-10 → 2026-08-12 · 3 obs
● 2026-06-10 17:23:28
● 2026-08-12 11:21:38
●A165.160.15.202026-02-20 → 2026-08-12 · 3 obs
● 2026-02-20 11:19:12
● 2026-08-12 11:21:38
○A80.92.65.1442015-07-14 → 2018-08-21 · 4 obs
● 2018-08-21 21:32:24
○ 2026-02-20 11:19:12
○ 2026-08-12 11:21:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| askmen.mx | ns1.zd-dns.com, ns2.zd-dns.com, ns3.zd-dns.com, ns4.zd-dns.com | - |
✅ Authoritative Response
Server:205.251.198.175
NS records: ns1.zd-dns.com, ns2.zd-dns.com, ns3.zd-dns.com, ns4.zd-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for askmen.mx (unsigned zone)
⏱️ Timing
Total: 574ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 165.160.15.20 |
| NS | 4 | ns-1014.awsdns-62.net, ns-1330.awsdns-38.org... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns-1330.awsdns-38.org awsdns-hostmaster. |
Analysis
IP Addresses
askmen.mx has exactly one IP address — 165.160.15.20.
xn--tv-auto-partner-zvb.de, mydisneytoday.dev, spiralsoftware.co.uk plus two other host names have IP numbers in common with askmen.mx.
Name Servers
askmen.mx delegates authority to 8 name servers: ns-430.awsdns-53.com, ns1.zd-dns.com, ns2.zd-dns.com plus 5 other.
The name servers of askmen.mx overlap at least partially with those of other domains — among them box-256.com, puppy.gallery, isource.co and two more.
These name servers tend to appear together with the name servers ns-1014.awsdns-62.net, ns-1330.awsdns-38.org and ns-1711.awsdns-21.co.uk, plus two others.
Host names pointing to two IP addresses:
ns-430.awsdns-53.com directs traffic to 205.251.193.174 and 2600:9000:5301:ae00::1.
ns1.zd-dns.com directs traffic to 205.251.193.174 and 2600:9000:5301:ae00::1.
ns2.zd-dns.com directs traffic to 205.251.197.50 and 2600:9000:5305:3200::1.
ns3.zd-dns.com directs traffic to 205.251.195.246 and 2600:9000:5303:f600::1.
ns4.zd-dns.com directs traffic to 205.251.198.175 and 2600:9000:5306:af00::1.
ns-1014.awsdns-62.net directs traffic to 205.251.195.246 and 2600:9000:5303:f600::1.
ns-1330.awsdns-38.org directs traffic to 205.251.197.50 and 2600:9000:5305:3200::1.
ns-1711.awsdns-21.co.uk directs traffic to 205.251.198.175 and 2600:9000:5306:af00::1.
Both ns-430.awsdns-53.com and ns1.zd-dns.com resolve to 2600:9000:5301:ae00::1 IP addresses each.
Both ns-430.awsdns-53.com and ns1.zd-dns.com resolve to 205.251.193.174 IP addresses each.
Both ns2.zd-dns.com and ns-1330.awsdns-38.org resolve to 2600:9000:5305:3200::1 IP addresses each.
Both ns2.zd-dns.com and ns-1330.awsdns-38.org resolve to 205.251.197.50 IP addresses each.
Both ns3.zd-dns.com and ns-1014.awsdns-62.net resolve to 2600:9000:5303:f600::1 IP addresses each.
Both ns3.zd-dns.com and ns-1014.awsdns-62.net resolve to 205.251.195.246 IP addresses each.
Both ns4.zd-dns.com and ns-1711.awsdns-21.co.uk resolve to 2600:9000:5306:af00::1 IP addresses each.
Both ns4.zd-dns.com and ns-1711.awsdns-21.co.uk resolve to 205.251.198.175 IP addresses each.