SOCKS5 Proxy Checker
SOCKS proxies get misreported constantly, a SOCKS5 proxy listed as SOCKS4 will simply fail against tools expecting the wrong handshake. This checker connects using the protocol you specify (socks4, socks5, or auto-detected from the URL prefix) and reports the real result, along with latency, country, and proxy type. Works alongside HTTP/HTTPS proxies in the same batch.
Live checking is discontinued
ProxyChecker.dev no longer runs proxy checks, the API, MCP tools or paid plans. Nothing on this site tests a proxy anymore. The guides below still explain how proxy testing works and what to look for.
Need working proxies? These are the two providers we tested with:
Frequently asked questions
How do I format a SOCKS5 proxy for checking?
Use socks5://ip:port for no-auth proxies, or socks5://user:pass@ip:port for authenticated ones. The checker also accepts ip:port:user:pass style if that's what your list uses.
Why does my SOCKS5 proxy show as dead here but work in my browser?
Browsers sometimes fall back silently between SOCKS versions or retry over a different protocol. This checker connects strictly using the protocol you specify, so a real handshake mismatch will show up as dead here even if a browser masked it.
Does this detect SOCKS4 vs SOCKS5 automatically?
If you don't specify a protocol prefix, it defaults to HTTP. Always prefix SOCKS proxies with socks4:// or socks5:// to get an accurate check.
Is SOCKS5 more anonymous than HTTP proxies?
Not inherently. Anonymity depends on whether the proxy leaks your real IP through headers or DNS requests, which applies to both SOCKS and HTTP proxies. SOCKS5 does support UDP and a wider range of traffic types, which is a separate advantage from anonymity.