| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 201.62.125.142:8080 | http | ✓ TLS | Brazil / Rio Claro | elite | 8047 ms | 27.27% | 22m ago |
| 2 | 45.227.195.121:8082 | http | ✓ TLS | Brazil / Concórdia | elite | 6125 ms | 17.02% | 7m ago |
| 3 | 179.48.11.6:8085 | http | ✓ TLS | Brazil / Campo Maior | elite | 5644 ms | 21.95% | 8h ago |
| 4 | 200.3.197.53:8080 | http | ✓ TLS | Brazil / Sinop | elite | 2570 ms | 27.12% | 3h ago |
| 5 | 45.175.171.4:8085 | http | ✓ TLS | Brazil / Castilho | elite | 2993 ms | 46.08% | 6h ago |
| 6 | 186.26.92.233:58339 | http | ✓ TLS | Brazil / São João de Meriti | elite | 6945 ms | 10% | 3h ago |
| 7 | 168.228.176.30:3139 | http | ✓ TLS | Brazil / Tianguá | elite | 7078 ms | 19.05% | 5h ago |
| 8 | 131.161.68.38:35944 | socks4 | — | Brazil / Rio de Janeiro | elite | 6018 ms | 54.55% | 44m ago |
| 9 | 177.136.44.194:54443 | http | ✓ TLS | Brazil / Salvador | elite | 7175 ms | 6.25% | 9h ago |
| 10 | 186.216.208.98:3128 | http | ✓ TLS | Brazil / Brasília | elite | 1980 ms | 37.14% | 1h ago |
| 11 | 181.191.14.5:8080 | http | ✓ TLS | Brazil / Castanhal | elite | 11184 ms | 31.58% | 54m ago |
| 12 | 201.54.176.64:8080 | http | ✓ TLS | Brazil / Icó | elite | 4157 ms | 25.42% | 1h ago |
| 13 | 45.238.112.229:56789 | http | ✓ TLS | Brazil / Fortaleza | elite | 8872 ms | 25% | 18h ago |
| 14 | 177.55.191.22:60606 | socks4 | ✓ TLS | Brazil / Pedro Leopoldo | elite | 1874 ms | 39.46% | 3h ago |
| 15 | 177.20.167.139:8080 | http | ✓ TLS | Brazil / Pardinho | elite | 1856 ms | 45.45% | 10h ago |
| 16 | 177.23.156.0:18800 | http | ✓ TLS | Brazil / Anápolis | elite | 9934 ms | 11.11% | 10h ago |
| 17 | 177.26.112.65:5678 | socks4 | ✓ TLS | Brazil / São Paulo | elite | 7047 ms | 45.89% | 30m ago |
| 18 | 201.218.189.212:4153 | socks4 | ✓ TLS | Brazil / Porto Seguro | elite | 1823 ms | 52.88% | 4h ago |
| 19 | 149.78.206.146:3600 | http | ✓ TLS | Brazil / Porto Seguro | elite | 1843 ms | 33.01% | 2h ago |
| 20 | 143.208.84.57:8589 | http | ✓ TLS | Brazil / Ubiratã | elite | 8119 ms | 29.17% | 18h ago |
| 21 | 177.125.144.94:1080 | socks4 | ✓ TLS | Brazil / Afonso Cláudio | elite | 2731 ms | 57.21% | 35m ago |
| 22 | 131.100.19.5:4321 | http | ✓ TLS | Brazil / Colinas do Tocantins | elite | 4922 ms | 35.71% | 3h ago |
| 23 | 179.48.25.1:8095 | http | ✓ TLS | Brazil / Timon | elite | 7232 ms | 26.6% | 1h ago |
| 24 | 191.36.128.62:8080 | http | ✓ TLS | Brazil / São Paulo | elite | 4261 ms | 27.03% | 11h ago |
| 25 | 168.194.248.18:8080 | http | ✓ TLS | Brazil / Goiânia | elite | 5808 ms | 23.94% | 6h ago |
| 26 | 179.48.80.9:8085 | http | ✓ TLS | Brazil / Teresina | elite | 3862 ms | 41.1% | 4h ago |
| 27 | 177.125.208.1:8080 | http | ✓ TLS | Brazil / Maringá | elite | 6507 ms | 15.15% | 13h ago |
| 28 | 200.201.134.184:8787 | http | ✓ TLS | Brazil / São Paulo | elite | 10281 ms | 32.81% | 18h ago |
| 29 | 186.26.95.249:61445 | socks5 | ✓ TLS | Brazil / São João de Meriti | elite | 9454 ms | 39.72% | 4h ago |
| 30 | 189.50.138.10:5678 | socks4 | ✓ TLS | Brazil / Presidente Prudente | elite | 5119 ms | 62.92% | 10m ago |
| 31 | 186.65.104.52:2024 | http | ✓ TLS | Brazil / Salvador | elite | 10841 ms | 26.74% | 3h ago |
| 32 | 177.93.72.82:4153 | socks4 | ✓ TLS | Brazil / Lagoa Grande | elite | 2935 ms | 50.22% | 3h ago |
| 33 | 179.48.8.9:8088 | http | ✓ TLS | Brazil / Campo Maior | elite | 7162 ms | 0% | 19h ago |
| 34 | 45.168.244.16:8080 | http | ✓ TLS | Brazil / São João Batista do Glória | elite | 10191 ms | 38.82% | 15h ago |
| 35 | 179.125.61.201:8080 | http | ✓ TLS | Brazil / Urânia | elite | 6597 ms | 23.75% | 1h ago |
| 36 | 168.194.226.178:4153 | socks4 | ✓ TLS | Brazil / Ibiraci | elite | 5000 ms | 11.11% | 12h ago |
| 37 | 191.6.112.5:8086 | http | ✓ TLS | Brazil / Macapá | elite | 2881 ms | 36.05% | 1d ago |
| 38 | 186.235.123.3:8080 | http | ✓ TLS | Brazil / Cachoeiras de Macacu | elite | 6118 ms | 33.33% | 16h ago |
| 39 | 45.180.84.105:443 | http | ✓ TLS | Brazil / Salvador | elite | 9124 ms | 25% | 8h ago |
| 40 | 45.4.192.225:8080 | http | ✓ TLS | Brazil / Brasília | elite | 4263 ms | 22.47% | 7h ago |
| 41 | 168.228.176.12:3139 | http | ✓ TLS | Brazil / Tianguá | elite | 6238 ms | 36.11% | 3m ago |
| 42 | 189.90.118.105:4153 | socks4 | ✓ TLS | Brazil / Leopoldina | elite | 2734 ms | 50% | 26m ago |
| 43 | 187.49.83.165:53000 | http | ✓ TLS | Brazil / Cascavel | elite | 9046 ms | 15% | 5h ago |
| 44 | 177.23.156.1:18800 | http | ✓ TLS | Brazil / Anápolis | elite | 7147 ms | 7.69% | 5h ago |
| 45 | 138.0.143.120:8080 | http | ✓ TLS | Brazil / Valparaíso | elite | 7580 ms | 20.34% | 30m ago |
| 46 | 177.125.212.244:4145 | socks4 | ✓ TLS | Brazil / Campo Mourão | elite | 6214 ms | 65.79% | 20m 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 Brazil 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.