How to check if a proxy works
A proxy “works” when it accepts your connection and successfully relays traffic to a target. A good check goes further and tells you how it works: how fast, what it exposes, and where it exits.
What gets tested
- Connectivity — can we open the proxy and complete a request through it? Failures are reported with a specific reason such as timeout, refused, auth failed or bad tunnel.
- Speed — connect time, time-to-first-byte and a small throughput sample. This is a quick diagnostic, not a full bandwidth benchmark.
- Protocol — whether it speaks HTTP, HTTPS (CONNECT) or SOCKS5. See proxy types.
- Anonymity — which forwarding headers it leaks. See anonymity levels.
- Exit IP & location — the address the destination actually sees, plus its network, country and risk signals.
Accepted formats
Paste one proxy per line in any of: ip:port, ip:port:user:pass,
user:pass@ip:port, or with a scheme like socks5://ip:port. Protocol is
auto-detected unless you pick one.
Reading the results
Working proxies appear under Good with their speed, anonymity, exit IP and location; failures appear under Bad with the reason. Export the working list as CSV or copy it straight from the results.
Frequently asked questions
What is the quickest way to check a free proxy list?
Paste the list into the bulk proxy checker, let protocol auto-detect run, then keep only the rows that come back working with an exit IP and acceptable latency.
Why does a proxy fail even when the host answers a TCP port scan?
A listening port does not prove the endpoint speaks the protocol you expect. The checker still has to complete an HTTP, HTTPS CONNECT or SOCKS5 round-trip through it.