finallyfox.com - dns.ninja

finallyfox.com

DNSSEC⚠️ Not signed
A64.6.158.20πŸ‡ΊπŸ‡Έ KansasNet64.6.158.0/24 WICH
PTRcp-01.hosting.kansas.net
NSns1.finallyfox.com ⭐
A64.6.158.20πŸ‡ΊπŸ‡Έ KansasNet64.6.158.0/24 WICH
PTRcp-01.hosting.kansas.net
NSns2.finallyfox.com
A64.6.158.5πŸ‡ΊπŸ‡Έ KansasNet64.6.158.0/24 WICH
PTRns2.kansas.net
NSns3.kansas.net ⚠️ Not in parent delegation
A23.23.80.80πŸ‡ΊπŸ‡Έ Amazon23.22.0.0/15 EC2 IAD prefix
PTRns3.kansas.net
MXfinallyfox.com ⭐
A64.6.158.20πŸ‡ΊπŸ‡Έ KansasNet64.6.158.0/24 WICH
PTRcp-01.hosting.kansas.net
TXTv=spf1 ip4:64.6.158.20 ip4:64.6.158.129 include:_spf.kansas.net +a +mx ~all
SOAns1.finallyfox.comksnet-cpanel@kansas.net 2026-07-03 #1

com

MX for

Subdomains

Same first word

DNS History

9 records (5 active, 4 former)

20162017201820192020202120222023202420252026NSns1.finallyfox.comns2.finallyfox.comns3.kansas.netns1.kansas.netns2.kansas.netMXfinallyfox.comspam-03.hosting.kansas.netA64.6.158.20158.247.220.53
●NSns1.finallyfox.com2026-03-12 β†’ 2026-07-28 Β· 3 obs
β—‹ 2017-10-05 10:55:48
● 2026-03-12 22:28:12
● 2026-07-28 02:28:42
β—‹NSns1.kansas.net2015-08-19 β†’ 2017-10-05 Β· 4 obs
● 2015-08-19 12:38:12
● 2017-10-05 10:55:48
β—‹ 2026-03-12 22:28:12
β—‹ 2026-07-28 02:28:42
●NSns2.finallyfox.com2026-03-12 β†’ 2026-07-28 Β· 3 obs
β—‹ 2017-10-05 10:55:48
● 2026-03-12 22:28:12
● 2026-07-28 02:28:42
β—‹NSns2.kansas.net2015-08-19 β†’ 2017-10-05 Β· 4 obs
● 2015-08-19 12:38:12
● 2017-10-05 10:55:48
β—‹ 2026-03-12 22:28:12
β—‹ 2026-07-28 02:28:42
●NSns3.kansas.net2026-03-12 β†’ 2026-07-28 Β· 3 obs
β—‹ 2017-10-05 10:55:48
● 2026-03-12 22:28:12
● 2026-07-28 02:28:42
●MXfinallyfox.com2026-03-12 β†’ 2026-07-28 Β· 3 obs
β—‹ 2017-10-05 10:55:48
● 2026-03-12 22:28:12
● 2026-07-28 02:28:42
β—‹MXspam-03.hosting.kansas.net2015-08-19 β†’ 2017-10-05 Β· 4 obs
● 2015-08-19 12:38:12
● 2017-10-05 10:55:48
β—‹ 2026-03-12 22:28:12
β—‹ 2026-07-28 02:28:42
β—‹A158.247.220.532015-08-19 β†’ 2017-10-05 Β· 4 obs
● 2015-08-19 12:38:12
● 2017-10-05 10:55:48
β—‹ 2026-03-12 22:28:12
β—‹ 2026-07-28 02:28:42
●A64.6.158.202026-03-12 β†’ 2026-07-28 Β· 3 obs
β—‹ 2017-10-05 10:55:48
● 2026-03-12 22:28:12
● 2026-07-28 02:28:42

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, b.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net...-
finallyfox.comns1.finallyfox.com, ns2.finallyfox.com2 records

βœ… Authoritative Response

Server:64.6.158.20

NS records: ns1.finallyfox.com, ns2.finallyfox.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for finallyfox.com (unsigned zone)

⏱️ Timing

Total: 3599ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A164.6.158.20
NS3ns2.finallyfox.com, ns1.finallyfox.com...
MX1finallyfox.com (pri: 0)
TXT1v=spf1 ip4:64.6.158.20 ip4:64.6.158.129
SOA1ns1.finallyfox.com ksnet-cpanel.kansas.n

πŸ“Œ Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.finallyfox.com, ns2.finallyfox.com)

Analysis

Hierarchy

finallyfox.com serves as the parent of ns2.finallyfox.com and ns1.finallyfox.com.

Mail Server Role

finallyfox.com serves as a mail server for finallyfox.com.

IP Addresses

finallyfox.com has exactly one IP address β€” 64.6.158.20.

marpc.org, cbsdoors.com, mail.neoshogardens.com plus two other host names have IP numbers in common with finallyfox.com.

Name Servers

finallyfox.com is delegated to three name servers: ns1.finallyfox.com, ns2.finallyfox.com and ns3.kansas.net.

finallyfox.com shares at least some of its name servers with other domains, including ssed.org, hammersmithmfg.net, briggspowersports.com and two others.

ns1.finallyfox.com, ns2.finallyfox.com and ns3.kansas.net each resolve to a single IP address: ns1.finallyfox.com resolves to 64.6.158.20, ns2.finallyfox.com resolves to 64.6.158.5 and ns3.kansas.net resolves to 23.23.80.80.

Mail Servers

finallyfox.com uses exactly one mail server, which is finallyfox.com.

finallyfox.com resolves to a single IP number: 64.6.158.20.