humanforce.com.mx - dns.ninja

`humanforce.com.mx`

DNSSEC	⚠️ Not signed
A	2600:3c00::f03c:91ff:fe37:d5b1^{🇺🇸 AKAMAI-LINODE-AP2600:3c00::/32 Akamai Technologies}
A	45.56.122.239^{🇺🇸 AKAMAI-LINODE-AP45.56.120.0/21 Akamai Technologies}
NS	`ns1.linode.com` ⭐
		A	2600:14c0:6::2^{🇺🇸 Akamai2600:14c0:6::/48 Technologies}
			PTR	`c1-2.akashield.net`
		A	92.123.94.2^{🇳🇱 Akamai92.123.94.0/24 Technologies}
			PTR	`c1-2.akashield.net`
NS	`ns2.linode.com`
		A	2600:14c0:6::3^{🇺🇸 Akamai2600:14c0:6::/48 Technologies}
			PTR	`c1-3.akashield.net`
		A	92.123.94.3^{🇳🇱 Akamai92.123.94.0/24 Technologies}
			PTR	`c1-3.akashield.net`
NS	`ns3.linode.com`
		A	2600:14c0:7::3^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-3.akashield.net`
		A	92.123.95.3^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-3.akashield.net`
NS	`ns4.linode.com`
		A	2600:14c0:7::4^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-4.akashield.net`
		A	92.123.95.4^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-4.akashield.net`
NS	`ns5.linode.com`
		A	2600:14c0:7::2^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-2.akashield.net`
		A	92.123.95.2^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-2.akashield.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.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	`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	`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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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`
SOA	`ns1.linode.com`phernandez@humanforce.com.mx 2018-08-22 #39

`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=1784866537

WOT: NOT_SAFE (44/100)

Same first word

humanforce.com.au

humanforce.co

humanforce.co.uk

humanforce.herokuapp.com

humanforce.be

humanforce.com.mx

humanforce.com

humanforce.io

humanforce.co.nz

humanforce.eu

humanforce.co.kr

humanforce.nl

Similar names

forumchane.ru

DNS History

17 records (12 active, 5 former)

○NSns1.fusionag.com2015-05-22 → 2017-04-04 · 3 obs

● 2015-05-22 12:15:44
● 2017-04-04 14:14:48
○ 2026-07-24 04:34:44

○NSns1.hospedando.us2015-05-22 → 2017-04-04 · 3 obs

● 2015-05-22 12:15:44
● 2017-04-04 14:14:48
○ 2026-07-24 04:34:44

●NSns1.linode.com2026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

○NSns2.hospedando.us2015-05-22 → 2017-04-04 · 3 obs

● 2015-05-22 12:15:44
● 2017-04-04 14:14:48
○ 2026-07-24 04:34:44

●NSns2.linode.com2026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

●NSns3.linode.com2026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

●NSns4.linode.com2026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

●NSns5.linode.com2026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

●MXalt1.aspmx.l.google.com2015-10-24 → 2026-07-24 · 3 obs

○ 2015-05-22 12:15:44
● 2015-10-24 16:53:04
● 2026-07-24 04:34:44

●MXalt2.aspmx.l.google.com2015-10-24 → 2026-07-24 · 3 obs

○ 2015-05-22 12:15:44
● 2015-10-24 16:53:04
● 2026-07-24 04:34:44

●MXalt3.aspmx.l.google.com2015-10-24 → 2026-07-24 · 3 obs

○ 2015-05-22 12:15:44
● 2015-10-24 16:53:04
● 2026-07-24 04:34:44

●MXalt4.aspmx.l.google.com2015-10-24 → 2026-07-24 · 3 obs

○ 2015-05-22 12:15:44
● 2015-10-24 16:53:04
● 2026-07-24 04:34:44

●MXaspmx.l.google.com2015-10-24 → 2026-07-24 · 3 obs

○ 2015-05-22 12:15:44
● 2015-10-24 16:53:04
● 2026-07-24 04:34:44

○MXhumanforce.com.mx2015-05-22 → 2015-05-22 · 3 obs

● 2015-05-22 12:15:44
○ 2015-10-24 16:53:04
○ 2026-07-24 04:34:44

●A2600:3c00::f03c:91ff:fe37:d5b12026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

●A45.56.122.2392026-07-24 → 2026-07-24 · 2 obs

○ 2017-04-04 14:14:48
● 2026-07-24 04:34:44

○A67.225.216.1482015-05-22 → 2017-04-04 · 3 obs

● 2015-05-22 12:15:44
● 2017-04-04 14:14:48
○ 2026-07-24 04:34:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx...	-
humanforce.com.mx	ns2.linode.com, ns1.linode.com, ns5.linode.com, ns4.linode.com...	-

✅ Authoritative Response

Server:92.123.94.3

NS records: ns2.linode.com, ns1.linode.com, ns5.linode.com, ns4.linode.com, ns3.linode.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 1100ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`45.56.122.239`
AAAA	1	`2600:3c00::f03c:91ff:fe37:d5b1`
NS	5	`ns4.linode.com, ns2.linode.com...`
MX	5	`ALT2.ASPMX.L.GOOGLE.COM (pri: 5), ALT1.ASPMX.L.GOOGLE.COM (pri: 5)...`
SOA	1	`ns1.linode.com phernandez.humanforce.com`

Analysis

IP Addresses

humanforce.com.mx directs to two IP numbers, 45.56.122.239 and 2600:3c00::f03c:91ff:fe37:d5b1

Name Servers

humanforce.com.mx has five name servers, which are ns1.linode.com, ns2.linode.com, ns3.linode.com and two others.

humanforce.com.mx has at least partial name server overlap with other domains, such as una.io, business.rehab, truedungeon.com and two others.

It is common to see these name servers used together with name servers ns4.linode.com and ns5.linode.com.

Hostnames that resolve to two IP addresses:

ns1.linode.com directs traffic to 92.123.94.2 and 2600:14c0:6::2.

ns2.linode.com directs traffic to 92.123.94.3 and 2600:14c0:6::3.

ns3.linode.com directs traffic to 92.123.95.3 and 2600:14c0:7::3.

ns4.linode.com directs traffic to 92.123.95.4 and 2600:14c0:7::4.

ns5.linode.com directs traffic to 92.123.95.2 and 2600:14c0:7::2.

Mail Servers

Mail for humanforce.com.mx is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

humanforce.com.mx has at least partial mail server overlap with other domains such as citycircus.gr, thesoiree.la, trs.nl 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 directs traffic to 192.178.155.26 and 2607:f8b0:4004:c07::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.