| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 186.5.94.206:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 1709 ms | 100% | 1h ago |
| 2 | 190.12.150.244:999 | http | ✓ TLS | Ecuador / Quininde | elite | 10636 ms | 85.94% | 1h ago |
| 3 | 177.234.217.235:999 | http | ✓ TLS | Ecuador / Quito | elite | 6517 ms | 80.47% | 1h ago |
| 4 | 200.24.153.79:8080 | http | ✓ TLS | Ecuador / Cuenca | elite | 6614 ms | 43.38% | 45m ago |
| 5 | 45.71.186.212:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 8185 ms | 64.68% | 1h ago |
| 6 | 45.71.186.213:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 3703 ms | 62.98% | 26m ago |
| 7 | 45.71.186.214:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 3893 ms | 64.59% | 28m ago |
| 8 | 181.188.216.3:8080 | http | ✓ TLS | Ecuador / Machachi | elite | 7313 ms | 43.2% | 31m ago |
| 9 | 181.78.203.3:999 | http | ✓ TLS | Ecuador / Rosa Zarate | elite | 4415 ms | 41.62% | 2h ago |
| 10 | 177.234.217.85:999 | http | ✓ TLS | Ecuador / Quito | elite | 4910 ms | 58.89% | 3h ago |
| 11 | 177.234.217.83:999 | http | ✓ TLS | Ecuador / Quito | elite | 7338 ms | 72.09% | 2h ago |
| 12 | 177.234.192.231:999 | http | ✓ TLS | Ecuador / Quito | elite | 10338 ms | 11.76% | 11h ago |
| 13 | 45.229.17.2:999 | http | ✓ TLS | Ecuador / Vinces | elite | 5869 ms | 28.13% | 28m ago |
| 14 | 186.33.40.133:999 | http | ✓ TLS | Ecuador / Guayaquil | elite | 1528 ms | 30.56% | 20h ago |
| 15 | 177.234.211.175:999 | http | ✓ TLS | Ecuador / Quito | elite | 5189 ms | 42.86% | 49m ago |
| 16 | 45.190.87.241:999 | http | ✓ TLS | Ecuador / Quito | elite | 9501 ms | 36.26% | 9m ago |
| 17 | 45.4.202.147:999 | http | ✓ TLS | Ecuador / Manta | elite | 6695 ms | 21.67% | 4h ago |
| 18 | 157.100.56.12:8080 | http | ✓ TLS | Ecuador / Zamora | elite | 6743 ms | 22.22% | 20m ago |
| 19 | 177.234.210.56:999 | http | ✓ TLS | Ecuador / Quito | elite | 9645 ms | 24.62% | 1h ago |
| 20 | 177.234.212.132:999 | http | ✓ TLS | Ecuador / Quito | elite | 7827 ms | 6.25% | 6h ago |
| 21 | 45.224.22.63:999 | http | ✓ TLS | Ecuador / Santa Ana de Vuelta Larga | elite | 1670 ms | 25.86% | 12h ago |
| 22 | 45.4.202.144:999 | http | ✓ TLS | Ecuador / Jipijapa | elite | 9241 ms | 18.18% | 37m ago |
| 23 | 181.78.203.148:999 | http | ✓ TLS | Ecuador / Rosa Zarate | elite | 9733 ms | 18.6% | 3h ago |
| 24 | 45.71.114.185:999 | http | ✓ TLS | Ecuador / Cuenca | elite | 8271 ms | 6.25% | 11h ago |
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.