HProxy · Free Brazil pool
Free Brazil proxy list 2026
Our checker re-tests every Brazilian entry below on a rolling cycle. Read the network column first, since a fifth of the list sits on Amazon addresses that barely relay.
BrazilTransparentYou're viewing free Brazilian proxies. See the full list.
Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
Brazil proxies right now, by the numbers
The pool currently holds 500 Brazil proxies spread across 204 different networks. They respond in 4724ms at the median, much slower than the 2629ms median across the whole free pool. The busiest exits are Sao Paulo, Niteroi, Goiania. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
The Brazil list, tested row by row
These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.
Verify before you use
Run any list through the Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free Brazilian proxies.
The table above lists every Brazilian entry that answered our checker in the last 48 hours. When one of them works, the site you visit usually sees a Brazilian address rather than your own.
At 21:29 UTC on 27 September 2026, 114 of 561 listed entries had passed the most recent check. That was every live Brazilian entry in our pool, which held 20,047 live entries in all. Of the 7,845 Brazilian entries retired off busy addresses since May, 7,377 never answered a single test.
At 00:23 UTC on 28 September, eight Amazon addresses in São Paulo carried 118 of the 539 rows. Every one offered HTTPS, and only one relayed a request for us. Asked to reach Cloudflare, 90 of them showed a certificate our server rejected.
Another 37 entries sit on addresses our location data puts in Niterói and Goiânia. The Latin American registry files those blocks under Turkey, and a network called HS-SYR routes them. Six of them relayed our request: four came out in Turkey and two in Aleppo, Syria.
The other 384 entries sat on 378 addresses, and in our test 92 of them relayed a request. Of those, 90 came out in Brazil, 75 of them from the very address we list. Their exits were spread over 19 states and the Federal District, from Rio Grande do Sul to Pará.
Live Brazilian entries passed a median 26.5 percent of their checks; the rest managed 34.8. Entries that worked and later died had a median life of about 22 days, against 10 elsewhere. Either figure counts only addresses with fewer than 20 such entries, skipping Amazon's networks and one June evening. When a job needs a Brazilian address all day, paid Brazilian proxies are the tool for it.
01
How Brazil compares with the rest of the free pool
Both columns come from read-only queries of our pool, run at about 21:29 UTC.
| Measured 27 to 28 September 2026 | Brazil | Rest of the pool |
|---|---|---|
| Live entries measured | 114 | 3,906 |
| Median success rate across its own checks | 26.5% | 34.8% |
| Passed ten checks at 90 percent | 0.9% | 9.2% |
| Median latency from our server in the United States | 6,014 ms | 6,447 ms |
| Answered in under one second | 3.5% | 7.0% |
| Median lifespan of entries that died | 531 hours | 233 hours |
| Died within a day | 12.6% | 24.9% |
| Lasted more than 30 days | 37.9% | 30.8% |
| Retired entries that never answered once | 94.0% | 88.5% |
| On datacenter address space | 4.4% | 23.7% |
Brazil's live column was read at about 21:29 UTC on 27 September. The rest column and the retired shares are from 12:17 UTC on 28 September, every lifespan from 17:18. The lifespan rows cover entries that answered at least once and later stopped. On both sides, addresses holding 20 or more of a row's entries are left out. The lifespans also leave out the June evening our checker failed, and Amazon's networks.
A quarter of Brazilian entries that died were gone within about four days, against about one elsewhere. The datacenter row is the starkest: only 5 of the 114 live entries sat on datacenter space.
02
Eight Amazon addresses in São Paulo
All 539 entries our public API returned at 00:23 UTC on 28 September went through our test. Each entry had 30 seconds per request to fetch an echo page, then Cloudflare, then Google.
| Tested at 00:23 UTC, 28 September 2026 | On 8 Amazon addresses | On 415 other addresses |
|---|---|---|
| Entries on the list | 118 | 421 |
| Passed their latest check | 0 | 138 |
| Did not accept a connection | 1 | 255 |
| Completed at least one request | 1 | 120 |
| Relayed our echo | 1 | 98 |
| Came out in Brazil | 1 | 90 |
| Failed a certificate check | 90 | 0 |
All tests ran from a single HProxy server in the United States, with exits located by ip-api.com. The second column includes the 37 entries on net-High-Speed.
They stay listed because each still passes now and then. At 21:29 UTC the day before, the median Amazon entry had passed 169 of 1,175 checks. A certificate probe at 00:30 UTC went back to 50 of them, and 27 finished the encrypted handshake. Each showed a certificate made out to www.cloudflare.com, and our server could verify none of them.
Most issuers read like device labels, such as Vigor Router, cert-web-mikrotik and Tuya Smart Device. One named a GlobalSign authority; we fetched its real certificate, and that key refused the signature. Asked for a plain page, 48 answered under 42 server names, each with the words "Could not connect".
One row did relay our request, from its own Amazon address in São Paulo. We cannot tell who runs these addresses, but the rest act less like proxies than like a honeypot. NIST's glossary describes that as a system built to attract intruders.
03
The 37 entries that are not in Brazil
Our table shows 37 entries under the network name net-High-Speed, each placed in Niterói or Goiânia. Eleven of them had passed their latest check when we tested the list.
LACNIC, the registry for Latin America, lists Turkey as the country of all six blocks they sit on. When we checked on 27 September, RIPEstat's routing data showed a network called HS-SYR announcing those blocks.
Six of the 37 relayed our request: four exits in Himmetdede, Turkey, and two in Aleppo, Syria. Cloudflare answered through three of them from its Istanbul data center. Every other source that gave a location put these addresses outside Brazil.
04
Which entries carried traffic
We asked each entry in a single protocol, trying SOCKS5 first when it was offered. Off Amazon, the SOCKS4-only entries relayed most often: 49 of 120.
| Tested at 00:23 UTC, 28 September 2026 | Entries | Relayed our echo |
|---|---|---|
| HTTPS | 148 | 24 |
| HTTP | 139 | 23 |
| SOCKS5 | 14 | 2 |
| SOCKS4 only | 120 | 49 |
| All entries off Amazon | 421 | 98 |
We preferred SOCKS5, then HTTPS, HTTP and SOCKS4, and tried each entry in only one of them. A SOCKS4 row was asked with a plain SOCKS4 request, which carries the site's numeric address.
SOCKS4 rows relayed at more than twice the rate of any other protocol in this test. A second test at 05:11 UTC agreed, by less: 35 of 120 against 31 of 115 for HTTP.
05
Where the working entries came out
Cloudflare answered 58 of our requests, 53 of them from its Brazilian data centers. São Paulo led with 25, then Rio de Janeiro with 21, and four more came from Istanbul.
The Tor Project's own check reached 41 of the 99 working entries and found none on Tor. One entry our list places in Brasília came out in Singapore instead.
06
How to use a free Brazilian proxy
Check each row's network before you copy it, and skip Amazon and net-High-Speed. Try the SOCKS4 rows first: they relayed best in both our tests, 49 and then 35 of 120. The second time the lead was narrow: 29 percent against 27 for HTTP rows.
Among the 114 live entries, 30 answered on port 8080 and 10 on port 5432. Match the port and protocol exactly to what the row shows.
After connecting, open a page that shows your address and country before any real work. Eight of the 99 working entries came out abroad, and 15 more used a different Brazilian address.
Thirty of the 114 live entries were graded transparent: they pass your own address to the site. Whoever runs an entry can read anything you send without HTTPS, so keep logins and payments off it.
Plan on replacing entries often: the typical live Brazilian entry passed only about a quarter of its checks.
The Uptime column is a fair guide. In the 00:23 test, rows showing 50 percent or more relayed 11 of 36. The other 503 relayed 88, a little over half as often. An Amazon row can still fool it: one showed 75 percent or more and relayed nothing.
Questions
Frequently asked.
Yes, and no account is needed, but others share every entry, so test one right before it matters.
Over a fifth of the list sits on eight Amazon addresses, and only one of those rows relayed. From our server in the United States, 255 of the other 421 did not connect within 30 seconds.
Live Brazilian entries needed a median 6.0 seconds to answer, timed from our server in the United States. Elsewhere, busy addresses aside, it was 6.4 seconds; neither suits work that waits on each page.
Only a few: 7 of the 114 live entries were placed in São Paulo city on 27 September. The 118 Amazon rows our list places there relayed just one request in our test.
Brazil proxies that target down to the city are available from HProxy, billed as you go. Purchased traffic has no scheduled expiry date, and nothing is billed by subscription.
Most working ones do: 91 of the 99 that relayed our request came out in Brazil. The other eight exited in Turkey, Syria and Singapore. Every request went from our server in the United States, on 28 September 2026.
Not for anything private: in our test, 90 Amazon entries showed certificates our server could not verify. Another 30 live entries were transparent, passing your own address along. Keep logins and payments away from every free entry.
Half of those that worked and later died lasted over 22 days, against 10 for the rest. Just 12.6 percent died within their first day, against 24.9 percent elsewhere. Both counts skip Amazon's networks, one June evening and addresses carrying 20 or more such entries.
Our location data files 37 entries under Brazil, but LACNIC lists Turkey as the country of their blocks. A network called HS-SYR routes them; in our test, two relayed from Aleppo and four from Turkey.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
Docs and AI
The free list, in your assistant and in your code.
We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude, ChatGPT, Cursor or any assistant that speaks MCP, and the list's API is documented end to end.
Every product has its own reference in the docs. Something the list does not give you? Tell us.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
Let your assistant pull the list
The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.
The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.
All the machine lanes- MCP server
- Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from a terminal. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Install it in one line: curl -fsSL https://hproxy.com/install.sh | sh (macOS, Linux) or irm https://hproxy.com/install.ps1 | iex (Windows). - REST, no key
- Plain HTTP with CORS on, which is all an agent with a fetch tool needs.
curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"
Instructions for an assistant, in full
Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.
You can use HProxy's free proxy list, which needs no API key and no account.
GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.
Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it. It is rate limited per IP (120 requests in a burst, then 2 a second) and answers 429 with Retry-After past that.
These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt
There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. From a terminal the same tool is `hproxy list --country DE --protocol socks5 --limit 20`. Install the hproxy command in one line: curl -fsSL https://hproxy.com/install.sh | sh on macOS and Linux, or irm https://hproxy.com/install.ps1 | iex in PowerShell on Windows. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.