`geforcenow.com.mx`

DNSSEC	⚠️ Not signed
A	34.194.97.138^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
		PTR	`ec2-34-194-97-138.compute-1.amazonaws.com`
NS	`dns1.p02.nsone.net` ⭐
		A	2620:4d:4000:6259:7:2:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p02.nsone.net`
		A	198.51.44.2^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p02.nsone.net`
NS	`dns2.p02.nsone.net`
		A	2a00:edc0:6259:7:2::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p02.nsone.net`
		A	198.51.45.2^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns2.p02.nsone.net`
NS	`dns3.p02.nsone.net`
		A	2620:4d:4000:6259:7:2:0:3^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns3.p02.nsone.net`
		A	198.51.44.66^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns3.p02.nsone.net`
NS	`dns4.p02.nsone.net`
		A	2a00:edc0:6259:7:2::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p02.nsone.net`
		A	198.51.45.66^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns4.p02.nsone.net`
SOA	`dns1.p02.nsone.net`hostmaster@nsone.net serial=1603990012

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

WOT: NOT_SAFE (44/100)

Same first word

DNS History

5 records (5 active, 0 former)

●NSdns1.p02.nsone.net2026-02-14 → 2026-08-02 · 2 obs

● 2026-02-14 18:54:48
● 2026-08-02 18:24:32

●NSdns2.p02.nsone.net2026-02-14 → 2026-08-02 · 2 obs

● 2026-02-14 18:54:48
● 2026-08-02 18:24:32

●NSdns3.p02.nsone.net2026-02-14 → 2026-08-02 · 2 obs

● 2026-02-14 18:54:48
● 2026-08-02 18:24:32

●NSdns4.p02.nsone.net2026-02-14 → 2026-08-02 · 2 obs

● 2026-02-14 18:54:48
● 2026-08-02 18:24:32

●A34.194.97.1382026-02-14 → 2026-08-02 · 2 obs

● 2026-02-14 18:54:48
● 2026-08-02 18:24:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, o.mx-ns.mx, m.mx-ns.mx...	12 records
geforcenow.com.mx	dns2.p02.nsone.net, dns1.p02.nsone.net, dns4.p02.nsone.net, dns3.p02.nsone.net	-

✅ Authoritative Response

Server:198.51.45.2

NS records: dns2.p02.nsone.net, dns1.p02.nsone.net, dns4.p02.nsone.net, dns3.p02.nsone.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 523ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`34.194.97.138`
NS	4	`dns1.p02.nsone.net, dns2.p02.nsone.net...`
SOA	1	`dns1.p02.nsone.net hostmaster.nsone.net`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (x.mx-ns.mx, o.mx-ns.mx, m.mx-ns.mx...)

Analysis

IP Addresses

geforcenow.com.mx has exactly one IP address — 34.194.97.138.

geforce.computer, nvidia.nz, geforcenow.eu plus two other host names have IP numbers in common with geforcenow.com.mx.

Name Servers

Four name servers handle the delegation for geforcenow.com.mx: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net and dns4.p02.nsone.net.

geforcenow.com.mx shares at least some of its name servers with other domains, including matesfordating.com, inspirationaldraperies.com, alignerds.com and two others.

These name servers are frequently seen alongside ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com and 7 other name servers.

The host names dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net and dns4.p02.nsone.net each resolve to two IP addresses: dns1.p02.nsone.net resolves to 198.51.44.2 and 2620:4d:4000:6259:7:2:0:1; dns2.p02.nsone.net resolves to 198.51.45.2 and 2a00:edc0:6259:7:2::2; dns3.p02.nsone.net resolves to 198.51.44.66 and 2620:4d:4000:6259:7:2:0:3; dns4.p02.nsone.net resolves to 198.51.45.66 and 2a00:edc0:6259:7:2::4.

geforcenow.com.mx - robtex.com