| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 45.61.129.165:9050 | socks5 | ✓ TLS | United States / Seattle | elite | 8557 ms | 100% | 28m ago |
| 2 | 107.150.41.226:18080 | socks5 | ✓ TLS | United States / Kansas City | elite | 2178 ms | 100% | 21m ago |
| 3 | 213.111.146.36:18080 | socks5 | ✓ TLS | The Netherlands / Haarlem | elite | 302 ms | 100% | 47m ago |
| 4 | 185.195.71.218:18080 | socks5 | ✓ TLS | Switzerland / Hünenberg | elite | 829 ms | 100% | 26m ago |
| 5 | 103.75.118.84:1080 | socks5 | ✓ TLS | Japan / Tokyo | elite | 3177 ms | 97.8% | 1h ago |
| 6 | 171.25.158.95:1080 | socks5 | ✓ TLS | Sweden / Vaxjo | elite | 8893 ms | 98.7% | 41m ago |
| 7 | 156.225.20.83:1080 | socks5 | ✓ TLS | Hong Kong / Hong Kong | elite | 5512 ms | 97.85% | 44m ago |
| 8 | 101.36.104.46:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 5168 ms | 91.96% | 1h ago |
| 9 | 162.120.16.210:1080 | socks5 | ✓ TLS | United States / New York | elite | 4930 ms | 66.32% | 1h ago |
| 10 | 144.24.111.128:1088 | socks5 | ✓ TLS | India / Mumbai | elite | 2108 ms | 97.8% | 27m ago |
| 11 | 101.36.104.239:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 3269 ms | 89.26% | 46m ago |
| 12 | 109.123.251.109:1080 | socks5 | ✓ TLS | France / Lauterbourg | elite | 1425 ms | 88.6% | 19m ago |
| 13 | 38.49.210.79:40000 | socks5 | ✓ TLS | Canada / Montreal | elite | 6203 ms | 82.64% | 1h ago |
| 14 | 5.255.103.55:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 4253 ms | 75% | 1h ago |
| 15 | 121.169.46.116:1090 | socks5 | ✓ TLS | South Korea / Suwon | elite | 4305 ms | 75.46% | 1h ago |
| 16 | 193.25.215.182:22222 | socks5 | ✓ TLS | United States / Los Angeles | elite | 4272 ms | 98.86% | 21m ago |
| 17 | 124.248.177.43:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 5364 ms | 72.32% | 13m ago |
| 18 | 45.61.188.134:44499 | socks5 | ✓ TLS | United States / Miami | elite | 1404 ms | 88.33% | 8m ago |
| 19 | 202.79.27.12:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 3064 ms | 61.73% | 18m ago |
| 20 | 103.206.68.241:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 5764 ms | 59.89% | 9m ago |
| 21 | 144.31.255.9:1080 | socks5 | ✓ TLS | Germany / Frankfurt am Main | elite | 3280 ms | 44% | 9m ago |
| 22 | 163.53.204.178:9813 | socks5 | ✓ TLS | India / Dharmapuri | elite | 6139 ms | 40.2% | 5m ago |
| 23 | 67.210.146.50:11080 | socks5 | ✓ TLS | United States / Princeton | elite | 5622 ms | 46.15% | 14m ago |
| 24 | 5.255.117.127:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 1836 ms | 61.46% | 1m ago |
| 25 | 186.26.95.249:61445 | socks5 | ✓ TLS | Brazil / São João de Meriti | elite | 6448 ms | 46.75% | 27m ago |
| 26 | 5.255.117.250:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 9641 ms | 68.49% | 2m ago |
| 27 | 220.158.232.118:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 5204 ms | 83.45% | 5m ago |
| 28 | 138.3.218.141:54261 | socks5 | ✓ TLS | Japan / Tokyo | elite | 10754 ms | 9.09% | 2h ago |
| 29 | 144.31.182.250:1080 | socks5 | ✓ TLS | Finland / Helsinki | elite | 397 ms | 0% | 14h ago |
| 30 | 103.103.146.149:7080 | socks5 | ✓ TLS | Indonesia / Pangkalpinang | elite | 4325 ms | 52.46% | 4h ago |
| 31 | 188.168.51.56:1080 | socks5 | ✓ TLS | Russia / Rybinsk | elite | 2563 ms | 16% | 2h ago |
| 32 | 168.119.173.104:47486 | socks5 | ✓ TLS | Germany / Nuremberg | elite | 2843 ms | 22.5% | 13h ago |
| 33 | 91.210.151.184:1080 | socks5 | ✓ TLS | Russia / Moscow | elite | 2977 ms | 42.86% | 3h ago |
| 34 | 27.131.14.9:1088 | socks5 | ✓ TLS | Bangladesh / Dhaka | elite | 5126 ms | 38.92% | 18m ago |
| 35 | 158.220.101.43:1080 | socks5 | ✓ TLS | France / Strasbourg | elite | 1673 ms | 30.36% | 52m ago |
| 36 | 119.148.7.10:22122 | socks5 | ✓ TLS | Bangladesh / Dhaka | elite | 6366 ms | 53.65% | 1h ago |
| 37 | 103.151.75.21:2025 | socks5 | ✓ TLS | Bangladesh / Burirchar | elite | 5030 ms | 36.49% | 17m ago |
| 38 | 203.189.153.170:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 3697 ms | 19.23% | 14m ago |
| 39 | 102.69.146.59:7080 | socks5 | ✓ TLS | Nigeria / Lagos | elite | 2734 ms | 36.59% | 1m ago |
| 40 | 103.119.60.219:1080 | socks5 | ✓ TLS | Indonesia / Central Jakarta | elite | 4963 ms | 35.85% | 43m ago |
| 41 | 213.27.29.153:51000 | socks5 | ✓ TLS | Russia / Rostov-on-Don | elite | 2032 ms | 37.67% | 3h ago |
| 42 | 188.242.163.28:21 | socks5 | ✓ TLS | Russia / St Petersburg | elite | 4379 ms | 44.81% | 2h ago |
| 43 | 91.226.172.214:1080 | socks5 | ✓ TLS | Russia / Moscow | elite | 3612 ms | 19.35% | 1h ago |
| 44 | 161.97.106.223:9050 | socks5 | ✓ TLS | Germany / Brandenburg an der Havel | elite | 10058 ms | 10.53% | 1h ago |
| 45 | 109.199.107.68:1080 | socks5 | ✓ TLS | France / Strasbourg | elite | 699 ms | 33.81% | 25m ago |
| 46 | 110.235.252.74:1080 | socks5 | ✓ TLS | Cambodia / Phnom Penh | elite | 6356 ms | 55.05% | 4m ago |
| 47 | 89.110.98.72:9050 | socks5 | ✓ TLS | Germany / Brandenburg an der Havel | elite | 2444 ms | 8.33% | 2h ago |
| 48 | 47.252.47.39:1080 | socks5 | ✓ TLS | United States / Charlottesville | elite | 1000 ms | 11.11% | 46m ago |
| 49 | 161.97.129.202:9060 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 9435 ms | 7.14% | 5h ago |
| 50 | 113.176.118.150:1080 | socks5 | ✓ TLS | Vietnam / Hoi An | elite | 5601 ms | 23.53% | 13h 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.