finalfantasy.mx - dns.ninja

`finalfantasy.mx`

DNSSEC	⚠️ Not signed
A	107.161.23.26^{🇺🇸 AS3842107.161.23.0/24}
		PTR	`atlshared9.ramnode.com`
NS	`na3.ns.ramnode.com` ⭐
		A	107.191.102.178^{🇺🇸 AS3842107.191.100.0/22 InMotion Hosting, Inc.}
			PTR	`107-191-102-178.cloud.ramnode.com`
NS	`na4.ns.ramnode.com`
		A	107.161.24.103^{🇺🇸 AS3842107.161.24.0/22}
			PTR	`107-161-24-103.cloud.ramnode.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c08::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f27.1e100.net`
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f26.1e100.net`
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	2607:f8b0:4004:c29::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f27.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
		A	172.253.63.27^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f27.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
		A	192.178.218.26^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f26.1e100.net`
TXT	`v=spf1 a mx include:relay.mailchannels.net ?all`
SOA	`na3.ns.ramnode.com`noreply@ramnode.com 2026-06-27 #1

`mx`

	DNSSEC	🔒 Signed (DS record present)
	NS	`m.mx-ns.mx` ⭐
	NS	`c.mx-ns.mx`
	NS	`e.mx-ns.mx`
	NS	`i.mx-ns.mx`
	NS	`o.mx-ns.mx`
	NS	`x.mx-ns.mx`
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1785507448

Previously MX for

finalfantasy.mx

Same first word

Similar names

fantasyfinal.com

DNS History

27 records (4 active, 23 former)

○NSdns.site5.com2017-01-05 → 2017-01-10 · 5 obs

○ 2016-11-21 23:45:02
● 2017-01-05 13:17:16
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○NSdns2.site5.com2017-01-05 → 2017-01-10 · 5 obs

○ 2016-11-21 23:45:02
● 2017-01-05 13:17:16
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○NSfirewall2015-08-22 → 2016-11-21 · 7 obs

● 2015-08-22 02:10:30
○ 2015-12-06 07:17:44
○ 2016-06-27 16:02:32
● 2016-08-05 10:51:40
● 2016-11-21 23:45:02
○ 2017-01-05 13:17:16
○ 2026-07-31 14:24:24

○NSmpweb01.promapsa.com.mx2015-12-06 → 2016-06-27 · 5 obs

○ 2015-08-22 02:10:30
● 2015-12-06 07:17:44
● 2016-06-27 16:02:32
○ 2016-08-05 10:51:40
○ 2026-07-31 14:24:24

●NSna3.ns.ramnode.com2026-02-18 → 2026-07-31 · 3 obs

○ 2017-09-28 09:43:02
● 2026-02-18 19:54:08
● 2026-07-31 14:24:24

●NSna4.ns.ramnode.com2026-02-18 → 2026-07-31 · 3 obs

○ 2017-09-28 09:43:02
● 2026-02-18 19:54:08
● 2026-07-31 14:24:24

○NSns1.adwebsys.com2017-08-28 → 2017-09-28 · 5 obs

○ 2017-01-10 09:53:24
● 2017-08-28 15:01:10
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○NSns2.adwebsys.com2017-08-28 → 2017-09-28 · 5 obs

○ 2017-01-10 09:53:24
● 2017-08-28 15:01:10
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○NSpuente.com.mx2015-08-22 → 2016-11-21 · 4 obs

● 2015-08-22 02:10:30
● 2016-11-21 23:45:02
○ 2017-01-05 13:17:16
○ 2026-07-31 14:24:24

○MXalt1.aspmx.l.google.com2015-08-22 → 2017-09-28 · 4 obs

● 2015-08-22 02:10:30
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○MXalt2.aspmx.l.google.com2015-08-22 → 2017-09-28 · 4 obs

● 2015-08-22 02:10:30
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○MXalt3.aspmx.l.google.com2017-08-28 → 2017-09-28 · 5 obs

○ 2017-01-10 09:53:24
● 2017-08-28 15:01:10
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○MXalt4.aspmx.l.google.com2017-08-28 → 2017-09-28 · 5 obs

○ 2017-01-10 09:53:24
● 2017-08-28 15:01:10
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○MXaspmx.l.google.com2015-08-22 → 2017-09-28 · 4 obs

● 2015-08-22 02:10:30
● 2017-09-28 09:43:02
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○MXaspmx2.googlemail.com2015-08-22 → 2017-01-10 · 4 obs

● 2015-08-22 02:10:30
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○MXaspmx3.googlemail.com2015-08-22 → 2017-01-10 · 4 obs

● 2015-08-22 02:10:30
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○MXaspmx4.googlemail.com2015-08-22 → 2017-01-10 · 4 obs

● 2015-08-22 02:10:30
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○MXaspmx5.googlemail.com2015-08-22 → 2017-01-10 · 4 obs

● 2015-08-22 02:10:30
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○MXfinalfantasy.mx2026-02-18 → 2026-04-05 · 5 obs

○ 2017-09-28 09:43:02
● 2026-02-18 19:54:08
● 2026-04-05 07:42:26
○ 2026-05-22 21:58:12
○ 2026-07-31 14:24:24

●MXsmtp.google.com2026-05-22 → 2026-07-31 · 3 obs

○ 2026-04-05 07:42:26
● 2026-05-22 21:58:12
● 2026-07-31 14:24:24

●A107.161.23.262026-02-18 → 2026-07-31 · 3 obs

○ 2017-09-28 11:02:20
● 2026-02-18 19:54:08
● 2026-07-31 14:24:24

○A143.95.107.2482017-01-05 → 2017-01-10 · 5 obs

○ 2016-11-21 23:45:02
● 2017-01-05 13:17:16
● 2017-01-10 09:53:24
○ 2017-08-28 15:01:10
○ 2026-07-31 14:24:24

○A189.240.94.1352016-08-05 → 2016-11-21 · 5 obs

○ 2016-06-27 16:02:32
● 2016-08-05 10:51:40
● 2016-11-21 23:45:02
○ 2017-01-05 13:17:16
○ 2026-07-31 14:24:24

○A189.240.95.572017-08-28 → 2017-09-28 · 5 obs

○ 2017-01-10 09:53:24
● 2017-08-28 15:01:10
● 2017-09-28 11:02:20
○ 2026-02-18 19:54:08
○ 2026-07-31 14:24:24

○A192.168.0.252015-08-22 → 2015-08-22 · 3 obs

● 2015-08-22 02:10:30
○ 2015-12-06 07:17:44
○ 2026-07-31 14:24:24

○A201.157.19.2162015-12-06 → 2016-06-27 · 5 obs

○ 2015-08-22 02:10:30
● 2015-12-06 07:17:44
● 2016-06-27 16:02:32
○ 2016-08-05 10:51:40
○ 2026-07-31 14:24:24

○A201.157.19.2222015-08-22 → 2015-08-22 · 3 obs

● 2015-08-22 02:10:30
○ 2015-12-06 07:17:44
○ 2026-07-31 14:24:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	o.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, c.mx-ns.mx...	-
finalfantasy.mx	na4.ns.ramnode.com, na3.ns.ramnode.com	-

✅ Authoritative Response

Server:107.161.24.103

NS records: na4.ns.ramnode.com, na3.ns.ramnode.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for finalfantasy.mx (unsigned zone)

⏱️ Timing

Total: 666ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.161.23.26`
NS	2	`na4.ns.ramnode.com, na3.ns.ramnode.com`
MX	1	`smtp.google.com (pri: 1)`
TXT	1	`v=spf1 a mx include:relay.mailchannels.n`
SOA	1	`na3.ns.ramnode.com noreply.ramnode.com`

Analysis

IP Addresses

finalfantasy.mx resolves to one IP address: 107.161.23.26.

www.craftbeerattorney.com, reedconsult.com, webmailt.com and two other host names share IP numbers with finalfantasy.mx.

Name Servers

DNS delegation for finalfantasy.mx points to two name servers: na3.ns.ramnode.com and na4.ns.ramnode.com.

finalfantasy.mx uses the same name servers as several other domains — among them moduloweb.net, goobs.me, laurayoungbird.com and two more.

finalfantasy.mx at least partially shares name servers with other domains, including lelangon.com, cleaningshop.com.mx, kelomgeulis.com and extintoresenqueretaro.com.

These name servers are frequently seen alongside the name servers ns03.nolsatu.net, ns04.nolsatu.net, us.ns1.zeticloud.net and us.ns2.zeticloud.net.

na3.ns.ramnode.com and na4.ns.ramnode.com each resolve to one IP number: na3.ns.ramnode.com points to 107.191.102.178 and na4.ns.ramnode.com points to 107.161.24.103.

Mail Servers

Mail for finalfantasy.mx is handled by a single mail server, smtp.google.com.

finalfantasy.mx uses an identical mail server configuration to several other domains — among them larita.it, fazilcrypto.com, walhalla-deurne.nl and two more.

finalfantasy.mx has at least partial mail server overlap with other domains such as kjbullion.com, gotseats.com, moves.ai and two more.

These mail servers commonly appear together with aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two other mail servers.

smtp.google.com resolves to 9 IP addresses — 142.251.163.26, 172.253.63.27, 173.194.45.26 and 6 others.