sensorcm.com - dns.ninja

`sensorcm.com`

DNSSEC	⚠️ Not signed
A	186.64.116.240^{🇨🇱 ZAM-INTERNET186.64.116.0/24 Zgh Client - Proxy}
		PTR	`pyme82.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	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c0b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2803::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausr-in-f27.1e100.net`
		A	172.217.216.27^{🇺🇸 Google172.217.0.0/16}
			PTR	`lcausr-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f27.1e100.net`
		A	172.253.145.27^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 a mx ip4:186.64.116.240 ip4:186.64.116.241 ip4:186.64.116.242 ip...`
SOA	`ns1.pymedns.net`notificaciones_whm@haulmer.net 2026-05-12 #4

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1783777692

Same first word

sensorcm.com

Similar names

cmsensor.com

mnscores.com

cosemsrn.org.br

conresms.com

DNS History

20 records (9 active, 11 former)

○NSdns1.name-services.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○NSdns2.name-services.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○NSdns3.name-services.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○NSdns4.name-services.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○NSdns5.name-services.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

●NSns1.pymedns.net2026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

●NSns2.pymedns.net2026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

●NSns3.pymedns.net2026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

●MXalt1.aspmx.l.google.com2015-05-25 → 2026-07-11 · 2 obs

● 2015-05-25 00:26:02
● 2026-07-11 14:07:46

●MXalt2.aspmx.l.google.com2015-05-25 → 2026-07-11 · 2 obs

● 2015-05-25 00:26:02
● 2026-07-11 14:07:46

●MXalt3.aspmx.l.google.com2026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

●MXalt4.aspmx.l.google.com2026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

●MXaspmx.l.google.com2015-05-25 → 2026-07-11 · 2 obs

● 2015-05-25 00:26:02
● 2026-07-11 14:07:46

○MXaspmx2.googlemail.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○MXaspmx3.googlemail.com2015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

●A186.64.116.2402026-02-15 → 2026-07-11 · 3 obs

○ 2018-12-07 16:09:20
● 2026-02-15 12:17:54
● 2026-07-11 14:07:46

○A216.239.32.212015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○A216.239.34.212015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○A216.239.36.212015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

○A216.239.38.212015-05-25 → 2018-12-07 · 4 obs

● 2015-05-25 00:26:02
● 2018-12-07 16:09:20
○ 2026-02-15 12:17:54
○ 2026-07-11 14:07:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
sensorcm.com	ns1.pymedns.net, ns2.pymedns.net, ns3.pymedns.net	-

✅ Authoritative Response

Server:45.79.215.148

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sensorcm.com (unsigned zone)

⏱️ Timing

Total: 639ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`186.64.116.240`
NS	3	`ns3.pymedns.net, ns2.pymedns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 a mx ip4:186.64.116.240 ip4:1`
SOA	1	`ns1.pymedns.net notificaciones_whm.haulm`

Analysis

IP Addresses

sensorcm.com resolves to just one IP address, 186.64.116.240.

Two other host names, along with quilpueonline.cl, urbanos.cl and vipseguridad.cl, also share IP numbers with sensorcm.com.

Name Servers

DNS for sensorcm.com 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 sensorcm.com and other domains — solsis.net, acg-it.cl, todopublicidad.cl 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

Five mail servers handle sensorcm.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between sensorcm.com and other domains, including ns500731.ns500742.ns500742.ns500731.ns500742.ns500731.ns500705.ns500705.ns500649.ns500678.ns500671.lusty(0x736c7574)z.com, ns500699.ns500693.ns500734.ns500693.ns500693.ns500699.ns500734.ns500699.ns500588.ns500683.ns500683.ns500588.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, ns500671.ns500754.ns500671.ns500671.ns500742.ns500671.ns500705.ns500704.ns500291.ns500671.ns500649.ns500291.ns500131.lustychickser.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com has two IP addresses: 172.253.122.26 and 2607:f8b0:4004:c0b::1b.

alt1.aspmx.l.google.com has two IP addresses: 172.217.216.27 and 2607:f8b0:4023:2803::1b.

alt2.aspmx.l.google.com has two IP addresses: 172.253.145.27 and 2607:f8b0:4023:3003::1b.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.