How to Check if a Proxy Is Working (5 Quick Tests)

A proxy that "works" can still fail you. It may connect but be slow, exit in the wrong country, rotate when you need it to stay put, or be blocked by the one site you care about. Five quick tests tell you most of what you need to know before you commit a project or a payment to it.

1. Check that it connects and signs in

Enter the proxy into the proxy checker as host:port, adding the username and password if it uses them. The tool opens a tunnel through the proxy and fetches a page over HTTPS. If that succeeds, the proxy is alive and your credentials are accepted. If it fails, the message names the cause, and our guide to proxy errors 407, 403 and 502 explains each one.

2. Confirm the exit IP and country

The exit IP is the address websites see. It should differ from your own and sit in the country, and if you paid for it the city, that you chose. The checker shows it with its location, network owner and ASN. To look at any address in more detail, paste it into the IP lookup. Location databases disagree and are approximate, so a city that is off by a hundred miles is normal, while the wrong country is a real problem.

3. Check what kind of network it is

A proxy sold as residential should not sit on a hosting company's network. The IP reputation check classifies the owner as a hosting or data center network, a known VPN or proxy network, or a likely home or mobile provider, and tells you if the address is a Tor exit or is listed on spam blocklists. These are indicators, not proof. Residential proxies can look like any home connection, which is why they work, and datacenter proxies are easy to spot, which is why some sites block them. See residential vs datacenter proxies.

4. Run several requests, not one

One good request proves little. The checker makes three on separate connections, so you can see the success rate and whether the exit IP stays the same. A rotating proxy should show different addresses, and a static or sticky one should show the same address. If a proxy fails one request in three here, expect worse under load. Read rotating vs sticky proxies for what each result means.

5. Test the site you actually need

Many proxies work on test pages and fail on the website you bought them for, because that site blocks the network or rate-limits it. Enter the site's HTTPS address in the optional website field of the checker. A 200 means it let the proxy in. A 403, 429 or 503 means it is blocking or throttling that proxy, which no speed result will reveal.

Test from your own machine with cURL

A command-line check confirms a proxy from the machine that will use it. For an HTTP proxy, run curl -x http://user:password@host:port https://www.cloudflare.com/cdn-cgi/trace. For SOCKS5, run curl -x socks5h://user:password@host:port https://www.cloudflare.com/cdn-cgi/trace. The reply includes a line starting with ip=, which is the exit IP. If a password contains characters such as @ or :, write them as %40 and %3A in the URL.

What a quick test cannot prove

A free online test runs from one place for a few seconds. It cannot tell you how a proxy behaves over a day, how many of its IPs are already burned on your target, or how it handles heavy traffic. Treat it as a screening step, then run a small trial on your real workload before you buy more. To measure speed properly, follow how to test proxy speed.