X-Content-Type-Options header not found

Rule from http under security category

What is a trooper!

we have submitted your edit to the community for review! We'll review and make it live on the site in the next few hours, the internet thanks you :).

Browse another section of the knowledge base

Suggest an edit


This rule has no content... yet.

Add content to this rule

Or just browse to view rules that have content


When your server serves a file, the browser uses the content-type as specified by your server. Certain (legacy) servers have problems serving the correct MIME type which resulted in Microsoft adding a feature which tries to "sniff" the content-type (en.wikipedia.org/wiki/Content_sniffing). This is done by looking at the first 256 bytes of a file.

This introduced an attack vector which could allow an attacker to upload an image file (for example) containing HTML which the browser will execute.

This HTTP header forces the browser to use the declared content-type and stops the browser from MIME sniffing.

The recommended value:

X-Content-Type-Options: nosniff

How do I fix this ?

Although you may set http headers in your application code it is often simpler to configure the web server to set it properly.

// nginx
add_header X-Content-Type-Options nosniff;

// apache
<IfModule mod_headers.c>
  Header set X-Content-Type-Options: nosniff


Browse another section of the knowledge base

Signup icon
Ready to see how well your site scores?

Passmarked works best when you have an account. It allows you to keep a dashboard with saved data of the sites you have run through the system, we’ll alert you about important updates and you get access to the Passmarked Slack forum.

Sign up to get started