forcebalance.com.mx - dns.ninja

`forcebalance.com.mx`

DNSSEC	⚠️ Not signed
A	13.248.243.5^{🇺🇸 Amazon13.248.240.0/20}
		PTR	`a16e665f42988324c.awsglobalaccelerator.com`
A	76.223.105.230^{🇺🇸 Amazon76.223.96.0/20}
NS	`ns39.domaincontrol.com` ⭐
		A	2603:5:21d1::14^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns39.domaincontrol.com`
		A	97.74.109.20^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns39.domaincontrol.com`
NS	`ns40.domaincontrol.com`
		A	2603:5:22d1::14^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns40.domaincontrol.com`
		A	173.201.77.20^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns40.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-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::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::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::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
SOA	`ns39.domaincontrol.com`dns@jomax.net 2026-03-04 #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=1785537150

WOT: NOT_SAFE (44/100)

Same first word

forcebalance.com.mx

forcebalance.com

DNS History

17 records (9 active, 8 former)

●NSns39.domaincontrol.com2016-07-19 → 2026-07-31 · 3 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2026-07-31 23:08:50

●NSns40.domaincontrol.com2016-07-19 → 2026-07-31 · 3 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2026-07-31 23:08:50

○NSns8.e-digitalhosting.net2015-07-13 → 2016-03-03 · 4 obs

● 2015-07-13 07:40:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

○NSns9.e-digitalhosting.net2015-07-13 → 2016-03-03 · 4 obs

● 2015-07-13 07:40:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

●MXalt1.aspmx.l.google.com2015-07-13 → 2026-07-31 · 2 obs

● 2015-07-13 07:40:02
● 2026-07-31 23:08:50

●MXalt2.aspmx.l.google.com2016-07-19 → 2026-07-31 · 3 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2026-07-31 23:08:50

●MXalt3.aspmx.l.google.com2016-07-19 → 2026-07-31 · 3 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2026-07-31 23:08:50

●MXalt4.aspmx.l.google.com2016-07-19 → 2026-07-31 · 3 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2026-07-31 23:08:50

●MXaspmx.l.google.com2015-07-13 → 2026-07-31 · 2 obs

● 2015-07-13 07:40:02
● 2026-07-31 23:08:50

○MXaspmx2.googlemail.com2015-07-13 → 2016-03-03 · 4 obs

● 2015-07-13 07:40:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

○MXaspmx3.googlemail.com2015-07-13 → 2016-03-03 · 4 obs

● 2015-07-13 07:40:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

○MXlt2.aspmx.l.google.com2015-07-13 → 2016-03-03 · 4 obs

● 2015-07-13 07:40:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

○A107.180.5.562016-07-19 → 2017-05-17 · 5 obs

○ 2016-03-03 06:56:06
● 2016-07-19 10:15:42
● 2017-05-17 04:04:12
○ 2026-06-10 21:25:16
○ 2026-07-31 23:08:50

●A13.248.243.52026-06-10 → 2026-07-31 · 3 obs

○ 2017-05-17 04:04:12
● 2026-06-10 21:25:16
● 2026-07-31 23:08:50

○A189.211.180.1422015-11-24 → 2016-03-03 · 5 obs

○ 2015-07-13 07:40:02
● 2015-11-24 23:02:02
● 2016-03-03 06:56:06
○ 2016-07-19 10:15:42
○ 2026-07-31 23:08:50

○A69.162.117.2502015-07-13 → 2015-07-13 · 3 obs

● 2015-07-13 07:40:02
○ 2015-11-24 23:02:02
○ 2026-07-31 23:08:50

●A76.223.105.2302026-06-10 → 2026-07-31 · 3 obs

○ 2017-05-17 04:04:12
● 2026-06-10 21:25:16
● 2026-07-31 23:08:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	x.mx-ns.mx, i.mx-ns.mx, c.mx-ns.mx, e.mx-ns.mx...	-
forcebalance.com.mx	ns39.domaincontrol.com, ns40.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.77.20

NS records: ns39.domaincontrol.com, ns40.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 532ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.105.230, 13.248.243.5`
NS	2	`ns39.domaincontrol.com, ns40.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns39.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

forcebalance.com.mx points to the IP addresses 13.248.243.5 and 76.223.105.230

Two other host names, along with bufero.com, canerello.com and auratechltd.com, also share IP numbers with forcebalance.com.mx.

Name Servers

forcebalance.com.mx has two authoritative name servers — ns39.domaincontrol.com and ns40.domaincontrol.com.

forcebalance.com.mx shares its NS records with other domains, for example zensoda.com, kosiarek.info, goldbirdpictures.com and two others.

Both ns39.domaincontrol.com and ns40.domaincontrol.com have two IP addresses each. ns39.domaincontrol.com resolves to 97.74.109.20 and 2603:5:21d1::14; ns40.domaincontrol.com resolves to 173.201.77.20 and 2603:5:22d1::14.

Mail Servers

forcebalance.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.

There is at least a partial MX overlap between forcebalance.com.mx and other domains, including ns500768.ns500758.ns500758.ns500758.ns500758.ns500698.ns500698.ns500735.ns500698.ns500736.ns500698.ns500736.ns500576.ns500698.ns500576.ns500698.ns500576.trackreceptor.com, ns500731.ns500671.ns500671.ns500754.ns500731.ns500742.ns500704.ns500671.ns500705.ns500705.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500758.ns500758.ns500758.ns500698.ns500758.ns500736.ns500736.ns500735.ns500735.ns500736.ns500698.ns500735.ns500698.ns500652.ns500619.ns500619.trackreceptor.com and two others.

These mail servers frequently co-occur with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and two others.

Host names that have two IP addresses:

aspmx.l.google.com resolves to 142.251.16.27 and 2607:f8b0:4004:c1b::1b.

alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

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

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

alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.