What it means
Your home page doesn't send X-Content-Type-Options: nosniff. Without it, some browsers guess a
file's type from its content instead of trusting the Content-Type header your server sends.
Why it matters
Content sniffing lets a file uploaded as an image or text be run as a script or rendered as a
page if its bytes look like one, which turns harmless uploads into cross-site scripting. With nosniff the
browser refuses scripts and stylesheets whose type doesn't match. The header costs nothing and breaks
nothing as long as your server labels files correctly.
How to fix it
Send the header on every response, not only the home page.
Nginx
add_header X-Content-Type-Options "nosniff" always; in the server block.
Apache
Header always set X-Content-Type-Options "nosniff" with mod_headers enabled.
Cloudflare and other CDNs
Add it with a response header transform rule, or in your framework's security headers setting (for example Helmet in Node.js, which sends it by default).
Then check that scripts are served as text/javascript and stylesheets as text/css; a wrong type now
stops them loading.
Check it worked
Run the HTTP and security headers check again. The header table should show X-Content-Type-Options as set, and the finding should be gone.