Blog

IP authentication or username and password: which should you use?

How the two ways to log in to a proxy differ, which products support each one, and how to pick.

October 31, 2026 · 1 min read

A proxy has to know that a connection is yours. There are two ways to prove it, and the better one depends on where your software runs.

Username and password

Your client sends the plan's login with each connection. It works from any network, which suits laptops, home connections and anything that moves around. Every product includes it. Treat the login like a key: anyone who has it can use your plan's threads.

IP authentication

You add your machine's public IP to the plan, and connections from that address are let in with no password. It's useful for tools that handle proxy logins badly, and it keeps credentials out of config files. The catch is that it needs a stable address. Most home connections change IP from time to time, and when yours changes, the proxies stop working until you update the whitelist.

To find a machine's public IP, run this on it without a proxy:

curl https://api.ipify.org

What each product supports

  • Datacenter IPv4 (Plan #2): both. Whitelisted IPv4 addresses connect without a password, using 1 slot or 5 with the extra IP authentication add-on, and the username and password keep working from anywhere.
  • Residential Lite, Shared ISP · USA (Plan #3), IPv6 Residential and IPv6 Datacenter: username and password always. An allowlist can be added as an extra lock, so the plan only works from addresses you list.
  • Dedicated ISP Pool and Dedicated ISP: username and password only.

How to choose

  • Running on a server with a fixed IP: IP authentication is the simplest setup
  • Running from home or several places: use username and password
  • Sharing a machine, or worried about a leaked login: keep the password and add an allowlist where your product offers one