| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 193.25.215.182:22222 | socks5 | ✓ TLS | United States / Los Angeles | elite | 2125 ms | 100% | 1h ago |
| 2 | 220.158.232.118:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 4578 ms | 92.11% | 1h ago |
| 3 | 171.25.158.95:1080 | socks5 | ✓ TLS | Sweden / Vaxjo | elite | 7947 ms | 96.84% | 1h ago |
| 4 | 5.255.123.162:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 8459 ms | 98.86% | 1h ago |
| 5 | 212.77.75.25:1088 | socks5 | ✓ TLS | Italy / Empoli | elite | 326 ms | 91.45% | 7m ago |
| 6 | 101.36.104.239:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 2237 ms | 93.4% | 30m ago |
| 7 | 67.210.146.50:11080 | socks5 | ✓ TLS | United States / Princeton | elite | 6709 ms | 52.97% | 44s ago |
| 8 | 195.135.255.98:1080 | socks5 | ✓ TLS | Latvia / Riga | elite | 393 ms | 60.51% | 1h ago |
| 9 | 101.36.104.46:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 3903 ms | 94.85% | 19m ago |
| 10 | 45.61.188.134:44499 | socks5 | ✓ TLS | United States / Miami | elite | 1024 ms | 90.68% | 19m ago |
| 11 | 223.25.109.163:8199 | socks5 | ✓ TLS | Indonesia / Somba | elite | 6183 ms | 37.5% | 56m ago |
| 12 | 128.199.37.92:1080 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 3324 ms | 75.25% | 1h ago |
| 13 | 202.62.55.95:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 9533 ms | 47.32% | 1h ago |
| 14 | 129.151.128.225:1080 | socks5 | ✓ TLS | United Arab Emirates / Abu Dhabi | elite | 1189 ms | 49.01% | 19m ago |
| 15 | 5.255.103.55:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 4713 ms | 75.5% | 12m ago |
| 16 | 163.47.37.190:1080 | socks5 | ✓ TLS | Bangladesh / Paltan | elite | 2656 ms | 55.38% | 26m ago |
| 17 | 43.130.38.45:51029 | socks5 | ✓ TLS | United States / Santa Clara | elite | 8662 ms | 40% | 19m ago |
| 18 | 103.119.60.219:1080 | socks5 | ✓ TLS | Indonesia / Central Jakarta | elite | 6969 ms | 40.57% | 24m ago |
| 19 | 110.235.247.206:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 10251 ms | 46.84% | 7m ago |
| 20 | 202.62.42.92:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 8884 ms | 48.3% | 30m ago |
| 21 | 202.62.50.52:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 3067 ms | 36.79% | 22m ago |
| 22 | 87.107.68.231:1081 | socks5 | ✓ TLS | Iran / Tehran | elite | 4321 ms | 40% | 26m ago |
| 23 | 103.239.52.100:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 4125 ms | 32.93% | 12m ago |
| 24 | 103.174.122.197:8199 | socks5 | ✓ TLS | Indonesia / Sumedang | elite | 2607 ms | 50% | 30m ago |
| 25 | 37.18.73.60:5566 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 792 ms | 63.08% | 19m ago |
| 26 | 125.24.156.113:7080 | socks5 | ✓ TLS | Thailand / Phang Nga | elite | 7141 ms | 38.32% | 17m ago |
| 27 | 103.206.68.241:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 7086 ms | 47.7% | 26m ago |
| 28 | 103.96.233.10:1080 | socks5 | ✓ TLS | Afghanistan / Kabul | elite | 2385 ms | 41.43% | 28m ago |
| 29 | 158.101.8.92:1080 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 6291 ms | 39.81% | 3h ago |
| 30 | 5.255.113.177:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 1085 ms | 81.29% | 26m ago |
| 31 | 176.126.70.111:16379 | socks5 | ✓ TLS | Germany / Brandenburg an der Havel | elite | 10883 ms | 29.17% | 1h ago |
| 32 | 152.70.237.238:3128 | socks5 | ✓ TLS | South Korea / Seoul | elite | 5995 ms | 60.96% | 27m ago |
| 33 | 119.148.7.10:22122 | socks5 | ✓ TLS | Bangladesh / Dhaka | elite | 2813 ms | 64.52% | 4h ago |
| 34 | 109.107.166.207:30385 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 4261 ms | 22.58% | 12h ago |
| 35 | 102.69.146.59:7080 | socks5 | ✓ TLS | Nigeria / Lagos | elite | 4516 ms | 35.77% | 5h ago |
| 36 | 95.211.190.26:9100 | socks5 | ✓ TLS | United States / Seattle | elite | 9994 ms | 8.33% | 1h ago |
| 37 | 188.128.86.74:1080 | socks5 | ✓ TLS | Russia / Ulan-Ude | elite | 2353 ms | 6.67% | 2m ago |
| 38 | 222.102.194.158:1111 | socks5 | ✓ TLS | South Korea / Gwangyang-si | elite | 8462 ms | 6.67% | 18h ago |
| 39 | 109.199.107.68:1080 | socks5 | ✓ TLS | France / Strasbourg | elite | 409 ms | 35.24% | 14h ago |
| 40 | 218.95.39.5:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 1835 ms | 26.32% | 22h ago |
| 41 | 110.235.252.74:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 2271 ms | 45.89% | 24m ago |
| 42 | 121.169.46.116:1090 | socks5 | ✓ TLS | South Korea / Suwon | elite | 4603 ms | 71.07% | 2s ago |
| 43 | 167.86.79.35:1080 | socks5 | ✓ TLS | Germany / Karlsruhe | elite | 1610 ms | 46.72% | 5h ago |
| 44 | 47.252.47.39:1080 | socks5 | ✓ TLS | United States / Charlottesville | elite | 1033 ms | 8.33% | 7m ago |
| 45 | 218.95.39.107:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 3540 ms | 25% | 6h ago |
| 46 | 103.131.104.125:10800 | socks5 | ✓ TLS | Indonesia / Yogyakarta | elite | 6457 ms | 11.54% | 11h ago |
| 47 | 113.176.118.150:1080 | socks5 | ✓ TLS | Vietnam / Hanoi | elite | 4573 ms | 22.03% | 5h ago |
| 48 | 113.160.188.21:1080 | socks5 | ✓ TLS | Vietnam / Phu Ly | elite | 4773 ms | 40.54% | 4h ago |
| 49 | 103.162.57.42:1080 | socks5 | ✓ TLS | Bangladesh / Cox's Bazar | elite | 5977 ms | 43.53% | 20h ago |
| 50 | 79.76.52.220:1080 | socks5 | ✓ TLS | Sweden / Stockholm | elite | 2366 ms | 43.75% | 11m 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.