Your scan report says "HSTS Missing From HTTPS Server (RFC 6797)" , you add one header, you rescan, and the finding is still there. That second part is why most people end up searching for it. The header itself is one line. The finding keeps coming back because a scanner checks the response you didn't look at: a redirect, a different hostname, an error page or another port.
I found two of those on this site while writing this, so the curl output below is real. Here's what the scanner actually checks, the fix for IIS, ASP.NET Core, Nginx, Apache, Next.js and Cloudflare, and how to make sure the next scan comes back clean.
What the finding means
HSTS (HTTP Strict Transport Security, defined in RFC 6797) is a response header:
Strict-Transport-Security: max-age = 31536000
Enter fullscreen mode
Exit fullscreen mode
When a browser receives it over HTTPS, it remembers for max-age seconds (here one year) that this host must only be reached over HTTPS.β¦