← Back to browse

Finhover Pro

Finance tracker built for entrepreneurs & insurance agents

finhover.com · Added June 16, 2026 · Last analysed June 16, 2026 · via · 67% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 16 June 2026; the live site may have changed since.

Finhover Pro is early-stage. Visible gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on June 16, 2026. The site is hosted on Amazon.com in the United States, with a domain registered in 2025. We've detected 4 technologies on this site, covering DNS providers, hosting, package cdn, and security. The stack includes GoDaddy DNS, HSTS, and jsDelivr.

It's on one of the most common stacks we track, shared by 992 launches.

If you own this site, refresh the snapshot and see the full fix list any time →

Vibe Score 85 · Strong AI signals
Informational pattern-match signal. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (4)

Infrastructure
DNS GoDaddy DNS
Hosting Netlify
Security HSTS
Build & Framework
Package CDN jsDelivr

Infrastructure

Network
AS16509 · US
DNS
GoDaddy DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 13 Jun 2026 to 11 Sep 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
1 year
Registered Apr 2025 · GoDaddy.com, LLC

Email Security

SPF Not published. Your domain can be spoofed in phishing emails.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC p=reject Reject (strict). Strong.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (0)

This site uses no client-side storage we could detect on page load.

Readiness Breakdown How?

Custom title and meta description (partial) missing meta description
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
- Open Graph tags (title, image, description)
- Canonical URL declared
- Twitter card meta tags

Performance How?

741 ms Server response
20% Faster than peers
284 ms Largest contentful paint
0.00 Cumulative layout shift
169 KB Page weight
1 Third-party domains
0 Console errors
0 Failed requests

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

Vibe Score Breakdown How?

SignalPoints
Placeholder branding +10
AI writing signals +5
AI iconography signals +5
AI code-structure signals +5
Recognised AI builder signature +30
AI layout signals +5
AI CSS signals +15

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

AI Stance

No AI stance declared
llms.txt published
No AI bots blocked in robots.txt
? No directive declared
? None advertised

Well-Known Files

robots.txt
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
? Privacy Policy not detected
? Terms of Service not detected
Detection works best on English language sites.

Security Headers (1/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

1 JS files
0 CSS files
1 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.