Security headers checker
See which HTTP security headers a page sends, which ones are missing, and the exact line to add.
What this checks
We request the page the way a browser does and read the response headers: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and Cross-Origin-Opener-Policy. We also flag headers that reveal your server software and version.
Why it matters
Security headers are cheap to add and block whole classes of attacks: clickjacking, protocol downgrades, MIME sniffing and a large share of cross-site scripting. Many audits and security questionnaires ask for them by name.
Where to add them
On Nginx use add_header in the server block. On Apache use Header set in .htaccess. On Vercel, Netlify and Cloudflare Pages there is a headers config file. In Next.js you can set them in next.config with the headers() function.
Want the full picture?
This tool covers one thing. A Mozolite scan runs up to 201 checks on how search engines find, read and rank the page, in about 20 seconds.