Proxy Judge: Test Any Proxy in Seconds

Free · No signup · Public API

A proxy judge is an HTTP endpoint specifically designed to reflect everything a proxy reveals about its client. Send a request through the proxy you want to test, look at the response, and you instantly learn whether the proxy is alive, how fast it is, what protocol it really speaks, and how much of your identity it forwards to the target.

What our judge reports

• Reachability — does the connection complete at all? Many proxies on public lists are stale within minutes.
• Round-trip latency — how long the TCP + TLS + HTTP round trip took, in milliseconds. Use this to filter for fast exits.
• Detected protocol — HTTP, HTTPS-CONNECT, SOCKS4 or SOCKS5. Mislabelled proxies on public lists are common; the judge tells you the truth.
• Anonymity level
  • Transparent — proxy adds your real IP to X-Forwarded-For or Via headers. The target sees the proxy and you.
  • Anonymous — proxy advertises itself (sends Via:) but hides your IP. The target knows you went through a proxy but not who you are.
  • Elite (high-anonymity) — no proxy-related headers at all. From the target's point of view the proxy is the client.
• Geolocation — country, ASN and ISP for the exit IP, derived from MaxMind GeoLite2.

How it works under the hood

The judge endpoint responds with a deterministic JSON envelope that echoes every header it received plus the connection metadata it can observe. Hitting it through a candidate proxy reveals exactly what a third-party server would see when you scrape it.

# Test a proxy with curl
curl --proxy http://1.2.3.4:8080 https://proxyspace.pro/judge/check

# Test a SOCKS5 proxy
curl --socks5-hostname 1.2.3.4:1080 https://proxyspace.pro/judge/check

When to run a judge

1. Before launching a scrape — filter your candidate list down to proxies that actually pass the latency and anonymity bar you need.
2. While auditing your own infrastructure — make sure your egress proxy doesn't leak X-Forwarded-For when you expect elite anonymity.
3. Debugging a broken pipeline — sometimes a proxy works for HTTP but breaks on HTTPS-CONNECT, or vice versa. The judge tells you which.

Limits and fair use

The judge endpoint is rate-limited per source IP — typically 10 requests per second with a small burst allowance. That is enough for ad-hoc validation but not for replacing a paid validation pool. If you need to validate tens of thousands of proxies an hour, run your own judge: the code path is trivial and the load belongs on your machine, not ours.

→ Compare proxy protocols  ·  → How ProxySpace.pro builds its lists