Skip to content
IPOK

My HTTP Request Headers · Browser Self-check

On every request your browser announces a set of headers: User-Agent, Accept-Language (language preference), Accept-Encoding, sec-ch-ua (client hints) and more. This tool shows them verbatim — the server only echoes, never stores.

More importantly it compares your Accept-Language with your exit IP's country: if the language preference says zh-CN but the exit IP is in the US, that mismatch is one of the ways platforms cross-check and correlate accounts. For multi-account work, changing the UA but not the language header — or a language header that doesn't match the IP — still gives you away.

These are the headers your browser actually sent on this request (echoed verbatim, not stored):

Reading your request headers…

Headers like Accept-Language and sec-ch-ua (client hints) are profiling material, just like UA and timezone. Changing the UA but not the language header — or a language header that doesn't match the exit IP — still gives you away.

Check whether my IP + browser disguise are all self-consistent →
Check your own IP — purity, risk score, native vs datacenter, leaksCheck IP →

FAQ

What is Accept-Language and why does it matter?

It's the language preference your browser declares (e.g. zh-CN,zh;q=0.9). Platforms cross-check it against exit-IP geo; a mismatch is an anomaly / proxy signal.

Do you store these request headers?

No. The server only echoes the headers from this request — no logging, no storage — and only a fingerprint-relevant whitelist (never cookies or other sensitive headers).

How do I make my headers consistent with my IP?

Language, timezone, UA and exit-IP geo should all agree. Run this site's IP + browser disguise check for a full self-audit.

More tools