Skip to main content
Antybrowser
Request headers

HTTP Header Checker

See every HTTP header your browser just sent to this page — with plain-English notes on what each one reveals. Free, no signup.

This capture shows what our server received from your request a moment ago. Cookies and authorization headers are never captured or stored.

Every profile should send different headers

Antybrowser profiles each carry their own complete header set — user-agent, Client Hints, languages and privacy flags — consistent per account. Mixed headers across accounts are how platforms link them.

How it works

1. Send a request

Clicking capture sends a normal request from your browser — the same one every site receives when you visit it.

2. Server-side capture

Everything except credentials is recorded server-side, exactly as received — no parsing in between that could hide anything.

3. Annotated report

Each header is grouped and annotated so you can see which ones identify you, which leak location and which are added by the network.

Frequently asked questions

What is an HTTP header?

HTTP headers are the metadata your browser attaches to every request: the user-agent string, accepted languages, privacy flags, fetch context and more. Each request you make carries a full set of them, and the server (and any observer on the path) reads every one.

What does this checker show?

Exactly what our server received from your browser a moment ago — every header except credentials (cookies and authorization headers are never captured or stored). Each header is annotated with what it reveals about you.

Which headers matter for privacy?

The user-agent and Client Hints identify your browser and OS down to the version; accept-language usually reveals your country; x-forwarded-for carries your public IP; DNT and sec-gpc are the only headers where you can signal privacy intent.

Why are some headers not from my browser?

Proxies and CDNs add their own headers on the way (via, x-amzn-trace-id, x-forwarded-for). We label those as infrastructure headers so you can see the difference between what you send and what the network adds.

Do you store these headers?

Reports are kept for 30 days so share links work — minus any credential headers, which are stripped before storage. Raw IPs are never stored; reports are keyed by a salted hash.