IP whitelist

The IP whitelist authenticates a connection by its public source address. Add an address to a service’s whitelist and connections from it are accepted without a password. Your username and password keep working alongside any whitelisted IPs.

Add an IP to the whitelist

1. Find the address you will connect from

   Run this on the machine that will open the proxy connections:

   curl https://httpbin.org/ip

2. Add it to the service

   Open the service in the dashboard, go to its Whitelisted IPs tab, enter the address and choose Add to whitelist. Each IP can be whitelisted by one service at a time.

3. Connect to the same host and ports

   A whitelisted IP uses the service’s usual Connection host and ports. There are no separate endpoints for the IP whitelist.

Connecting

Send no credentials at all to connect without targeting:

curl -x http://YOUR_HOST:YOUR_HTTP_PORT \
  https://httpbin.org/ip

Targeting without a password

Targeting travels on the username. To keep country, city, region, ASN or session targeting from a whitelisted IP, send your username with its options and leave the password empty:

curl -x http://YOUR_HOST:YOUR_HTTP_PORT \
  -U "YOUR_USERNAME-session-ab12cd-country-de:" \
  https://httpbin.org/ip

The username must be the service’s own username from its Proxy setup tab, followed by the options from How to connect. A whitelisted IP admits connections only to the service whose whitelist holds it.

The same works for SOCKS5 clients that offer a username but no password:

curl --socks5-hostname YOUR_HOST:YOUR_SOCKS_PORT \
  --proxy-user "YOUR_USERNAME-country-de:" \
  https://httpbin.org/ip

Note

Sending your proxy password with the username uses normal password authentication, from any address, and the password must be correct. A whitelisted IP only admits connections that send no password.

A connection with no credentials from an address that is not on the whitelist is refused with No credentials sent, and this address is not on the service's trusted IP list. (see Proxy errors).

Choosing between the two

The IP whitelist keeps your proxy password off the network you connect from — worth having on the plain http and socks5 ports, where credentials would otherwise travel in clear text. It requires a stable address.

Password authentication works from anywhere, which is what you want from a laptop, a dynamic connection, or anywhere you cannot pin an address.

Both work at once, so you can use whichever suits each machine.

Caution

A whitelisted IP trusts every process that can reach the internet through that address, including anything else on the same network. Use a stable, controlled source, and remove addresses you no longer use.