Skip to contentBrazil: free HTTP proxies 🇧🇷
Brazil HTTP: 19 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 122 (working first, then history)
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 12323 | HTTP | 🇧🇷Goiânia | Transparent | – | 221 ms | 100% | ||
| 8080 | HTTP | 🇧🇷Caicó | Transparent | – | 192 ms | 100% | ||
| 6666 | HTTP | 🇧🇷Salvador | Transparent | – | 193 ms | 100% | ||
| 8080 | HTTP | 🇧🇷Olímpia | Transparent | – | 227 ms | 100% | ||
| 3128 | HTTP | 🇧🇷Pirapora | Transparent | – | 231 ms | 100% | ||
| 8402 | HTTP | 🇧🇷Livramento | Transparent | – | 182 ms | 100% | ||
| 8084 | HTTP | 🇧🇷Cabo de Santo Agostinho | Transparent | – | 199 ms | 99% | ||
| 8118 | HTTP | 🇧🇷São Paulo | Elite | – | 193 ms | 99% | ||
| 8080 | HTTP | 🇧🇷Araranguá | Transparent | – | 217 ms | 99% | ||
| 3128 | HTTP | 🇧🇷Taquara | Elite | – | 214 ms | 47% | ||
| 8088 | HTTP | 🇧🇷Campo Maior | Transparent | – | 1131 ms | 46% | ||
| 28080 | HTTP | 🇧🇷São Paulo | Elite | – | 7404 ms | 45% | ||
| 8080 | HTTP | 🇧🇷São Caetano de Odivelas | Transparent | – | 3757 ms | 27% | ||
| 8080 | HTTP | 🇧🇷Valparaíso | Elite | – | 4502 ms | 26% | ||
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 33333 | HTTP | 🇧🇷Regente Feijó | Transparent | – | 4120 ms | 25% | ||
| 54443 | HTTP | 🇧🇷Salvador | Transparent | – | 3340 ms | 23% | ||
| 8989 | HTTP | 🇧🇷São Paulo | Transparent | – | 8993 ms | 18% | ||
| 8080 | HTTP | 🇧🇷Três Lagoas | Transparent | – | 8589 ms | 15% | ||
| 8080 | HTTP | 🇧🇷Venha-Ver | Transparent | – | 3713 ms | 13% | ||
| 9191 | HTTP | 🇧🇷Ipatinga | Transparent | – | 204 ms | 49% | not working last alive | |
| 9999 | HTTP | 🇧🇷Salvador | Transparent | – | 224 ms | 49% | not working last alive | |
| 8080 | HTTP | 🇧🇷Fortaleza | Transparent | – | 203 ms | 49% | not working last alive | |
| 1028 | HTTP | 🇧🇷Maravilha | Transparent | – | 216 ms | 48% | not working last alive | |
| 8080 | HTTP | 🇧🇷Canaã dos Carajás | Transparent | – | 228 ms | 47% | not working last alive | |
| 8080 | HTTP | 🇧🇷Fortaleza | Transparent | – | 173 ms | 45% | not working last alive | |
| 8080 | HTTP | 🇧🇷Itaquaquecetuba | Transparent | – | 197 ms | 43% | not working last alive | |
| 3128 | HTTP | 🇧🇷Janaúba | Transparent | – | 223 ms | 43% | not working last alive | |
| 9292 | HTTP | 🇧🇷Bady Bassitt | Transparent | – | 220 ms | 43% | not working last alive | |
| 8080 | HTTP | 🇧🇷São João de Meriti | Transparent | – | 206 ms | 41% | not working last alive | |
| 8080 | HTTP | 🇧🇷Guaratuba | Transparent | – | 224 ms | 40% | not working last alive | |
| 90 | HTTP | 🇧🇷Sao Paulo | Elite | – | 213 ms | 39% | not working last alive | |
| 8080 | HTTP | 🇧🇷Montes Claros | Transparent | – | 6501 ms | 39% | not working last alive | |
| 54443 | HTTP | 🇧🇷Salvador | Transparent | – | 4581 ms | 36% | not working last alive | |
| 8080 | HTTP | 🇧🇷Brasília | Transparent | – | 225 ms | 35% | not working last alive | |
| 8080 | HTTP | 🇧🇷Arapongas | Transparent | – | 5089 ms | 34% | not working last alive | |
| 8080 | HTTP | 🇧🇷Salvador | Transparent | – | 382 ms | 34% | not working last alive | |
| 3128 | HTTP | 🇧🇷Eunápolis | Transparent | – | 2060 ms | 31% | not working last alive | |
| 9292 | HTTP | 🇧🇷Buritama | Transparent | – | 5347 ms | 31% | not working last alive | |
| 8403 | HTTP | 🇧🇷Livramento | Transparent | – | 2080 ms | 30% | not working last alive | |
| 8080 | HTTP | 🇧🇷Valparaíso | Transparent | – | 224 ms | 28% | not working last alive | |
| 9191 | HTTP | 🇧🇷Ipatinga | Transparent | – | 198 ms | 28% | not working last alive | |
| 8080 | HTTP | 🇧🇷Vitória | Transparent | – | 216 ms | 26% | not working last alive | |
| 3132 | HTTP | 🇧🇷Fortaleza | Transparent | – | 5288 ms | 26% | not working last alive | |
| 8080 | HTTP | 🇧🇷Salvador | Transparent | – | 206 ms | 26% | not working last alive | |
| 4321 | HTTP | 🇧🇷Colinas do Tocantins | Elite | – | 231 ms | 25% | not working last alive | |
| 54121 | HTTP | 🇧🇷Betim | Elite | – | 246 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇧🇷Ribeirão Preto | Elite | – | 5032 ms | 24% | not working last alive | |
| 3180 | HTTP | 🇧🇷Muqui | Transparent | – | 3088 ms | 23% | not working last alive | |
| 8088 | HTTP | 🇧🇷Fortaleza | Transparent | – | 6678 ms | 23% | not working last alive | |
| 8080 | HTTP | 🇧🇷Penápolis | Transparent | – | 3785 ms | 22% | not working last alive | |
| 54443 | HTTP | 🇧🇷Salvador | Transparent | – | 1434 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇧🇷São Caetano de Odivelas | Transparent | – | 2208 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇧🇷Campo Grande | Transparent | – | 248 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇧🇷Laguna | Transparent | – | 209 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇧🇷São João Batista | Transparent | – | 3514 ms | 21% | not working last alive | |
| 8080 | HTTP | 🇧🇷Tangará da Serra | Transparent | – | 224 ms | 21% | not working last alive | |
| 3128 | HTTP | 🇧🇷São Mateus | Transparent | – | 2479 ms | 20% | not working last alive | |
| 3126 | HTTP | 🇧🇷Sertãozinho | Transparent | – | 2317 ms | 20% | not working last alive | |
| 80 | HTTP | 🇧🇷Porto Alegre | Elite | – | 233 ms | 20% | not working last alive | |
| 3128 | HTTP | 🇧🇷Montes Claros | Transparent | – | 217 ms | 19% | not working last alive | |
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
At a glance
This page has 19 entries marked working. Mean recorded check success across these entries is 62%; mean recorded response time, where available, is 2506 ms. By protocol: HTTP (19). By anonymity level: Elite (4), Transparent (15). The most common ports are 8080, 3128, 33333. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Brazil / HTTP. Use the recorded status and timestamps to interpret the table, then recheck before use. Availability and anonymity labels do not certify operator trust or privacy.
For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.
Free proxies — FAQ
How often is this free proxy list checked?
Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.
Are free public proxies safe to use?
Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.
How do I use a proxy from this list?
Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
People found this page by searching for
- HTTP
- SOCKS5 & HTTP proxies
- HTTP proxy list
- proxy server HTTP
- HTTP ip address
- proxy list for scraping
- free proxies
- dedicated ip
- free proxy list
- fresh elite proxies
- what is anonymous proxies
- what is a SOCKS5 proxy
- elite proxies
- socks5 proxies step by step
- is dedicated ip safe
- socks5 proxies list
- anonymous proxies
- socks5 proxy for windows
Real search phrases this page answers — the linked ones open the page that covers them in depth.