HTTP and SOCKS5 protocols
Check whether an HTTP CONNECT or SOCKS5 proxy can establish an HTTPS connection. The protocol shown is the one you selected in your input.
Paste one to five proxies to start.
Check whether an HTTP CONNECT or SOCKS5 proxy can establish an HTTPS connection. The protocol shown is the one you selected in your input.
See the public IPv4 or IPv6 address returned through the proxy by a fixed IP echo service. It may differ from the proxy server address.
When GeoIP data is enabled for this site, see the exit IP’s estimated country, region and city. These values describe a database record, not a precise device location.
The measured time includes connecting through the proxy and receiving the HTTPS echo response. It is one sample, not a bandwidth or reliability guarantee.
Enter up to five proxies, one per line, using any format shown above. Select Check proxies to test each line. Credentials are used only for the proxy handshake and are not returned in results.
A successful check confirms that this server reached the fixed HTTPS echo service through the proxy at that moment. A failed check may be caused by authentication, network policy, timeout or proxy availability. The result does not prove anonymity, safety or future uptime.
Compare the proxy products currently available on this site.
Use login:password@host:port, host,port,login,password, an HTTP or SOCKS5 URL with credentials, or host:port:login:password. An unauthenticated host:port also works.
No. This test checks connectivity and the observed exit IP only. It does not test browser leaks, header forwarding, anonymity level or whether another site will accept the proxy.
The address may be unavailable, credentials may be rejected, the proxy may block the HTTPS target, or the connection may time out. Confirm the format and try again before drawing a conclusion.
GeoIP location is an estimate that can be missing or outdated. Response time is a single measurement from this server to the echo service and will vary with network conditions.