Proxy Checker
Test up to 1,000 HTTP, HTTPS, SOCKS4 and SOCKS5 proxies at once. Live status, speed, anonymity level and exit country — free, no signup.
Real requests
Every proxy is actually connected to.
Live results
Rows appear as each check finishes.
Free, no signup
Up to 1,000 proxies per check.
Check Your Proxies
Paste your list, one proxy per line. Each one is tested with a real request through it — no guessing.
Accepts ip:port, ip:port:user:pass, user:pass@ip:port and scheme://… — mixed formats in one list are fine. Up to 1,000 per check.
Proxies are tested against Proxyon's own judge endpoint and nothing else. Your list isn't stored after the check finishes.
Proxy Tester: What It Checks
A proxy checker is only worth using if it tests the proxy rather than guessing at it. Every field below comes from a request that actually travelled through your proxy.
Alive or dead
A real HTTP request is routed through the proxy. If it answers within your timeout it's alive; if not you get the reason, not just a red cross.
Working protocol
Auto-detect probes HTTP, SOCKS5, SOCKS4 and HTTPS in turn and reports the one that actually connected — useful when a list is mislabelled.
Anonymity level
Transparent, anonymous or elite, decided from the headers the destination really received, not from the port number.
Latency and speed
Round-trip time to first byte in milliseconds, plus throughput in KB/s from a fixed 100 KB download through the proxy.
Exit IP and country
The address the destination saw, geolocated to a country and ASN, so you can confirm a pool is where the seller says it is.
Failure reason
Timeout, connection refused, auth failed or bad response — enough to tell a dead proxy from a wrong password.
How It Works
Browsers can't open raw sockets through arbitrary proxies, so the test runs server-side. Each proxy gets its own request to a judge endpoint that reports the source IP it saw and mirrors back every header it received.
Paste your list, one proxy per line, in any common format.
Pick a protocol, or leave it on auto-detect.
Hit Check Proxies. Results stream in as they finish.
Copy the working ones or export the full run as CSV.
Anonymity Levels Explained
Anonymity isn't a property you can read off a proxy list. It's decided by what arrives at the other end, which is why the checker inspects the headers the destination actually received.
High anonymity
No proxy-indicating headers and no IP leak. The destination sees an ordinary request from the exit IP and has no way to tell a proxy was involved. This is what you want for scraping, ad verification and account work.
Hides you, announces itself
Your originating IP never reaches the destination, but headers like Via, Forwarded or Proxy-Connection make it obvious a proxy is in the path. Fine for geo-testing, risky anywhere proxies are actively blocked.
No privacy at all
The originating IP is forwarded in X-Forwarded-For, X-Real-IP or Forwarded, so the destination sees both the proxy and the client behind it. Useful for caching, useless for anonymity.
One caveat worth knowing: because the request originates on our server rather than in your browser, the "real IP" a transparent proxy leaks is our checker's address, not yours. That's what makes the leak detectable at all — and it means running the test costs you nothing in exposure.
Supported Protocols
Leave the selector on auto-detect and the checker probes each protocol until one connects. Force a protocol when you already know what you bought and want a straight yes or no.
HTTP
The default for most lists. Requests are forwarded in absolute form, which is also what makes anonymity measurable — the proxy can rewrite headers, and the checker reads what it did.
HTTPS
TLS to the proxy itself, so the connection between you and the proxy is encrypted before any traffic is forwarded. Select it explicitly if your provider issued HTTPS endpoints.
SOCKS5
Protocol-agnostic tunnelling with optional username and password auth. Carries any TCP traffic, not just HTTP, and adds no headers of its own.
SOCKS4
The older SOCKS revision, without password authentication or IPv6 support. Still common on free lists, which is why auto-detect probes for it.
Proxy Speed Test: Why It Matters
Latency and throughput measure different failures
Latency is the round trip to the first byte. It's dominated by distance and by how long the proxy takes to establish its own outbound connection, and it's the number that decides how a session feels: 80 ms is imperceptible, 2,000 ms will time out half the requests in a scraper with default settings. Throughput is how much data the proxy can actually move once the connection is open. A proxy can have excellent latency and terrible throughput if it's oversubscribed — the handshake is quick, the transfer crawls. The checker reports both because a list that looks healthy on latency alone can still be unusable for anything that downloads real pages.
What a good result looks like
Datacenter proxies close to your target should land well under 200 ms with throughput limited mainly by the payload size. Residential proxies route through a real consumer connection, so 300–900 ms is normal and not a fault — you're paying for the IP's reputation, not its speed. Anything past a couple of seconds, or a throughput figure in the low tens of KB/s, usually means the proxy is shared far past its capacity. Run the same list twice a few minutes apart: a pool whose numbers swing wildly between runs is congested rather than merely distant.
Reading the results table
Sort by latency to find your fastest working proxies, then filter by anonymity to keep only the elite ones, then copy what's left straight into your tool. The exit IP and country columns are worth a glance even when everything is green: a "US residential" pool whose exit IPs geolocate to a hosting ASN in a different country is a pool that will get blocked, however fast it tests.
Works With Any Provider
The checker isn't tied to Proxyon infrastructure — test proxies from anywhere, including the ones you're thinking of buying. If the results aren't what the seller promised, Proxyon's residential proxies and datacenter proxies are pay-as-you-go with no subscription. Full breakdown on the pricing page, or clean up a messy list first with the proxy formatter.
Frequently Asked Questions
Everything else you might want to know about checking proxies.
How do I test if a proxy is working?
Paste it into the box above and press Check Proxies. The tool opens a real connection through the proxy to a judge endpoint and reports what came back. If the judge answers within your timeout the proxy is alive, and you also get its exit IP, latency and anonymity level. If it fails you get the reason — timeout, connection refused, auth failed or a bad response.
What is an elite proxy?
An elite (high-anonymity) proxy forwards your request without adding any header that reveals a proxy is in use, and without leaking the originating IP. The destination sees a normal request coming from the proxy's exit IP. An anonymous proxy hides your IP but still announces itself through headers like Via or Forwarded, and a transparent proxy passes your real IP straight through in X-Forwarded-For.
How do I check proxy speed?
Leave the speed test enabled in Settings. After a proxy passes the liveness check the tool downloads a fixed 100 KB payload through it and reports throughput in KB/s, alongside the latency figure — the round-trip time to the first byte. Latency tells you how responsive the proxy will feel; throughput tells you how fast it will move a large page or file.
What proxy formats does the checker accept?
ip:port, ip:port:username:password, username:password@ip:port and any of those with a scheme prefix such as http://, https://, socks4:// or socks5://. You can mix formats in one list — each line is parsed independently, and a line that can't be parsed is marked invalid rather than stopping the run.
How many proxies can I check at once?
Up to 1,000 per run, with concurrency adjustable from 1 to 100 in Settings. Results stream back one row at a time, so you can start copying working proxies before the run finishes. For bigger lists, split them into batches.
Why does a proxy show as dead here when it works in my browser?
Three common reasons: the proxy is IP-authorised and only accepts connections from your own address, not from our checker; it requires credentials you didn't include on the line; or it only accepts CONNECT traffic on 443 and refuses plain HTTP. Try forcing the protocol explicitly and raising the timeout before writing it off.
Do you store the proxies I paste?
No. The list is held in memory for the duration of the check and discarded when the run ends. Credentials are never written to logs, and the results table shows authenticated proxies as host:port (auth) rather than echoing the password back.
Tired of dead proxies?
Proxyon is pay-as-you-go, no subscriptions.