| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 45.61.129.165:9050 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 2055 ms | 97.78% | 1h ago |
| 2 | 109.236.88.82:80 | http | — | The Netherlands / Naaldwijk | elite | 228 ms | 61.73% | 1h ago |
| 3 | 5.255.113.177:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 1395 ms | 82.72% | 1h ago |
| 4 | 128.199.37.92:1080 | socks5 | — | The Netherlands / Amsterdam | elite | 3300 ms | 75.63% | 28m ago |
| 5 | 5.255.123.162:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 4671 ms | 98.86% | 29m ago |
| 6 | 5.255.117.127:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 3031 ms | 71.25% | 34m ago |
| 7 | 5.255.117.250:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 6007 ms | 75.35% | 29m ago |
| 8 | 18.188.168.99:13543 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 4634 ms | 39.02% | 21m ago |
| 9 | 35.78.252.142:19049 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 3655 ms | 56.41% | 2m ago |
| 10 | 35.78.252.142:37244 | http | ✓ TLS | The Netherlands / Dronten | elite | 5376 ms | 52.71% | 19m ago |
| 11 | 37.18.73.60:5566 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 1814 ms | 63.05% | 16m ago |
| 12 | 13.126.183.60:43900 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 1949 ms | 34.25% | 8m ago |
| 13 | 5.255.103.55:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 1715 ms | 75.65% | 29m ago |
| 14 | 5.255.99.75:1080 | socks5 | ✓ TLS | The Netherlands / Dronten | elite | 1221 ms | 80.95% | 17m ago |
| 15 | 13.126.183.60:47712 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 4807 ms | 32.11% | 14m ago |
| 16 | 158.101.8.92:1080 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 6291 ms | 39.45% | 1h ago |
| 17 | 5.189.17.23:9050 | socks4 | — | The Netherlands / Amsterdam | elite | 9491 ms | 10.71% | 6h ago |
| 18 | 56.68.116.64:12719 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 7032 ms | 49.74% | 3h ago |
| 19 | 109.107.166.207:30385 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 4261 ms | 22.58% | 5h ago |
| 20 | 195.26.224.135:80 | http | — | The Netherlands / Amsterdam | elite | 206 ms | 77.86% | 1m ago |
| 21 | 56.68.116.64:10300 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 2036 ms | 43.67% | 1m ago |
| 22 | 95.211.83.181:3128 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 8027 ms | 14.71% | 14h ago |
| 23 | 185.185.40.118:3128 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 791 ms | 5.88% | 20h ago |
| 24 | 158.101.175.124:5566 | http | — | The Netherlands / Amsterdam | elite | 8640 ms | 11.11% | 10h ago |
| 25 | 5.255.104.109:8082 | http | — | The Netherlands / Dronten | elite | 1172 ms | 37.21% | 8m ago |
| 26 | 147.45.187.104:8080 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 5729 ms | 11.76% | 19h ago |
| 27 | 43.153.84.220:9050 | socks4 | ✓ TLS | The Netherlands / Amsterdam | elite | 9221 ms | 22.86% | 47m ago |
| 28 | 217.12.209.4:1080 | socks5 | ✓ TLS | The Netherlands / Amsterdam | elite | 1311 ms | 36.8% | 1h ago |
| 29 | 71.168.71.12:8889 | http | — | The Netherlands / Amsterdam | elite | 912 ms | 6.67% | 5h ago |
| 30 | 164.92.148.68:3128 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 9711 ms | 11.11% | 2h ago |
| 31 | 35.78.252.142:8411 | http | ✓ TLS | The Netherlands / Amsterdam | elite | 4642 ms | 49.76% | 5h ago |
| 32 | 37.49.224.167:1080 | socks5 | — | The Netherlands / Amsterdam | elite | 3278 ms | 18.6% | 1h ago |
Browse proxies by country
Use public proxies with caution. These are open, third-party servers we did not set up. A working proxy can still log your traffic, inject content, or expose your real IP through DNS, WebRTC, or application headers.
Never send passwords, financial data, or other sensitive traffic through an untrusted proxy. Verify a proxy with our Proxy Tester before relying on it, and only use proxies where you are authorized to do so.
ℹ️ About The Netherlands Proxy List
What is this free proxy list?
This page publishes a live list of public HTTP, HTTPS, SOCKS4, and SOCKS5 proxy servers drawn from our continuously monitored proxy database. Every proxy is re-tested on a short interval by a distributed worker fleet, so the status, latency, anonymity level, and geographic location reflect recent checks rather than a stale dump. Only proxies that are currently alive are listed, and credentialed/private proxies are never published.
The first 50 results load instantly. To reveal the rest (up to 200) a lightweight, invisible human-verification check runs first — this keeps the list useful for people while discouraging automated bulk scraping. There is intentionally no bulk download or public API.
HTTP vs HTTPS vs SOCKS proxies
- HTTP — forwards plain HTTP requests; best for simple web traffic and scraping non-TLS endpoints.
- HTTPS — supports the
CONNECTmethod to tunnel TLS, so it can carry encryptedhttps://traffic. - SOCKS4 — a lower-level TCP tunnel; no authentication of the proxied protocol and no UDP/IPv6.
- SOCKS5 — the most flexible: TCP and UDP, IPv6, and optional auth. Defined in RFC 1928. HTTP semantics are defined in RFC 9110 and the standardized forwarding header in RFC 7239.
The HTTPS column (✓ TLS) marks proxies we verified can tunnel encrypted https:// traffic — confirmed either by a live TLS probe or by the proxy reaching our HTTPS test endpoint. This is independent of the proxy's own scheme: an HTTP-listed proxy can still be HTTPS-capable via CONNECT. Use the HTTPS filter to show only TLS-capable proxies.
Anonymity levels & safety ratings
| Level | Reveals your IP? | Privacy rating | Use |
|---|---|---|---|
| Elite | No — and hides that a proxy is used | Strongest | Best choice for anonymity |
| Anonymous | No, but reveals a proxy is in use | Medium | OK for general use |
| Transparent | Yes — forwards your real IP | None | Caching/testing only, not privacy |
How "reliability" and uptime are measured
The default sort ranks proxies by recent success streak. The Uptime (7d) column is the share of our last week of checks that succeeded for that proxy. Latency is the most recent measured round-trip time. Because public proxies are volatile, a proxy that is up now may be down within hours — re-verify before depending on it.