Proxy tools
SOCKS5 proxy checker
Verify SOCKS5 proxies against the actual protocol: negotiation, authentication and a tunnelled request that proves traffic flows.
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
Method negotiation
We offer no-auth, and username/password if you provided credentials.
CONNECT by name
We ask the proxy to connect to a reference host by domain, which also tests remote DNS.
Tunnelled TLS request
We complete a TLS request through the tunnel and read the exit IP.
How to read the result
If negotiation fails the endpoint is probably not a SOCKS5 server — try the HTTP checker.
SOCKS5 UDP is not tested; this checker verifies TCP tunnelling.
In depth
The details that decide the outcome
The SOCKS5 handshake, step by step (RFC 1928 and RFC 1929)
The client opens with a greeting: version 5, the number of methods and the methods themselves. Without credentials this tool offers only “no authentication”; with credentials it offers “no authentication” and “username/password”. The server replies with the method it picked. A reply starting with anything other than version 5 means the endpoint is not SOCKS5, and the value 255 means no offered method is acceptable. If the server picks username/password, the client sends a short sub-negotiation containing the user name and password, and a status of zero means success.
Next comes the request: version 5, command CONNECT, and the destination as a domain name, here api.ipify.org on port 443. Sending the name rather than an address is remote DNS: the proxy resolves it, so your own resolver is not involved and a pass also shows the proxy’s resolver works. The reply carries a result code, where zero is success and other values mean refusal, such as a ruleset block or an unreachable network, and the tool reports that as connect_denied. Only TCP CONNECT is exercised. UDP ASSOCIATE, the command used for UDP traffic, is never tested.
| Step | Client sends (hex) | Server answers |
|---|---|---|
| Greeting | 05 01 00, or 05 02 00 02 when credentials are given | 05 followed by the chosen method: 00, 02 or FF |
| Authentication, only if method 02 | 01, name length, name, password length, password | 01 00 for success |
| Connect request | 05 01 00 03, name length, api.ipify.org, port 443 | 05, a result code, 00, then the bound address |
Worked reading: three common SOCKS5 outcomes
Case one, authentication. If you supplied credentials and the server rejects them, you get an authentication failure. You get the same result if you supplied none and the server demands a password, or if it offers only methods you did not propose. Whitelist-based servers add a twist: they may accept your own address without a password but offer nothing to this site’s server, so the check fails here although your client works. Next steps are to confirm the user name and password character by character, then retest from your own network with curl.
Case two, refusal after login: the proxy authenticated you, then denied the CONNECT, which points to account status, destination rules or routing rather than credentials. Case three, wrong protocol or port: an HTTP proxy that receives the three-byte greeting typically closes the connection or answers with an HTTP error, which appears as a closed connection or “not a SOCKS5 proxy”. Switch to the HTTP checker or Auto mode. If the check passes but your game or app still fails, the cause is usually UDP, a client that resolves names locally, or application-level proxy support.
FAQ
Tool questions
Does it test UDP?
No, only TCP CONNECT.
Does it support SOCKS4?
No — SOCKS5 only.
What does remote DNS mean here?
The proxy resolves the target’s name, so your own DNS is not involved.
What is the difference between socks5 and socks5h in client settings?
In curl and many libraries, a socks5 setting resolves the host name locally and sends an address to the proxy, while socks5h sends the name so the proxy resolves it. This checker always sends the name, so it proves remote DNS works at the proxy. If your client resolves locally, its DNS queries bypass the proxy.
My game needs UDP. Does a pass here prove it will work?
No. The checker exercises TCP CONNECT only. The mobile plans list UDP over SOCKS5 and gaming plans offer SOCKS5 at checkout, but no ping or compatibility is guaranteed for games, so test inside the game client with a small plan first.
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.