X-Content-Type-Options: nosniff
nosniff stops the browser guessing a file type from its contents, which is how an uploaded image ends up executed as a script.
Browsers used to “sniff” files: if a response looked like a script or HTML, they treated it as one, whatever its declared type. That made it possible to upload a file disguised as an image or text and have the browser execute it. The X-Content-Type-Options: nosniff header turns sniffing off: the browser trusts only the Content-Type the server sent, and refuses to run a script or apply a stylesheet whose type does not match.
How SiteScan grades it
The header has only one valid value. Exactly nosniff is “Strong”; any other value is “Weak”, because browsers ignore it; no header is “Missing”.
How to set it
- nginx:
add_header X-Content-Type-Options "nosniff" always; - Apache:
Header always set X-Content-Type-Options "nosniff"
Send it on every response, not just HTML. Before enabling it, check that your server sends correct types — text/css for stylesheets, text/javascript or application/javascript for scripts — otherwise those files will stop loading. This is one of the cheapest headers to add and rarely breaks anything. See the full set in the security headers overview.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Security headers”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data