Proxy tools
Proxy checker (HTTP and SOCKS5)
Paste your proxies and find out which ones really work: the checker opens a tunnel through each one and reports the exit IP, protocol and response time.
Formats: host:port · host:port:user:pass · user:pass@host:port. Credentials are used only for this test and are not stored.
How it works
What this tool does
We connect to the proxy
Our server opens a TCP connection to your proxy’s public address.
We speak the protocol
It performs an HTTP CONNECT or a SOCKS5 handshake, including username and password where given.
We fetch a reference page
Through the tunnel, it requests an IP-echo service over HTTPS and reads the address it reports.
How to read the result
A result of “Working” means the full path succeeded. The exit IP is the address websites would see; compare it with the proxy’s own IP to understand whether the proxy forwards from a different address.
Common failures: “Authentication failed” (wrong credentials or IP not whitelisted), “Connection refused” (nothing listens on that port), “Timed out” (host offline or filtered) and “Not an HTTP/SOCKS5 proxy” (wrong protocol).
Private, loopback and cloud-metadata addresses are blocked for safety, so you can test public proxies only.
In depth
The details that decide the outcome
What one check does: connect, tunnel, TLS and an exit-IP probe
Each line is parsed, its host name is resolved and every address is required to be public, then the connection is pinned to that verified address. The tool opens a TCP connection with a deadline of about eight seconds, performs an HTTP CONNECT or a SOCKS5 handshake to api.ipify.org on port 443, starts TLS 1.2 or later through the tunnel, sends a short GET and reads the IP that the echo service reports. All of those steps share one deadline, so a proxy that connects but then stalls still fails.
Auto mode runs the HTTP and the SOCKS5 probe at the same time, each with a six-second limit, and reports whichever succeeds. If both fail, it shows the most informative error: an authentication or refusal error outranks “not a SOCKS5 proxy”, so a wrong-protocol probe cannot hide a bad password. Up to ten proxies are accepted per request and three are tested in parallel, so in the worst case ten dead proxies in auto mode take roughly four rounds of six seconds, about 24 seconds. The table shows protocol, exit IP and total time.
Accepted line format
host:portfor proxies without credentials.host:port:user:pass, exactly four colon-separated fields.user:pass@host:port, which tolerates colons in the password.scheme://user:pass@host:port, where the scheme prefix is ignored and the protocol comes from the mode you choose.
Reading results and errors: a worked triage
Suppose you paste four lines. Line one shows Working, protocol HTTP, an exit IP different from the proxy host and 410 ms. Line two shows Authentication failed, line three Timed out and line four Not an HTTP proxy. The 410 ms is the whole sequence run from this site’s server: name resolution, TCP, the CONNECT exchange, a TLS handshake and one HTTPS request. Several round trips are included, so it is not comparable with an ICMP ping and mostly reflects the distance between this server and the proxy. Use it to compare proxies against each other.
Then triage each failure. Authentication failed means wrong credentials or a proxy that identifies you by whitelisted IP address. Because the test request comes from this site’s server, not from your network, a whitelist-only proxy will usually fail here even though it works for you, so test it with curl from your own machine. Timed out means no answer within the deadline: check the host, the port and any firewall in the path. Not an HTTP proxy means the endpoint speaks something else, usually SOCKS5, so switch the mode to SOCKS5 or Auto.
| Result (error code) | Typical cause | Next step |
|---|---|---|
| Authentication failed (auth) | Wrong user or password, or whitelist-only access | Re-enter credentials exactly; test whitelisted proxies from your own network. |
| Connection refused (refused) | Nothing listens on that port | Check the port number and that the service is running. |
| Timed out (timeout) | Host offline, firewalled or very slow | Run the port checker, then review firewall rules. |
| Not an HTTP or SOCKS5 proxy (not_http_proxy, not_socks5) | Wrong protocol for that port | Switch to the other mode or use Auto. |
| Tunnel refused (connect_denied) | The proxy accepted you but denies the destination | Check the account status and any destination rules. |
| TLS failed or no response (tls, no_response) | The tunnel opened but the secure request failed or returned no IP | Retry once; if it repeats, ask the provider. |
Credentials reach the proxy the way the protocol defines: HTTP Basic or SOCKS5 username and password, both readable on the wire when the proxy port is not encrypted. Use credentials you can rotate.
FAQ
Tool questions
Are my credentials saved?
No. They are used for the test request and then discarded.
Why can’t I test a proxy on my LAN?
The server only connects to public internet addresses to avoid being used to reach private networks.
How many proxies per check?
Up to 10, with a per-minute rate limit.
Why can a proxy that works in my browser fail here?
The test runs from this site’s server, not from your device. Whitelist-only access, a firewall that admits only your network, a port that needs a different protocol, or the eight-second deadline can each make a proxy fail here yet work for you. Retest from your own machine with curl through the proxy.
How should I use the latency figure?
As a relative number. It covers resolution, connection, handshake, TLS and one HTTPS request from this server, so it includes the distance between this server and the proxy. Compare several proxies in the same run, and measure from your own location against your real target when planning.
Not sure which plan fits?
Describe your use case and target countries and we will recommend a product — or tell you honestly when another type suits you better.