How to check if a proxy is working
- Paste your proxies. One per line, as ip:port, ip:port:login:password, login:password@ip:port or a URL such as socks5://login:password@ip:port.
- Pick the protocol. Auto tries HTTP first, then SOCKS5. Choose HTTP(S) or SOCKS5 to test one protocol only.
- Run the check. We connect through each proxy to an HTTPS page and read the IP address it reports back.
- Read the result. A working proxy shows its exit IP, location, network and latency. A failed one shows the reason.
What the proxy checker tests
| Result | What it means |
|---|---|
| Status | Whether the proxy accepted the connection and the login, and completed an HTTPS request |
| Protocol | HTTP(S) or SOCKS5: the protocol that worked |
| Exit IP | The IP address websites see when you use the proxy |
| Country and city | Where public IP databases place the exit IP; this is approximate |
| ISP and ASN | The network that owns the exit IP, and its autonomous system number |
| IP type | Whether the network belongs to a hosting provider or data centre, or to an internet provider |
| Latency | Time to connect to the proxy, and time for the whole request, measured from our server |
Why a proxy check fails
- Login rejected (407): the login or password is wrong. Copy them again, with no spaces.
- Connection refused: nothing answers on that port. Check the port, and use the HTTP port for HTTP and the SOCKS5 port for SOCKS5.
- Timed out: the proxy did not answer within 10 seconds. It may be offline, busy or far away, or use another protocol.
- IP allow-listing: a proxy that only accepts allow-listed IPs will refuse our checker. Test it with its login, or from your own machine.
- Expired order: proxies stop working at the end of their term. Renew before the end to keep them.
- Private address: the checker only tests proxies on public IP addresses.
Check a proxy from the command line
Our /ip endpoint prints the IP address it sees, so a request through the proxy shows the proxy's exit IP. If the output is your own IP, the proxy is not being used.
curl -x http://LOGIN:PASSWORD@IP:PORT https://t7proxy.com/ip
curl -x socks5h://LOGIN:PASSWORD@IP:SOCKS_PORT https://t7proxy.com/ip
HTTP vs SOCKS5 proxy checks
HTTP proxies are tested with an HTTPS request through a CONNECT tunnel, the way browsers and most tools use them. SOCKS5 proxies are tested with the proxy looking up the host name (socks5h). A proxy that serves both protocols on different ports needs one check per port, each with its own protocol.
Learn how SOCKS5 proxies work →
Is it safe to check my proxy here?
We use the proxy details only for the check you start. They are not saved to a database, a log or a cache, and the result shows only the host and port. The location lookup of the exit IP may be cached for up to 24 hours, as on What is my IP.
Only check proxies you have the right to use.
