The free proxy list that is actually verified.
π Download Β· β‘ Pro API Β· π What does an AI agent cost to run? Β· π¬ Which country do you need? Β· π Issues
English Β· δΈζ Β· ζ₯ζ¬θͺ Β· νκ΅μ΄ Β· EspaΓ±ol Β· PortuguΓͺs Β· Π ΡΡΡΠΊΠΈΠΉ Β· TΓΌrkΓ§e Β· Bahasa Indonesia Β· TiαΊΏng Viα»t
Public snapshot Β· updated every 30 minutes Β· no signup
A while back I was building a small price-tracking scraper. Every run kept getting rate-limited from my single IP, so I went looking for free proxies. Every list told the same story: half the entries were dead, the "updated daily" ones had not moved in months, and the sites with working proxies wanted a credit card before I could even test one.
I already ran automated health checks for my own scraping, so I started publishing the results β a free proxy list that is actually verified, re-checked every 30 minutes, and pullable from a stable CDN link. No signup, no credit card, no dashboard. That is all this is. If it saves you the afternoon I lost, a star helps the next developer find it. The data is free either way.
One command per format. Stable paths that never move.
# All proxies
curl -sL https://raw.githubusercontent.com/xyzs996/free-proxy-health-list/main/all.txt -o proxies.txt
# SOCKS5
curl -sL https://raw.githubusercontent.com/xyzs996/free-proxy-health-list/main/socks5.txt -o socks5.txt| List | Proxies | TXT | JSON | CSV | CDN |
|---|---|---|---|---|---|
| All proxies | 4,382 |
TXT | JSON | CSV | jsDelivr |
| HTTP | 1,449 |
TXT | JSON | CSV | jsDelivr |
| HTTPS | 1,429 |
TXT | JSON | CSV | jsDelivr |
| SOCKS4 | 932 |
TXT | JSON | CSV | jsDelivr |
| SOCKS5 | 572 |
TXT | JSON | CSV | jsDelivr |
| Fast proxies | 1,000 |
TXT | JSON | CSV | jsDelivr |
| Stable proxies | 1,915 |
TXT | JSON | CSV | jsDelivr |
| Elite proxies | 2,949 |
TXT | JSON | CSV | jsDelivr |
Browse by country: Indonesia, United States, Philippines, India, Mexico, China, Russia, Canada, Brazil, Bangladesh, Japan, Colombia, Vietnam, Singapore, Hong Kong, South Africa, Germany, Ecuador, Thailand, Venezuela, Turkey, South Korea, Netherlands, Pakistan β View all
Most proxy lists claim to be verified and none publish a number. This one does: a sample drawn evenly from each protocol is fetched end to end through each proxy against a third-party URL, and the result ships with the data. Drawing evenly measures every protocol equally well, so the headline is an average over protocols rather than the rate of the list; the snapshot carries both numbers.
| List | Working in sample |
|---|---|
| Latest sample | 42% (sampled 400) |
Method: sample drawn evenly per protocol, end-to-end fetch through the proxy, 8s timeout. The headline is that sample; listSuccessRate in stats/reliability.json re-weights it by how many of each protocol were published. β http://api.ipify.org/, http://icanhazip.com/, https://api.ipify.org/, https://icanhazip.com/
- Proxies for web scraping β Rotate IPs to avoid rate limits and IP bans.
- Python requests proxy β HTTP and SOCKS5 examples with retry handling.
- Build a rotating proxy pool β A working rotation loop in about 20 lines.
- Scrapy proxy middleware β Drop-in middleware that rotates on failure.
- curl proxy flags β HTTP, HTTPS and SOCKS flags with real commands.
- HTTP β Simplest for web requests. Works with every HTTP client.
- HTTPS β HTTP proxies verified to tunnel TLS via CONNECT.
- SOCKS4 β Lightweight legacy tunnel for raw TCP.
- SOCKS5 β Any TCP traffic, plus UDP and remote DNS.
data.txt holds one host:port per line. data.json carries the health metadata behind every entry:
{
"proxy": "203.0.113.10:8080",
"host": "203.0.113.10",
"port": 8080,
"protocol": "http",
"latencyMs": 842,
"qualityScore": 91,
"checkType": "http_probe",
"supportsHttps": true,
"country": "US",
"anonymity": "elite",
"consecutiveSuccesses": 4,
"reliabilityScore": 96.75,
"reliabilitySamples": 41,
"lastChecked": "2026-07-25T11:09:35Z"
}Reading this with a program? llms.txt is the whole snapshot in one request β every list with its count, its download URLs and the date it was checked.
Same maintainer, same idea β public data you can read without an account:
- Free LLM API list β permanent free tiers, every published limit linked to its official source.
- LLM API pricing list β the list price on a row is not the price of a request. It keeps the column other price tables drop: the second, higher rate card that switches on once the prompt gets long β and that one bills every token in the request, not only the ones past the threshold. Every figure from the write-ups is in one table too, each row carrying the sentence it came from (JSON / CSV). Start with where the token bill actually goes.
Are these free proxies safe to use?
Free public proxies are shared and run by unknown operators, so never send passwords, tokens or personal data through them. Use them for testing, scraping public pages and automation β not sensitive traffic.
How often is the proxy list updated?
Every proxy is re-checked and the list republished every 30 minutes. Each JSON record carries a lastChecked timestamp and a latency value so you can drop stale or slow entries yourself.
What does 'verified' actually mean here?
Each entry completed a protocol-correct handshake and relayed a real request end to end before publication. Entries that only answered a TCP connect are not published.
Why do some proxies stop working within minutes?
Free proxies are volatile by nature β they appear and disappear constantly. That is exactly why the list is re-checked every 30 minutes and sorted fastest-first. Always loop to the next entry on failure.
Which proxy type should I use?
HTTP is simplest for web requests. SOCKS5 handles any TCP traffic plus UDP and remote DNS. SOCKS4 is a lighter legacy fallback. HTTPS entries are HTTP proxies verified to tunnel TLS.
Do I need to sign up or star the repository?
No. The list is a fully public snapshot on stable URLs, with no account and no credit card. A star just helps other developers find it.
The answers above are short on purpose. These are not β each one opens with a direct answer and then shows every measured figure behind it, with the sample size and the timestamp it came from:
- How many free proxies actually work? Here is the measured rate, by protocol. β the measured end-to-end success rate of a random sample, broken out by protocol, with the method and the timeout it was measured under.
- Where do I get a free proxy list by country, and how many are in each? β the per-country file path, how many entries each country has in the current snapshot, and how thin the tail gets.
- How do I check whether a free proxy actually works? β a working checker in ten lines, plus the four ways a naive check calls a dead proxy alive.
The GitHub list is a free public snapshot with no SLA. The Pro API adds fresher checks, filtering by protocol, country and latency, a rotating endpoint and usage monitoring.
Free public proxies are shared and operated by unknown parties. Never send passwords, tokens or personal data through them. Follow the GitHub Acceptable Use Policies: no spam, no attacks, no bypassing access controls, no scraping against site policies.
Contributions are welcome for docs, examples and data usability. See CONTRIBUTING.md
No source, no screenshot and no pull request needed β which country did you need, and did this list have it?

