HProxy · Free Australia pool
Free Australia proxy list 2026
Our checker heard from every Australian entry below within the past two days. Most sat on Amazon addresses that carried nothing in our test, so check a row first.
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
Australia proxies right now, by the numbers
The pool currently holds 213 Australia proxies spread across 16 different networks. They respond in 1102ms at the median, much quicker than the 3664ms median across the whole free pool. The busiest exits are Sydney, Melbourne, South Brisbane. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
Australia's free list, as our test saw it
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 Australian proxies.
Each row below is a free Australian entry that answered our checker within the last 48 hours. Set one in your tool, then check where it exits before you trust it. Only 8 entries relayed our test request, and 6 of them came out inside Australia.
Only 14 live entries in our whole pool were Australian at 03:53 UTC, out of 25,967. Off busy addresses, 1,376 of the 1,529 Australian entries retired since May never answered once. That is close to the rest's share; counting 22 busy addresses, Australia's falls to 36.5 percent.
Our 03:54 UTC test found 207 of the 230 rows on 11 Amazon addresses in Sydney and Melbourne. None of those rows had passed a check since 26 September, and none carried a request for us. Asked for Cloudflare, 87 of them showed a certificate that failed our server's check.
The other 23 rows sat on 21 addresses in 16 networks; only 8 relayed our echo. Five left from the listed address inside Australia, and a sixth from another address on the same network. The last two exited in Indonesia and Los Angeles from the very address our list places in Australia.
Our server in the United States got answers from live Australian entries in 5.9 seconds at the median. At the median, Australian entries that worked before dying lasted about 4 days; elsewhere, about 10. Far fewer lasted past 30 days: 17.0 percent, against 31.0 for the rest of our pool. The rule leaves out busy addresses with 20 or more such entries, which sets aside 2,708 of 2,861. Nor does it count Amazon's networks, or the evening in June when our checker went wrong. For an Australian address that stays up, paid Australian proxies are the better fit.
01
Australia against the rest of the free pool
The 14 Australian entries face the rest of the pool here, minus its busy addresses.
| Measured 28 September 2026 | Australia | Rest of the pool |
|---|---|---|
| Live entries measured | 14 | 3,975 |
| Median success rate across its own checks | 35.6% | 34.7% |
| Passed ten checks at 90 percent | 0.0% | 9.0% |
| Median latency from our server in the United States | 5,881 ms | 6,405 ms |
| Answered in under one second | 0.0% | 7.0% |
| Median lifespan of entries that died | 107 hours | 236 hours |
| Died within a day | 19.3% | 24.7% |
| Lasted more than 30 days | 17.0% | 31.0% |
| Retired entries that never answered once | 90.0% | 88.6% |
Australia's live figures are from 03:53 UTC, the rest column and retired shares from 12:17, lifespans from 17:18. Lifespans cover entries that answered before they died, on addresses with under 20 such entries. Busy addresses are left out of every row. No lifespan here includes an entry on Amazon's networks, or one from the June evening our checker failed.
Australia's 14 live entries pass about as many checks as the rest and answer a little faster. None of them passed ten checks at 90 percent or answered within a second.
02
Eleven Amazon addresses behind 207 of 230 rows
We put all 230 rows of the Australian list through our test at 03:54 UTC. For every row we asked for three things in turn: its exit, then Cloudflare, then Google. Each request had up to 30 seconds.
| Tested at 03:54 UTC, 28 September 2026 | On 11 Amazon addresses | On 21 other addresses |
|---|---|---|
| Entries on the list | 207 | 23 |
| Passed their latest check | 0 | 14 |
| Did not accept a connection | 1 | 11 |
| Completed at least one request | 0 | 10 |
| Relayed our echo with a visible exit | 0 | 8 |
| Exited in Australia from the listed address | 0 | 5 |
| Opened Google | 0 | 4 |
| Failed a certificate check | 87 | 0 |
One HProxy server in the United States sent every request. The exit country is the one ip-api.com gives, and Google means its generate_204 check.
At 03:56 UTC we probed 72 Amazon rows; all 72 completed the handshake with a certificate for www.cloudflare.com. Our server trusted none of them; their 35 issuer names ran from DigiCert to GitLab and Cisco Firepower. Twenty-two named a public authority; we tested 19 against that authority's own key, and every signature failed.
Asked for a plain page, 71 replied with Could not connect, under 65 server names. We do not know who runs these 11 servers. What they returned looks like a honeypot, which NIST describes as attractive to potential crackers and intruders.
03
Where the Australian relays exited
Five relays left from the listed Australian address, in Sydney, Brisbane and Melbourne. A sixth came out of another address on the same Melbourne network.
Two exited abroad from their own listed address: one in Indonesia, one in Los Angeles. For those two, the location our list shows and the echo's answer disagree.
Cloudflare's trace answered five times: twice from Melbourne, once each from Sydney and Jakarta. The fifth answer carried T1, Cloudflare's country code for Tor, through an entry that never relayed our echo. The Tor Project's check answered for 2 of the 8 relays, and neither was Tor.
04
How to use a free Australian proxy
Use each row as a whole: its address, port and protocol belong together in your tool. Pass over the Sydney and Melbourne rows on Amazon addresses, since not one of 207 relayed for us.
Look up your exit through the entry before real work: two of the 8 relays exited outside Australia.
Drop any entry that triggers a certificate warning; a proxy that only relays shows the site's own certificate. Free SOCKS5 entries add no encryption: under RFC 1928 they take the method with no authentication.
Two of the 14 live Australian entries were transparent: they hand the site your own address.
Keep a few rows ready, since free entries stop without notice. One in four Australian entries that died did so within 36 hours of first being seen.
Questions
Frequently asked.
Yes, nobody charges for them or asks you to register, and other people may use the same entry. Test one right before the task that needs it.
Nine rows in ten sat on Amazon addresses that relayed nothing: 207 of 230 on 28 September 2026.
Slightly quicker than other free entries: a median 5.9 seconds, against 6.4 for the rest. We measured both from our server in the United States, leaving busy addresses out.
Melbourne had 5 of the 14 live Australian entries on 28 September 2026, and Sydney had 2. The Amazon rows placed in both cities relayed nothing in our test.
Six of the 8 entries that relayed in our test on 28 September 2026 came out in Australia. The other two exited in Indonesia and the United States, from their listed address.
Not for anything private: the person behind an entry can read what you send unencrypted. In our test, 87 Amazon rows answered Cloudflare with a certificate that did not verify. Keep logins and card numbers off free proxies.
About 4 days at the median for entries that answered and then died, well under the 10 elsewhere. Only 17.0 percent passed 30 days, about half the rate of the rest of our pool. Addresses that held 20 or more such entries were not counted on either side. Amazon's networks were left out as well, as was the evening in June when our checker failed.
HProxy sells paid Australian proxies, residential or datacenter, and the residential ones can target down to the city. Purchased traffic has no scheduled expiry date, and with no subscription, a quiet month costs nothing.
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.