Analyzing HTTP headers...

Transparent or poorly configured proxies often add headers that immediately tell the target site an intermediary is in the chain. This analyzer surfaces those headers so you can see whether the proxy looks elite, anonymous, or obviously proxied.

How it works

  1. 1Your request is sent to our endpoint and echoed back with the full header set the server receives.
  2. 2The tool highlights headers commonly inserted by forward proxies, load balancers, and reverse proxies.
  3. 3We grade the exposure level based on whether the header set reveals proxy use, original IPs, or forwarded chains.
  4. 4You can use the result to reject bad IPs or change provider before running sensitive workflows.

What it checks

  • Via, Forwarded, X-Forwarded-For, X-Real-IP, and related headers
  • Exposure of the original client IP in proxy-added chains
  • Header patterns typical for transparent or anonymous proxies
  • Overall anonymity grade from elite to unsafe

Frequently asked questions

Which proxy level is safest for accounts and automation?
Elite is the safest because it does not advertise proxy usage in the HTTP layer. Anonymous can still work for some tasks, but transparent proxies are a poor fit for anything sensitive.
Can a residential IP still send bad proxy headers?
Yes. Residential origin helps, but misconfigured routing can still attach proxy-revealing headers. IP quality and header hygiene are separate checks.
Should I reject every IP that shows Forwarded or Via?
For strict anti-fraud surfaces, yes. For lighter tasks such as basic scraping, the risk depends on the target. But the cleanest setup is still the best long-term default.