Leak test & benchmark

Find proxies that quietly reveal your real address, and measure not just how fast a proxy is but how consistently it performs — every signal and result field.

2 Min. LesezeitDiese Anleitung gibt es nur auf Englisch.

Once you know which proxies are alive, two tools tell you which ones are actually good: one checks that a proxy keeps your identity to itself, the other checks that it is fast and stays fast.

A proxy is only useful for privacy work if it does not give you away. Some proxies quietly attach signs that reveal they are a proxy — or worse, reveal your real address — in the background of every request.

Leak test dials each proxy and inspects what came back for four tell-tale signals, plus one direct check:

Signal	What it means when present
`Via` header	The proxy identified itself to the destination as a proxy.
`Forwarded` header	The proxy passed along forwarding metadata — potentially including your address.
`X-Forwarded-For` header	The proxy explicitly attached an originating address.
`Proxy-Authorization` header	The proxy leaked its own auth header downstream instead of stripping it.
Origin mismatch	The address the destination sees does not match the proxy's own exit address — a sign your real address slipped through.

Each of these that fires is added to a leak signal list, and the total count becomes the proxy's leak severity — the more signals present, the worse the leak. A clean proxy shows none of them and no origin mismatch. The result also carries the usual identity fields (protocol, latency, exit IP, geo, anonymity) so you can see leak severity alongside everything else you already know about the proxy.

Alive and fast-once are not the same as reliably fast. Benchmark dials a proxy multiple times in a row and reports the spread of its response times, not just a single reading.

This matters because a proxy can look quick on one lucky request and then stall on the next. Benchmark's result carries:

Field	What it tells you
Pass / fail / total runs	How many of the repeated dials actually succeeded.
Success rate	Pass count over total, as a percentage.
Average latency	The mean response time across all successful runs.
Best / worst latency	The fastest and slowest individual run — the spread between them is the "how consistent is it" read.
HTTPS support	Whether the proxy carried secure traffic.
Exit IP + geo	Where the proxy actually exits, same as Check.
Last error	The most recent failure reason, if any runs failed.

A tight gap between best and worst means the proxy is consistently fast; a wide gap means it is only occasionally lucky. Benchmark labels results so you can compare candidates at a glance and pick the ones that will hold up under real, sustained use — not just a single test request.