Proxy checker: is your proxy working?
Our server sends one real request through the proxy you enter, then shows whether it worked, how long it took and which IP address came out the other end.
How to use it, and what the result means
Copy the details exactly as your proxy provider gave them. Three layouts work: ip:port, ip:port:user:pass and user:pass@ip:port, and a host name can stand in for the IP. Then choose the protocol, which is the way your app talks to the proxy. The box starts on HTTP; switch to HTTPS or SOCKS5 only if your provider's details name one of those.
- Latency: how long the whole test took, in milliseconds (thousandths of a second). It covers reaching the proxy and the proxy fetching a small test page, so expect it to be higher than a ping.
- Exit IP: the address websites will see while you use this proxy. It can differ from the IP you typed, because many providers send your traffic out through another address.
- An error: usually a typo in the address or port, a wrong username or password, or the wrong protocol. If the message includes the number 407, the proxy didn't accept your username and password.
A working result means the proxy passed on one request from our server. It doesn't show where the IP is located or how private your setup is; the IP location lookup and the anonymity checker cover those.
To find the exit IP, our server asks api.ipify.org, a public service that reports the IP it sees, through your proxy. We don't keep the proxy details you enter. Only proxies on the public internet can be checked.
