setting.cl - dns.ninja
setting.cl
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.pymedns.net ⚠️ Not in zone NS records | ||||||
| A | 186.64.112.77🇨🇱 ZAM-INTERNET186.64.112.0/24 Zgh Client - Proxy | ||||||
| PTR | serverdns1.pymedns.net | ||||||
| NS | ns2.pymedns.net ⚠️ Not in zone NS records | ||||||
| A | 45.79.215.148🇺🇸 AKAMAI-LINODE-AP45.79.192.0/19 Akamai Technologies | ||||||
| PTR | serverdns2.pymedns.net | ||||||
| NS | ns3.pymedns.net ⚠️ Not in zone NS records | ||||||
| A | 144.217.14.218🇨🇦 OVH144.217.0.0/16 Hosting route | ||||||
| PTR | serverdns3.pymedns.net | ||||||
cl
| DNSSEC | ⚠️ Not signed | ||||||
| NS | a.nic.cl ⚠️ Not in zone NS records | ||||||
| NS | b.nic.cl ⚠️ Not in zone NS records | ||||||
| NS | c.nic.cl ⚠️ Not in zone NS records | ||||||
Same first word
Similar names
DNS History
17 records (3 active, 14 former)
○NSdrew.ns.cloudflare.com2019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
●NSns1.pymedns.net2026-02-18 → 2026-07-23 · 3 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
●NSns2.pymedns.net2026-02-18 → 2026-07-23 · 3 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
●NSns3.pymedns.net2026-02-18 → 2026-07-23 · 3 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-07-23 18:30:42
○NSviolet.ns.cloudflare.com2019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○MXalt2.aspmx.l.google.com2026-02-18 → 2026-03-29 · 5 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
○MXalt3.aspmx.l.google.com2026-02-18 → 2026-03-29 · 5 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
○MXalt4.aspmx.l.google.com2026-02-18 → 2026-03-29 · 5 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
○MXaspmx.l.google.com2026-02-18 → 2026-03-29 · 5 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
○MXdc-3823c43677bb.setting.cl2019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○MXsmtp.google.com2026-04-13 → 2026-07-21 · 7 obs
○ 2026-03-29 00:39:24
● 2026-04-13 00:25:12
○ 2026-07-02 16:06:14
● 2026-07-03 03:48:56
○ 2026-07-10 09:58:34
● 2026-07-21 07:38:28
○ 2026-07-23 18:30:42
● 2026-04-13 00:25:12
○ 2026-07-02 16:06:14
● 2026-07-03 03:48:56
○ 2026-07-10 09:58:34
● 2026-07-21 07:38:28
○ 2026-07-23 18:30:42
○A104.28.24.1702019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○A104.28.25.1702019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○A186.64.114.402026-02-18 → 2026-03-29 · 5 obs
○ 2019-01-07 02:43:54
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
● 2026-02-18 13:17:00
● 2026-03-29 00:39:24
○ 2026-04-13 00:25:12
○ 2026-07-23 18:30:42
○A186.64.119.952026-04-13 → 2026-07-21 · 7 obs
○ 2026-03-29 00:39:24
● 2026-04-13 00:25:12
○ 2026-07-02 16:06:14
● 2026-07-03 03:48:56
○ 2026-07-10 09:58:34
● 2026-07-21 07:38:28
○ 2026-07-23 18:30:42
● 2026-04-13 00:25:12
○ 2026-07-02 16:06:14
● 2026-07-03 03:48:56
○ 2026-07-10 09:58:34
● 2026-07-21 07:38:28
○ 2026-07-23 18:30:42
○A2606:4700:30::681c:18aa2019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○A2606:4700:30::681c:19aa2019-01-07 → 2019-01-07 · 3 obs
● 2019-01-07 02:43:54
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
○ 2026-02-18 13:17:00
○ 2026-07-23 18:30:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cl | a.nic.cl, c.nic.cl, b.nic.cl | - |
| setting.cl | ns2.pymedns.net, ns3.pymedns.net, ns1.pymedns.net | - |
✅ Authoritative Response
Server:186.64.112.77
NS records: ns2.pymedns.net, ns3.pymedns.net, ns1.pymedns.net
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
Validation error at cl: Error: DNS query timeout: 190.124.27.10 for DNSKEY cl
⏱️ Timing
Total: 3899ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 186.64.119.95 |
| NS | 3 | ns1.pymedns.net, ns3.pymedns.net... |
| MX | 1 | smtp.google.com (pri: 1) |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns1.pymedns.net notificaciones_whm.haulm |
Analysis
Name Servers
The authoritative name servers for setting.cl are ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net — three in total.
setting.cl shares at least some of its name servers with other domains, including clubaereocuracavi.cl, decocasa.cl, casasuenos.cl and two others.
The hostnames ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net each resolve to a single IP: ns1.pymedns.net → 186.64.112.77, ns2.pymedns.net → 45.79.215.148, ns3.pymedns.net → 144.217.14.218.