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 proxies strip all of these. Check for their presence using this tool.
Critically. An outdated, missing, or headless-browser User-Agent is the easiest way to get blocked. Always use a current, real-browser User-Agent string and rotate it across sessions. This tool shows what your current UA looks like.
Browsers send headers in a consistent order specific to each browser engine. Chrome, Firefox, and Safari each have distinct header orderings. Anti-bot systems detect automation by checking if the header order matches the claimed User-Agent.
Run this check again from a clean all proxy types exit and see what actually reaches the other side.