Connection status
Distinguish a successful connection from a timeout or authentication error. Format validation alone cannot confirm connectivity.
Get your SOCKS5 proxy list ready for applications and automation tools. Validate endpoints and understand authentication, DNS and connection results.
One proxy per line. Up to 100 entries.
host:port or host:port:username:password
http://username:password@host:port
Also supports https://, socks5:// and bracketed IPv6 addresses. URL schemes override your selected protocol. Percent-encode special characters in URL credentials.
100 proxies / batch · 32 KB input limit · 3-minute batch deadline
Your results will appear here
Explore an example report with connection status, exit IP, location and response time, or validate your list and run a live test when the service is online.
Distinguish a successful connection from a timeout or authentication error. Format validation alone cannot confirm connectivity.
Compare request latency in milliseconds. Distance, destination and network load all affect results.
See the IP exposed to the test destination. Geolocation is approximate and can differ between databases.
A quick guide
Select SOCKS5 for host:port entries or include socks5:// in each URL. A SOCKS5 endpoint needs a client that understands the SOCKS handshake; it cannot be treated as an HTTP proxy.
SOCKS5 can use username/password authentication. DNS may be resolved by the client or by the proxy, depending on the application. Check your application's remote-DNS settings when location matters.
A TCP connection test can verify a SOCKS5 path to a test destination. It does not establish support for UDP traffic, prove DNS privacy in your application or guarantee access to other sites.
Formats, protocols and what a proxy check can tell you.
Explore residential, ISP and mobile proxies, or get help configuring your current endpoints.