API & HTTP

HTTP Header Analyzer

Paste request or response headers (including the status line) to get a plain-English explanation of each one, plus warnings for missing security headers and risky cookie settings.

Guide: HTTP Headers Explained: Missing Security Headers and Cookies

Ready. Paste response headers below.

What it does

Paste headers copied from a browser's Network tab, curl's -i output, or server logs (an optional status/request line on the first line is fine). Each header gets a short explanation, and for responses the tool checks for commonly recommended security headers and risky cookie flags.

What it checks for responses

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

Good to know

These are general-purpose suggestions, not a security audit: some headers are unnecessary for a given site (for example an internal API with no cookies), and this list is not exhaustive. Nothing you paste is sent anywhere.

Example

The pre-filled sample is a 200 OK JSON response with cache-control: no-store, a cookie without flags, access-control-allow-origin: * and x-powered-by: Express. It produces the missing-header warnings, one warning for each missing cookie flag, and a note that X-Powered-By exposes the framework. Switch the selector to "Request headers" for headers you send: the security checks are skipped, because they apply to responses only.

How to read the notes

  • Missing headers are suggestions. 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. To write the headers you decide to add, use the Security Headers Generator.
  • Credentials with * is reported only when Access-Control-Allow-Credentials is true; with false there is no conflict.
  • HTTP/2 pseudo-headers such as :status and :authority, as copied from some browser tools, are read as normal headers.
  • A header split over several lines (obsolete folding) is not supported and is reported as a missing colon; join it into one line first.

The numeric code in the status line is explained in HTTP Status Codes, the media type in a Content-Type header can be looked up in the MIME Type Lookup, and curl -i output, as built by the cURL Command Generator, can be pasted straight in. For a URL's own parts, use the URL Parser.

Example: a response with several problems

Paste this response, copied from a browser’s Network tab or from curl:

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

The tool explains each of the 6 headers in a table. Under Notes it reports what is missing or risky:

  • Missing security headers: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy and permissions-policy.
  • 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 second cookie, theme, has all three flags and produces no note. The header Access-Control-Allow-Origin: * is not flagged on its own; it is reported only when it is combined with credentials, which browsers reject. To build the headers that are missing, use the Security Headers Generator.

Frequently asked questions

Is this a security audit?

No. These are general-purpose suggestions. Some headers are unnecessary for a given site, such as an internal API without cookies, and the list of checks is not exhaustive.

Does it fetch my website?

No. You paste the headers, so nothing is requested from any site. That also means it works for headers that are not publicly reachable.

Why can headers appear more than once?

Some headers, such as Set-Cookie, are repeated once per value. For other headers a repeat is usually meant to be combined, and the tool points it out.

Is what I paste uploaded?

No. The headers are analysed in your browser.

Privacy

This tool runs entirely in your browser. What you enter is processed on your device and is not sent to a server.

Share this tool

Your data is not included in this link.