| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 34.102.241.71:80 | http | — | Spain / Madrid | elite | 147 ms | 100% | 50m ago |
| 2 | 16.163.88.228:80 | http | — | — | elite | 365 ms | 100% | 1h ago |
| 3 | 95.3.69.222:8080 | http | ✓ TLS | Türkiye / Istanbul | elite | 636 ms | 100% | 1h ago |
| 4 | 107.150.41.226:18080 | http | ✓ TLS | United States / Kansas City | elite | 2316 ms | 100% | 1h ago |
| 5 | 213.111.146.36:18080 | http | ✓ TLS | The Netherlands / Haarlem | elite | 357 ms | 100% | 54m ago |
| 6 | 12.50.107.217:80 | http | — | United States / Hialeah | elite | 334 ms | 100% | 15m ago |
| 7 | 12.50.107.219:80 | http | — | United States / Hialeah | elite | 375 ms | 100% | 52m ago |
| 8 | 65.108.159.129:8081 | http | ✓ TLS | Finland / Helsinki | elite | 3035 ms | 100% | 28m ago |
| 9 | 12.50.107.221:80 | http | — | United States / Hialeah | elite | 332 ms | 100% | 1h ago |
| 10 | 95.211.174.135:3128 | http | ✓ TLS | The Netherlands / Haarlem | elite | 292 ms | 100% | 1h ago |
| 11 | 221.178.239.200:7302 | http | — | — | elite | 557 ms | 100% | 35m ago |
| 12 | 12.50.107.222:80 | http | — | United States / Hialeah | elite | 332 ms | 98.85% | 50m ago |
| 13 | 119.188.131.55:17981 | http | ✓ TLS | China / Jinan | elite | 4651 ms | 98.84% | 1h ago |
| 14 | 122.246.3.12:17981 | http | ✓ TLS | China / Beijing | elite | 3296 ms | 97.78% | 1h ago |
| 15 | 116.202.108.111:3128 | http | — | Spain / Madrid | elite | 175 ms | 98.85% | 1h ago |
| 16 | 12.50.107.220:80 | http | — | United States / Hialeah | elite | 547 ms | 97.8% | 14m ago |
| 17 | 120.232.115.170:17981 | http | ✓ TLS | China / Guangzhou | elite | 3218 ms | 98.85% | 1h ago |
| 18 | 34.44.49.215:80 | http | — | United States / Council Bluffs | elite | 296 ms | 98.86% | 11m ago |
| 19 | 115.239.234.43:7302 | http | — | — | elite | 1019 ms | 90.35% | 1h ago |
| 20 | 176.61.151.123:80 | http | — | Portugal / Faro Municipality | elite | 241 ms | 83.33% | 1h ago |
| 21 | 47.91.104.88:3128 | http | ✓ TLS | United Arab Emirates / Dubai | elite | 1273 ms | 88.98% | 49m ago |
| 22 | 129.226.93.232:80 | http | — | Spain / Madrid | elite | 859 ms | 92.23% | 32m ago |
| 23 | 164.52.11.194:18080 | http | — | Taiwan / Taipei | elite | 6647 ms | 84.56% | 1h ago |
| 24 | 219.65.73.81:80 | http | — | India / Kolkata | elite | 836 ms | 90.99% | 1h ago |
| 25 | 38.253.88.242:999 | http | ✓ TLS | Dominican Republic / Jarabacoa | elite | 1206 ms | 94.85% | 6m ago |
| 26 | 37.59.125.131:8888 | http | — | Spain / Madrid | elite | 1886 ms | 80% | 1h ago |
| 27 | 41.220.16.210:80 | http | — | Zimbabwe / Harare | elite | 913 ms | 67.03% | 51m ago |
| 28 | 34.111.147.163:80 | http | — | Spain / Madrid | elite | 180 ms | 94% | 13m ago |
| 29 | 190.12.150.244:999 | http | — | Spain / Madrid | elite | 5298 ms | 85.95% | 1h ago |
| 30 | 183.110.216.128:8091 | http | — | South Korea / Seongnam-si | elite | 3005 ms | 70.45% | 1h ago |
| 31 | 3.211.120.181:443 | http | — | United States / Ashburn | elite | 206 ms | 71.22% | 29m ago |
| 32 | 201.20.42.46:3128 | http | ✓ TLS | Brazil / São Paulo | elite | 4451 ms | 47.14% | 31m ago |
| 33 | 185.191.239.248:3128 | http | ✓ TLS | Switzerland / Wetzikon | elite | 7705 ms | 89.22% | 1h ago |
| 34 | 37.187.74.125:80 | http | — | France / Roubaix | elite | 5175 ms | 84.56% | 16m ago |
| 35 | 195.114.209.50:80 | http | — | Spain / Alcobendas | elite | 254 ms | 71.58% | 1h ago |
| 36 | 185.135.69.34:80 | http | — | Russia / Chistopol' | elite | 192 ms | 61.76% | 50m ago |
| 37 | 200.10.30.5:8083 | http | ✓ TLS | Colombia / Pereira | elite | 4007 ms | 56.49% | 1h ago |
| 38 | 41.184.92.220:80 | http | — | Nigeria / Lagos | elite | 650 ms | 48.48% | 1h ago |
| 39 | 197.221.234.253:80 | http | — | Zimbabwe / Harare | elite | 860 ms | 77.47% | 34m ago |
| 40 | 175.139.233.79:80 | http | — | Malaysia / Donggongon | elite | 1133 ms | 66.15% | 1h ago |
| 41 | 163.172.167.48:80 | http | — | France / Paris | elite | 3902 ms | 46.49% | 52m ago |
| 42 | 219.65.73.80:80 | http | — | India / Kolkata | elite | 917 ms | 88.43% | 1h ago |
| 43 | 176.111.37.216:39811 | http | ✓ TLS | Hong Kong / Tsim Sha Tsui | elite | 512 ms | 74.15% | 1h ago |
| 44 | 46.47.197.210:3128 | http | — | Russia / St Petersburg | elite | 287 ms | 68.45% | 35m ago |
| 45 | 197.221.249.197:80 | http | — | Zimbabwe / Harare | elite | 5011 ms | 73.86% | 27m ago |
| 46 | 186.5.94.206:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 10114 ms | 98.89% | 1h ago |
| 47 | 197.221.240.176:80 | http | — | Zimbabwe / Harare | elite | 1921 ms | 76.74% | 1h ago |
| 48 | 80.74.54.148:3128 | http | — | Germany / Tönisvorst | elite | 253 ms | 52.28% | 42m ago |
| 49 | 197.221.240.246:80 | http | — | Zimbabwe / Harare | elite | 2965 ms | 71.96% | 53m ago |
| 50 | 197.221.237.248:80 | http | — | Zimbabwe / Harare | elite | 2010 ms | 70.32% | 1h ago |
A quick automated human-verification check runs before more proxies load. We don't offer bulk download or an API — this list is for manual use.
Browse proxies by country
Use public proxies with caution. These are open, third-party servers we did not set up. A working proxy can still log your traffic, inject content, or expose your real IP through DNS, WebRTC, or application headers.
Never send passwords, financial data, or other sensitive traffic through an untrusted proxy. Verify a proxy with our Proxy Tester before relying on it, and only use proxies where you are authorized to do so.
ℹ️ About Free Proxy List
What is this free proxy list?
This page publishes a live list of public HTTP, HTTPS, SOCKS4, and SOCKS5 proxy servers drawn from our continuously monitored proxy database. Every proxy is re-tested on a short interval by a distributed worker fleet, so the status, latency, anonymity level, and geographic location reflect recent checks rather than a stale dump. Only proxies that are currently alive are listed, and credentialed/private proxies are never published.
The first 50 results load instantly. To reveal the rest (up to 200) a lightweight, invisible human-verification check runs first — this keeps the list useful for people while discouraging automated bulk scraping. There is intentionally no bulk download or public API.
HTTP vs HTTPS vs SOCKS proxies
- HTTP — forwards plain HTTP requests; best for simple web traffic and scraping non-TLS endpoints.
- HTTPS — supports the
CONNECTmethod to tunnel TLS, so it can carry encryptedhttps://traffic. - SOCKS4 — a lower-level TCP tunnel; no authentication of the proxied protocol and no UDP/IPv6.
- SOCKS5 — the most flexible: TCP and UDP, IPv6, and optional auth. Defined in RFC 1928. HTTP semantics are defined in RFC 9110 and the standardized forwarding header in RFC 7239.
The HTTPS column (✓ TLS) marks proxies we verified can tunnel encrypted https:// traffic — confirmed either by a live TLS probe or by the proxy reaching our HTTPS test endpoint. This is independent of the proxy's own scheme: an HTTP-listed proxy can still be HTTPS-capable via CONNECT. Use the HTTPS filter to show only TLS-capable proxies.
Anonymity levels & safety ratings
| Level | Reveals your IP? | Privacy rating | Use |
|---|---|---|---|
| Elite | No — and hides that a proxy is used | Strongest | Best choice for anonymity |
| Anonymous | No, but reveals a proxy is in use | Medium | OK for general use |
| Transparent | Yes — forwards your real IP | None | Caching/testing only, not privacy |
How "reliability" and uptime are measured
The default sort ranks proxies by recent success streak. The Uptime (7d) column is the share of our last week of checks that succeeded for that proxy. Latency is the most recent measured round-trip time. Because public proxies are volatile, a proxy that is up now may be down within hours — re-verify before depending on it.