HProxy · Free Netherlands pool
Free Netherlands proxy list 2026
Every Dutch row on our free list, tested twice from our server. Most run on rented servers in Amsterdam, and a few exit in other countries.
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
Netherlands proxies right now, by the numbers
The pool currently holds 256 Netherlands proxies spread across 48 different networks. They respond in 1069ms at the median, much quicker than the 3234ms median across the whole free pool. The busiest exits are Amsterdam, Dronten, Haarlem. 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 Dutch 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 Dutch proxies.
Plenty of free proxies claim a Dutch address, and few of them answer. Our pool had 68 live Dutch entries at 05:39 UTC on 28 September 2026.
Most sat on rented servers in Amsterdam, and 50 of the 68 carried our datacenter flag.
One address there, 144.124.251.24, held 113 of the 235 rows on the 48-hour list. None of them relayed anything for us in two passes.
Tested from our US server, only 13 of the 68 live entries relayed a request. Four of those 13 exited outside the Netherlands.
Nearly half the live entries, 32 of 68, were transparent and passed your address along. For work that has to stay Dutch, paid Netherlands proxies are the steadier choice.
01
Rented servers, mostly in Amsterdam
The table compares the Dutch slice at 12:01 UTC with the entries on the pool's ordinary addresses.
| Measured 28 September 2026 | Netherlands | Rest of the pool |
|---|---|---|
| Live entries measured | 47 | 3,846 |
| Median success rate across its own checks | 46.2% | 34.3% |
| Passed ten checks at 90 percent | 4.3% | 9.3% |
| Median latency from our server in the United States | 6,969 ms | 6,281 ms |
| Flagged as datacenter by our list | 80.9% | 22.2% |
Read at 12:01 UTC, leaving out addresses that hold 20 or more live entries; no Dutch address did.
At 05:39 UTC, the hosting networks VDSINA, Timeweb's TWC-EU and Liteserver carried 21, 8 and 6 live entries.
Amsterdam held 54 of the 68, Dronten 6, and Rotterdam none at all.
02
Nearly half the list on one address
At 05:40 UTC, 113 of the 235 list rows sat on one VDSINA address in Amsterdam, 144.124.251.24.
Our checker had passed 18 of them between 05:00 and 05:08, on ports from 10101 to 11480.
None took a connection in either of our tests at 05:40, nor one at a time at 05:45.
At 06:20 its 16 live entries let us connect, then answered with HTTP 429, too many requests.
In the list test that followed, none of its 114 rows took a connection. Tried one at a time from 06:23, its live entries took none either.
At 05:40 our list showed them at 4 to 33 percent uptime, so most checks found them shut.
All 18 were graded transparent when they last worked.
03
Thirteen relays, four of them abroad
For each live row, ip-api.com reported which address reached it and where it placed that address.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 68 |
| Did not accept a connection | 32 |
| Relayed the plain web request | 13 |
| Of those, exiting in the Netherlands | 9 |
| Of those, leaving from the listed address | 11 |
| Opened Google over an encrypted connection | 16 |
| Certificate did not verify | 0 |
Run from one server in the United States at 05:40 UTC; ip-api.com placed the exits.
The thirteen relays took a median of about 9.3 seconds, and 23 more rows connected but relayed nothing.
Two relays handed our request to another address, in Moscow and in England.
Two more left from their own address, which ip-api places in Los Angeles and Istanbul.
Location databases disagree on such rows: for one of them, ours, the registry and ip-api named three countries.
The 122 list rows off the Amsterdam address gave 17 relays, 15 of them exiting in the Netherlands.
Forty minutes later, 10 of 67 live entries relayed; one of them exited in Seattle from another address.
The second list test drew 15 relays from the same 122 rows, 11 of them in the Netherlands.
Cloudflare marked three of those relays T1, its code for Tor; they exited in Austria and Germany.
About eight minutes later, the Tor Project's own check got no answer through any of the three.
Only 4 of the 17 rows that relayed in the first list test relayed again in the second.
04
Working entries last longer here
Nearly nine in ten retired entries on ordinary addresses never answered: 6,630 of 7,699, against 88.7 percent elsewhere.
Each working entry is timed from first sighting to last answer, and one busy Amsterdam address stays out.
| Measured 28 September 2026 | Netherlands | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,404 | 296,519 |
| Left out: on addresses with 20 or more | 316 | 261,353 |
| Left out: the evening of 14 June | 129 | 9,063 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 959 | 25,037 |
| Median lifespan of those counted | 16.3 days | 9.7 days |
| Of those counted, stopped within a day | 21.2% | 24.8% |
| Of those counted, lasted more than thirty days | 20.9% | 31.3% |
Read at 17:18 UTC; the June evening our checker failed, marking about 128,000 entries dead, stays out.
So the median working Dutch entry lasts about a week longer than the pool's. Fewer passed thirty days, though: 20.9 percent against 31.3.
05
Light filtering on Dutch networks
OONI's volunteers ran 1,027,568 web tests from the Netherlands in the month to 28 September.
Of those, 94.2 percent loaded normally, and just 1,698 matched a known block page.
No site tested 100 times or more was confirmed blocked in even 3 percent of its tests. Facebook opened normally in 9,354 of 9,997.
06
Putting a Dutch row to work
The common ports were 3128 with 18 live entries, 8080 with 11 and 1080 with 8.
SOCKS5 entries relayed 5 of 12 in the first live test, then 5 of 13.
Rows at 50 percent uptime or more relayed at least twice as often as the rest, both times.
That comparison leaves out the rows on 144.124.251.24, which relayed nothing.
Even so, most of those rows failed, so test any row before you rely on it.
A row that fails may still work minutes later. In the first pass, 17 of the 22 live rows that relayed did it in only one test.
The second pass gave 9 of 14.
Skip rows on 144.124.251.24; none of them relayed for us in two passes.
Paste a row into our proxy checker for its speed, anonymity and country before relying on it.
Questions
Frequently asked.
Usually, not always: 44 of the 55 relays in our four tests exited in the Netherlands. The rest either passed our request to another address abroad or left from an address ip-api places abroad.
A little slower than the pool: half the live Dutch entries needed over 6,969 ms at 12:01 UTC. Half of the pool's ordinary entries answered within 6,281 ms, both timed from our US server. The thirteen live relays took about 9.3 seconds at the median.
Keep private work off them: 32 of the 68 live Dutch entries were transparent that morning. Some relays also passed our request on to a second server abroad. Cloudflare read three of those as Tor exits.
Once working, a Dutch entry lasted a median 16.3 days; entries elsewhere in the pool lasted 9.7. Addresses with 20 or more such entries are left out, which removes one Amsterdam address with 316. Both also skip Amazon's networks and the evening of 14 June, when a checker fault recorded mass deaths.
Nearly half the 48-hour list sat on one Amsterdam address that relayed nothing in either pass. Of the other 122 rows, 17 relayed in the first pass and 15 in the second.
Amsterdam, yes: it held 54 of the 68 live entries at 05:39 UTC, and Rotterdam none. Towns come from a location database, and such databases disagree, as the exits above show.
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.