codeff.cl - robtex.com

codeff.cl

DNSSEC⚠️ Not signed
A186.64.114.70🇨🇱 ZAM-INTERNET186.64.114.0/24 Zgh Client - Proxy
PTRpyme98.pymedns.net
NSns1.pymedns.net ⭐
A186.64.112.77🇨🇱 ZAM-INTERNET186.64.112.0/24 Zgh Client - Proxy
PTRserverdns1.pymedns.net
NSns2.pymedns.net
NSns3.pymedns.net
MXaspmx.l.google.com ⭐
A2607:f8b0:4004:c07::1b🇺🇸 Google2607:f8b0:4004::/48
PTRbc-in-f27.1e100.net
A192.178.218.27🇺🇸 Google192.178.218.0/24
PTRyuiadtq-in-f27.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1a🇨🇱 Google2800:3f0:4003::/48
A108.177.123.26🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1b🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f27.1e100.net
A172.253.116.27🇺🇸 Google172.253.116.0/24
PTRdj-in-f27.1e100.net
MXaspmx2.googlemail.com(10)
A2800:3f0:4003:c0f::1a🇨🇱 Google2800:3f0:4003::/48
A108.177.123.27🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f27.1e100.net
MXaspmx3.googlemail.com(10)
A2a00:1450:400b:c02::1a🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f26.1e100.net
A172.253.116.27🇺🇸 Google172.253.116.0/24
PTRdj-in-f27.1e100.net
TXTgoogle-site-verification=VY9uTWSifoemw-o5X3SP4PlSdJMeoooS1-oXYwQOrsY
TXTMS=ms75712251
TXTv=spf1 a mx ip4:186.64.114.70 ip4:186.64.114.71 ip4:186.64.114.72 ip4:1...
SOAns1.pymedns.netnotificaciones_whm@haulmer.net 2026-06-09 #0

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
NScl-ns.anycast.pch.net ⚠️ Not in zone NS records
NScl1-tld.d-zone.ca ⚠️ Not in zone NS records
NScl1.dnsnode.net ⚠️ Not in zone NS records
NScl2-tld.d-zone.ca ⚠️ Not in zone NS records
WOT: SAFE (83/100)

Same first word

codeff.cl

Similar names

decoff.ru

DNS History

13 records (9 active, 4 former)

20162017201820192020202120222023202420252026NSns1.pymedns.netns2.pymedns.netns3.pymedns.netdns1.metropolisinternet.netdns2.metropolisinternet.netMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA186.64.114.70158.69.168.209186.64.113.240
○NSdns1.metropolisinternet.net2015-08-28 → 2016-11-25 · 4 obs
● 2015-08-28 04:56:48
● 2016-11-25 03:53:54
○ 2017-08-22 04:49:36
○ 2026-06-14 21:28:20
○NSdns2.metropolisinternet.net2015-08-28 → 2016-11-25 · 4 obs
● 2015-08-28 04:56:48
● 2016-11-25 03:53:54
○ 2017-08-22 04:49:36
○ 2026-06-14 21:28:20
●NSns1.pymedns.net2017-08-22 → 2026-06-14 · 3 obs
○ 2016-11-25 03:53:54
● 2017-08-22 04:49:36
● 2026-06-14 21:28:20
●NSns2.pymedns.net2017-08-22 → 2026-06-14 · 3 obs
○ 2016-11-25 03:53:54
● 2017-08-22 04:49:36
● 2026-06-14 21:28:20
●NSns3.pymedns.net2017-08-22 → 2026-06-14 · 3 obs
○ 2016-11-25 03:53:54
● 2017-08-22 04:49:36
● 2026-06-14 21:28:20
●MXalt1.aspmx.l.google.com2015-08-28 → 2026-06-14 · 4 obs
● 2015-08-28 04:56:48
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20
●MXalt2.aspmx.l.google.com2015-08-28 → 2026-06-14 · 4 obs
● 2015-08-28 04:56:48
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20
●MXaspmx.l.google.com2015-08-28 → 2026-06-14 · 4 obs
● 2015-08-28 04:56:48
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20
●MXaspmx2.googlemail.com2015-08-28 → 2026-06-14 · 4 obs
● 2015-08-28 04:56:48
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20
●MXaspmx3.googlemail.com2015-08-28 → 2026-06-14 · 4 obs
● 2015-08-28 04:56:48
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20
○A158.69.168.2092015-08-28 → 2016-11-25 · 4 obs
● 2015-08-28 04:56:48
● 2016-11-25 03:53:54
○ 2017-08-22 04:49:36
○ 2026-06-14 21:28:20
○A186.64.113.2402017-08-22 → 2017-08-22 · 4 obs
○ 2016-11-25 03:53:54
● 2017-08-22 04:49:36
○ 2026-06-11 04:00:36
○ 2026-06-14 21:28:20
●A186.64.114.702026-06-14 → 2026-06-14 · 2 obs
○ 2026-06-11 04:00:36
● 2026-06-14 21:28:20

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
cla.nic.cl, b.nic.cl, c.nic.cl, cl1.dnsnode.net...14 records
codeff.clns1.pymedns.net, ns3.pymedns.net, ns2.pymedns.net-

✅ Authoritative Response

Server:186.64.112.77

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

📄 Records

TypeCountSample Data
A1186.64.114.70
NS3ns2.pymedns.net, ns1.pymedns.net...
MX5alt1.aspmx.l.google.com (pri: 5), aspmx3.googlemail.com (pri: 10)...
TXT3v=spf1 a mx ip4:186.64.114.70 ip4:18, MS=ms75712251...
SOA1ns1.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

IP Addresses

codeff.cl directs to one IP number, which is 186.64.114.70.

Among the host names that share IP numbers with codeff.cl are casadelapaz.cl, intrachile.cl, kintegra.cl and two others.

Name Servers

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

The name servers of codeff.cl overlap at least partially with those of other domains — among them grupomt.com.pe, pyme155.pymedns.net, hostalrayenco.cl and two more.

Hosts that resolve to one IP address:

ns1.pymedns.net has the IP address 186.64.112.77.

Mail Servers

Five mail servers handle codeff.cl: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

Hosts with two IP numbers each:

aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 192.178.218.27 and 2607:f8b0:4004:c07::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.