Guide

HTTP Headers Explained: Missing Security Headers and Cookies

Short answer: to get HTTP headers explained, paste headers copied from the browser's Network tab, from curl -i output or from server logs into the HTTP Header Analyzer. Each header gets a short plain-English explanation, and for responses the tool warns about missing security headers and risky cookie settings. You paste the text, so the tool never fetches your website.

What it accepts

Request or response headers, with an optional status line or request line on the first line. HTTP/2 pseudo-headers such as :status and :authority are read as normal headers. A header split over several lines (obsolete folding) is not supported and is reported as a missing colon, so join it into one line first.

What it checks in responses

  • Missing security headers: HSTS, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy.
  • Cookies set without Secure, HttpOnly or SameSite.
  • Access-Control-Allow-Origin: * combined with credentials, which browsers reject.
  • Repeated header names, which are usually meant to be combined.

A worked example

This response:

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Server: nginx
Set-Cookie: session=abc123; Path=/
Set-Cookie: theme=dark; Secure; HttpOnly; SameSite=Lax
Access-Control-Allow-Origin: *
Cache-Control: no-store

is explained as six headers, and the notes report:

  • the six missing security headers;
  • cookie without Secure: the session cookie may be sent over plain HTTP;
  • cookie without HttpOnly: it is readable from JavaScript, which is riskier if the page has an XSS bug;
  • cookie without SameSite: it may be sent on cross-site requests.

The theme cookie has all three flags and produces no note. Access-Control-Allow-Origin: * is not flagged on its own; it is reported only when combined with Access-Control-Allow-Credentials: true.

Reading the notes sensibly

  • Missing headers are suggestions, not verdicts. X-Frame-Options is not reported as missing when the Content-Security-Policy contains frame-ancestors, which does the same job.
  • A Content-Security-Policy-Report-Only header does not count as an enforced policy.
  • An internal API with no cookies may not need every header. The tool is not a security audit and its list is not exhaustive.
  • A header like X-Powered-By: Express gets a note that it exposes the framework.

To decide what to add and how to write it, follow the HTTP security headers checklist and use the Security Headers Generator.

Request headers

Switch the selector to "Request headers" for headers you send. The security checks are skipped, because they apply to responses only.

HTTP headers explained: how to use the HTTP Header Analyzer

  1. Copy the headers (Network tab, curl -i, logs). Build the curl command with the curl guide if needed.
  2. Open the HTTP Header Analyzer and pick Response or Request.
  3. Paste and read the table and the notes.
  4. Look up the status code in HTTP status codes explained and the media type in the MIME Type Lookup.

Limits to know

  • General-purpose suggestions, not a security audit.
  • Nothing is requested from the site; the result is only as good as what you paste.
  • Everything runs in your browser.

Frequently asked questions

Is this a security audit? No. It gives general suggestions.

Does it fetch my site? No. You paste the headers.

Why is Access-Control-Allow-Origin: * not flagged? It is reported only together with credentials.

What do Secure, HttpOnly and SameSite do? Secure: HTTPS only. HttpOnly: hidden from JavaScript. SameSite: limits cross-site sending.

Where do I copy headers from? The browser's Network tab, curl -i or server logs.

Related tools and guides