eventcom.com.mx - dns.ninja

`eventcom.com.mx`

DNSSEC	⚠️ Not signed
A	65.99.252.102^{🇺🇸 TierPoint65.99.192.0/18 LLC}
		PTR	`svgrs66.cloud-mx-ns.net`
NS	`ns401.controldns.mx` ⭐ ⚠️ Not in parent delegation
		A	174.136.53.245^{🇺🇸 TierPoint174.136.0.0/18 LLC}
			PTR	`ns401.controldns.mx`
NS	`ns1.pikodegallo.com` ⚠️ Not in zone NS records
		A	65.99.252.102^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`svgrs66.cloud-mx-ns.net`
NS	`ns2.pikodegallo.com` ⚠️ Not in zone NS records
		A	65.99.252.102^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`svgrs66.cloud-mx-ns.net`
NS	`ns402.controldns.mx` ⚠️ Not in parent delegation
		A	65.99.248.132^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`ns402.controldns.mx`
NS	`ns403.controldns.mx` ⚠️ Not in parent delegation
		A	72.249.55.3^{🇺🇸 TierPoint72.249.48.0/20 LLC}
			PTR	`ns403.controldns.mx`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f26.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=Mf_GE_NpTgMHZ9hfmv6BnfnxZc_B1krIMPN2MEq656E`
TXT	`v=spf1 ip4:65.99.252.102 include:spf.antispamcloud.com ip4:198.59.144.165 inc...`
SOA	`ns401.controldns.mx`edgar@pikodegallo.com 2026-05-30 #1

`com.mx`

	DNSSEC	⚠️ Not signed
	NS	`m.mx-ns.mx` ⭐ ⚠️ Not in parent delegation
	NS	`c.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`e.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`i.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`o.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`x.mx-ns.mx` ⚠️ Not in parent delegation
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1784896775

WOT: NOT_SAFE (44/100)

Same first word

eventcom.info

eventcom.de

eventcom.jp

eventcom.org

eventcom.com

eventcom.at

eventcom.com.mx

eventcom.ch

eventcom.hu

Similar names

cmoevent.com

comevent.dk

cmveneto.com

comvente.com

comevent.com

comevent.fr

metcoenv.com

venomtec.com

vecomnet.vn

vecomnet.com

mecovent.de

DNS History

19 records (11 active, 8 former)

○NSns1.bluebrand.com.mx2016-02-26 → 2017-01-29 · 5 obs

○ 2015-11-16 12:47:58
● 2016-02-26 11:56:40
● 2017-01-29 09:49:20
○ 2026-02-23 02:38:26
○ 2026-07-24 12:55:28

●NSns1.pikodegallo.com2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

○NSns2.bluebrand.com.mx2016-02-26 → 2017-01-29 · 5 obs

○ 2015-11-16 12:47:58
● 2016-02-26 11:56:40
● 2017-01-29 09:49:20
○ 2026-02-23 02:38:26
○ 2026-07-24 12:55:28

●NSns2.pikodegallo.com2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●NSns401.controldns.mx2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●NSns402.controldns.mx2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●NSns403.controldns.mx2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

○NSpdns01.domaincontrol.com2015-07-19 → 2015-11-16 · 4 obs

● 2015-07-19 14:09:14
● 2015-11-16 12:47:58
○ 2016-02-26 11:56:40
○ 2026-07-24 12:55:28

○NSpdns02.domaincontrol.com2015-07-19 → 2015-11-16 · 4 obs

● 2015-07-19 14:09:14
● 2015-11-16 12:47:58
○ 2016-02-26 11:56:40
○ 2026-07-24 12:55:28

●MXalt1.aspmx.l.google.com2015-07-19 → 2026-07-24 · 5 obs

● 2015-07-19 14:09:14
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●MXalt2.aspmx.l.google.com2015-07-19 → 2026-07-24 · 5 obs

● 2015-07-19 14:09:14
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●MXalt3.aspmx.l.google.com2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●MXalt4.aspmx.l.google.com2026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

●MXaspmx.l.google.com2015-07-19 → 2026-07-24 · 5 obs

● 2015-07-19 14:09:14
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

○MXaspmx2.googlemail.com2015-07-19 → 2017-01-29 · 4 obs

● 2015-07-19 14:09:14
● 2017-01-29 09:49:20
○ 2026-02-23 02:38:26
○ 2026-07-24 12:55:28

○MXaspmx3.googlemail.com2015-07-19 → 2017-01-29 · 4 obs

● 2015-07-19 14:09:14
● 2017-01-29 09:49:20
○ 2026-02-23 02:38:26
○ 2026-07-24 12:55:28

○A138.128.186.1862016-02-26 → 2017-01-29 · 5 obs

○ 2015-11-16 12:47:58
● 2016-02-26 11:56:40
● 2017-01-29 09:49:20
○ 2026-02-23 02:38:26
○ 2026-07-24 12:55:28

○A50.63.35.12015-07-19 → 2015-11-16 · 4 obs

● 2015-07-19 14:09:14
● 2015-11-16 12:47:58
○ 2016-02-26 11:56:40
○ 2026-07-24 12:55:28

●A65.99.252.1022026-02-23 → 2026-07-24 · 6 obs

○ 2017-01-29 09:49:20
● 2026-02-23 02:38:26
● 2026-06-08 17:31:20
○ 2026-06-08 18:43:26
● 2026-06-08 20:12:22
● 2026-07-24 12:55:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
eventcom.com.mx	ns1.pikodegallo.com, ns2.pikodegallo.com	-

✅ Authoritative Response

Server:65.99.252.102

NS records: ns1.pikodegallo.com, ns2.pikodegallo.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for eventcom.com.mx (unsigned zone)

⏱️ Timing

Total: 840ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`65.99.252.102`
NS	3	`ns402.controldns.mx, ns401.controldns.mx...`
MX	5	`ALT4.ASPMX.L.GOOGLE.COM (pri: 10), ALT1.ASPMX.L.GOOGLE.COM (pri: 5)...`
TXT	2	`v=spf1 ip4:65.99.252.102 include:spf.ant, google-site-verification=Mf_GE_NpTgMHZ9h`
SOA	1	`ns401.controldns.mx edgar.pikodegallo.co`

Analysis

IP Addresses

eventcom.com.mx resolves to one IP address: 65.99.252.102.

teceng.mx, envasesmultiusos.com, movimed.com.mx and two other host names share IP numbers with eventcom.com.mx.

Name Servers

eventcom.com.mx has five name servers, which are ns1.pikodegallo.com, ns2.pikodegallo.com, ns401.controldns.mx and two others.

At least some of eventcom.com.mx's name servers are shared with other domains, for example mecana.com.mx, luft.com.mx, l-it.mx and two more.

These name servers tend to be deployed in combination with the name servers ns402.controldns.mx and ns403.controldns.mx.

Hosts with just one IP address:

ns1.pikodegallo.com directs to 65.99.252.102.

ns2.pikodegallo.com directs to 65.99.252.102.

ns401.controldns.mx directs to 174.136.53.245.

ns402.controldns.mx directs to 65.99.248.132.

ns403.controldns.mx directs to 72.249.55.3.

Host names pointing to 65.99.252.102 IP addresses: ns1.pikodegallo.com and ns2.pikodegallo.com.

Mail Servers

eventcom.com.mx has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

eventcom.com.mx has at least partial mail server overlap with other domains such as ns500742.ns500742.ns500671.ns500704.ns500688.ns500688.ns500678.ns500671.ns500678.ns500649.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500731.ns500742.ns500742.ns500671.ns500731.ns500671.ns500688.ns500678.ns500705.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500759.ns500698.ns500759.ns500736.ns500698.ns500735.ns500698.ns500736.ns500708.ns500708.ns500698.ns500619.ns500686.ns500619.ns500576.trackreceptor.com and two more.

The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com has two IP addresses: 142.251.111.27 and 2607:f8b0:4004:c08::1a.

alt1.aspmx.l.google.com has two IP addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.27 and 2a00:1450:400b:c02::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::1b.