HProxy · Free Israel pool
Free Israel proxy list 2026
Israeli rows from our free list, each tested twice from our server. Few work, and most of the list sits on Amazon addresses in Tel Aviv.
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
Israel proxies right now, by the numbers
The pool currently holds 139 Israel proxies spread across 6 different networks. They respond in 1650ms at the median, quicker than the 1890ms median across the whole free pool. The busiest exits are Tel Aviv, Haifa, Rishon LeTsiyyon. 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 our tests found on the Israeli list
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 Israeli proxies.
Israel's free list is nearly empty: at 06:51 UTC on 28 September 2026, 3 entries were live.
The 48-hour list showed 69 rows, but 63 of them sat on five Amazon addresses in Tel Aviv.
None of the 63 passed our request on; 51 showed a certificate our server could not verify.
The six other rows gave two relays, each leaving from its listed address in Israel.
With so few working rows, paid Israel proxies are the realistic route to a steady Israeli address.
01
Three live entries, three networks
Bezeq International, Hot-Net and O.M.C. Computers each carried one of the three live entries, by their registry records.
Our database placed them in Tel Aviv, Rishon LeZion and Haifa, and none in Jerusalem.
Two were graded elite and one transparent, so one of three showed sites the address behind it.
02
Five Amazon addresses in Tel Aviv
At 06:52 UTC, 63 of the 69 list rows sat on 51.17.154.141, 51.17.99.135, 51.16.4.39, 51.85.44.149 and 51.84.101.19.
Our database puts all five on Amazon's network in Tel Aviv. RIPE files their blocks under A100 ROW Inc.
Each took our connection, then answered the plain request with an error or cut it off.
The second pass at 07:32 met 57 rows on those five addresses: no relay, 53 bad certificates.
By the time we tested, twelve Amazon addresses there had carried 1,091 entries that worked and then stopped. Four of these five were among the twelve.
On another free list, read that same morning, all 20 first-page rows sat on these blocks. That list printed an uptime of 100 percent beside every one of those 20 rows.
| Measured 28 September 2026 | Amazon rows | Other rows |
|---|---|---|
| Rows tested | 63 | 6 |
| Took no connection | 0 | 1 |
| Relayed the plain web request | 0 | 2 |
| Of those, exiting in Israel | 0 | 2 |
| Certificate did not verify | 51 | 0 |
Every list row at 06:53 UTC, tested from one server in the United States; ip-api.com placed exits.
03
Two relays, both in Israel
The two relays came from Bezeq in Rishon LeZion and from O.M.C. Computers in Haifa.
Of the three live entries, only the Bezeq row relayed in our live test, in under a second.
The Haifa row timed out there, then relayed in the list test half a minute later.
Thirty-nine minutes on, only the Bezeq entry was still live, and it relayed again in about two seconds.
This time the Hot-Net row relayed from the list, while the Haifa row took no connection.
04
Too few Israeli entries to time
Nearly all retired Israeli entries on ordinary addresses never answered: 1,063 of 1,105, 96.2 percent against 88.6 elsewhere.
The table shows what our lifespan rules leave out, and how few Israeli entries remain.
| Measured 28 September 2026 | Israel | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,168 | 296,661 |
| Left out: on addresses with 20 or more | 1,108 | 260,481 |
| Left out: the evening of 14 June | 4 | 9,189 |
| Left out: other entries on Amazon's networks | 45 | 1,021 |
| Left to time | 11 | 25,970 |
Taken at 15:55 UTC; on the June evening, our checker failed and marked about 128,000 entries dead. The Amazon rows of this list relayed nothing in 120 tries.
Eleven entries are too few for a median, so we give none for Israel. The 25,970 entries timed elsewhere in the pool lasted about 10 days at the median.
05
Almost no filtering in Israel
OONI counted 123,679 web tests by volunteers in Israel over the month to 28 September.
Nearly all, 97.0 percent, loaded normally; exactly one test matched a known block page.
Facebook loaded as usual in 638 of 654 tests, and YouTube in 639 of 648.
06
Putting an Israeli row to work
Skip rows on the 51.16, 51.17 and 51.84 to 51.88 blocks; none relayed in 120 tries.
Run any row through our proxy checker first; it shows speed, anonymity and country.
Questions
Frequently asked.
When one relays, yes: all six relays in our four tests left from listed Israeli addresses. We ran those tests from one server in the United States, with ip-api.com placing each exit.
Measured from the United States, the three live entries answered our checker in a median 3,210 ms. The Bezeq relay took 932 ms in the first pass and 1,940 in the second.
Not for anything private: the Amazon rows showed 51 certificates that failed verification, then 53. One of the three live entries was also transparent.
We cannot say yet: only 11 Israeli entries that worked and later stopped can be timed. Those 11 remain after busy addresses, Amazon's networks and one June evening are left out. Eleven is too few for a median; elsewhere in the pool it was about 10 days.
Most of the 48-hour list sat on five Amazon addresses in Tel Aviv, which relayed nothing. The six other rows gave two relays in each pass, all in Israel.
One live entry sat in Tel Aviv at 06:51 UTC, and none in Jerusalem. With three live entries in the country, and one by 07:32, there is little to choose from.
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.