powerdata.cl - dns.ninja

`powerdata.cl`

DNSSEC	⚠️ Not signed
A	186.64.114.60^{🇨🇱 ZAM-INTERNET186.64.114.0/24 Zgh Client - Proxy}
		PTR	`pyme102.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	`ns1.cdmon.net` ⚠️ Not in zone NS records
		A	35.189.106.232^{🇬🇧 Google35.189.96.0/20}
			PTR	`ns1.cdmon.net`
NS	`ns2.cdmon.net` ⚠️ Not in zone NS records
		A	35.195.57.29^{🇧🇪 Google35.195.48.0/20}
			PTR	`29.57.195.35.bc.googleusercontent.com`
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` ⚠️ Not in parent delegation
		A	144.217.14.218^{🇨🇦 OVH144.217.0.0/16 Hosting route}
			PTR	`serverdns3.pymedns.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`ilaspmx3.googlema.com`⁽¹⁰⁾
MX	`ms87434303.msv1.invalid`^(32767)
TXT	`google-site-verification=J84SoZ-Vs5R46GO3fS47zOTMHG1UnJ2fEAQ8qETe-hQ`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.pymedns.net`notificaciones_whm@haulmer.net 2026-08-01 #3

`cl`

	DNSSEC	⚠️ Not signed
	NS	`a.nic.cl` ⚠️ Not in zone NS records
	NS	`b.nic.cl` ⚠️ Not in zone NS records
	NS	`c.nic.cl` ⚠️ Not in zone NS records
	NS	`cl-ns.anycast.pch.net` ⚠️ Not in zone NS records
	NS	`cl1-tld.d-zone.ca` ⚠️ Not in zone NS records
	NS	`cl1.dnsnode.net` ⚠️ Not in zone NS records
	NS	`cl2-tld.d-zone.ca` ⚠️ Not in zone NS records

Same first word

powerdata.co.th

powerdata.dk

powerdata.cl

powerdata.online

powerdata.es

powerdata.de

powerdata.com.co

powerdata.at

powerdata.us

powerdata.pro

powerdata.co.uk

powerdata.ru

powerdata.com

powerdata.gr

powerdata.ch

powerdata.nl

powerdata.pe

powerdata.cz

powerdata.eu

powerdata.cn

powerdata.org

powerdata.it

powerdata.net

powerdata.com.au

powerdata.com.br

Similar names

DNS History

18 records (12 active, 6 former)

●NSns1.cdmon.net2015-06-09 → 2026-08-01 · 6 obs

● 2015-06-09 19:05:50
● 2015-10-25 22:44:14
○ 2016-01-20 06:39:50
○ 2017-09-01 15:14:26
● 2026-07-08 20:09:06
● 2026-08-01 20:06:20

●NSns1.pymedns.net2016-01-20 → 2026-08-01 · 3 obs

○ 2015-10-25 22:44:14
● 2016-01-20 06:39:50
● 2026-08-01 20:06:20

●NSns2.cdmon.net2015-06-09 → 2026-08-01 · 6 obs

● 2015-06-09 19:05:50
● 2015-10-25 22:44:14
○ 2016-01-20 06:39:50
○ 2017-09-01 15:14:26
● 2026-07-08 20:09:06
● 2026-08-01 20:06:20

●NSns2.pymedns.net2016-01-20 → 2026-08-01 · 3 obs

○ 2015-10-25 22:44:14
● 2016-01-20 06:39:50
● 2026-08-01 20:06:20

○NSns3.cdmon.net2015-06-09 → 2026-07-08 · 7 obs

● 2015-06-09 19:05:50
● 2015-10-25 22:44:14
○ 2016-01-20 06:39:50
○ 2017-09-01 15:14:26
● 2026-07-08 20:09:06
○ 2026-08-01 20:06:18
○ 2026-08-01 20:06:20

●NSns3.pymedns.net2026-03-12 → 2026-08-01 · 8 obs

○ 2017-09-01 15:14:26
● 2026-03-12 10:22:40
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
○ 2026-07-08 20:09:06
● 2026-08-01 20:06:18
● 2026-08-01 20:06:20

○NSns4.cdmondns-01.org2026-07-08 → 2026-07-08 · 4 obs

○ 2026-06-28 03:05:28
● 2026-07-08 20:09:06
○ 2026-08-01 20:06:18
○ 2026-08-01 20:06:20

○NSns5.cdmondns-01.com2026-07-08 → 2026-07-08 · 4 obs

○ 2026-06-28 03:05:28
● 2026-07-08 20:09:06
○ 2026-08-01 20:06:18
○ 2026-08-01 20:06:20

●MXalt1.aspmx.l.google.com2015-06-09 → 2026-08-01 · 5 obs

● 2015-06-09 19:05:50
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

●MXalt2.aspmx.l.google.com2015-06-09 → 2026-08-01 · 5 obs

● 2015-06-09 19:05:50
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

●MXaspmx.l.google.com2015-06-09 → 2026-08-01 · 5 obs

● 2015-06-09 19:05:50
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

●MXaspmx2.googlemail.com2015-06-09 → 2026-08-01 · 5 obs

● 2015-06-09 19:05:50
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

○MXaspmx3.googlemail.com2015-06-09 → 2015-10-25 · 4 obs

● 2015-06-09 19:05:50
● 2015-10-25 22:44:14
○ 2016-01-20 06:39:50
○ 2026-08-01 20:06:20

●MXilaspmx3.googlema.com2016-01-20 → 2026-08-01 · 6 obs

○ 2015-10-25 22:44:14
● 2016-01-20 06:39:50
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

●MXms87434303.msv1.invalid2026-03-12 → 2026-08-01 · 6 obs

○ 2016-01-20 06:39:50
● 2026-03-12 10:22:40
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
● 2026-08-01 20:06:20

○A134.0.10.1042015-06-09 → 2015-10-25 · 4 obs

● 2015-06-09 19:05:50
● 2015-10-25 22:44:14
○ 2016-01-20 06:39:50
○ 2026-08-01 20:06:20

●A186.64.114.602026-03-12 → 2026-08-01 · 8 obs

○ 2017-09-01 15:14:26
● 2026-03-12 10:22:40
● 2026-05-10 12:42:30
○ 2026-06-13 05:29:32
● 2026-06-28 03:05:28
○ 2026-07-08 20:09:06
● 2026-08-01 20:06:18
● 2026-08-01 20:06:20

○A186.64.119.832016-01-20 → 2017-09-01 · 5 obs

○ 2015-10-25 22:44:14
● 2016-01-20 06:39:50
● 2017-09-01 15:14:26
○ 2026-03-12 10:22:40
○ 2026-08-01 20:06:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cl	a.nic.cl, b.nic.cl, c.nic.cl, cl1.dnsnode.net...	14 records
powerdata.cl	ns2.pymedns.net, ns1.cdmon.net, ns1.pymedns.net, ns2.cdmon.net	-

✅ Authoritative Response

Server:35.195.57.29

NS records: ns2.pymedns.net, ns1.cdmon.net, ns1.pymedns.net, ns2.cdmon.net

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

Validation error at cl: Error: DNS query timeout: 190.124.27.10 for DNSKEY cl

⏱️ Timing

Total: 4081ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`186.64.114.60`
NS	3	`ns3.pymedns.net, ns2.pymedns.net...`
MX	6	`ms87434303.msv1.invalid (pri: 32767), aspmx2.googlemail.com (pri: 10)...`
TXT	2	`google-site-verification=J84SoZ-Vs5R46GO, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1.cdmon.net hostmaster.powerdata.cl`

📌 Glue Records Collected

Total: 14

In-bailiwick: 6 (a.nic.cl, b.nic.cl, c.nic.cl...)

Out-of-bailiwick: 8 (cl1.dnsnode.net, cl-ns.anycast.pch.net, cl1-tld.d-zone.ca...)

Analysis

IP Addresses

powerdata.cl has exactly one IP address — 186.64.114.60.

masterview.cl, magesta.cl, mail.musik.bio plus two other host names have IP numbers in common with powerdata.cl.

Name Servers

Five name servers handle delegation for powerdata.cl: ns1.cdmon.net, ns2.cdmon.net, ns1.pymedns.net and two others.

powerdata.cl shares at least some of its name servers with other domains, including difaher.com, interdiesel.com, noddon.tech and two others.

These name servers tend to appear together with the name servers ns2.pymedns.net, ns3.pymedns.net and ns3.cdmon.net, plus two others.

Host names resolving to a single IP address:

ns1.cdmon.net resolves to 35.189.106.232.

ns2.cdmon.net resolves to 35.195.57.29.

ns1.pymedns.net resolves to 186.64.112.77.

ns2.pymedns.net resolves to 45.79.215.148.

ns3.pymedns.net resolves to 144.217.14.218.

Mail Servers

powerdata.cl is handled by 6 mail servers: ilaspmx3.googlema.com, aspmx2.googlemail.com, ms87434303.msv1.invalid and 3 other.

At least some of the mail servers used by powerdata.cl are shared with other domains: ns500599.ns500724.ns500737.ns500724.ns500737.ns500724.ns500599.ns500599.ns500697.ns500599.ns500682.ns500669.www.yummyflingsfinder.com, ns500731.ns500731.ns500731.ns500742.ns500731.ns500754.ns500671.ns500704.ns500678.ns500291.ns500678.ns500666.ns500142.lusty(0x736c7574)z.com, ns500693.ns500699.ns500699.ns500699.ns500734.ns500699.ns500588.ns500588.ns500693.ns500683.ns500588.ns500693.ns500693.ns500683.ns500588.dtrkdll.com and two others among them.

These mail servers are often deployed together with aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and 5 other mail servers.

aspmx2.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com each resolve to two IP addresses. aspmx2.googlemail.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a. aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c25::1a. alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1a IP addresses.