Analyze any website's HTTP response headers and get a security score. Instant, free, no signup required.
HTTP security headers are directives sent by a web server in every HTTP response. They tell browsers how to behave when handling your site's content, forming a critical layer of defense against common web vulnerabilities like cross-site scripting (XSS), clickjacking, and data injection attacks.
Even if your application code is secure, missing headers leave the door open for attackers to exploit browser behavior. A properly configured set of security headers takes minutes to add and dramatically reduces your attack surface.
HSTS tells browsers to only connect to your site over HTTPS. Once a browser sees this header, it will refuse to make insecure HTTP connections for the specified duration. This prevents protocol downgrade attacks and cookie hijacking. Example: Strict-Transport-Security: max-age=31536000; includeSubDomains
CSP defines which resources (scripts, styles, images, fonts) the browser is allowed to load. It is the most powerful defense against XSS attacks because it blocks unauthorized inline scripts and external resources. Example: Content-Security-Policy: default-src 'self'; script-src 'self'
This header controls whether your pages can be embedded in <iframe> elements on other sites. Setting it to DENY or SAMEORIGIN prevents clickjacking attacks where an attacker overlays your page with an invisible frame to trick users into clicking hidden buttons.
When set to nosniff, this header prevents browsers from MIME-type sniffing a response away from the declared Content-Type. Without it, a browser might interpret a file as a script or HTML, enabling injection attacks through uploaded files.
Referrer-Policy controls how much referrer information is included when navigating away from your site. Policies like strict-origin-when-cross-origin prevent leaking sensitive URL paths to third-party sites while still providing origin information for analytics.
Permissions-Policy (formerly Feature-Policy) lets you control which browser features and APIs can be used on your site. You can disable access to the camera, microphone, geolocation, and more for embedded content and even for your own pages. Example: Permissions-Policy: camera=(), microphone=(), geolocation=()
Getting a perfect 6/6 score is straightforward. Add the missing headers to your web server or CDN configuration. Most headers require just a single line in your Nginx, Apache, or Cloudflare settings:
1. Run a scan with this tool to see which headers are missing.
2. Add the missing headers to your server config or CDN rules.
3. Re-scan to verify the changes are live.
4. Set up continuous monitoring with Valpero to get alerts if a header is ever removed during deployments.
Get instant alerts when security headers change or disappear. Free forever — no credit card required.
Start Monitoring Free