Content-Type Sniffer Checker
Review Content-Type and X-Content-Type-Options from saved HTTP headers. Compare an optional body file’s signature and check the Fetch nosniff rule for scripts or styles.
Explain a Stylesheet Blocked by nosniff
Content-Type Sniffer Checker: how to use it
- Paste a Content-Type value, named header lines or a saved response header capture. Use Response block number for an earlier response in a capture.
- Choose Stylesheet or Script-like to check the destination-specific nosniff rule. Add a saved body file to inspect its signature.
- Run Check content type. Compare the declared type with the local signature and inspect or download the evidence report.
Limits and notes
Uses up to 50,000 characters of saved headers and the first 4,096 bytes of an optional local file. It identifies selected binary signatures and checks the recorded script/style nosniff rule. Other browser behavior depends on the request context and complete response.
How your privacy works →Content-Type Sniffer Checker: common questions
Does nosniff always block a mislabeled file?
The rule checked here compares the parsed type with the script or stylesheet destination. Other destinations and browser settings follow their own rules.
Why does a CSS file show no signature?
A stylesheet is text and has no fixed binary magic header. Use the recorded type and request destination to check the stylesheet rule.
Which response is analyzed after a redirect?
The checker uses the last final response by default. Choose an explicit block if the body bytes belong to a different response.