Updated

Netherlands: free public proxies 🇳🇱

Netherlands: 36 public proxies marked working in this snapshot. The table also includes check history; recheck before use.

showing 1–60 of 300 (working first, then history)

36Entries marked working
22%Mean check success
3064 msMedian recorded latency
88%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.

11725SOCKS5🇳🇱EygelshovenElite–2339 ms56%
8118HTTPS🇳🇱UtrechtElite✓3046 ms53%
8644SOCKS5🇳🇱EygelshovenElite–10 ms50%
9883SOCKS5🇳🇱EygelshovenElite–12 ms50%
8443SOCKS5🇳🇱AmsterdamElite–3225 ms49%
8080HTTP🇳🇱AmsterdamTransparent–4142 ms46%
8080HTTP🇳🇱AmsterdamTransparent–2569 ms46%
8080HTTP🇳🇱AmsterdamTransparent–65 ms45%
8080HTTPS🇳🇱AmsterdamTransparent✓1040 ms42%
3128HTTP🇳🇱UtrechtElite–8261 ms37%
6989SOCKS5🇳🇱EygelshovenElite–7663 ms36%
1080SOCKS5🇳🇱AmsterdamElite–1430 ms31%
1080SOCKS5🇳🇱AmsterdamElite–124 ms24%
8787SOCKS5🇳🇱AmsterdamElite–5761 ms24%
Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy →
9786SOCKS5🇳🇱EygelshovenElite–2224 ms24%
9837SOCKS5🇳🇱EygelshovenElite–3098 ms21%
9830SOCKS5🇳🇱EygelshovenElite–3297 ms21%
13060SOCKS5🇳🇱EygelshovenElite–3082 ms13%
5113SOCKS5🇳🇱EygelshovenElite–3291 ms13%
4253SOCKS5🇳🇱EygelshovenElite–655 ms13%
9443SOCKS5🇳🇱EygelshovenElite–3654 ms12%
4035SOCKS5🇳🇱EygelshovenElite–2163 ms11%
4175SOCKS5🇳🇱EygelshovenElite–8874 ms11%
1080SOCKS5🇳🇱AmsterdamElite–347 ms11%
4211SOCKS5🇳🇱EygelshovenElite–7952 ms9%
9076SOCKS5🇳🇱EygelshovenElite–7473 ms9%
12378SOCKS5🇳🇱EygelshovenElite–758 ms8%
10251SOCKS5🇳🇱EygelshovenElite–2847 ms8%
4582SOCKS5🇳🇱EygelshovenElite–2339 ms6%
4038SOCKS5🇳🇱EygelshovenElite–4034 ms6%
9819SOCKS5🇳🇱EygelshovenElite–6000 ms6%
10743SOCKS5🇳🇱EygelshovenElite–3495 ms5%
14553SOCKS5🇳🇱EygelshovenElite–696 ms4%
5026SOCKS5🇳🇱EygelshovenElite–1427 ms4%
13598SOCKS5🇳🇱EygelshovenElite–4967 ms4%
12554SOCKS5🇳🇱EygelshovenElite–5004 ms3%
1088SOCKS5🇳🇱HaarlemElite–186 ms87%not working last alive
10605HTTPS🇳🇱AmsterdamElite✓334 ms79%not working last alive
3128HTTPS🇳🇱HaarlemAnonymous✓11 ms77%not working last alive
10829HTTPS🇳🇱AmsterdamElite✓1207 ms76%not working last alive
18080SOCKS5🇳🇱HaarlemElite–13 ms75%not working last alive
10526HTTPS🇳🇱AmsterdamElite✓251 ms75%not working last alive
3128HTTP🇳🇱HaarlemAnonymous–134 ms72%not working last alive
7777SOCKS5🇳🇱AmsterdamElite–10 ms70%not working last alive
9050SOCKS4🇳🇱AmsterdamElite–13 ms68%not working last alive
1080SOCKS4🇳🇱AmsterdamElite–14 ms68%not working last alive
9050SOCKS4🇳🇱HaarlemElite–10 ms68%not working last alive
10122HTTP🇳🇱AmsterdamElite–162 ms68%not working last alive
10551HTTP🇳🇱AmsterdamElite–376 ms68%not working last alive
902SOCKS4🇳🇱AmsterdamElite–14 ms68%not working last alive
1080SOCKS4🇳🇱RoosendaalElite–10 ms67%not working last alive
1080SOCKS4🇳🇱AmsterdamElite–12 ms67%not working last alive
1080SOCKS5🇳🇱AmsterdamElite–17 ms65%not working last alive
10404HTTPS🇳🇱AmsterdamElite✓162 ms65%not working last alive
1080SOCKS5🇳🇱AlblasserdamElite–8 ms64%not working last alive
1080SOCKS4🇳🇱AmsterdamElite–10 ms64%not working last alive
10805HTTPS🇳🇱AmsterdamElite✓181 ms64%not working last alive
32712SOCKS5🇳🇱AmsterdamElite–29 ms63%not working last alive
1080SOCKS5🇳🇱EygelshovenElite–18 ms62%not working last alive
1080HTTPS🇳🇱Los AngelesElite✓3248 ms61%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.

At a glance

This page has 36 entries marked working. Mean recorded check success across these entries is 22%; mean recorded response time, where available, is 3260 ms. By protocol: SOCKS5 (30), HTTP (4), HTTPS (2). By anonymity level: Elite (32), Transparent (4). The most common ports are 8080, 1080, 12378. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.

This catalogue groups public proxy records under Netherlands. Country and anonymity labels are catalogue metadata, not verified operator identity or a privacy guarantee. Check the protocol and recorded times, then recheck before use. Do not send sensitive traffic through public proxies.

For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.

FAQ

Free proxies — FAQ

How often is this free proxy list checked?

Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.

Are free public proxies safe to use?

Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.

How do I use a proxy from this list?

Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.

Private connection options

Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.

Explore s4m Proxy →

People found this page by searching for

Real search phrases this page answers — the linked ones open the page that covers them in depth.