X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the
Content-Type headers should not be changed and be followed. This allows to opt-out of MIME type sniffing, or, in other words, it is a way to say that the webmasters knew what they were doing.
This header was introduced by Microsoft in IE 8 as a way for webmasters to block content sniffing that was happening and could transform non-executable MIME types into executable MIME types. Since then, other browsers have introduced it, even if their MIME sniffing algorithms were less aggressive.
Site security testers usually expect this header to be set.
nosniff only applies to "
script" and "
style" types. Also applying
nosniff to images turned out to be incompatible with existing web sites.
|Header type||Response header|
|Forbidden header name||no|
- Blocks a request if the requested type is
style" and the MIME type is not "
The definition of 'X-Content-Type-Options definition' in that specification.
|Living Standard||Initial definition|
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Feature||Android webview||Chrome for Android||Edge mobile||Firefox for Android||IE mobile||Opera Android||iOS Safari|