60-Second Hack

60 seconds. Type fast. Breach the mainframe.

Games

Added April 18, 2026 · Last analysed April 18, 2026 · via Hacker News · 60% 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 18 April 2026; the live site may have changed since.

60-Second Hack is missing several launch fundamentals. What needs work: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Hacker News on April 18, 2026. The site is hosted on Vercel. Our crawler found 2 technologies on this site, covering hosting and security. The stack includes HSTS and Vercel.

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

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

2.4

StackScope Score

Poor

67/100 Launch Readiness

Well prepared

1/6 Security Headers

Poor

0/3 Legal

Missing

0/2 Crawl files

Missing

Vibe Score 20 · Few 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	Vercel (2)
Security	HSTS (2)

Infrastructure

Network

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

AS16509 · US

DNSSEC

Not enabled

DNS responses unsigned. Cache-poisoning vulnerable.

SSL Certificate

Google Trust Services

Valid 26 Feb 2026 to 27 May 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.

Readiness Breakdown How?

✓ Custom title and meta description

⚠

Open Graph tags (title, image, description) (partial) missing og:image

✓ Twitter card meta tags

✓ Responsive viewport meta tag

✓ Favicon present

- Canonical URL declared

- Semantic HTML (nav, main, article)

Vibe Score Breakdown How?

Signal	Points
AI writing 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

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

117ms response time

Faster than 90% of sites

Build

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