Live directory
Free Proxy List
Export list
Loading verified endpoints…
Live directory
Loading verified endpoints…
Four columns decide whether an entry is worth trying. Protocol — HTTP proxies carry web traffic and can read it; SOCKS5 passes any TCP traffic and does not interpret it, which is why it is the one to pick when the software supports it. Anonymity — transparent endpoints forward your address and are useless for anything but caching, anonymous ones announce themselves as proxies, elite ones do neither. Latency is the floor on how slow every request through that endpoint will be. Last checked is the only honest expiry date on the row: a free proxy verified an hour ago is a very different proposition from one verified a minute ago.
Almost none of them are donated. A public proxy is usually a misconfigured server, a device someone compromised, or an endpoint deliberately opened to watch what passes through it. That last category is the reason for the rule that matters most: never send anything through a free proxy that you would mind a stranger reading. No logins, no payment details, no API keys, no session cookies. HTTPS protects the contents of a request, but the operator still sees which hosts you connect to, and an HTTP request through an HTTP proxy is readable in full.
The rest follows from the same fact. Free endpoints appear and disappear within hours, the good ones are shared by thousands of people simultaneously, and their addresses are already in the reputation databases of every large site — which is why a free proxy often fails on exactly the targets you wanted it for.
Checking how a page looks from another country when nothing sensitive is involved.
Testing that your own code handles proxies, timeouts and failures correctly.
Low-volume, non-authenticated requests where a failure costs nothing.
Learning how protocols and anonymity levels differ, with real endpoints rather than a diagram.
Anything that involves an account, a payment or a deadline needs paid proxies — not because free ones are slow, but because nobody is accountable for them. Before relying on any entry here, put it through the proxy checker: the list records what was true at the last check, and the checker tells you what is true now.
Treat them as untrusted. You do not know who runs the endpoint, and some exist specifically to observe the traffic through them. Never pass credentials, payment details or session cookies through a free proxy.
Continuously, and each row carries its own last-checked time. Free endpoints change state within hours, so the time on the row matters more than the fact the address is listed.
Usually it has died since the last check, or it is saturated because it is shared, or the target you are using it against already blocks its address. Re-check the entry before concluding it was never alive.
SOCKS5 when your software supports it: it passes any TCP traffic without interpreting it. HTTP proxies understand the requests they carry, which makes them both more visible to the destination and more revealing to the operator.
That the proxy adds no forwarded address and no proxy header, so the destination cannot tell from the request that a proxy was involved. Anonymous proxies identify themselves without exposing you; transparent ones expose you outright.
For small, tolerant jobs, yes. For anything with a deadline or a volume target, no — uptime is unpredictable and the addresses are widely shared and widely blocked, so you spend more time on retries than the proxies save you.