About ProxySpace

Who runs it

ProxySpace is built and run by one person, bribe. It started in 2022 for a selfish reason: I needed proxies for my own projects, and every list I found was either buried under ads, behind a sign-up, or quietly abandoned. So I wrote a script that pulled the public lists together, cleaned them up and put them in one plain file. The name came with it: one quiet corner of space where all those scattered proxies end up.

Other people started fetching the files too, and then their scripts did. Today the same small setup answers hundreds of thousands of requests a day, still free, still without accounts. The proxy judge, the IP ranges and the tools grew out of the same itch: things I needed myself and could not find in a form I liked.

What I hold myself to: no fake claims (the lists are not tested, so the site does not say they are), data straight from the source where one exists (the regional registries and the providers’ own feeds), and every file reachable at the same address for as long as the site runs. The servers are in the EU, in Germany.

How the lists are built

1. Collect. Every 20 minutes we collect proxies from 21 sources, grouped by protocol.
2. Clean. We keep only lines that are a valid IPv4 address and port, and remove duplicates across sources.
3. Publish. The result replaces /http.txt, /https.txt, /socks4.txt and /socks5.txt. New addresses are also appended to the archive.
4. Locate. Each address is matched to the country its IP is registered in, which feeds the per-country lists.

What we do not do

We do not test whether each proxy is online, fast or anonymous. Public proxies come and go within minutes and a large share of any list is dead. If you need working proxies, filter the list yourself, for example with the proxy judge, or use a paid provider.

Who uses it

In the last 24 hours the lists were downloaded 527,516 times and the judge answered 646,670 requests, mostly from scripts and proxy checkers in 161 countries.

What we log

Like any web server, ours keeps access logs with the requesting IP address, time, path and user agent. We use them to keep the service running and to block abuse, keep them for a limited time and do not sell or share them. Page views are counted with a cookieless analytics script.

Contact

Updates go out on the Telegram channel. Questions, abuse reports or requests: message the maintainer. The changelog lists what changed and when.