Good Proxies

Proxy judges

A curated list of working proxy judges for checking anonymity and debugging your checker pipeline.

Every judge endpoint on this page can be copied individually or all at once in plain text. Instead of a dry URL list, each entry also includes a compact profile so you can choose the right judge for manual debugging, automation or legacy fallback checks.

Judge list Plain text Check flow

Quick list snapshot

Timestamp is taken from the latest update of this page and its curated judge catalog.

4 primary judges
Endpoints 6
HTTPS 5
Azenv / env dump 5
Updated 2026-04-25 00:33

A proxy judge is a server-side script that returns the client HTTP headers. From these headers you can tell whether the proxy hides your real IP. The directory below adds quick context for each endpoint: transport, output format and the best use case.

Working judge endpoints

This denser table helps you pick an endpoint faster: manual debugging, automation, fallback without HTTPS, or cross-checking header dumps.

Judge URL Judge profile Best fit
https://wfuchs.de/azenv.php
Classic Azenv judge in PHP Recommended
Transport: HTTPS Script: Azenv PHP Format: Full ENV dump

Note: A strong primary judge for everyday anonymity checks.

 Baseline manual validation and comparing headers across proxies.
https://www.proxy-listen.de/azenv.php
Azenv mirror Recommended
Transport: HTTPS Script: Azenv PHP Format: Full ENV dump

Note: A convenient backup endpoint when the primary judge is unstable.

 Fallback automation and cross-checking results against a second judge.
https://www.cooleasy.com/azenv.php
Alternative Azenv
Transport: HTTPS Script: Azenv PHP Format: Full ENV dump

Note: Useful as a third independent judge for disputed cases.

 Spot-checking difficult proxies when you want another header source.
http://azenv.net/
The most well-known Azenv Recommended
Transport: HTTP Script: Azenv classic Format: Full ENV dump

Note: Old but compatible endpoint without HTTPS for legacy fallback checks.

 Older scripts, legacy checkers and networks where testing without TLS is useful.
https://httpheader.net/azenv.php
Returns all headers as plain text Recommended
Transport: HTTPS Script: Header dump Format: Readable header output

Note: Useful when the judge is meant for human debugging rather than only machine parsing.

 Manual investigation, demoing extra headers, and checking `Via` / `X-Forwarded-For` quickly.
https://www.proxyjudge.info/azenv.php
Fast European judge
Transport: HTTPS Script: Azenv PHP Format: Full ENV dump

Note: A compact backup judge that fits well into fallback endpoint lists.

 Extra validation in automation pipelines and a reserve judge for CI / cron.

Plain-text list

Copy all judge URLs at once and paste them into your checker.

How to use?

Send a request through the tested proxy to the judge URL. If your real IP appears in the response — the proxy is transparent. If the IP is hidden but there is a Via or X-Forwarded-For header with another IP — the proxy is anonymous. If no extra headers — the proxy is elite.

Anonymity levels

Quick validation flow

  1. 1 Pick 1-2 HTTPS judges for the main validation path and keep one plain HTTP endpoint as a legacy fallback.
  2. 2 Run the same proxy through several judge URLs and check whether the headers are consistent and the real IP stays hidden.
  3. 3 If one judge is unreliable or too terse, keep it as backup and use a more verbose env dump as the primary reference.

How to read the response

  • Your real IP is visible: the proxy is transparent.
  • Your real IP is hidden, but Via / X-Forwarded-For is present: the proxy is anonymous.
  • No extra headers and no real IP: the proxy is elite.

Need already verified proxies?

Full access gives you a ready-to-use live proxy list, filters by type and anonymity, and API access for automation.

Buy access Open proxy list