IP whitelisting
Authenticate by source address instead of sending credentials.
If your traffic originates from static addresses, you can whitelist them and drop the credentials entirely. This is common on fixed scraping fleets, where distributing passwords to workers is more of a liability than a convenience.
Adding an address
- 1Dashboard → Proxy users → select a user → Whitelist.
- 2Add an individual address or a CIDR block up to /24.
- 3Whitelist entries propagate to every gateway within about thirty seconds.
# once whitelisted, no -U flag is needed
curl -x res.wproxy.io:8000 https://ipinfo.io/json
# targeting still works: encode it in the username field with no password
curl -x res.wproxy.io:8000 -U "wp-acc4821-country-de:" https://ipinfo.io/jsonThe obvious caveat
Anything sharing your source address can spend your balance. Do not whitelist a NAT gateway that fronts untrusted workloads, and never whitelist a residential address you do not control end to end.
Combining both
Whitelisting and credentials coexist. A whitelisted address may still send credentials, and it should if you need per-sub-user attribution in usage reports — otherwise traffic is attributed to the sub-user that owns the whitelist entry.