HTTP Security Headers Scanner
Audit HSTS, CSP, X-Frame-Options, and Permissions-Policy response headers with A+ to F grading.
HTTP Security Headers Audit & Hardening Guide
HTTP security headers instruct modern web browsers on how to enforce strict security policies. Configuring HSTS, CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy provides robust protection against XSS, Clickjacking, and MitM attacks.
Audit security headers via CLI: curl cyber-tool.org/headers/example.com.
Frequently Asked Questions
What is HSTS and why should domains join the HSTS Preload list?
HSTS (HTTP Strict Transport Security) forces browsers to communicate strictly over encrypted HTTPS connections. Preloading embeds your domain into browser source code (Chrome/Firefox/Safari), completely eliminating SSL-stripping vulnerabilities on the very first visit.
How does Content-Security-Policy (CSP) prevent Cross-Site Scripting (XSS)?
CSP restricts resource loading and script execution. Protection depends on the policy, enforcement and browser support. A header being present does not prove XSS protection; this tool checks presence only.
How does X-Frame-Options stop Clickjacking attacks?
X-Frame-Options tells browsers whether a page can be rendered inside a <frame>, <iframe>, or <embed>. Setting it to 'SAMEORIGIN' or 'DENY' ensures attackers cannot overlay invisible iframes to steal administrative clicks.
What is Permissions-Policy and what capabilities does it manage?
Permissions-Policy governs access to sensitive browser features and APIs (geolocation, microphone, camera, payment, USB) for both top-level documents and embedded third-party iframes.