← Back to browse

Cards-against-capital

The party game for founders, funds, and the money that ruins them.

Added July 21, 2026 · Last analysed July 21, 2026 · via Hacker News · 69% unique tagline

Own this Launch?
Screenshot of Cards-against-capital

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

Cards-against-capital is missing several launch fundamentals. Worth fixing first: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Hacker News on July 21, 2026. The site is hosted on Vercel. Our crawler found 5 technologies on this site, covering analytics, frameworks, hosting, and meta-frameworks. The stack includes Next.js, React, and HSTS.

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

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

1.7
StackScope Score
Poor
41/100 Launch Readiness
Partially ready
1/6 Security Headers
Poor
0/3 Legal
Missing
0/2 Crawl files
Missing
100/100 Performance
Fast
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 (5)

Infrastructure
Hosting Vercel
Security HSTS
Build & Framework
Framework React
Meta-framework Next.js (4)
Analytics & Marketing
Analytics Vercel Analytics medium

Infrastructure

Network
AMAZON-02 - Amazon.com, Inc., US
AS16509 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
Green hosting
Not green hosted
No green-energy record. Data from The Green Web Foundation.
SSL Certificate
Google Trust Services
Valid 28 Jun 2026 to 26 Sep 2026
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.

Storage (0)

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

Readiness Breakdown How?

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

Performance How?

98 ms Server response
95% Faster than peers
348 ms Largest contentful paint
0.07 Cumulative layout shift
222 KB Page weight
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.

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
? Analytics present, but it set no tracking cookies on our visit (it may be opt-in-gated).
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)

Build

✓ Code splitting
8 JS files
1 CSS files
0 Third-party domains
Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.