Fluidez Finance

Privacy-first wealth management vault. No AI, no tracking.

Finance

Added April 8, 2026 · Last analysed April 10, 2026 · via · 67% unique tagline

Own this Launch?

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 10 April 2026; the live site may have changed since.

Fluidez Finance still has work before launch. Main gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on April 8, 2026. The site is hosted on Netlify. The crawl picked up 2 technologies on this site, covering hosting and security. The stack includes HSTS and Netlify.

For context, it's on one of the most common stacks we track, shared by 1,571 launches.

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

1.3

StackScope Score

Poor

29/100 Launch Readiness

Needs work

1/6 Security Headers

Poor

0/3 Legal

Missing

0/2 Crawl files

Missing

Vibe Score 0 · No AI signals

How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (2)

Infrastructure

Hosting	Netlify (3)
Security	HSTS (2)

Infrastructure

Network

AMAZON-02 - Amazon.com, Inc., US

AS16509 · US

DNSSEC

Not enabled

DNS responses unsigned. Cache-poisoning vulnerable.

SSL Certificate

DigiCert Inc

Valid 16 Feb 2026 to 19 Mar 2027

Certificate as captured in this snapshot, not a live check.

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 Not published. Receivers fall back to permissive defaults.

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.

Readiness Breakdown How?

✓ Responsive viewport meta tag

✓ Semantic HTML (nav, main, article)

- Custom title and meta description

- Open Graph tags (title, image, description)

- Canonical URL declared

- Twitter card meta tags

- Favicon present

AI Stance

No AI stance declared

✗ llms.txt published

✓ No AI bots blocked in robots.txt

Content-Signal

? No directive declared

Link headers

? None advertised

Well-Known Files

✗ robots.txt

✗ sitemap.xml

✗ security.txt

✗ llms.txt

✗ ads.txt

✗ humans.txt

Legal

? Privacy Policy not detected

? Terms of Service not detected

Detection works best on English language sites.

Security Headers (1/6)

✗

Referrer-Policy

✗

X-Frame-Options

✗

Permissions-Policy experimental (check browser support)

✗

X-Content-Type-Options

✗

Content-Security-Policy

✓

Strict-Transport-Security

–

X-XSS-Protection deprecated (use Content-Security-Policy)

Performance

682ms response time

Faster than 22% of sites

Build

0 JS files

0 CSS files

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