View the HTTP request headers your browser sends to websites, including User-Agent, Accept, and proxy-revealing headers.
Click "Show My Headers" to display the HTTP headers your browser sends.
Review each header for proxy-revealing values (X-Forwarded-For, Via).
Compare your headers against a standard browser profile to spot anomalies.
All HTTP request headers including User-Agent, Accept, Accept-Language, Accept-Encoding, Connection, and any proxy-added headers like X-Forwarded-For, Via, or X-Real-IP that reveal proxy usage.
Header fingerprinting is a primary anti-bot technique. Missing headers, unusual orderings, or automation-specific values (like a headless Chrome User-Agent) immediately flag traffic as non-human. Proxy users must ensure their headers look natural and that no forwarding headers leak their setup.
The tool reads the browser navigator properties and constructs the header set that would be sent with a typical fetch request. It also uses the Navigation API and Performance API to detect additional header behaviors. For a complete server-side view, the tool can optionally hit an echo endpoint that returns the exact headers received.
The main proxy-revealing headers are X-Forwarded-For (contains your real IP), Via (names the proxy server), X-Real-IP, and Forwarded. Elite (high-anonymity) proxies strip all of these before forwarding your request. Check for their presence in your own traffic using the header viewer above.
Critically. An outdated, missing, or headless-browser User-Agent is the easiest way to get blocked by anti-bot systems. Always use a current, real-browser User-Agent string and rotate it across sessions to avoid patterns. This tool shows exactly what your current UA string looks like.
Browsers send HTTP headers in a consistent, predictable order specific to each rendering engine. Chrome, Firefox, and Safari each produce distinct header orderings for the same request type. Anti-bot systems detect automation by checking whether the header order actually matches the User-Agent a request claims.
Run this check again from a clean all proxy types exit and see what actually reaches the other side.