HProxy · Free Netherlands HTTPS pool
Free Netherlands HTTPS proxy list 2026
Every proxy below speaks HTTPS from an address in the Netherlands, re-checked on a rolling cycle. The numbers on this page come from our own checker, measured on 15 September 2026.
Netherlands HTTPS proxies right now, by the numbers
The pool currently holds 134 Netherlands HTTPS proxies spread across 15 different networks. They respond in 1127ms at the median, much quicker than the 8254ms median across the whole free pool. The busiest exits are Amsterdam, Alphen aan den Rijn, Haarlem. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By protocol
By anonymity
Biggest hosting networks
About
About these free Netherlands HTTPS proxies
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 checker and see which proxies are alive, fast and anonymous right now.
The long read
About free Netherlands HTTPS proxies.
The list above holds every free HTTPS proxy in the Netherlands that answered our checker recently. At 16:51 UTC on 15 September 2026, 5 HTTPS entries in the Netherlands were alive.
That is 13.2 percent of the 38 live entries in the Netherlands at the same moment. HTTPS was the least common protocol in the country, behind SOCKS4 with 10 live entries. Among the 81 countries with live HTTPS entries, the Netherlands held the 37th largest number.
5 live entries are too few for a fair success rate, so this page reports counts.
All 5 live entries were flagged for recent abuse, and 4 sat on datacenter space. For work that has to keep running, paid Netherlands proxies are built for it.
01
HTTPS entries in the Netherlands against the rest of the pool
The table compares these entries with all of the Netherlands and with HTTPS entries worldwide.
| Measured 15 September 2026 | Netherlands HTTPS | Netherlands, every protocol | HTTPS, every country |
|---|---|---|---|
| Live entries | 5 | 38 | 1,589 |
| Classed as datacenter | 80.0% | 76.3% | 35.2% |
| Flagged for recent abuse | 100.0% | 89.5% | 97.7% |
HProxy free pool, one read-only query at 16:51 UTC on 15 September 2026.
02
How the Netherlands HTTPS entries were graded
All 5 live entries were graded elite: sites saw neither your address nor a proxy header.
| Grade at the last check | Live entries |
|---|---|
| Elite | 5 |
| Anonymous | 0 |
| Transparent | 0 |
| All live Netherlands HTTPS entries | 5 |
HProxy free pool, live set at 16:51 UTC on 15 September 2026.
03
What a free Netherlands HTTPS proxy can reach
On 15 September 2026 we tested 91 Netherlands HTTPS entries from our server in Germany. Through each one, the server fetched Cloudflare's trace page over plain HTTP and TLS, then Google's connectivity check.
| Tested 15 September 2026 | Entries |
|---|---|
| Tested | 91 |
| Did not accept a connection | 77 |
| Completed at least one request | 7 |
| Carried encrypted traffic | 6 |
| Opened Google | 1 |
| Certificate did not verify | 0 |
| Showed an exit address | 7 |
| Of those, exiting in the Netherlands | 6 |
HProxy test from one server in Germany. A random sample of the Netherlands list was tested. Exit countries from Cloudflare's own trace. An entry that listed several protocols was tested over one: SOCKS5 first, then HTTPS, HTTP and SOCKS4.
6 of the 7 entries that showed an exit address were exiting in the Netherlands. The rest were exiting in the United States instead. 1 of them left through an exit address different from the one on the list.
None of the 6 entries that carried encrypted traffic tampered with the site's certificate.
04
Networks under the Netherlands HTTPS entries
The largest network under these entries was Sollutium NL, with 1 of the 5 live entries. The names below are the network names our address data records for each AS number.
| Network | AS number | Live entries | Classed as datacenter |
|---|---|---|---|
| Sollutium-NL | AS43641 | 1 | 1 |
| Oy Creanova Hosting Solutions Ltd. | AS51765 | 1 | 1 |
| TWC-EU | AS210976 | 1 | 1 |
| PLAY2GO-NET | AS215439 | 1 | 1 |
| VDSINA | AS216071 | 1 | 0 |
| All live Netherlands HTTPS entries | All networks | 5 | 4 |
HProxy free pool, live set at 16:51 UTC on 15 September 2026.
05
How to use a free Netherlands HTTPS proxy
Set an entry as the HTTPS proxy in your client, then open an https:// page through it. Take several entries and rotate between them, because a free entry can drop between two checks.
Questions
Frequently asked.
Yes, every entry on this page is free to copy and use, with no signup. They are public and shared, so test one right before you rely on it.
At 16:51 UTC on 15 September 2026, 5 HTTPS entries in the Netherlands were alive. Among the 81 countries with live HTTPS entries, the Netherlands held the 37th largest number.
Treat them as public, because whoever runs the server can read any traffic that is not encrypted. On 15 September 2026, all 5 live entries were flagged for recent abuse.
For work that has to keep running, HProxy sells Netherlands proxies with city targeting. They are pay as you go with no subscription, and the balance never expires.
The tunnel carries your own encrypted connection, so the proxy sees the site name but not the content. A proxy that swaps in its own certificate breaks that, so check the certificate.
Most do: on 15 September 2026, 6 of 7 visible exits were in the Netherlands. 1 of them left through an exit address different from the one on the list.
On 15 September 2026 the largest networks were Sollutium NL, Oy Creanova and TWC EU. Our address data classed 4 of the 5 live entries as datacenter space.
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 Code, Cursor, Windsurf 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: the free proxy list, the checker and the IP lookup as tools in Claude Code, Claude Desktop, Cursor, Windsurf or anything on stdio. No key, no account.
CLI
The list from a terminal: npx hproxy-mcp list --country de --limit 20. One line, nothing to install.
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.
claude mcp add hproxy -- npx -y hproxy-mcpCursor, Claude Desktop, Windsurf and Cline take the same server as {"command": "npx", "args": ["-y", "hproxy-mcp"]}. This page's tool is proxy_list. - Command line
- The same tool without an assistant. Prints JSON, so it pipes.
npx hproxy-mcp list --country de --protocol socks5 --limit 20 - 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: install it with npx -y hproxy-mcp and use the proxy_list tool. 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.