> For the complete documentation index, see [llms.txt](https://dinproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dinproxy.gitbook.io/docs/getting-started/ip-whitelist.md).

# IP whitelist

Connect from your own servers without a password.

Instead of a password, the proxy can recognise your server by its IP address. Add up to **10** public IPv4 addresses. Each is linked to one of your [proxy users](https://dinproxy.gitbook.io/docs/getting-started/proxy-users.md), and traffic from it is charged to that proxy user, within its traffic limit.

The whitelist works for residential and mobile proxies. The [Web Unlocker](https://dinproxy.gitbook.io/docs/guides/web-unlocker.md) always signs in with a username and password.

## Add an IP

1. Go to **Tools → Whitelist** and click **Add IP**.
2. Enter the address, or click **Use my current IP** to fill in the one you are on now.
3. Choose the **Proxy user** its traffic is charged to, and add a note if you like.
4. Click **Save**. It works within 15 seconds.

Add your server's public IPv4 address. If the address is already in use on another account, contact <support@dinproxy.com>.

## Connect

From a whitelisted IP, leave out the username and password:

```bash
curl --proxy 'http://proxy.dinproxy.com:7777' 'https://httpbin.org/ip'
```

You get a rotating IP from any location. For mobile proxies use port `7779`. To choose a location or a sticky session ([residential](https://dinproxy.gitbook.io/docs/guides/residential-proxies/location-and-sessions.md), [mobile](https://dinproxy.gitbook.io/docs/guides/mobile-proxies/location-and-sessions.md)), send the proxy user's connection username with the options, and an empty password:

```bash
curl --proxy 'http://proxy.dinproxy.com:7777' \
  --proxy-user '1024~myuser@country=us:' \
  'https://httpbin.org/ip'
```

The username must be one of your own proxy users. Endpoints made for a whitelisted IP work from any IP on your whitelist; without a username, traffic is charged to the proxy user linked to the IP it comes from.

SOCKS5 clients that offer no authentication work the same way. In Java and .NET, send the username as the code examples ([residential](https://dinproxy.gitbook.io/docs/guides/residential-proxies/code-examples.md), [mobile](https://dinproxy.gitbook.io/docs/guides/mobile-proxies/code-examples.md)) do.

## Remove an IP

Delete it in **Tools → Whitelist**. New connections from that IP then need a password again; connections already open are not cut.

Deleting a proxy user also removes the whitelisted IPs linked to it.
