General dev

HTTP Headers Reference

Runs locally

Use HTTP Headers Reference

What it does

Search 26 common HTTP request and response headers, each with its direction and a one-line purpose. Useful when you read the redirect chain or the cookies of a phishing link in curl or the browser dev tools.

It runs entirely in your browser: nothing you enter is uploaded.

Example

Search for cookie

Input
cookie
Output (captured 2026-10-20)
HEADER	TYPE	DESCRIPTION
Cookie	Request	Cookies sent to server
Set-Cookie	Response	Server sets a cookie on client

Shows Cookie (request) and Set-Cookie (response). Phishing kits often set a cookie on the first visit and show the real page only when it comes back, so both headers matter when you replay a link.

FAQ

What does each row show?

The header name, whether it is sent in requests, responses or both, and a short description. The search matches names and descriptions, so redirect finds Location.

Is this the complete list of HTTP headers?

No. It covers 26 frequent headers; the IANA HTTP Field Name Registry lists hundreds more. X-XSS-Protection is a legacy header: Chrome and Edge removed the filter it controls and Firefox never had one.

Does the tool send any requests?

No. It is a static table filtered in your browser. To see the headers of a real response, use curl -I or your browser's network panel.