Connecting
Authentication: password or IP whitelist
A proxy lets you in either by username and password or by recognising the IP you connect from. Password works on every product. The whitelist exists on ISP and datacenter, and mobile in the US has its own version.
Updated 16 October 2026
What each product supports#
| Product | Username and password | By your IP |
|---|---|---|
| Residential | Yes | No |
| ISP | Yes | Yes, IP whitelist |
| Datacenter | Yes | Yes, IP whitelist |
| Mobile, US | Yes | Authorised IPs, instead of the password |
| Mobile, UK | Yes | No |
| MTProto, WEB | The secret inside the link | No |
Username and password#
The default on every product. It works from any network, which is what you need on cloud workers whose address changes, on a laptop, or on a phone. The credentials go either into the client's username and password fields or into the proxy URL.
IP whitelist#
On ISP and datacenter orders you can list the addresses of your own servers. Traffic from those addresses is let in with no credentials at all. It suits fixed servers and tools that cannot send a proxy password, for example Selenium with plain Chrome. Setup is on the IP whitelist page.
Which one to use#
- Your IP changes, or you work from several places: password.
- Fixed servers, and the tool cannot send a proxy password: whitelist.
- You rely on OS fingerprint spoofing: password, and keep the whitelist empty.
Didn't find the answer?
Support answers in the chat on this site around the clock. On Telegram the reply usually comes fastest, and a ticket gets an answer by email.
