HProxy · Free Italy pool
Free Italy proxy list 2026
Only a handful of Italian free proxies are live at a time in our pool. We name the Amazon rows in Milan that never relayed for us.
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
Italy proxies right now, by the numbers
The pool currently holds 138 Italy proxies spread across 28 different networks. They respond in 2036ms at the median, much quicker than the 4060ms median across the whole free pool. The busiest exits are Milan, Siena, Vignola. 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 Italian 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 Italian proxies.
Italy's free list is small. When we read our pool at 04:32 UTC on 28 September 2026, 10 Italian entries were live.
The 48-hour list held 76 rows, and 39 of them sat on three Amazon addresses in Milan.
None of those 39 relayed our test request; the other 37 gave 11, all exiting in Italy.
Of the 10 live entries, 4 relayed a plain request from our server in the United States. A second pass, 39 minutes later, got 2 relays from 12 live entries.
Half the live entries were transparent, 5 of 10, and showed every site your address. For steady work, paid Italy proxies are the safer route.
01
Few live entries, almost one network each
The Italian figures date from 13:25 UTC; beside them sit the pool's ordinary addresses, read that minute.
| Measured 28 September 2026 | Italy | Rest of the pool |
|---|---|---|
| Live entries measured | 11 | 4,152 |
| Median success rate across its own checks | 31.3% | 34.4% |
| Passed ten checks at 90 percent | 0% | 8.7% |
| Median latency from our server in the United States | 7,857 ms | 6,318 ms |
| Flagged as datacenter by our list | 27.3% | 21.2% |
Read at 13:25 UTC; busy addresses, those with 20 or more live entries, sit outside both columns.
At 04:32 UTC, every live entry sat on a different network. Among them were FASTWEB, Aruba, MegaWeb and Sirius Technology.
Four of the ten carried our datacenter flag, the Aruba entry among them.
02
Four live relays, then two
Our server sent a plain request through each live row to ip-api.com, which reports the address it sees.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 10 |
| Did not accept a connection | 3 |
| Relayed the plain web request | 4 |
| Of those, exiting in Italy | 4 |
| Of those, leaving from the listed address | 3 |
| Opened Google over an encrypted connection | 0 |
| Certificate did not verify | 0 |
From one server in the United States, begun at 04:33 UTC; ip-api.com located each exit.
The four relays took a median of about 4.8 seconds; three more rows connected and relayed nothing.
Across the whole 48-hour list, the 37 rows off Amazon gave 11 relays, each from its listed address.
The second pass drew just 3 relays from the same 37 list rows. Of the 11 rows that relayed in the first pass, only one relayed in the second.
03
The Amazon rows in Milan
Three addresses carried 39 of the 76 list rows on 28 September: 15.161.59.54, 15.160.132.166 and 15.160.116.45.
ARIN files both of their blocks as AMAZON-MXP, held by Amazon Data Services Italy. Our database places all three in Milan, and none of their 39 rows was live.
Every one of the 39 took our connection, then answered the plain request with an error. At 04:33, 27 of them also presented a certificate that failed verification.
At 05:12, the same three addresses held 34 rows; none relayed, and 4 showed a failed certificate.
By 13:27 UTC, 1,059 entries on ten Amazon addresses in Milan had worked and stopped, these three included.
Another free list, read that morning, put 18 of its first 20 Italian rows on these blocks. It gave each of the 18 an uptime of 100 percent.
04
Short lives for working entries
Most retired Italian entries never answered even once: 1,030 of the 1,182 on ordinary addresses.
The pool's other ordinary addresses show nearly the same share, 88.6 percent.
Those that did work are timed from first sighting to last answer, without the ten busy Amazon addresses.
Other entries on Amazon's networks stay out as well; the Amazon rows in our test relayed nothing.
| Measured 28 September 2026 | Italy | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,232 | 296,691 |
| Left out: on addresses with 20 or more | 1,058 | 260,611 |
| Left out: the evening of 14 June | 10 | 9,182 |
| Left out: other entries on Amazon's networks | 33 | 1,033 |
| Counted | 131 | 25,865 |
| Median lifespan of those counted | 3.5 days | 9.8 days |
| Of those counted, stopped within a day | 41.2% | 24.6% |
| Of those counted, lasted more than thirty days | 19.1% | 31.0% |
Read at 17:19 UTC. The five hours on 14 June when our checker wrongly marked about 128,000 entries dead stay out.
A working Italian entry lasted a median 3.5 days, about a third of the pool's figure. Two in five stopped within their first day, against a quarter across the pool.
05
Italian filtering follows the exit
A request through an Italian row leaves from a network in Italy, where Italy's own blocks apply.
OONI's volunteers tested 2,206 sites from Italy in the month to 28 September, 863,562 tests in all. They confirmed blocks on 265, among them film and sport streaming, music download and betting sites.
Large platforms loaded normally: Facebook opened in 8,496 of 8,555 tests, and YouTube in 8,545 of 8,567.
06
Putting an Italian row to work
Ports 8080 and 3128 carried four live entries each; copy the port along with the address.
Eight live entries spoke HTTP, three HTTPS and one SOCKS4; none offered SOCKS5 when we read the pool.
Before real use, run each candidate through our proxy checker for its status, speed, anonymity, country and network.
Skip rows on 15.160 and 15.161 addresses in Milan; they relayed nothing in 73 tries over two passes.
Try a failing row a second time. In the first pass, 4 of 6 relaying live rows did so in one test of two. In the second, 3 of 3 did.
Questions
Frequently asked.
Yes, when one relayed: all 20 relays in our four tests on 28 September exited in Italy. All four ran from our server in the United States, and ip-api.com placed each exit.
At 13:25 UTC our checker in the United States timed the median live entry at 7,857 ms. On the pool's ordinary addresses the figure was 6,318 ms, so Italian rows ran slower. The four live relays answered in about 4.8 seconds at the median.
Not for anything private: half the live Italian entries, 5 of 10, were transparent on 28 September 2026. In our first pass, 27 Amazon rows also showed certificates that failed verification.
Not long: working entries lasted a median 3.5 days, against 9.8 elsewhere in the pool. Of those, 41.2 percent stopped within a day. Ten Amazon addresses with 20 or more such entries each, 1,058 in all, are left out. The count also skips the rest of Amazon's entries and the June evening our checker failed.
Over half the 48-hour list sat on three Amazon addresses in Milan, which took connections and relayed nothing. The 37 other rows gave 11 relays in our first pass and 3 in the second.
Hardly: Milan held one live entry at 04:32 UTC and two at 05:12, and Rome none. The town beside each row comes from a geolocation database, so treat it as an estimate.
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 the free HProxy app's command line. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Comes with the free HProxy app: hproxy.com/proxy-checker - 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.
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`. 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.