infospace.com.mx - dns.ninja
infospace.com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.digitalocean.com ⚠️ Not in zone NS records | ||||||
| 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 ⚠️ Not in zone NS records | ||||||
| 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 | ||||||
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=1786470157 | ||||||
Same first word
Similar names
DNS History
11 records (2 active, 9 former)
●NSns1.digitalocean.com2026-02-19 → 2026-08-11 · 3 obs
● 2026-02-19 08:37:02
● 2026-08-11 18:03:32
○NSns1.pagina.mx2015-08-11 → 2017-08-23 · 4 obs
● 2017-08-23 16:25:54
○ 2026-02-19 08:37:02
○ 2026-08-11 18:03:32
●NSns2.digitalocean.com2026-02-19 → 2026-08-11 · 3 obs
● 2026-02-19 08:37:02
● 2026-08-11 18:03:32
○NSns2.pagina.mx2015-08-11 → 2017-08-23 · 4 obs
● 2017-08-23 16:25:54
○ 2026-02-19 08:37:02
○ 2026-08-11 18:03:32
○NSns3.digitalocean.com2026-02-19 → 2026-05-12 · 5 obs
● 2026-02-19 08:37:02
● 2026-05-12 18:26:08
○ 2026-06-07 00:45:44
○ 2026-08-11 18:03:32
○MXmail.pagina.mx2015-08-11 → 2017-08-23 · 4 obs
● 2017-08-23 16:25:54
○ 2026-02-19 08:37:02
○ 2026-08-11 18:03:32
○A108.178.44.2022016-08-11 → 2016-08-11 · 4 obs
● 2016-08-11 23:36:02
○ 2016-11-26 21:02:58
○ 2026-08-11 18:03:32
○A144.217.65.1492016-11-26 → 2017-08-23 · 5 obs
● 2016-11-26 21:02:58
● 2017-08-23 16:25:54
○ 2026-02-19 08:37:02
○ 2026-08-11 18:03:32
○A207.182.141.302016-05-12 → 2016-07-14 · 5 obs
● 2016-05-12 15:41:10
● 2016-07-14 01:42:16
○ 2016-08-11 23:36:02
○ 2026-08-11 18:03:32
○A207.182.141.932015-08-11 → 2016-02-25 · 4 obs
● 2016-02-25 18:45:20
○ 2016-05-12 15:41:10
○ 2026-08-11 18:03:32
○A64.227.102.1072026-02-19 → 2026-05-12 · 5 obs
● 2026-02-19 08:37:02
● 2026-05-12 18:26:08
○ 2026-06-07 00:45:44
○ 2026-08-11 18:03:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | m.mx-ns.mx, o.mx-ns.mx, c.mx-ns.mx, i.mx-ns.mx... | - |
| infospace.com.mx | ns1.digitalocean.com, ns2.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.53.21
NS records: ns1.digitalocean.com, ns2.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for infospace.com.mx (unsigned zone)
⏱️ Timing
Total: 358ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The NS records for infospace.com.mx delegate to ns1.digitalocean.com and ns2.digitalocean.com.
infospace.com.mx shares its NS records with other domains, for example soldbae.com, banil.com.np, hospnet.us and two others.
There is at least partial name server overlap between infospace.com.mx and other domains — 1.0.0.d.c.5.3.2.0.0.0.0.0.0.0.0.0.d.0.0.2.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa, 1.0.0.9.d.1.c.0.0.0.0.0.0.0.0.0.0.d.0.0.d.a.c.0.0.8.8.a.4.0.6.2.ip6.arpa, 1.0.0.5.2.3.b.0.0.0.0.0.0.0.0.0.0.d.0.0.d.a.c.0.0.8.8.a.4.0.6.2.ip6.arpa and two more among them.
These name servers are routinely deployed together with the name servers ns3.digitalocean.com.
ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2. Likewise, ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515 — two IP addresses apiece.