| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 95.3.69.222:8080 | http | ✓ TLS | Türkiye / Istanbul | elite | 636 ms | 100% | 1h ago |
| 2 | 45.61.129.165:9050 | socks5 | ✓ TLS | United States / Seattle | elite | 8557 ms | 100% | 29m ago |
| 3 | 107.150.41.226:18080 | http | ✓ TLS | United States / Kansas City | elite | 2316 ms | 100% | 1h ago |
| 4 | 107.150.41.226:18080 | socks5 | ✓ TLS | United States / Kansas City | elite | 2178 ms | 100% | 23m ago |
| 5 | 213.111.146.36:18080 | http | ✓ TLS | The Netherlands / Haarlem | elite | 357 ms | 100% | 54m ago |
| 6 | 213.111.146.36:18080 | socks5 | ✓ TLS | The Netherlands / Haarlem | elite | 302 ms | 100% | 48m ago |
| 7 | 185.195.71.218:18080 | socks5 | ✓ TLS | Switzerland / Hünenberg | elite | 829 ms | 100% | 27m ago |
| 8 | 65.108.159.129:8081 | http | ✓ TLS | Finland / Helsinki | elite | 3035 ms | 100% | 27m ago |
| 9 | 95.211.174.135:3128 | http | ✓ TLS | The Netherlands / Haarlem | elite | 292 ms | 100% | 1h ago |
| 10 | 103.75.118.84:1080 | socks5 | ✓ TLS | Japan / Tokyo | elite | 3177 ms | 97.8% | 1h ago |
| 11 | 171.25.158.95:1080 | socks5 | ✓ TLS | Sweden / Vaxjo | elite | 8893 ms | 98.7% | 42m ago |
| 12 | 119.188.131.55:17981 | http | ✓ TLS | China / Jinan | elite | 4651 ms | 98.84% | 1h ago |
| 13 | 122.246.3.12:17981 | http | ✓ TLS | China / Beijing | elite | 3296 ms | 97.78% | 1h ago |
| 14 | 120.232.115.170:17981 | http | ✓ TLS | China / Guangzhou | elite | 3218 ms | 98.85% | 1h ago |
| 15 | 156.225.20.83:1080 | socks5 | ✓ TLS | Hong Kong / Hong Kong | elite | 5512 ms | 97.85% | 46m ago |
| 16 | 101.36.104.46:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 5168 ms | 91.96% | 1h ago |
| 17 | 47.91.104.88:3128 | http | ✓ TLS | United Arab Emirates / Dubai | elite | 1273 ms | 88.98% | 48m ago |
| 18 | 38.253.88.242:999 | http | ✓ TLS | Dominican Republic / Jarabacoa | elite | 1206 ms | 94.85% | 6m ago |
| 19 | 103.149.75.82:1080 | socks4 | ✓ TLS | Bangladesh / Dhaka | elite | 2692 ms | 95.7% | 3m ago |
| 20 | 162.120.16.210:1080 | socks5 | ✓ TLS | United States / New York | elite | 4930 ms | 66.32% | 1h ago |
| 21 | 139.255.94.123:57853 | socks4 | ✓ TLS | Indonesia / Central Jakarta | elite | 2897 ms | 69.81% | 1h ago |
| 22 | 201.20.42.46:3128 | http | ✓ TLS | Brazil / São Paulo | elite | 4451 ms | 47.14% | 31m ago |
| 23 | 144.24.111.128:1088 | socks5 | ✓ TLS | India / Mumbai | elite | 2108 ms | 97.8% | 28m ago |
| 24 | 101.36.104.239:10808 | socks5 | ✓ TLS | Japan / Tokyo | elite | 3269 ms | 89.26% | 48m ago |
| 25 | 185.191.239.248:3128 | http | ✓ TLS | Switzerland / Wetzikon | elite | 7705 ms | 89.22% | 1h ago |
| 26 | 109.123.251.109:1080 | socks5 | ✓ TLS | France / Lauterbourg | elite | 1425 ms | 88.6% | 21m ago |
| 27 | 200.10.30.5:8083 | http | ✓ TLS | Colombia / Pereira | elite | 4007 ms | 56.49% | 1h ago |
| 28 | 176.111.37.216:39811 | http | ✓ TLS | Hong Kong / Tsim Sha Tsui | elite | 512 ms | 74.15% | 1h ago |
| 29 | 186.5.94.206:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 10114 ms | 98.89% | 1h ago |
| 30 | 38.49.210.79:40000 | socks5 | ✓ TLS | Canada / Montreal | elite | 6203 ms | 82.64% | 1h ago |
| 31 | 38.194.246.34:999 | http | ✓ TLS | Mexico / Huauchinango | elite | 2291 ms | 83.33% | 1h ago |
| 32 | 186.96.111.214:999 | http | ✓ TLS | Colombia / Granada | elite | 4381 ms | 59.01% | 45m ago |
| 33 | 1.179.151.165:31948 | socks4 | ✓ TLS | Thailand / Bangkok | elite | 3899 ms | 67.34% | 1h ago |
| 34 | 62.201.212.198:4673 | socks4 | ✓ TLS | Iraq / Sulaymaniyah | elite | 1674 ms | 60.62% | 15m ago |
| 35 | 85.237.62.189:3629 | socks4 | ✓ TLS | Russia / Penza | elite | 5760 ms | 61.7% | 1h ago |
| 36 | 45.65.138.48:999 | http | ✓ TLS | Colombia / Villa del Rosario | elite | 2952 ms | 55.62% | 51m ago |
| 37 | 121.169.46.116:1090 | socks5 | ✓ TLS | South Korea / Suwon | elite | 4305 ms | 75.46% | 1h ago |
| 38 | 159.194.228.40:8888 | http | ✓ TLS | United States / Houston | elite | 11971 ms | 47.5% | 1h ago |
| 39 | 124.128.149.84:8090 | http | ✓ TLS | China / Beijing | elite | 8640 ms | 68.45% | 17m ago |
| 40 | 193.25.215.182:22222 | socks5 | ✓ TLS | United States / Los Angeles | elite | 4272 ms | 98.86% | 23m ago |
| 41 | 181.78.195.137:999 | http | ✓ TLS | Ecuador / Cuenca | elite | 8796 ms | 64% | 28m ago |
| 42 | 187.251.224.167:8081 | http | ✓ TLS | Mexico / San José de Durán | elite | 3751 ms | 52.3% | 3m ago |
| 43 | 189.50.138.10:5678 | socks4 | ✓ TLS | Brazil / Presidente Prudente | elite | 6239 ms | 68.29% | 25m ago |
| 44 | 103.115.255.225:36331 | socks4 | ✓ TLS | Bangladesh / Savar Upazila | elite | 6846 ms | 63.23% | 28m ago |
| 45 | 45.65.137.218:999 | http | ✓ TLS | Colombia / Villa del Rosario | elite | 8655 ms | 51.57% | 12m ago |
| 46 | 1.4.195.114:4145 | socks4 | ✓ TLS | Thailand / Mueang Chan | elite | 8742 ms | 50.62% | 8m ago |
| 47 | 181.78.17.131:999 | http | ✓ TLS | Colombia / Andalucía | elite | 7300 ms | 43.83% | 31m ago |
| 48 | 103.191.254.1:7777 | http | ✓ TLS | Indonesia / Rembang | elite | 5319 ms | 47.46% | 20m ago |
| 49 | 176.111.37.5:39811 | http | ✓ TLS | Hong Kong / Tsim Sha Tsui | elite | 8956 ms | 71.43% | 5m ago |
| 50 | 45.71.186.213:999 | http | ✓ TLS | Ecuador / Cuenca | elite | 3652 ms | 51.43% | 21m 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.