capcom.cl - dns.ninja

capcom.cl

DNSSEC⚠️ Not signed
NSns1.capcom.cl ⚠️ Not in zone NS records
A66.225.201.115🇺🇸 SERVERCENTRAL66.225.192.0/18 Summit Hosting Network
PTRsingle-priva16.privatednsorg.com
NSns2.capcom.cl ⚠️ Not in zone NS records
A66.225.201.116🇺🇸 SERVERCENTRAL66.225.192.0/18 Summit Hosting Network
PTRsingle-priva16.privatednsorg.com

cl

DNSSEC⚠️ Not signed
NSa.nic.cl ⚠️ Not in zone NS records
NSb.nic.cl ⚠️ Not in zone NS records
NSc.nic.cl ⚠️ Not in zone NS records

Previously MX for

Subdomains

Same first word

Similar names

DNS History

15 records (2 active, 13 former)

20162017201820192020202120222023202420252026NSns1.capcom.clns2.capcom.clns21.benzahosting.clns21.benzahosting.netns22.benzahosting.clns22.benzahosting.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comcapcom.clA131.72.236.38190.196.10.8666.225.201.117
NSns1.capcom.cl2015-07-09 → 2026-07-13 · 5 obs
● 2015-07-09 06:31:46
● 2016-02-05 06:55:10
○ 2016-05-06 12:26:50
● 2026-03-02 00:07:30
● 2026-07-13 11:59:42
NSns2.capcom.cl2015-07-09 → 2026-07-13 · 5 obs
● 2015-07-09 06:31:46
● 2016-02-05 06:55:10
○ 2016-05-06 12:26:50
● 2026-03-02 00:07:30
● 2026-07-13 11:59:42
NSns21.benzahosting.cl2016-05-06 → 2016-05-06 · 4 obs
○ 2016-02-05 06:55:10
● 2016-05-06 12:26:50
○ 2026-03-02 00:07:30
○ 2026-07-13 11:59:42
NSns21.benzahosting.net2016-05-06 → 2016-05-06 · 4 obs
○ 2016-02-05 06:55:10
● 2016-05-06 12:26:50
○ 2026-03-02 00:07:30
○ 2026-07-13 11:59:42
NSns22.benzahosting.cl2016-05-06 → 2016-05-06 · 4 obs
○ 2016-02-05 06:55:10
● 2016-05-06 12:26:50
○ 2026-03-02 00:07:30
○ 2026-07-13 11:59:42
NSns22.benzahosting.net2016-05-06 → 2016-05-06 · 4 obs
○ 2016-02-05 06:55:10
● 2016-05-06 12:26:50
○ 2026-03-02 00:07:30
○ 2026-07-13 11:59:42
MXalt1.aspmx.l.google.com2015-07-09 → 2026-05-03 · 4 obs
● 2015-07-09 06:31:46
● 2026-05-03 11:39:38
○ 2026-05-09 02:46:02
○ 2026-07-13 11:59:42
MXalt2.aspmx.l.google.com2015-07-09 → 2026-05-03 · 4 obs
● 2015-07-09 06:31:46
● 2026-05-03 11:39:38
○ 2026-05-09 02:46:02
○ 2026-07-13 11:59:42
MXalt3.aspmx.l.google.com2015-07-09 → 2026-05-03 · 4 obs
● 2015-07-09 06:31:46
● 2026-05-03 11:39:38
○ 2026-05-09 02:46:02
○ 2026-07-13 11:59:42
MXalt4.aspmx.l.google.com2015-07-09 → 2026-05-03 · 4 obs
● 2015-07-09 06:31:46
● 2026-05-03 11:39:38
○ 2026-05-09 02:46:02
○ 2026-07-13 11:59:42
MXaspmx.l.google.com2026-03-02 → 2026-05-03 · 5 obs
○ 2015-07-09 06:31:46
● 2026-03-02 00:07:30
● 2026-05-03 11:39:38
○ 2026-05-09 02:46:02
○ 2026-07-13 11:59:42
MXcapcom.cl2026-05-09 → 2026-06-18 · 28 obs
○ 2026-05-03 11:39:38
● 2026-05-09 02:46:02
● 2026-06-04 13:27:18
○ 2026-06-06 15:33:32
● 2026-06-06 23:49:58
● 2026-06-08 14:17:08
○ 2026-06-08 16:39:36
● 2026-06-08 17:20:28
● 2026-06-08 17:57:56
○ 2026-06-08 18:36:58
○ 2026-06-08 23:37:02
● 2026-06-09 20:03:22
● 2026-06-11 03:45:00
○ 2026-06-11 04:59:52
○ 2026-06-11 06:47:32
● 2026-06-12 00:51:34
○ 2026-06-12 05:35:04
● 2026-06-13 00:09:56
● 2026-06-13 12:27:18
○ 2026-06-13 16:26:22
● 2026-06-13 21:39:50
○ 2026-06-13 22:38:40
● 2026-06-14 05:39:38
● 2026-06-15 08:02:56
○ 2026-06-15 09:31:30
● 2026-06-18 15:55:16
○ 2026-06-21 23:38:52
○ 2026-07-13 11:59:42
A131.72.236.382016-01-31 → 2016-05-06 · 5 obs
○ 2015-11-18 21:40:26
● 2016-01-31 14:32:00
● 2016-05-06 12:26:50
○ 2026-03-02 00:07:30
○ 2026-07-13 11:59:42
A190.196.10.862015-07-09 → 2015-11-18 · 4 obs
● 2015-07-09 06:31:46
● 2015-11-18 21:40:26
○ 2016-01-31 14:32:00
○ 2026-07-13 11:59:42
A66.225.201.1172026-03-02 → 2026-06-18 · 28 obs
○ 2016-05-06 12:26:50
● 2026-03-02 00:07:30
● 2026-06-04 13:27:18
○ 2026-06-06 15:33:32
● 2026-06-06 23:49:58
● 2026-06-08 14:17:08
○ 2026-06-08 16:39:36
● 2026-06-08 17:20:28
● 2026-06-08 17:57:56
○ 2026-06-08 18:36:58
○ 2026-06-08 23:37:02
● 2026-06-09 20:03:22
● 2026-06-11 03:45:00
○ 2026-06-11 04:59:52
○ 2026-06-11 06:47:32
● 2026-06-12 00:51:34
○ 2026-06-12 05:35:04
● 2026-06-13 00:09:56
● 2026-06-13 12:27:18
○ 2026-06-13 16:26:22
● 2026-06-13 21:39:50
○ 2026-06-13 22:38:40
● 2026-06-14 05:39:38
● 2026-06-15 08:02:56
○ 2026-06-15 09:31:30
● 2026-06-18 15:55:16
○ 2026-06-21 23:38:52
○ 2026-07-13 11:59:42

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
cla.nic.cl, b.nic.cl, c.nic.cl-
capcom.clns1.capcom.cl, ns2.capcom.cl2 records

✅ Authoritative Response

Server:66.225.201.116

NS records: ns1.capcom.cl, ns2.capcom.cl

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at cl: Error: DNS query timeout: 190.124.27.10 for DNSKEY cl

⏱️ Timing

Total: 3259ms | Queries: -

📄 Records

TypeCountSample Data
A166.225.201.117
NS2ns2.capcom.cl, ns1.capcom.cl
MX1capcom.cl (pri: 0)
TXT2facebook-domain-verification=v1ulw4rbjjg, v=spf1 +mx +a +ip4:66.225.201.114 includ
SOA1ns1.capcom.cl servers.privatednsorg.com

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns2.capcom.cl, ns1.capcom.cl)

Analysis

Hierarchy

capcom.cl serves as the parent of ns2.capcom.cl and ns1.capcom.cl.

Name Servers

capcom.cl has two authoritative name servers — ns1.capcom.cl and ns2.capcom.cl.

The name server configuration of capcom.cl is shared with other domains, for instance constructoralazcano.cl, hotelcentral.cl, comintec.cl and two others.

ns1.capcom.cl directs to 66.225.201.115 and ns2.capcom.cl directs to 66.225.201.116; each host name points to exactly one IP number.