defensa.com.mx - dns.ninja
defensa.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| A | 134.122.125.97🇺🇸 DIGITALOCEAN134.122.112.0/20 DigitalOcean | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| SOA | ns1.digitalocean.comhostmaster@defensa.com.mx serial=0 | ||||||
com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | m.mx-ns.mx ⭐ ⚠️ Not in parent delegation | ||||||
| NS | c.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | e.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | i.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | o.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | x.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1781658654 | ||||||
Same first word
Similar names
DNS History
9 records (4 active, 5 former)
○NSdns1.triara.com2015-07-10 → 2017-01-02 · 4 obs
● 2017-01-02 18:33:58
○ 2017-12-25 05:55:04
○ 2026-06-17 01:13:24
○NSdns2.triara.com2015-07-10 → 2017-01-02 · 4 obs
● 2017-01-02 18:33:58
○ 2017-12-25 05:55:04
○ 2026-06-17 01:13:24
○NSdns3.triara.com2015-07-10 → 2017-01-02 · 4 obs
● 2017-01-02 18:33:58
○ 2017-12-25 05:55:04
○ 2026-06-17 01:13:24
●NSns1.digitalocean.com2026-02-18 → 2026-06-17 · 3 obs
● 2026-02-18 03:37:38
● 2026-06-17 01:13:24
●NSns2.digitalocean.com2026-02-18 → 2026-06-17 · 3 obs
● 2026-02-18 03:37:38
● 2026-06-17 01:13:24
●NSns3.digitalocean.com2026-02-18 → 2026-06-17 · 3 obs
● 2026-02-18 03:37:38
● 2026-06-17 01:13:24
○MXsmtp.mail1.triara.com2015-07-10 → 2017-01-02 · 4 obs
● 2017-01-02 18:33:58
○ 2017-12-25 05:55:04
○ 2026-06-17 01:13:24
●A134.122.125.972026-02-18 → 2026-06-17 · 3 obs
● 2026-02-18 03:37:38
● 2026-06-17 01:13:24
○A200.57.128.472015-07-10 → 2017-01-02 · 4 obs
● 2017-01-02 18:33:58
○ 2017-12-25 05:55:04
○ 2026-06-17 01:13:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | e.mx-ns.mx, i.mx-ns.mx, x.mx-ns.mx, o.mx-ns.mx... | - |
| defensa.com.mx | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for defensa.com.mx (unsigned zone)
⏱️ Timing
Total: 433ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 134.122.125.97 |
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.defensa. |
Analysis
IP Addresses
defensa.com.mx has exactly one IP address — 134.122.125.97.
smartadvancedrobotics.com, intellinergy.com, vertexvue.com plus two other host names have IP numbers in common with defensa.com.mx.
Name Servers
The authoritative name servers for defensa.com.mx are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
At least some of defensa.com.mx's name servers are shared with other domains, for example haychange.com, websa100.com, atlantis.escael.org and two more.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.