We Checked 137 New Launches' Homepages. Almost Nobody Ships Security Headers.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

We Checked 137 New Launches' Homepages. Almost Nobody Ships Security Headers.

For the last week of October 2026, our daily routine included a small, unglamorous experiment: take the products that had just launched — Show HN posts, Product Hunt and TinyLaunch listings, the apps founders were proudly announcing that morning — and run one passive check against each homepage. No probing, no accounts, just the response headers any browser can see.

137 homepages later (107 from the daily launch runs, October 22–28, plus a 30-product backlog of mid-October launches), the pattern is consistent enough to publish: the security headers that browsers rely on are the exception in freshly launched apps, not the rule.

The headline numbers

The cleanest sample is October 27's run — 30 Show HN launches from the previous 48 hours, every result verified twice before we recorded it:

The surrounding days agree. October 28's 29 launches produced six more homepages with all five headers missing. The 30-product launch backlog (October 13–27) found 23 of 30 with at least one gap and only 7 fully clean — including products with polished marketing pages, paying customers, and launch-day attention, in some cases serving their homepage over plain http:// with a 200 response and no redirect to HTTPS at all. Email addresses were harder to find than vulnerabilities were: 17 of those 30 products publish no contact email anywhere on their site.

One thing we did not find: across all 137, not one homepage disclosed a PHP version in the range hit by the php2shell RCE — the only disclosed PHP version in the set was already the patched build. Founders may skip headers, but the week's scariest headline had clearly gotten through.

What this does and doesn't mean

Honesty about method, because these numbers deserve it: this is a passive, one-page, one-moment check — the same curl -sI anyone can run. Security headers are baseline hygiene, not a verdict on an app's security. A site can send all five and still have an open database (we wrote the Firebase and Supabase versions of that story this week); a site can miss all five and have solid internals. What a missing header set actually tells you is narrower and still useful: nobody ran a launch checklist. The headers take minutes to set, they're on every platform's hardening guide, and their absence correlates with the other unglamorous basics — the cookie flags, the exposed config files, the test rules — being skipped too.

We also re-verified before believing ourselves: a first automated pass misread several sites' headers through redirect chains (one launch that looked bare was fully covered), so every figure above comes from a raw-header re-check. Two of the "findings" in our earliest pass didn't survive that process and were corrected the same day. Small samples cut both ways; we'd rather publish the careful version.

Why launches ship like this

Nothing in the data suggests founders don't care. It suggests the launch checklist ends at "it works and looks right" — because modern builders, human and AI alike, are graded on the demo. Frameworks can set most of these headers, but the defaults are opt-in, the agent doesn't volunteer them, and launch day rewards the visible. The four launches in our study that sent the full set weren't doing anything exotic; someone (or some template) had headers on a list.

The fix is genuinely short — our guide to checking your site's security headers walks through what each one does and how to verify yours in minutes. That's the point of publishing this: in a week when critical plugin flaws were dropping daily, the most common gap we found costs an afternoon at most, and usually far less.

The number we'd like to change

4 out of 30. If you launched recently, we'd like your homepage to be in that group — and the check below is the same one we ran: your site's headers, cookies, TLS, and exposed-file basics, scored in about a minute.


Run the free mini-scan at preshipit.com/free-scan and see which side of the 4-in-30 line your launch is on.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report