socks5
The form you will most often be handed on this site. Write it as socks5 followed by the credentials, the host and the port. This is the scheme the proxy listings here actually name.
Loading HstockPlus
Use this page as an online proxy tester: run an HTTP proxy online test or a SOCKS proxy online test (SOCKS4/SOCKS5) through a public probe URL you choose. Test up to 20 proxy lines per run and see latency, bytes, and optional exit IP.
You can paste these shapes into the proxy list. HTTP shorthand is normalized on the server.
SOCKS URLs must include the scheme (socks4:// or socks5://) and slashes.
Must be http or https. Only common web ports are allowed. Hostname must resolve to a public address.
Maximum 20 proxy URLs per run. Credentials are used only for this test and are not stored.
Proxy credentials, proxy URLs, and the probe URL are sent to our API only for this connectivity test and are not stored.
An online proxy tester can only be as good as the lines you give it, and the format is the part people get wrong, and a malformed line looks identical to a dead proxy. These are the three forms the tester accepts.
The form you will most often be handed on this site. Write it as socks5 followed by the credentials, the host and the port. This is the scheme the proxy listings here actually name.
The older variant, still sold and still in use. Same shape as socks5. If a supplier gave you a bare host and port with no scheme, socks4 and socks5 are both worth trying before concluding it is dead.
Accepted, though notably no live proxy listing on this site uses the phrase in its own text. If your line came from elsewhere, this is the scheme it most likely wants.
A proxy has more than two states, and treating the test as pass or fail throws away most of what it told you.
| Result | What it means | What to do |
|---|---|---|
| Answers, low latency | The proxy is reachable and responsive from where the test ran. | Nothing. This is the outcome you wanted, and it is worth recording the number so you can tell later whether it degraded. |
| Answers, high latency | It works and it is slow. Slow proxies pass a check and then fail in use, because the thing you point at them times out rather than errors. | Compare against the others in the same batch. A single slow line among fast ones is usually that line, not the network. |
| No answer | The host did not respond, or the credentials were missing or wrong, or the scheme was wrong. These three look the same from outside. | Re-check the line format first, then the credentials, and only then treat it as dead. |
Measured on the live proxy listings rather than assumed, and the result shapes what this page leads with.
Of the live proxy listings here, well over a third name SOCKS somewhere in their own text, and not one of them uses the phrase http proxy at all. So a buyer arriving from a listing is holding a socks line, and the http field on this page is for lines that came from somewhere else.
Roughly one listing in five names residential. That word describes where the address is registered, not how fast it is and not whether it is shared. Latency is measurable and this page measures it; the rest of the claim is not something any tester can check.
Most people arrive here holding more than one line, and the batch tells you things a single test never can.
When you check proxy list entries side by side, proxy latency becomes readable as a comparison rather than a raw number. One line at four times its neighbours is that line, not your connection, and that is only visible in a batch.
Run your socks5 proxy checker pass and your socks4 proxy test pass separately when a supplier handed you a mixed list. A whole group failing together points at the scheme or the credentials; scattered failures point at the addresses.
An http proxy test on day one is the baseline you compare against in a fortnight, when something has slowed down and you cannot remember whether it always was. Nothing else will tell you later what it used to do.
The honest boundary of this page, stated so nobody reads more into a green result than it carries.
Whether a site can tell you are behind a proxy depends on that site, not on the proxy answering a request. No tester settles it, and any tool claiming to is telling you about one target at one moment.
A shared address can be perfectly fast and already burned by somebody else's traffic. That is the risk with cheap proxies and it does not show up as a latency figure or as an error.