| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 170.155.2.119:80 | http | — | Argentina / La Plata | elite | 879 ms | 53.85% | 21m ago |
| 2 | 201.190.178.191:8080 | http | ✓ TLS | Argentina / Mendoza | elite | 8688 ms | 54.87% | 6m ago |
| 3 | 138.121.114.54:8080 | http | ✓ TLS | Argentina / Formosa | elite | 8586 ms | 18.57% | 12h ago |
| 4 | 138.117.14.251:8090 | http | ✓ TLS | Argentina / San Miguel de Tucumán | elite | 8592 ms | 16.67% | 4h ago |
| 5 | 181.209.110.27:999 | http | ✓ TLS | Argentina / Quimili | elite | 7776 ms | 19.44% | 13h ago |
| 6 | 190.111.243.150:1085 | socks4 | ✓ TLS | Argentina / San Juan Bautista | elite | 4248 ms | 39.31% | 14m ago |
| 7 | 181.209.115.98:999 | http | ✓ TLS | Argentina / Benavídez | elite | 6690 ms | 34.21% | 2h ago |
| 8 | 181.209.59.178:999 | http | ✓ TLS | Argentina / Benavídez | elite | 4284 ms | 24.62% | 2h ago |
| 9 | 190.210.62.131:8080 | http | ✓ TLS | Argentina / Buenos Aires | elite | 8343 ms | 15.38% | 21m ago |
| 10 | 200.70.35.2:8080 | http | ✓ TLS | Argentina / Mendoza | elite | 7565 ms | 55.15% | 58m ago |
| 11 | 45.65.225.17:999 | http | ✓ TLS | Argentina / Buenos Aires | elite | 7805 ms | 30.61% | 1m ago |
| 12 | 200.122.92.211:5678 | socks4 | ✓ TLS | Argentina / Bell Ville | elite | 2230 ms | 48.33% | 1h ago |
| 13 | 179.43.103.97:8080 | http | ✓ TLS | Argentina / Laferrere | elite | 8202 ms | 16.13% | 1d ago |
| 14 | 168.196.227.203:999 | http | ✓ TLS | Argentina / Malvinas Argentinas | elite | 9516 ms | 21.05% | 2h ago |
| 15 | 45.65.227.161:999 | http | ✓ TLS | Argentina / Buenos Aires | elite | 6681 ms | 10.53% | 13h ago |
| 16 | 181.209.96.157:999 | http | ✓ TLS | Argentina / Urundel | elite | 3986 ms | 29.51% | 4h ago |
| 17 | 181.209.108.218:999 | http | ✓ TLS | Argentina / Campo Gallo | elite | 5664 ms | 22.64% | 19h ago |
| 18 | 138.117.13.65:999 | http | ✓ TLS | Argentina / 28 de Noviembre | elite | 3312 ms | 44.44% | 5h ago |
| 19 | 45.178.246.8:999 | http | ✓ TLS | Argentina / San Carlos | elite | 2511 ms | 14.29% | 15h ago |
| 20 | 138.121.113.179:999 | http | ✓ TLS | Argentina / Formosa | elite | 7984 ms | 42.34% | 44m ago |
| 21 | 200.110.218.13:999 | http | ✓ TLS | Argentina / Monte Grande | elite | 9531 ms | 31.34% | 2h ago |
| 22 | 181.209.125.237:999 | http | ✓ TLS | Argentina / Santa Rosa | elite | 3104 ms | 18.87% | 2h ago |
| 23 | 201.234.24.89:4153 | socks4 | ✓ TLS | Argentina / Buenos Aires | elite | 3003 ms | 54.98% | 1h 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.