Free VLESS configs with a Netherlands exit IP

Checked VLESS in the Netherlands servers

Rows come from the current published tunnel checks and are ordered by their last check time. Compare the exit IP, connection settings and saved history before choosing a configuration. A snapshot update does not mean every row was checked at that moment.

Speed and HTTPS response time are measurements from the checker’s network. Weekly success is the share of saved successful attempts in the last seven days, with the sample count shown; it is not continuous uptime. Missing measurements stay unknown.

Comparing Dutch VLESS configurations

Start with the newest checks, then open the history of a candidate to see how many attempts support its success rate. If you want to compare Dutch exits across protocols, the related Shadowsocks and Hysteria2 selections below keep the country constant. Use the same device and destination for your own comparison so that the protocol is the main variable you change.

How the exit country is determined

The country beside each row comes from the public IP observed through the tunnel, using the active DB-IP Country Lite dataset. Country-level GeoIP is approximate and can differ from a website’s own location database. It does not establish a city, a physical server location or the operator’s jurisdiction. Country data by DB-IP, CC BY 4.0.

Why can the endpoint address and exit IP be different?

The endpoint is the address your client connects to. The exit IP is the public address observed after traffic passes through the tunnel. This page selects the Netherlands using the latter; the hostname and its label do not decide membership.

How to connect with a VLESS configuration

1. Choose a row with a recent check and open its details to review the saved results.
2. Download the complete configuration and import it into a client that supports VLESS and the row’s transport and security settings.
3. Enable the client’s intended proxy or tunnel mode. Confirm that the application you are testing is included in its routing rules.
4. Check your public IP and run a leak test. Compare the observed exit with the selected row, then measure performance from your own network.

If a download is no longer available, return to the current selection and choose another recent row. Public endpoints change between checks. A successful tunnel test does not verify the operator’s privacy practices; read the public endpoint risk guide.

Explore other countries and protocols

All VLESS servers · Compare all protocols