Web and SSL Certificates · #71

Online HTTP Security Header Analyzer

Interprets response headers only from the text you paste; no request is sent to any site.

  • Data is processed in your browser and not sent to a server

Tool

One 'Name: value' per line. Data does not leave the browser.

What does this tool do?

Security headers tell the browser how to protect a site: HSTS blocks unencrypted connections, CSP blocks injected scripts, X-Frame-Options blocks clickjacking. A missing or wrong header is often the first finding in a penetration test. The tool gives a status and a concrete fix for each header.

How to use it

  1. Get the headers: browser developer tools → Network → document request → Response headers, or curl -sI https://domain.
  2. Paste the text (status line optional) and press Run.

Fields

HTTP response headers
One 'Name: value' per line. Data does not leave the browser.

Worked example

InputValue
HTTP response headers
HTTP/2 200
content-type: text/html; charset=UTF-8
strict-transport-security: max-age=31536000; includeSubDomains
content-security-policy: default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; object-src 'none'; frame-ancestors 'self'
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
server: nginx/1.18.0
x-powered-by: PHP/8.1.2
set-cookie: PHPSESSID=abc123; path=/; HttpOnly

Expected result: HSTS, X-Content-Type-Options and Referrer-Policy are fine; CSP frame-ancestors replaces X-Frame-Options. CSP contains 'unsafe-inline'; Permissions-Policy is missing; nginx and PHP versions are disclosed; the PHPSESSID cookie lacks Secure and SameSite.

The top fix is adding Secure; SameSite=Lax to the session cookie. Then hide version information (server_tokens off;, expose_php = Off) and replace inline scripts in CSP with nonces or hashes.

Second scenario

InputValue
HTTP response headers
HTTP/1.1 200 OK
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-XSS-Protection: 1; mode=block
Set-Cookie: ASP.NET_SessionId=xyz; path=/; HttpOnly; SameSite=Lax

Expected result: An old IIS response lacks HSTS, CSP, X-Frame-Options and X-Content-Type-Options; X-XSS-Protection is on; IIS and ASP.NET versions show; the session cookie is not Secure.

Method and assumptions

Header names are read case-insensitively. HSTS max-age below 180 days gives a warning. In CSP, 'unsafe-inline' without nonce/hash, 'unsafe-eval', wildcard script sources and missing object-src 'none' are flagged. Cookies are checked for Secure, HttpOnly and SameSite.

X-XSS-Protection is only positive with value 0 because it enables a legacy browser filter. Server and X-Powered-By headers containing a version number give a warning.

Using the result and troubleshooting

Manage headers in one place (web server, application or CDN/WAF) and rerun this tool after changes. Trial CSP with Content-Security-Policy-Report-Only first.

Limits and common mistakes

  • Only the pasted response is evaluated; other pages, redirects or API responses may differ. Full semantic validation of CSP is not performed.

Frequently asked questions

Can't the tool fetch the headers if I enter the URL?

This version deliberately sends no request to any target. Paste curl -sI output or the response headers from browser developer tools.

Related tools and service

Related service: Web Application Security and WAF

Web online tools · See all online tools