bitcode.cl - robtex.com
bitcode.cl
| DNSSEC | ⚠️ Not signed | ||||||
| A | 186.64.116.160🇨🇱 ZAM-INTERNET186.64.116.0/24 Zgh Client - Proxy | ||||||
| PTR | pyme135.pymedns.net | ||||||
| NS | ns1.pymedns.net ⭐ | ||||||
| A | 186.64.112.77🇨🇱 ZAM-INTERNET186.64.112.0/24 Zgh Client - Proxy | ||||||
| PTR | serverdns1.pymedns.net | ||||||
| NS | ns2.pymedns.net | ||||||
| A | 45.79.215.148🇺🇸 AKAMAI-LINODE-AP45.79.192.0/19 Akamai Technologies | ||||||
| PTR | serverdns2.pymedns.net | ||||||
| NS | ns3.pymedns.net | ||||||
| A | 144.217.14.218🇨🇦 OVH144.217.0.0/16 Hosting route | ||||||
| PTR | serverdns3.pymedns.net | ||||||
| MX | mail.bitcode.cl ⭐ | ||||||
| A | 186.64.116.160🇨🇱 ZAM-INTERNET186.64.116.0/24 Zgh Client - Proxy | ||||||
| PTR | pyme135.pymedns.net | ||||||
| TXT | google-site-verification=7KtX79ewVQtw-jTKryj4dxNUBoIt6iw6OIt9pDMesJ4 | ||||||
| TXT | v=spf1 +a +mx +ip4:186.64.114.245 +ip4:186.64.114.247 +ip4:186.64.116.161 +ip... | ||||||
| SOA | ns1.pymedns.netnotificaciones_whm@haulmer.net 2026-08-31 #1 | ||||||
cl
| DNSSEC | ⚠️ Not signed | ||||||
| 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 Mon Aug 31 01:00:01 -04 2026 | ||||||
| SOA | a.nic.cldnsadmin@nic.cl 2026-08-31 #2 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
5 records (5 active, 0 former)
●NSns1.pymedns.net2026-08-28 → 2026-08-31 · 2 obs
● 2026-08-31 05:45:12
●NSns2.pymedns.net2026-08-28 → 2026-08-31 · 2 obs
● 2026-08-31 05:45:12
●NSns3.pymedns.net2026-08-28 → 2026-08-31 · 2 obs
● 2026-08-31 05:45:12
●MXmail.bitcode.cl2026-08-28 → 2026-08-31 · 2 obs
● 2026-08-31 05:45:12
●A186.64.116.1602026-08-28 → 2026-08-31 · 2 obs
● 2026-08-31 05:45:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cl | cl2-tld.d-zone.ca, cl-ns.anycast.pch.net, a.nic.cl, c.nic.cl... | 14 records |
| bitcode.cl | ns2.pymedns.net, ns1.pymedns.net, ns3.pymedns.net | - |
✅ Authoritative Response
Server:186.64.112.77
NS records: ns2.pymedns.net, ns1.pymedns.net, ns3.pymedns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitcode.cl (unsigned zone)
⏱️ Timing
Total: 776ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 186.64.116.160 |
| NS | 3 | ns2.pymedns.net, ns3.pymedns.net... |
| MX | 1 | mail.bitcode.cl (pri: 0) |
| TXT | 2 | google-site-verification=7KtX79ewVQtw-jT, v=spf1 +a +mx +ip4:186.64.114.245 +ip4:1 |
| SOA | 1 | ns1.pymedns.net notificaciones_whm.haulm |
📌 Glue Records Collected
Total: 14
In-bailiwick: 6 (a.nic.cl, a.nic.cl, c.nic.cl...)
Out-of-bailiwick: 8 (cl2-tld.d-zone.ca, cl2-tld.d-zone.ca, cl-ns.anycast.pch.net...)
Analysis
IP Addresses
bitcode.cl has exactly one IP address — 186.64.116.160.
mail.eventoselcampito.cl, frate.pe, rescure-lawyer.net plus two other host names have IP numbers in common with bitcode.cl.
Name Servers
DNS for bitcode.cl is handled by three authoritative name servers: ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net.
bitcode.cl shares at least some of its name servers with other domains, including transpower.cl, zuri.cl, gestionhipotecaria.cl and two others.
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.
Mail Servers
bitcode.cl uses one mail server — mail.bitcode.cl.
mail.bitcode.cl has exactly one IP number: 186.64.116.160.