response.mx - dns.ninja
response.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns09.gcd-dns.com ⭐ | ||||||
| A | 2603:5:21e2::36🇺🇸 GODADDY-DNS2603:5:21e0::/44 | ||||||
| PTR | pdns09.domaincontrol.com | ||||||
| A | 97.74.110.54🇺🇸 GODADDY-DNS97.74.110.0/23 | ||||||
| PTR | pdns09.domaincontrol.com | ||||||
| NS | ns10.gcd-dns.com | ||||||
| A | 2603:5:22e2::36🇺🇸 GODADDY-DNS2603:5:22e0::/44 | ||||||
| PTR | pdns10.domaincontrol.com | ||||||
| A | 173.201.78.54🇺🇸 GODADDY-DNS173.201.78.0/23 | ||||||
| PTR | pdns10.domaincontrol.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns09.gcd-dns.comdns@jomax.net 2023-11-01 #0 | ||||||
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=1780954132 | ||||||
Same first word
Similar names
DNS History
7 records (2 active, 5 former)
○NSdns1.cscdns.net2015-07-22 → 2017-04-18 · 4 obs
● 2015-07-22 08:48:02
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
○NSdns2.cscdns.net2015-07-22 → 2017-04-18 · 4 obs
● 2015-07-22 08:48:02
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
●NSns09.gcd-dns.com2026-03-05 → 2026-06-08 · 3 obs
○ 2017-04-18 21:08:08
● 2026-03-05 13:49:42
● 2026-06-08 22:00:04
● 2026-03-05 13:49:42
● 2026-06-08 22:00:04
●NSns10.gcd-dns.com2026-03-05 → 2026-06-08 · 3 obs
○ 2017-04-18 21:08:08
● 2026-03-05 13:49:42
● 2026-06-08 22:00:04
● 2026-03-05 13:49:42
● 2026-06-08 22:00:04
○MXcustmx.cscdns.net2015-07-22 → 2017-04-18 · 4 obs
● 2015-07-22 08:48:02
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
○A165.160.13.202015-07-22 → 2017-04-18 · 4 obs
● 2015-07-22 08:48:02
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
○A165.160.15.202015-07-22 → 2017-04-18 · 4 obs
● 2015-07-22 08:48:02
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
● 2017-04-18 21:08:08
○ 2026-03-05 13:49:42
○ 2026-06-08 22:00:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx... | - |
| response.mx | ns09.gcd-dns.com, ns10.gcd-dns.com | - |
✅ Authoritative Response
Server:97.74.110.54
NS records: ns09.gcd-dns.com, ns10.gcd-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for response.mx (unsigned zone)
⏱️ Timing
Total: 555ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns09.gcd-dns.com, ns10.gcd-dns.com |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns09.gcd-dns.com dns.jomax.net |
Analysis
Name Servers
DNS delegation for response.mx points to two name servers: ns09.gcd-dns.com and ns10.gcd-dns.com.
response.mx uses the same name servers as several other domains — among them tmz.com.mx, foxteens.org, rumsn.net and two more.
ns09.gcd-dns.com directs to 97.74.110.54 and 2603:5:21e2::36. ns10.gcd-dns.com directs to 173.201.78.54 and 2603:5:22e2::36. Each host name carries two IP addresses.