Question 1

What does this page actually show?

Accepted Answer

Three things in parallel: (1) the headers your browser sent on a real fetch request to httpbin.org — that includes the user agent, accept-language, all the modern Sec-* client hints, and any X-Forwarded-* chain added by intermediate proxies; (2) Cloudflare edge metadata for a separate connection to 1.1.1.1, which adds TLS version, HTTP version, and the Cloudflare data center; and (3) what your browser exposes locally via the navigator API. Together they give you a fuller picture than any one source alone.

Question 2

Are these the headers my browser sent to this page?

Accepted Answer

No — and we want to be honest about that. This site is statically exported, which means there is no server runtime that could read the headers from your page-load request. The headers shown are from a separate cross-origin fetch the widget made to httpbin.org after the page loaded. They are a representative sample of what your browser would transmit to any HTTPS endpoint, but they are not the literal headers from your page-load request.

Question 3

Why don't I see Sec-Fetch-User or my cookies?

Accepted Answer

Sec-Fetch-User: ?1 is only sent on user-activated top-level navigations, never on programmatic fetch() calls — so even though your browser sent it when you loaded the page, the cross-origin fetch we make to httpbin doesn't carry it. Cookies for any site other than httpbin.org are also not sent on a cross-origin fetch — that's a basic browser security restriction that protects you from exactly this kind of cross-site read.

Question 4

What are all the Sec-Ch-Ua headers?

Accepted Answer

These are User-Agent Client Hints — a Chromium initiative that splits the legacy User-Agent string into structured pieces. Sec-Ch-Ua tells the server your browser brand and major version, Sec-Ch-Ua-Mobile says whether you're on a phone, Sec-Ch-Ua-Platform names your operating system. Modern Chromium-based browsers (Chrome, Edge, Opera, Brave) send a stripped User-Agent and let servers ask for more detail via these headers. Firefox and Safari currently ignore the proposal.

Question 5

Why are some headers different between the table and what I expected?

Accepted Answer

Browser extensions, content blockers, and corporate proxies all rewrite or strip request headers in ways the browser itself can't see. If a header looks unfamiliar — or if a header you expected is missing — the most common cause is an extension or proxy in between you and the public internet. Comparing the headers httpbin saw against what your browser exposes via navigator (in the Browser-reported card below) is one way to spot rewriting in flight.

Question 6

Is anything I see here stored or sent anywhere?

Accepted Answer

No. The page makes two HTTPS requests on load — one to httpbin.org for the header reflection (with echo.zuplo.io as a fallback) and one to 1.1.1.1 for the Cloudflare edge metadata. Both services see your IP and headers for those requests. Everyday Tools Hub does not log, store, or transmit anything about your visit.

HTTP Headers Viewer

Headers your browser sent

Connection metadata

Browser-reported

How to use this http headers viewer