dagger.cl - dns.ninja

dagger.cl

DNSSEC⚠️ Not signed
A186.64.119.30πŸ‡¨πŸ‡± ZAM-INTERNET186.64.119.0/24 Zgh Client - Proxy
PTRpyme152.pymedns.net
NSns1.pymedns.net ⭐
A186.64.112.77πŸ‡¨πŸ‡± ZAM-INTERNET186.64.112.0/24 Zgh Client - Proxy
PTRserverdns1.pymedns.net
NSns2.pymedns.net
A45.79.215.148πŸ‡ΊπŸ‡Έ AKAMAI-LINODE-AP45.79.192.0/19 Akamai Technologies
PTRserverdns2.pymedns.net
NSns3.pymedns.net
A144.217.14.218πŸ‡¨πŸ‡¦ OVH144.217.0.0/16 Hosting route
PTRserverdns3.pymedns.net
MXmail.dagger.cl ⭐
A186.64.119.30πŸ‡¨πŸ‡± ZAM-INTERNET186.64.119.0/24 Zgh Client - Proxy
PTRpyme152.pymedns.net
TXTv=spf1 a mx ip4:186.64.119.30 ip4:186.64.119.31 ip4:186.64.119.32 ip4:1...
SOAns1.pymedns.netnotificaciones_whm@haulmer.net 2026-06-09 #2

cl

DNSSEC⚠️ Not signed
NSa.nic.cl ⭐
NSb.nic.cl
NSc.nic.cl
NScl-ns.anycast.pch.net
NScl1-tld.d-zone.ca
NScl1.dnsnode.net
NScl2-tld.d-zone.ca
TXTINFO=CL zone generated Tue Aug 4 07:30:02 -04 2026
SOAa.nic.cldnsadmin@nic.cl 2026-08-04 #15

Previously MX for

Same first word

Similar names

DNS History

9 records (5 active, 4 former)

20162017201820192020202120222023202420252026NSns1.pymedns.netns2.pymedns.netns3.pymedns.netns1.tuwebdns.netns2.tuwebdns.netMXmail.dagger.cldagger.clA186.64.119.30186.64.117.180
●NSns1.pymedns.net2026-02-19 β†’ 2026-08-04 Β· 3 obs
β—‹ 2017-04-02 21:32:16
● 2026-02-19 18:49:08
● 2026-08-04 13:47:34
β—‹NSns1.tuwebdns.net2015-06-28 β†’ 2017-04-02 Β· 4 obs
● 2015-06-28 13:08:16
● 2017-04-02 21:32:16
β—‹ 2026-02-19 18:49:08
β—‹ 2026-08-04 13:47:34
●NSns2.pymedns.net2026-02-19 β†’ 2026-08-04 Β· 3 obs
β—‹ 2017-04-02 21:32:16
● 2026-02-19 18:49:08
● 2026-08-04 13:47:34
β—‹NSns2.tuwebdns.net2015-06-28 β†’ 2017-04-02 Β· 4 obs
● 2015-06-28 13:08:16
● 2017-04-02 21:32:16
β—‹ 2026-02-19 18:49:08
β—‹ 2026-08-04 13:47:34
●NSns3.pymedns.net2026-02-19 β†’ 2026-08-04 Β· 3 obs
β—‹ 2017-04-02 21:32:16
● 2026-02-19 18:49:08
● 2026-08-04 13:47:34
β—‹MXdagger.cl2015-06-28 β†’ 2017-04-02 Β· 4 obs
● 2015-06-28 13:08:16
● 2017-04-02 21:32:16
β—‹ 2026-02-19 18:49:08
β—‹ 2026-08-04 13:47:34
●MXmail.dagger.cl2026-02-19 β†’ 2026-08-04 Β· 3 obs
β—‹ 2017-04-02 21:32:16
● 2026-02-19 18:49:08
● 2026-08-04 13:47:34
β—‹A186.64.117.1802015-06-28 β†’ 2017-04-02 Β· 4 obs
● 2015-06-28 13:08:16
● 2017-04-02 21:32:16
β—‹ 2026-02-19 18:49:08
β—‹ 2026-08-04 13:47:34
●A186.64.119.302026-02-19 β†’ 2026-08-04 Β· 3 obs
β—‹ 2017-04-02 21:32:16
● 2026-02-19 18:49:08
● 2026-08-04 13:47:34

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
cla.nic.cl, b.nic.cl, c.nic.cl-
dagger.clns3.pymedns.net, ns2.pymedns.net, ns1.pymedns.net-

βœ… Authoritative Response

Server:186.64.112.77

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

πŸ“„ Records

TypeCountSample Data
A1186.64.119.30
NS3ns1.pymedns.net, ns3.pymedns.net...
MX1mail.dagger.cl (pri: 0)
TXT1v=spf1 a mx ip4:186.64.119.30 ip4:18
SOA1ns1.pymedns.net notificaciones_whm.haulm

Analysis

IP Addresses

dagger.cl resolves to one IP address: 186.64.119.30.

cmcochrane.cl, mail.controldecalidad.cl, aptitude.cl and two other host names share IP numbers with dagger.cl.

Name Servers

DNS for dagger.cl is handled by three authoritative name servers: ns1.pymedns.net, ns2.pymedns.net and ns3.pymedns.net.

There is at least partial name server overlap between dagger.cl and other domains β€” maningroup.com, 120horas.com, inbioma.pe and two more among them.

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

Mail for dagger.cl is handled by a single mail server, mail.dagger.cl.

mail.dagger.cl has exactly one IP number: 186.64.119.30.