ladoverde.cl - robtex.com
ladoverde.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 | ||||||
cl
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nic.cl ⭐ | ||||||
| NS | b.nic.cl | ||||||
| NS | c.nic.cl | ||||||
| NS | cl-ns.anycast.pch.net ⚠️ Not in parent delegation | ||||||
| NS | cl1-tld.d-zone.ca ⚠️ Not in parent delegation | ||||||
| NS | cl1.dnsnode.net ⚠️ Not in parent delegation | ||||||
| NS | cl2-tld.d-zone.ca ⚠️ Not in parent delegation | ||||||
| TXT | INFO=CL zone generated Wed Jul 22 11:00:01 -04 2026 | ||||||
| SOA | a.nic.cldnsadmin@nic.cl 2026-07-22 #22 | ||||||
Same first word
ladoverde.cl |
Similar names
DNS History
13 records (1 active, 12 former)
○NSdns1.gnext.cl2018-06-09 → 2018-06-09 · 4 obs
○ 2016-12-31 09:55:34
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○NSdns2.gnext.cl2018-06-09 → 2018-06-09 · 4 obs
○ 2016-12-31 09:55:34
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
●NSns1.pymedns.net2026-06-13 → 2026-07-22 · 3 obs
○ 2018-06-09 00:21:46
● 2026-06-13 08:56:34
● 2026-07-22 16:03:42
● 2026-06-13 08:56:34
● 2026-07-22 16:03:42
○NSns1.wix.com2015-07-03 → 2016-12-31 · 4 obs
● 2015-07-03 17:12:30
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
○NSns2.wix.com2015-07-03 → 2016-12-31 · 4 obs
● 2015-07-03 17:12:30
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
○MXalt1.aspmx.l.google.com2018-06-09 → 2018-06-09 · 3 obs
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○MXalt2.aspmx.l.google.com2018-06-09 → 2018-06-09 · 3 obs
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○MXalt3.aspmx.l.google.com2018-06-09 → 2018-06-09 · 3 obs
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○MXalt4.aspmx.l.google.com2018-06-09 → 2018-06-09 · 3 obs
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○MXaspmx.l.google.com2018-06-09 → 2018-06-09 · 3 obs
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○A168.195.128.1642018-06-09 → 2018-06-09 · 4 obs
○ 2016-12-31 09:55:34
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
○A23.236.62.1472015-07-03 → 2016-12-31 · 4 obs
● 2015-07-03 17:12:30
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
● 2016-12-31 09:55:34
○ 2018-06-09 00:21:46
○ 2026-07-22 16:03:42
○A2803:3b80:c:0:e434:c8ff:fe62:e3232018-06-09 → 2018-06-09 · 4 obs
○ 2016-12-31 09:55:34
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
● 2018-06-09 00:21:46
○ 2026-06-13 08:56:34
○ 2026-07-22 16:03:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cl | c.nic.cl, a.nic.cl, b.nic.cl | - |
| ladoverde.cl | ns1.pymedns.net | - |
✅ Authoritative Response
Server:186.64.112.77
NS records: ns1.pymedns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ladoverde.cl (unsigned zone)
⏱️ Timing
Total: 4854ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
ladoverde.cl is served by a sole authoritative name server: ns1.pymedns.net.
ladoverde.cl has the same name server delegation as a number of other domains, such as pyme100.pymedns.net, pyme88.pymedns.net, pyme98.pymedns.net and two more.
At least some of ladoverde.cl's name servers are shared with other domains, for example ctvc.cl, brackets.cl, kosca.cl and two more.
These name servers tend to be deployed in combination with the name servers ns2.pymedns.net and ns3.pymedns.net.
ns1.pymedns.net resolves to a single IP number: 186.64.112.77.