Pick a proxy by the job it has to do
Everyday residential
Location-aware browsing
Advanced identity
Priority pools and ASN control
What teams run on Ludax
Collect
Gather public data at volume
Verify
Confirm what each market sees
Understand
Turn signals into decisions
Popular proxy locations, each with its own guide
Resources
Dutch residential proxies from $0.49/GB, 1 GB for $0.99: IPs by province, city and ISP (Premium), sticky up to 1000 min, HTTP/SOCKS5. No subscription. Route each request through a home connection in the Dutch province and city you choose, and read the page exactly as a local visitor sees it.
Pay per gigabyte, with no subscription. Test the provinces and cities you need on a small plan, then scale the same parameters. Plans are valid for 30 days from activation.
# Normal plans (Residential, Residential TLS)
YOUR_PASSWORD-country-nl
YOUR_PASSWORD-country-nl-state-zh
YOUR_PASSWORD-country-nl-state-nh-city-amsterdam
# Premium plans (Residential Premium, Premium TLS)
YOUR_PASSWORD-country-nl
YOUR_PASSWORD-country-nl-state-southholland-city-rotterdam
YOUR_PASSWORD-country-nl-asn-1136-os-windows
# Sticky: one Dutch exit for 30 minutes
YOUR_PASSWORD-session-nl01-time-30-country-nl-state-zh-city-rotterdamEvery Ludax plan reaches the Netherlands. Every plan goes down to the province and the city. Premium plans do it on a separate, screened pool, with the province and city written out in full, and add ISP (ASN) and device targeting. The TLS variant of each plan targets exactly like its normal one; it adds a real browser TLS handshake.
| Feature | Residential NORMAL | Residential TLS NORMAL | Residential Premium PREMIUM | Premium TLS PREMIUM |
|---|---|---|---|---|
| Country (NL) | Yes | Yes | Yes | Yes |
| Province | 12 provinces | 12 provinces | 12 provinces | 12 provinces |
| City | 64 cities | 64 cities | 376 cities | 376 cities |
| ISP / ASN | No | No | 128 Dutch networks | 128 Dutch networks |
| Device | No | No | Windows, Android, iOS, macOS | Windows, Android, iOS, macOS |
| Rotating IPs | Every request | Every request | Every request | Every request |
| Sticky session | Up to 1000 minutes | Up to 1000 minutes | Up to 1000 minutes | Up to 1000 minutes |
| Protocols and port | HTTP/HTTPS 7777 · SOCKS5 7575 | HTTP/HTTPS 9999 | HTTP/HTTPS 8080 · SOCKS5 1080 | HTTP/HTTPS 8081 |
| Browser TLS fingerprint | No | Yes | No | Yes |
| From | $0.99 / 1 GB | $1.49 / 1 GB | $3.49 / 1 GB | $5.24 / 1 GB |
Counts are the current targeting lists; the gateway host is gw.ludaxproxy.com for every plan. Product details: Residential, Residential TLS, Residential Premium, Residential Premium TLS, or compare every product.
Each level narrows where the exit IP is. Pick the widest level that still changes the page you read: a wider level draws from more homes, a narrower one is closer to a single local visitor.
Send the province’s code after the country. Normal plans list 12 provinces. Premium plans list 12 provinces, by full name: -state-southholland. A province is enough for most regional pricing, availability and search comparisons.
-country-nl-state-zhAdd a city after its province, written in lower case without spaces or accents. Normal plans list 64 cities across the Netherlands. Premium plans list 376, each sent with its province: -state-southholland-city-rotterdam.
-state-zh-city-rotterdamPremium plans choose the home network by its ASN: 128 Dutch networks, including KPN (AS1136), Odido (AS31615), Vodafone (AS33915), DELTA Fiber (AS15435), Solcon (AS12414). Premium combines it with a province, a city and a device: -os-windows, -os-android, -os-ios or -os-macos.
-country-nl-asn-31615One location per request: a province with an optional city on every plan, plus an optional ASN and device on Premium. Full syntax and order in the documentation.
Every province Normal plans can target in the Netherlands, with the number of cities listed in it. The code on each tile is the value of -state-.
The exact parameter for the most requested cities in the Netherlands, with its province. Premium plans write the province and city in full (-country-nl-state-southholland-city-rotterdam) and can add an ASN and a device.
| City | Province | Normal plans PROVINCE + CITY |
|---|---|---|
| Amsterdam | North Holland | -state-nh-city-amsterdam |
| Rotterdam | South Holland | -state-zh-city-rotterdam |
| The Hague | South Holland | -state-zh-city-thehague |
| Utrecht | Utrecht | -state-ut-city-utrecht |
| Eindhoven | North Brabant | -state-nb-city-eindhoven |
| Groningen | Groningen | -state-gr-city-groningen |
| Tilburg | North Brabant | -state-nb-city-tilburg |
| Almere | Flevoland | -state-fl-city-almerestad |
| Breda | North Brabant | -state-nb-city-breda |
| Nijmegen | Gelderland | -state-ge-city-nijmegen |
| Haarlem | North Holland | -state-nh-city-haarlem |
| Maastricht | Limburg | -state-li-city-maastricht |
Every code goes after -country-nl. The dashboard’s generator lists each province’s cities and builds the string for you.
The same mechanic each time: a request that leaves from a home connection in the right province and city, so the source answers as it answers a local visitor. What changes is what you read from the page.
Read the prices Dutch shoppers are shown on Dutch retailers and marketplaces, on a schedule.
Price monitoring guideFollow stock, delivery estimates and assortment changes from a Dutch home connection.
Price monitoring guideSee the Google.nl results, map packs and ads a searcher in Amsterdam, Rotterdam or Utrecht is shown.
SEO monitoring guideCheck that campaigns bought for a Dutch province or city render there, on the ISP you choose.
Ad verification guideCompare prices, assortment and availability between Dutch provinces with one sampling method.
Market research guideCheck Dutch copy, euro pricing, payment options and consent banners as Dutch visitors receive them.
Collect public Dutch pages at scale, rotating per request or holding one exit for a multi-step job.
Web scraping guideWith no session parameter, every request leaves from a new Dutch home connection inside the location you chose. Use it for independent page loads at scale.
DO -country-nl-state-zh for wide coverage, add -city- only where the page changes by city
Search, filter and paginate inside one session: the same exit for up to 1000 minutes on every plan.
DO -session-nl01-time-30 · a new session id gives a new exit
Ask the whoami endpoint through the same proxy and store its city and network with every result, so a country-level fallback never passes for a local one.
DO keep province, city or ASN and run time in each row
import requests
USER, PASS = "YOUR_USERNAME", "YOUR_PASSWORD"
def nl_proxy(state, city=None, session=None):
pw = PASS
if session: pw += f"-session-{session}-time-30"
pw += f"-country-nl-state-{state}"
if city: pw += f"-city-{city}"
url = f"http://{USER}:{pw}@gw.ludaxproxy.com:7777"
return {"http": url, "https": url}
# the same page, read from three Dutch cities
for state, city in [("nh", "amsterdam"), ("zh", "rotterdam"), ("ut", "utrecht")]:
p = nl_proxy(state, city)
exit_ = requests.get("https://api.ludaxproxy.com/whoami", proxies=p, timeout=15).json()
page = requests.get("https://example.com/stores", proxies=p, timeout=30)
print(state, city, exit_.get("city"), len(page.content))Residential gateway gw.ludaxproxy.com:7777 (HTTP and HTTPS) or :7575 (SOCKS5). Every parameter in the documentation.
Yes, on every plan. Normal plans (Residential and Residential TLS) list 12 provinces and 64 cities, each city sent after its province: -country-nl-state-nh-city-amsterdam. Premium plans (Residential Premium and Residential Premium TLS) list 12 provinces and 376 cities by full name, with an optional ISP (ASN) and device: -country-nl-state-southholland-city-rotterdam-os-windows.
Normal plans list 64 Dutch cities in all 12 provinces, most of them in North Holland (15), South Holland (13) and North Brabant (9). They include Amsterdam, Rotterdam, The Hague, Utrecht, Eindhoven, Groningen, Tilburg and Maastricht.
On Premium plans, 128 Dutch networks can be chosen by their ASN, for example KPN (AS1136), Odido (AS31615), Vodafone (AS33915), DELTA Fiber (AS15435), Solcon (AS12414): -country-nl-asn-1136. Normal plans choose the province and the city instead.
In lower case, without spaces or punctuation: The Hague is thehague, ’s-Hertogenbosch is shertogenbosch and Almere is listed as almerestad. Each city follows its province: -country-nl-state-zh-city-thehague.
The request resolves at country level rather than failing. Check the exit with a whoami request and record the city it actually came from, so a fallback is never mistaken for a local result.
Rotate on every request, or hold one exit with a sticky session: up to 1000 minutes on every plan, Premium included.
Residential (port 7575) and Residential Premium (port 1080) accept SOCKS5 as well as HTTP and HTTPS. The TLS plans, Residential TLS and Residential Premium TLS, are HTTP and HTTPS gateways, because they rebuild the browser TLS handshake themselves.
Normal Residential covers most open pages and localized search results, with province and city targeting. Residential TLS fits sources that inspect the connection or render content in JavaScript. Premium adds ISP (ASN) and device targeting on a screened pool, for sources that challenge ordinary traffic.
Buy the smallest amount of traffic, check the provinces and cities you need, and keep the same parameters when you scale. Premium, with ISP (ASN) and device targeting on a screened pool, starts at $3.49 for 1 GB.
$0.99/ 1 GB · $0.49 / GB at 1 TB