controlsolution.cl - dns.ninja
controlsolution.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 | 🔒 Signed (DS record present) | ||||||
| NS | a.nic.cl ⭐ | ||||||
| NS | b.nic.cl | ||||||
| NS | c.nic.cl | ||||||
| NS | cl-ns.anycast.pch.net | ||||||
| NS | cl1-tld.d-zone.ca | ||||||
| NS | cl1.dnsnode.net | ||||||
| NS | cl2-tld.d-zone.ca | ||||||
| TXT | INFO=CL zone generated Fri Oct 16 06:30:02 -03 2026 | ||||||
| SOA | a.nic.cldnsadmin@nic.cl 2026-10-16 #13 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
5 records (3 active, 2 former)
●NSns1.pymedns.net2026-10-13 → 2026-10-16 · 2 obs
● 2026-10-16 09:51:46
●NSns2.pymedns.net2026-10-13 → 2026-10-16 · 2 obs
● 2026-10-16 09:51:46
●NSns3.pymedns.net2026-10-13 → 2026-10-16 · 2 obs
● 2026-10-16 09:51:46
○MXmail.controlsolution.cl2026-10-13 → 2026-10-13 · 2 obs
○ 2026-10-16 09:51:46
○A186.64.116.2402026-10-13 → 2026-10-13 · 2 obs
○ 2026-10-16 09:51:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cl | a.nic.cl, b.nic.cl, c.nic.cl, cl1.dnsnode.net... | 14 records |
| controlsolution.cl | ns2.pymedns.net, ns3.pymedns.net, ns1.pymedns.net | - |
✅ Authoritative Response
Server:45.79.215.148
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: 4425ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 186.64.116.240 |
| NS | 3 | ns3.pymedns.net, ns2.pymedns.net... |
| MX | 1 | mail.controlsolution.cl (pri: 0) |
| TXT | 1 | v=spf1 a mx ip4:186.64.116.240 ip4:1 |
| SOA | 1 | ns1.pymedns.net notificaciones_whm.haulm |
📌 Glue Records Collected
Total: 14
In-bailiwick: 6 (a.nic.cl, a.nic.cl, b.nic.cl...)
Out-of-bailiwick: 8 (cl1.dnsnode.net, cl1.dnsnode.net, cl-ns.anycast.pch.net...)
Analysis
Name Servers
DNS for controlsolution.cl is handled by three authoritative name servers: ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net.
At least some of controlsolution.cl's name servers are shared with other domains, for example roninsenshi.com, empresasbruzzone.cl, glowmatrimonio.cl and two more.
These name servers tend to be used in conjunction with the name servers secundario.nic.cl.
ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net all have one IP address each — ns1.pymedns.net directs to 186.64.112.77, ns2.pymedns.net directs to 45.79.215.148 and ns3.pymedns.net directs to 144.217.14.218.