Free Proxy Checker
A proxy checker tests whether a proxy works and reveals what it exposes about you. Paste any HTTP or SOCKS5 proxy below to see if it is alive, its exit IP, country, ASN, anonymity level and latency - in a couple of seconds, with no signup.
Use it to verify a proxy before you buy, to weed out dead IPs from a list, or to confirm that a proxy hides your real address. Need reliable proxies that always pass these checks? See SotaProxy pricing or explore residential proxies.
How to check a proxy in 3 steps
- Paste your proxy as
host:port,host:port:user:passoruser:pass@host:port. - Pick the protocol - leave it on Auto to detect HTTP or SOCKS5 automatically.
- Press Check proxy and read the exit IP, location, ASN, anonymity and latency.
What each result means
| Field | What it tells you |
|---|---|
| Protocol | Whether the proxy answered over HTTP or SOCKS5. |
| Exit IP | The address the target website actually sees. |
| Location / ASN | Country, city and network operator of the exit IP. |
| Anonymity | Elite (nothing leaked), anonymous (proxy detectable), or transparent (real IP leaked). |
| Latency | Round-trip time through the proxy, in milliseconds. |
The check answers four questions about an address: is it alive, which protocol answers, where it exits, and what it tells the destination about you on the way. Below is how to read the result and what to do with each outcome.
What each line of the result means
The useful part is not that it works, but what exactly it works as.
- Protocol. An address may answer over HTTP, over SOCKS5 or both. If your tool speaks only one and the address answers the other, the connection never opens, and it looks exactly like a dead proxy.
- Exit address. This is what the site will see. If it does not match the country you paid for, there is nothing further to check: that is a question for the provider rather than for your settings.
- Round trip. Time to a test endpoint, not the speed of your collection. Useful for comparing addresses against each other, useless as a promise of throughput.
- Anonymity. A transparent exit inserts your real address into the headers, which makes the geography you bought decoration. An anonymous one does not, but announces itself as a proxy. An elite one does neither.
What to do with each outcome
Three answers cover almost every case.
No answer at all. Check the string format and the credentials first, the protocol second. What is usually dead is not the address but the combination of port and protocol: our static addresses live on 50100 for HTTP and 50101 for SOCKS5, while the rotating gateway is on 10000.
It answers, but the country is wrong. That is either a city request that could not be filled and fell back to country level, or a disagreement between geolocation databases. Trust the target’s behaviour over any lookup.
It answers and looks transparent. It cannot be used for work where geography matters, and no configuration on your side fixes that.
The limits of this check
It answers about the address and says nothing about the target.
A live address in the right country can still be refused by a particular site, because that decision is made on a combination that includes address class, pace, headers and whether scripts run. The checker sees the first of those and none of the rest.
So the same honest test always follows: the same request through two different exits to the site the whole thing exists for. If both get a 403, the addresses were never the problem.