Test any SOCKS5 or HTTP proxy in seconds: connectivity, exit IP, latency, and whether your real IP is hidden.
This tool routes a request through your proxy to an echo service and reports four things: whether the proxy accepts connections, which IP the target sees (the exit IP), how long the round trip took (latency), and whether the exit IP differs from your real IP, which is the core anonymity test.
The most common causes: wrong port (SOCKS5 gateways often run on 1080), a username/password mismatch, the proxy host only allowing certain source IPs, or the proxy's upstream being offline. If the proxy connects but the request stalls, the exit node is likely overloaded.
Anything under 500 ms is fine for browsing and API calls. 500–1500 ms works but will feel slow for scraping at scale. Above 2000 ms, the proxy is too slow for most automation workloads. Look for a node closer to your target sites.
ProxyBase sells residential SOCKS5 by the gigabyte for crypto: no KYC, credentials delivered through an API, built for AI agents and scrapers. Grab a package at the crypto store and paste the credentials into the checker above.