Request data
HTTP Headers Checker
See a deliberately limited selection of the HTTP headers that reached the WhatWebSees origin for this request.
Selected safe headers
Headers received by the origin
Loading selected request headers…
| Header | Value |
|---|
Raw technical view
The JSON below contains the same allowlisted values shown above.
Loading…
Cookie, Authorization, proxy IP headers and similar sensitive values are intentionally excluded by the backend allowlist.
What HTTP headers show
HTTP request headers provide context that helps a server respond, such as accepted content types, language preferences and a browser's User-Agent. This checker displays only the project's existing safe selection.
Why values may differ along the way
Cloudflare and reverse proxies sit between your browser and this Django application. They can normalize, add, remove or modify headers, so these values represent what reached the origin rather than a guaranteed byte-for-byte copy of the browser's original request.
A deliberate privacy boundary
This is not a dump of every incoming header. Cookies, credentials, visitor IP forwarding headers and Cloudflare internal or security metadata are not included. The response is also marked private and not cacheable.
What this result means
This is an allowlisted view of headers received by WhatWebSees, not every byte on the connection. Proxies and browser policy can add, remove or reduce values.