Core Tools
Proxy Leak Test
Detect proxy forwarding leaks, origin mismatch, and anonymity risk.
Proxy Leak Test checks whether a proxy exposes signals that reduce anonymity or indicate unexpected routing behavior.
What It Looks For
| Signal | Meaning |
|---|---|
| Via | The target saw a Via header, often indicating proxy traversal. |
| Forwarded | The target saw a standardized forwarding header. |
| X-Forwarded-For | The target saw a header that may include client or proxy IPs. |
| Proxy-Authorization | Proxy credentials may have reached the target side. |
| Origin mismatch | The target-reported origin does not match the observed exit IP. |
Inputs
Use a checked or benchmarked list. Leak testing dead or unstable proxies wastes time and can hide the useful signal.
Recommended Controls
| Control | Recommendation |
|---|---|
| Protocol hint | Auto for mixed lists. |
| Target URL | Keep the default inspectable JSON endpoint unless you operate a compatible target. |
| Resolve country | Enable when final filtering includes geography or network type. |
| Timeout | Match checker timeout for comparable results. |
The target must return inspectable JSON with headers and origin information.
Anonymity Labels
| Label | Meaning |
|---|---|
| Elite | No configured leak signals were detected. |
| Anonymous | The proxy works, but the signal set is not fully clean. |
| Transparent | Forwarding headers expose proxy behavior. |
| Unknown | The test could not classify the result confidently. |
Result Review
Start with:
- status
- leak count
- leak signals
- anonymity
- exit IP and origin value
- latency
Details That Matter
| Feature | Detail |
|---|---|
| Inputs | Single proxy, many proxies, file, pool, and handoff rows. |
| Target contract | The default endpoint is httpbin-style and must expose inspectable JSON, request headers, and origin. |
| Signals | Tracks via, forwarded, x-forwarded-for, proxy-authorization, and origin-mismatch. |
| Sorting | Leak signal lists are sorted so repeated runs are easy to compare. |
| Classification | Transparent if forwarding headers expose traversal, elite if no leak signals exist, anonymous for other working cases. |
| Enrichment | Includes exit IP and country/location fields when resolution is enabled. |
| Summary | Tested, clean, leaked, transparent, and average latency metrics help compare pools quickly. |
Treat leaked rows as unsuitable for workflows where anonymity is the reason for using a proxy.
Best Next Steps
- Save clean rows to a final pool.
- Use Proxy Viewer on surprising results.
- Re-run leak tests against a target you control when the default inspection endpoint is not representative.