ipkr.cl - dns.ninja

ipkr.cl

DNSSEC⚠️ Not signed
NSns1.pymedns.net ⚠️ Not in zone NS records
A186.64.112.77🇨🇱 ZAM-INTERNET186.64.112.0/24 Zgh Client - Proxy
PTRserverdns1.pymedns.net
NSns2.pymedns.net ⚠️ Not in zone NS records
A45.79.215.148🇺🇸 AKAMAI-LINODE-AP45.79.192.0/19 Akamai Technologies
PTRserverdns2.pymedns.net
NSns3.pymedns.net ⚠️ Not in zone NS records
A144.217.14.218🇨🇦 OVH144.217.0.0/16 Hosting route
PTRserverdns3.pymedns.net

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

Same first word

Similar names

DNS History

12 records (3 active, 9 former)

2020202120222023202420252026NSns1.pymedns.netns2.pymedns.netns3.pymedns.netns1.dnshosty.netns2.dnshosty.netns3.dnshosty.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA186.64.116.35
NSns1.dnshosty.net2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
NSns1.pymedns.net2026-03-25 → 2026-08-08 · 6 obs
○ 2019-12-19 22:55:28
● 2026-03-25 03:00:40
● 2026-05-15 05:17:14
○ 2026-05-31 14:24:42
● 2026-07-22 10:23:32
● 2026-08-08 15:24:06
NSns2.dnshosty.net2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
NSns2.pymedns.net2026-03-25 → 2026-08-08 · 6 obs
○ 2019-12-19 22:55:28
● 2026-03-25 03:00:40
● 2026-05-15 05:17:14
○ 2026-05-31 14:24:42
● 2026-07-22 10:23:32
● 2026-08-08 15:24:06
NSns3.dnshosty.net2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
NSns3.pymedns.net2026-03-25 → 2026-08-08 · 6 obs
○ 2019-12-19 22:55:28
● 2026-03-25 03:00:40
● 2026-05-15 05:17:14
○ 2026-05-31 14:24:42
● 2026-07-22 10:23:32
● 2026-08-08 15:24:06
MXalt1.aspmx.l.google.com2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
MXalt2.aspmx.l.google.com2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
MXalt3.aspmx.l.google.com2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
MXalt4.aspmx.l.google.com2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
MXaspmx.l.google.com2019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06
A186.64.116.352019-12-19 → 2019-12-19 · 3 obs
● 2019-12-19 22:55:28
○ 2026-03-25 03:00:40
○ 2026-08-08 15:24:06

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
cla.nic.cl, b.nic.cl, c.nic.cl-
ipkr.clns1.pymedns.net, ns2.pymedns.net, ns3.pymedns.net-

✅ Authoritative Response

Server:186.64.112.77

NS records: ns1.pymedns.net, ns2.pymedns.net, ns3.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: 3608ms | Queries: -

📄 Records

TypeCountSample Data

Analysis

Name Servers

The authoritative name servers for ipkr.cl are ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net — three in total.

ipkr.cl partially shares its NS delegation with several other domains, including limtec.cl, enger.cl, tecnisold.cl and two others.

The hostnames ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net each resolve to a single IP: ns1.pymedns.net186.64.112.77, ns2.pymedns.net45.79.215.148, ns3.pymedns.net144.217.14.218.