Notes · 10 November 2026

Security headers on 9 website builders' own homepages: Jimdo sends HSTS with max-age=0, only 2 of 7 readable sites send neither a frame policy nor a CSP

Security headers are the part of a site nobody sees and a migration quietly changes. On 10 November 2026 we requested the homepage of nine builders (curl, following redirects, one request each) and read four response headers from the final answer. These are the builders' own marketing sites, not customer sites.

What we found

PlatformHSTSX-Frame-OptionsCSPReferrer-Policy
Wix1 yearnonenoneno-referrer-when-downgrade
Squarespace180 daysnonenonenone
Webflow1 year, preloadSAMEORIGINenforced + report-onlystrict-origin-when-cross-origin
Jimdomax-age=0SAMEORIGINenforcedno-referrer-when-downgrade
WordPress.com1 year, preloadSAMEORIGINnonenone
Ghost1 yearSAMEORIGINenforcedno-referrer-when-downgrade
Framer1 year, preloadDENYnonestrict-origin-when-cross-origin
GoDaddy403DENY––
Weebly403SAMEORIGIN–same-origin

Three things to take from it

Limits

One request per site, from one machine, with a research user agent, so a different country or client could get different headers. We read only the four headers above, not the full set, and we did not judge whether any CSP is strong. For sites that redirect we used the headers of the final 200 response. The "none" entries mean the header did not appear in that response.

Related

See also what the homepages weigh and which robots.txt files name AI crawlers. Or scan your own site for free before you pay for anything.