SOCKS5 proxy tester
Get your SOCKS5 proxy list ready for applications and automation tools. Validate endpoints and understand authentication, DNS and connection results.
- Up to 100 proxies/batch
- HTTP/S & SOCKS5
- Format checks run in your browser
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.
Results
Results stream in here
Each proxy shows its status, exit IP, location and response time, and lands on the radar by speed. Paste a list and run a test, or preview an example report.
What a check tells you
Connection status
Distinguish a successful connection from a timeout or authentication error. Format validation alone cannot confirm connectivity.
Response time
Compare request latency in milliseconds. Distance, destination and network load all affect results.
Exit IP & location
See the IP exposed to the test destination. Geolocation is approximate and can differ between databases.
Testing SOCKS5 proxies
Use the right protocol
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.
Check credentials and DNS
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.
Understand the test's scope
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.
Validate your list locally, then select Test proxies when the page shows Live testing online. A separate worker checks connectivity, response time and exit IP. If the service is offline, you can still validate formats and view clearly labelled example results.
Use one proxy per line: host:port, host:port:username:password, or protocol://username:password@host:port. Explicit HTTP, HTTPS and SOCKS5 URL schemes take precedence over the selected protocol. Put IPv6 addresses in square brackets and percent-encode special characters in URL credentials.
Each batch accepts up to 100 entries and 32 KB. Duplicate entries are removed. Live tests allow up to 5 batches per minute, 20 per 10 minutes and 2,000 proxy checks per hour per public IP, with one active batch at a time. Shared connections share these limits.
Format validation runs locally without uploading your list. Starting a live test sends your endpoints and credentials to the testing service. Queue payloads are encrypted, expire after 15 minutes and are removed after processing. Credentials are never included in results or CSV exports, and the list is not saved in browser storage.
SOCKS5 does not encrypt traffic by itself. HTTPS or another encrypted application protocol protects the connection's content. Standard SOCKS5 username/password authentication is also not encrypted by the SOCKS protocol.
A successful TCP check does not verify UDP support. UDP requires a separate SOCKS5 UDP ASSOCIATE test and depends on both the provider and client application.
Ready for your next proxy?
Residential, ISP and mobile proxies, or help configuring the endpoints you already have.