Menu

I Checked the Security Headers on 11 of My Own Sites. 0 Send HSTS, and 5 Can Be Framed by Any Page
📰

I Checked the Security Headers on 11 of My Own Sites. 0 Send HSTS, and 5 Can Be Framed by Any Page

DEV Community: nextjs·Posting Dude·6 days ago
#zwqXC4Xa
#devtonextjs#devto#dev#headers#const
Reading 0:00
15s threshold

A November census from Defaults.Exposed counted 182,295 domains that send at least one security header the browser reads and then throws away. A stray semicolon after SAMEORIGIN , an ALLOWALL that no browser honours, max-age= with nothing after it. The header is there, a checklist ticks it, and the page behaves as if it was never sent.

One line in there made me stop: of the domains sending the dead ALLOWALL value, 14,884 say Next.js in X-Powered-By . All 11 of the sites I was about to check are Next.js. So this morning I checked them, expecting to find a few broken values.

I didn't find broken values. I found missing ones, which is a different and kind of more embarrassing problem.

What I checked

11 sites: five launch platforms (Aura++, EarlyHunt, IndieHunt, MakerHunt, SideHunt), Uno Directory, four small press sites I started last week, and Posting Dude. Three URLs each, so 33 responses: the homepage, one inner page from the sitemap, and a made-up path that should 404. The 404 is there on purpose.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.