← Back to browse

Gabify OS

Professional assessment and therapy management

Health

app.gabify.life · Added June 18, 2026 · Last analysed June 18, 2026 · via · 57% 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 18 June 2026; the live site may have changed since.

Gabify OS ships with the basics, with complete legal pages. What needs work: missing several security headers, no robots.txt or sitemap, and incomplete email security.

Launched on Product Hunt on June 18, 2026. The site is hosted on Amazon.com in the United States, with a domain registered in 2024. We've detected 7 technologies on this site, covering auth, CSS frameworks, frameworks, and meta-frameworks. The stack includes Auth.js, Next.js, and React.

It's running the same core stack as 2,715 other launches.

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

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

Tech Stack (7)

Infrastructure
OS Ubuntu
Server nginx
Build & Framework
Auth Auth.js (2)
CSS framework Tailwind CSS
Framework React
Meta-framework Next.js
UI library shadcn/ui

Infrastructure

Network
AS14618 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 14 Jun 2026 to 12 Sep 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
1.8 years
Registered Sep 2024 · HOSTINGER operations, UAB

Email Security

SPF ~all (via apex gabify.life) Soft-fail (~all). Common and accepted.
DKIM (via apex gabify.life) Detected on apex gabify.life
DMARC p=none (via apex gabify.life) None (p=none). Monitoring only.
?
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 (3)

Cookies (2)
NameLifetimeDetected as
__Host-next-auth.csrf-token session Auth.js
__Secure-next-auth.callback-url session Auth.js
Local storage (1)
KeySizeDetected as
nextauth.message 74 B Auth.js

Readiness Breakdown How?

Custom title and 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?

343 ms Server response
52% Faster than peers
4964 ms Largest contentful paint
0.00 Cumulative layout shift
352 KB Page weight
7 KB Image weight
2 Console errors
2 Failed requests
Broken first-party requests (2), worth fixing
  • 401 /api/billing/plans
  • 404 /&

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
AI palette signals +5
AI stack signals +10

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
92% unique

Security Headers (0/6)

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

Build

Code splitting
8 JS files
1 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.