Proxy checker
Paste your list and see which proxies are actually live, with real latency and exit country. Supports HTTP, HTTPS and SOCKS.
How this checker works
Paste up to twenty proxies, pick the protocol, and each one is opened from our server rather than from your browser.
We make a real connection through the proxy, fetch an address-echo endpoint on the other side, and report what came back: whether it answered, how long it took, the country it exited in, and the exit IP itself.
That last field is the one worth looking at. A proxy can accept your connection and still route you out through an address you did not expect — a stale rotation, a mislabelled country, a supplier reselling the same subnet twice.
Comparing the exit IP you got against the one you were sold takes two seconds and catches the difference.
HTTP, HTTPS, SOCKS4 and SOCKS5 all work, with or without a username and password. Each proxy gets six seconds before it is called a timeout, and eight run at once.
A batch is limited to twenty with twelve batches a minute — enough to sweep a few hundred addresses in a sitting, and bounded so the tool cannot be pointed at somebody else's network as a scanner.
What each result means
Online
The proxy accepted the connection and returned an address. It is alive and it forwards traffic. It does not mean your target site will accept it — see the limits below.
Timeout
Nothing came back within six seconds. Usually an overloaded or half-dead proxy, sometimes a firewall dropping packets silently. Worth a second run before you write it off: a proxy that times out twice is not coming back.
Offline
The connection was actively refused or the handshake failed. Wrong port, wrong protocol, expired credentials, or the proxy is simply gone. Check the protocol first — a SOCKS5 proxy tested as HTTP fails exactly like a dead one.
Invalid
The line could not be read as a proxy, or the host resolves to a private or reserved address. The second case is refused deliberately: this tool will not open connections into internal networks.
What this tool cannot tell you
Every checker in this category reports the same four states and stops there. These are the cases where a green result still leaves you with a problem, and knowing them is worth more than the check itself.
IP-whitelisted proxies will fail here
If your proxy trusts your own address instead of a password, our server is not on that list and the check comes back offline. That is a correct result for us and a wrong answer about your proxy. Test those with credentials, or from the machine that is whitelisted.
Alive is not the same as unblocked
We measure whether the proxy forwards traffic, not what your target thinks of it. A datacenter address can pass every check here and still collect a captcha on the first request to a protected site. The only test that settles that is your own target.
One reading, one moment
Latency depends on the route between our server and the proxy, which is not the route from your machine. Use the numbers to compare proxies against each other in the same batch, not as an absolute figure for your setup.
Country comes from the exit address
We report where the exit IP is registered, which is what a site sees. That can differ from where the hardware physically sits, and both can differ from what the seller wrote on the invoice.
Proxy checker questions
The things people ask before they paste a list in.
Paste it as host:port, choose the protocol, and run the check. Working means three things at once: the connection is accepted, an exit address comes back, and that address is the one you expected. A checker that only reports up or down answers the first of the three.
Yes, and there is no account. The limits are twenty proxies per batch and twelve batches a minute, which exist to keep the tool from being used as a port scanner rather than to push you toward a plan.
HTTP, HTTPS, SOCKS4 and SOCKS5, each with optional username and password authentication. If a proxy fails, check the protocol before anything else — testing a SOCKS5 proxy as HTTP produces exactly the same failure as a dead proxy.
Almost always IP authentication. The proxy is configured to trust your address, our server checks from a different one, and it is refused. Switch that proxy to username and password to test it here, or check it from the whitelisted machine.
No. The list is used for the check and not written to a database. We do keep ordinary request logs, and given that credentials pass through a form, use a throwaway password if the proxy is not yours.
Twenty in one batch, and twelve batches a minute. Eight run in parallel, so a full batch of twenty finishes in a few seconds unless several of them are timing out.
Round-trip time from our server, through the proxy, to the echo endpoint and back. It is useful for ranking proxies within one batch. It is not the latency you will see, because your route to the proxy is a different one.
Because those are separate questions. This tool asks whether the proxy forwards traffic; the site asks who owns the address and how the session behaves. Datacenter ranges commonly pass the first and fail the second — a residential or ISP address is what changes that answer.