limpyman.com.mx - dns.ninja

`limpyman.com.mx`

DNSSEC	⚠️ Not signed
A	198.49.23.144^{🇺🇸 SQUARESPACE-1198.49.23.0/24 Squarespace, Inc. 459 Broadway, 5th Floor New York, NY 10013 US} ✓ In HTTPS hints
A	198.49.23.145^{🇺🇸 SQUARESPACE-1198.49.23.0/24 Squarespace, Inc. 459 Broadway, 5th Floor New York, NY 10013 US} ✓ In HTTPS hints
A	198.185.159.144^{🇺🇸 SQUARESPACE-1198.185.159.0/24 Squarespace, Inc. 459 Broadway, 5th Floor New York, NY 10013 US} ✓ In HTTPS hints
A	198.185.159.145^{🇺🇸 SQUARESPACE-1198.185.159.0/24 Squarespace, Inc. 459 Broadway, 5th Floor New York, NY 10013 US} ✓ In HTTPS hints
NS	`ns-cloud-e1.googledomains.com` ⭐
		A	2001:4860:4802:32::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e1.googledomains.com`
		A	216.239.32.110^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-e1.googledomains.com`
NS	`ns-cloud-e2.googledomains.com`
		A	2001:4860:4802:34::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e2.googledomains.com`
		A	216.239.34.110^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-e2.googledomains.com`
NS	`ns-cloud-e3.googledomains.com`
		A	2001:4860:4802:36::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e3.googledomains.com`
		A	216.239.36.110^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-e3.googledomains.com`
NS	`ns-cloud-e4.googledomains.com`
		A	2001:4860:4802:38::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e4.googledomains.com`
		A	216.239.38.110^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-e4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.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`
HTTPS	HTTP/2, HTTP/1.1 ✓ hints match
		IPv4 hints	198.185.159.144, 198.185.159.145, 198.49.23.144, 198.49.23.145
SOA	`ns-cloud-e1.googledomains.com`cloud-dns-hostmaster@google.com serial=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=1785575128

WOT: NOT_SAFE (44/100)

Previously MX for

limpyman.com.mx

Same first word

limpyman.com.mx

Similar names

myimplan.com

DNS History

22 records (13 active, 9 former)

●NSns-cloud-e1.googledomains.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●NSns-cloud-e2.googledomains.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●NSns-cloud-e3.googledomains.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●NSns-cloud-e4.googledomains.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

○NSns143.neubox.net2017-09-05 → 2017-09-05 · 4 obs

○ 2016-12-29 19:56:48
● 2017-09-05 18:11:10
○ 2026-06-13 18:14:30
○ 2026-08-01 09:07:02

○NSns144.neubox.net2017-09-05 → 2017-09-05 · 4 obs

○ 2016-12-29 19:56:48
● 2017-09-05 18:11:10
○ 2026-06-13 18:14:30
○ 2026-08-01 09:07:02

○NSns245.neubox.net2017-09-05 → 2017-09-05 · 4 obs

○ 2016-12-29 19:56:48
● 2017-09-05 18:11:10
○ 2026-06-13 18:14:30
○ 2026-08-01 09:07:02

○NSpdns05.domaincontrol.com2015-08-15 → 2016-12-29 · 4 obs

● 2015-08-15 07:18:24
● 2016-12-29 19:56:48
○ 2017-09-05 18:11:10
○ 2026-08-01 09:07:02

○NSpdns06.domaincontrol.com2015-08-15 → 2016-12-29 · 4 obs

● 2015-08-15 07:18:24
● 2016-12-29 19:56:48
○ 2017-09-05 18:11:10
○ 2026-08-01 09:07:02

●MXalt1.aspmx.l.google.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●MXalt2.aspmx.l.google.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●MXalt3.aspmx.l.google.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●MXalt4.aspmx.l.google.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●MXaspmx.l.google.com2026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

○MXlimpyman.com.mx2017-09-05 → 2017-09-05 · 4 obs

○ 2016-12-29 19:56:48
● 2017-09-05 18:11:10
○ 2026-06-13 18:14:30
○ 2026-08-01 09:07:02

○MXmail.limpyman.com.mx2015-08-15 → 2016-12-29 · 4 obs

● 2015-08-15 07:18:24
● 2016-12-29 19:56:48
○ 2017-09-05 18:11:10
○ 2026-08-01 09:07:02

●A198.185.159.1442026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●A198.185.159.1452026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●A198.49.23.1442026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

●A198.49.23.1452026-06-13 → 2026-08-01 · 3 obs

○ 2017-09-05 18:11:10
● 2026-06-13 18:14:30
● 2026-08-01 09:07:02

○A23.229.184.2012015-08-15 → 2016-12-29 · 4 obs

● 2015-08-15 07:18:24
● 2016-12-29 19:56:48
○ 2017-09-05 18:11:10
○ 2026-08-01 09:07:02

○A65.99.252.1372017-09-05 → 2017-09-05 · 4 obs

○ 2016-12-29 19:56:48
● 2017-09-05 18:11:10
○ 2026-06-13 18:14:30
○ 2026-08-01 09:07:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	m.mx-ns.mx, o.mx-ns.mx, c.mx-ns.mx, i.mx-ns.mx...	-
limpyman.com.mx	ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com	-

✅ Authoritative Response

Server:216.239.32.110

NS records: ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 756ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`198.185.159.144, 198.185.159.145...`
NS	4	`ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h2",`
SOA	1	`ns-cloud-e1.googledomains.com cloud-dns-`

Analysis

IP Addresses

limpyman.com.mx resolves to four IP addresses: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.

Two other host names, along with generationrolling.org, mariaimaginario.com and fetznercollision.com, also share IP numbers with limpyman.com.mx.

Name Servers

The NS records for limpyman.com.mx point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

limpyman.com.mx shares at least some of its name servers with other domains, including jcedevelopment.com, gpjp.net, gradeflix.com and two others.

The host names ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com each resolve to two IP addresses: ns-cloud-e1.googledomains.com resolves to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com resolves to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com resolves to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com resolves to 216.239.38.110 and 2001:4860:4802:38::6e.

Mail Servers

limpyman.com.mx is handled by five mail servers: 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 limpyman.com.mx and other domains, including ns500698.ns500758.ns500758.ns500759.ns500758.ns500759.ns500698.ns500736.ns500735.ns500735.ns500735.ns500708.ns500708.ns500698.ns500619.ns500576.ns500619.trackreceptor.com, ns500742.ns500742.ns500742.ns500754.ns500731.ns500671.ns500742.ns500688.ns500649.ns500291.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500731.ns500742.ns500731.ns500742.ns500731.ns500731.ns500671.ns500671.ns500731.ns500688.ns500705.ns500671.ns500678.ns500704.ns500649.ns500291.ns500649.tenderladiesbz.com and two others.

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

Host names that have two IP addresses:

aspmx.l.google.com resolves to two addresses: 173.194.45.26 and 2607:f8b0:4004:c1b::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.