← Back to browse

Cuevera Inbox

The shared inbox for testing email — your whole team sees what your app sends, who's checked it, and who's on it. Live.

Developer Tools

inbox.cuevera.co · Added June 18, 2026 · Last analysed June 18, 2026 · via · 60% 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.

Cuevera Inbox is early-stage. Main gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on June 18, 2026. The site is hosted on Amazon.com in the United States. We've detected 5 technologies on this site, covering web fonts, frameworks, hosting, and meta-frameworks. The stack includes Next.js, React, and Google Fonts.

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

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

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

Tech Stack (5)

Infrastructure
Hosting Vercel
Security HSTS
Build & Framework
Font Google Fonts
Framework React
Meta-framework Next.js

Infrastructure

Network
AS16509 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 12 Jun 2026 to 10 Sep 2026
Certificate as captured in this snapshot, not a live check.

Email Security

SPF -all (via apex cuevera.co) Strict (-all). Strong.
DKIM (via apex cuevera.co) Detected on apex cuevera.co
DMARC p=quarantine (via apex cuevera.co) Quarantine (moderate)
?
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
Open Graph tags (title, image, description)
Twitter card meta tags
Responsive viewport meta tag
Favicon present
- Canonical URL declared
- Semantic HTML (nav, main, article)

Performance How?

266 ms Server response
62% Faster than peers
236 ms Largest contentful paint
0.38 Cumulative layout shift
375 KB Page weight
2 Third-party domains
1 Console errors
1 Failed requests
Broken first-party requests (1), worth fixing
  • 401 /api/teams

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 writing signals +5
AI typography signals +15
AI styling 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
? 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

Code splitting
6 JS files
1 CSS files
2 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.