Skip to contentUpdated
Netherlands: free HTTP proxies 🇳🇱
Netherlands HTTP: 7 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 121–174 of 174 (working first, then history)
7Entries marked working
44%Mean check success
4393 msMedian recorded latency
57%Elite-labelled share
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 12 ms | 33% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 15 ms | 33% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 15 ms | 33% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 12 ms | 33% | not working last alive | |
| 8443 | HTTP | 🇳🇱Amsterdam | Elite | – | 3523 ms | 33% | not working last alive | |
| 3128 | HTTP | 🇳🇱Amsterdam | Transparent | – | 9 ms | 32% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 8418 ms | 32% | not working last alive | |
| 3128 | HTTP | 🇳🇱Amsterdam | Transparent | – | 1147 ms | 32% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Elite | – | 3478 ms | 30% | not working last alive | |
| 443 | HTTP | 🇳🇱Amsterdam | Elite | – | 10 ms | 30% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Elite | – | 12 ms | 29% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 15 ms | 29% | not working last alive | |
| 3128 | HTTP | 🇳🇱Amsterdam | Transparent | – | 10 ms | 29% | not working last alive | |
| 1080 | HTTP | 🇳🇱Utrecht | Elite | – | 7222 ms | 28% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 8443 | HTTP | 🇳🇱Amsterdam | Elite | – | 3438 ms | 28% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 15 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇳🇱Amsterdam | Elite | – | 11 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇳🇱Utrecht | Elite | – | 12 ms | 24% | not working last alive | |
| 3127 | HTTP | 🇳🇱Haarlem | Transparent | – | 1327 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Transparent | – | 6899 ms | 21% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Transparent | – | 5182 ms | 21% | not working last alive | |
| 3128 | HTTP | 🇳🇱Utrecht | Elite | – | 6885 ms | 20% | not working last alive | |
| 1080 | HTTP | 🇳🇱Utrecht | Elite | – | 223 ms | 20% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 222 ms | 20% | not working last alive | |
| 1080 | HTTP | 🇳🇱Utrecht | Elite | – | 1904 ms | 20% | not working last alive | |
| 1081 | HTTP | 🇳🇱Utrecht | Elite | – | 5486 ms | 20% | not working last alive | |
| 3128 | HTTP | 🇳🇱Utrecht | Elite | – | 15 ms | 17% | not working last alive | |
| 8118 | HTTP | 🇳🇱Utrecht | Elite | – | 12 ms | 16% | not working last alive | |
| 3128 | HTTP | 🇳🇱Utrecht | Elite | – | 1592 ms | 16% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 1136 ms | 16% | not working last alive | |
| 1080 | HTTP | 🇳🇱Amsterdam | Elite | – | 11 ms | 16% | not working last alive | |
| 3128 | HTTP | 🇳🇱Utrecht | Elite | – | 137 ms | 15% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 170 ms | 14% | not working last alive | |
| 1080 | HTTP | 🇳🇱Utrecht | Elite | – | 1160 ms | 13% | not working last alive | |
| 9050 | HTTP | 🇳🇱Utrecht | Elite | – | 3746 ms | 13% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 1754 ms | 13% | not working last alive | |
| 1081 | HTTP | 🇳🇱Utrecht | Elite | – | 3224 ms | 12% | not working last alive | |
| 4145 | HTTP | 🇳🇱Utrecht | Elite | – | 611 ms | 11% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 224 ms | 11% | not working last alive | |
| 9050 | HTTP | 🇳🇱Utrecht | Elite | – | 134 ms | 11% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 5662 ms | 10% | not working last alive | |
| 8080 | HTTP | 🇳🇱Utrecht | Elite | – | 1160 ms | 10% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Elite | – | 15 ms | 8% | not working last alive | |
| 1082 | HTTP | 🇳🇱Amsterdam | Elite | – | 2995 ms | 6% | not working last alive | |
| 8118 | HTTP | 🇳🇱Utrecht | Elite | – | 1736 ms | 5% | not working last alive | |
| 80 | HTTP | 🇳🇱Amsterdam | Elite | – | 219 ms | 5% | not working last alive | |
| 80 | HTTP | 🇳🇱Amsterdam | Elite | – | 7443 ms | 5% | not working last alive | |
| 80 | HTTP | 🇳🇱Amsterdam | Elite | – | 14 ms | 5% | not working last alive | |
| 10801 | HTTP | 🇳🇱Amsterdam | Elite | – | 308 ms | 5% | not working last alive | |
| 1080 | HTTP | 🇳🇱Dronten | Elite | – | 235 ms | 4% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Transparent | – | 6930 ms | 2% | not working last alive | |
| 3128 | HTTP | 🇳🇱Dronten | Elite | – | 13 ms | 2% | not working last alive | |
| 2080 | HTTP | 🇳🇱Amsterdam | Elite | – | 3253 ms | 1% | not working last alive | |
| 8080 | HTTP | 🇳🇱Amsterdam | Transparent | – | 54 ms | 0% | not working last alive | |
Public proxy reminder
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
People found this page by searching for
- HTTP
- what is a SOCKS5 proxy
- free HTTP proxy
- free proxies HTTP
- anonymous proxies HTTP
- SOCKS5 & HTTP proxies
- proxy list for beginners
- elite proxies list txt
- free proxy list
- socks5 proxy
- dedicated ip provider
- public proxies
- download working proxies
- how public proxies works
Real search phrases this page answers — the linked ones open the page that covers them in depth.