HProxy · Free Iran pool
Free Iran proxy list 2026
The Iran list below holds only the entries our checker heard from in the last two days. In our test on September 28, 24 of its 115 entries carried a request.
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
Iran proxies right now, by the numbers
The pool currently holds 107 Iran proxies spread across 41 different networks. They respond in 4820ms at the median, slower than the 3245ms median across the whole free pool. The busiest exits are Tehran, Dubai, Shiraz. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
What the Iran list did when we tested 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 Iranian proxies.
Set a row's address and port in your browser; a working entry usually shows sites an Iranian address. Of 24 working entries in our test, 19 exited in Iran and five in Germany or Turkey.
At 22:57 UTC on September 27, 2026, 25 of the 115 listed entries were live. That was a small share of our pool, which held 21,627 live entries in the same minute. The list was once far longer: our engine has retired 229,600 Iranian entries since May. Of those, 152,203 sat on 73 addresses of a single network, and none of them is listed today.
Today's live entries are spread thin: 25 entries on 25 addresses across 18 networks. Respina held 4, the Iran Telecommunication Company 3, and 7 of the 25 sat on datacenter space. The rest of our pool, busy addresses aside, was close to that, at 23 percent.
The test began at 00:24 UTC on September 28 and covered all 115 entries. Each request came from our server in the United States and had 30 seconds. 58 of them never accepted a connection, and 24 relayed our request. Of those 24, 15 left from the listed address in Iran and 4 from another Iranian address.
The median Iranian entry that worked and later stopped answering for good lasted about 4 days. A third of them died within a day. Elsewhere in the pool, that median came to about 10 days. The 73 busy addresses fall outside both figures, which skip any address with 20 or more such entries. Neither counts Amazon's networks or the June evening of our checker's failure. The live ones held up better: 5 of the 25 passed ten checks at 90 percent.
Eleven of the 25 live entries were transparent, so they hand your real address to every site. When a task needs an Iranian address that stays up, paid Iran proxies are the option.
01
Iran next to the rest of the free pool
The Iranian column is our 22:57 UTC reading, set against a later read of the rest.
| Measured September 27 to 28, 2026 | Iran | Rest of the pool |
|---|---|---|
| Live entries measured | 25 | 3,984 |
| Median success rate across its own checks | 40.3% | 34.5% |
| Passed ten checks at 90 percent | 20.0% | 8.9% |
| Median latency from our server in the United States | 5,651 ms | 6,462 ms |
| Answered in under one second | 8.0% | 7.0% |
| Median lifespan of entries that died | 90 hours | 238 hours |
| Died within a day | 33.4% | 24.6% |
| Lasted more than 30 days | 18.2% | 31.1% |
| On datacenter address space | 28.0% | 23.2% |
Iran's live figures were read at 22:57 UTC on September. 27 Our 12:17 UTC read of September 28 supplies the other column, and a 17:18 read every lifespan. The lifespan rows count entries that answered and then died, on addresses with fewer than 20 such entries. The rest column also drops addresses with 20 or more live entries. No lifespan counts Amazon's networks, nor the June evening our checker failed.
Few live entries make every share here fragile: one server coming or going moves it by four points.
02
What the 115 entries did in our test
Each entry was asked to fetch an address-echo page, then Cloudflare, then Google.
| Tested at 00:24 UTC, September 28, 2026 | Entries |
|---|---|
| Entries on the list | 115 |
| Did not accept a connection | 58 |
| Completed at least one request | 26 |
| Relayed our echo | 24 |
| Came out in Iran | 19 |
| Left from the listed address in Iran | 15 |
| Opened Google | 3 |
| Failed a certificate check | 0 |
Tests ran from our server in the United States, and ip-api.com gave each exit's country.
Three of the five exits abroad were German, on G-Core and Hetzner networks, and two were in Turkey. By protocol, HTTP rows relayed 17 of 74 and SOCKS4 rows, asked in plain SOCKS4, 4 of 16. HTTPS rows relayed least often, 2 of 22, and the three SOCKS5 rows gave 1. No entry showed a certificate our server could not verify.
03
The Uptime column on the Iran list
We joined each test result to the Uptime figure the list showed for that row. Rows at 50 percent or more relayed 5 of 14; the other 101 relayed 19. The samples are small, so treat it as a pointer rather than a rule.
04
Filtering inside Iran
OONI, a nonprofit that publishes internet censorship measurements, collects tests run by people inside Iran. In the month to September 27, 3,891 of 5,053 tests of www.instagram.com there were confirmed blocked. YouTube showed 3,274 confirmed blocks in 4,545 tests, and x.com 1,714 in 2,663.
Read on September 27, OONI's month of tests from Iran held 214,803 confirmed blocks in 715,617 results. Google and Wikipedia loaded normally in almost every test.
A request that exits in Iran leaves through an Iranian network, so the same filtering can apply.
05
Where the requests surfaced
Cloudflare answered through only four entries: three times from its data center in Frankfurt and once from Istanbul. None of the four carried the code T1, which Cloudflare uses for traffic from the Tor network.
The Tor Project's own check did not answer through any of the 24 working entries.
06
How to use a free Iranian proxy
Enter the row's port and protocol exactly, then open a page through it that reports your country.
Five of the 24 exits in our test were outside Iran, so check before you rely on one. Whoever runs an entry can read anything sent without HTTPS, and 11 live entries also reveal your address.
Expect to switch often: half the entries that died were gone within about four days.
Questions
Frequently asked.
Yes: no payment and no account, though everyone shares the same entries, so test one right before use.
Many stop answering soon after they appear: half of those that died lasted about four days or less. Tested from our server in the United States, 58 of the 115 never took a connection at all.
Measured from our server in the United States, the typical live Iranian entry needed 5.7 seconds. For the rest of our pool, with busy addresses set aside, it was 6.5 seconds.
Usually not: a request that exits in Iran can meet the same filtering. OONI confirmed Instagram blocked in 3,891 of 5,053 tests from Iran in the month to September. 27
Iran proxies with targeting down to the city are on sale at HProxy, with no subscription. Purchased traffic has no scheduled expiry date: what you buy stays on your plan until you use it.
Usually: 19 of the 24 that relayed our request exited in Iran. The other five exited in Germany and Turkey. We ran that test on September 28, 2026, from our server in the United States.
Treat every entry as a stranger's server: it can read what you send without HTTPS. Eleven of the 25 live entries were transparent and pass your own address along. Keep logins and payments off them.
Not long: half the Iranian entries that worked and then died were gone within about 4 days. Elsewhere in our pool the figure was about 10 days. A third of the Iranian ones died within a day. Neither figure counts an address with 20 or more such entries. Amazon's networks are left out too, as is the June evening our checker failed.
Some: our list places 24 of its 115 entries in Tehran, though most rows carry no city.
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.