What this checks
The six response headers that do most to protect visitors: Strict-Transport-Security (HTTPS only), Content-Security-Policy (where scripts may load from), X-Frame-Options (no clickjacking), X-Content-Type-Options (no MIME sniffing), Referrer-Policy and Permissions-Policy. It also checks that plain HTTP redirects to HTTPS, that the TLS certificate is trusted and not about to expire, which TLS version is negotiated, and whether headers give away your server or framework version.
How the grade works
HSTS and CSP are worth 25 points each, X-Frame-Options and X-Content-Type-Options 15 each, and Referrer-Policy and Permissions-Policy 10 each. A header that is present but weak - a CSP that allows unsafe-inline scripts, an HSTS max-age under six months - earns half. 95 or more is an A+, 85 an A, and so on down to F. A site without HTTPS is graded F, because none of the rest can protect it.
Fixing it
For every missing or weak header, the result gives a ready-to-paste block for nginx, Apache (.htaccess) or IIS (web.config). Add them, reload, and check again. Be careful with Content-Security-Policy: a strict policy blocks any script it does not list, so roll it out as Content-Security-Policy-Report-Only first and watch for violations. Building the config from scratch? The nginx config generator includes these headers.
Only the address you enter is sent to our server, which makes one request to the site, reads the headers and certificate, and returns them. Page content is not stored. For performance rather than security, run the website speed test.

