toolqik

56 · API & Webhooks

HTTP Header Parser

Explain raw HTTP headers, decode cookies, caching and CSP, and audit security.

Runs in your browser

About this tool

Headers decide caching, security, cookies, CORS and content negotiation, but raw header dumps are hard to read. Paste request or response headers and this parser explains each one, breaks structured values into their parts (Cache-Control directives, cookie attributes, CSP directives), flags duplicates and weak settings, and audits responses for missing security headers. Basic credentials are decoded to show the user name only; the password is never displayed.

Getting headers to paste

# Response headers only
curl -sI https://example.com

# Request and response headers
curl -sv -o /dev/null https://example.com 2>&1 | grep '^[<>]'

In a browser, open DevTools → Network, select a request and view its headers (choose “Raw”). Output from curl -v (lines starting with < or >) and redirect chains from curl -IL work too; only the final response is analysed.

What the security check looks for

  • HSTS, a Content-Security-Policy, nosniff and a Referrer-Policy.
  • Clickjacking protection via CSP frame-ancestors or X-Frame-Options.
  • Version-revealing headers such as X-Powered-By or Server: nginx/1.18.0.
  • Cookies without Secure, HttpOnly or SameSite, and CSP values like 'unsafe-inline'.

Generate a fix with the HTTP Header Generator.

FAQ

How do I see a website’s HTTP headers?

Run curl -sI https://example.com, or open DevTools → Network in your browser and select the request. Paste the result here for an explanation.

What does Cache-Control: no-cache mean?

The response may be stored, but must be revalidated with the server before each use. To prevent storing entirely, use no-store.

Which headers reveal too much?

X-Powered-By and Server headers with version numbers tell attackers what software to target. Remove them or hide versions.

Is it safe to paste headers with cookies or tokens?

Parsing runs in your browser and nothing is sent anywhere, but treat session cookies and tokens as secrets: remove them before sharing headers with anyone.

esc
↑↓ navigate↵ open