:format(webp))
Username:password works from any network — best for laptops, distributed teams, and CI/CD where the source IP isn't fixed.
IP whitelisting authenticates by source IP instead of credentials — best for servers and VPS with a static IP.
Neither method is "more secure" in the abstract — it depends on whether your risk is a leaked credential or a compromised network.
Both are supported at no extra cost on SimplyNode residential and mobile proxies, and you can use both at once on the same account.
Short answer: Use username:password authentication if you rotate between networks, work from dynamic IPs, or run automation from multiple machines — it works anywhere without reconfiguration. Use IP whitelisting if you connect from a fixed set of static IPs (a server, an office network, a VPS) and want to skip sending credentials with every request. Most teams end up using both: whitelisting for their production servers, username:password for everything else.
Both methods are supported on SimplyNode residential and mobile proxies, over HTTP, HTTPS, and SOCKS5, and neither one is more "secure" in the abstract — the right choice depends entirely on where your traffic originates.
What is IP whitelisting authentication?
IP whitelisting (also called IP authorization) authenticates a connection based on the source IP address making the request, not on a username or password. You register one or more IPs in your dashboard, and the proxy provider allows any traffic originating from those IPs to pass through — no credentials required in the connection string.
python
import requests
# IP whitelisting - no username or password in the proxy URL
# Authentication happens because the request originates from a
# pre-registered IP address
proxies = {
"http": "http://ip.simplynode.io:10000",
"https": "http://ip.simplynode.io:10000",
}
response = requests.get("https://ifconfig.me", proxies=proxies, timeout=10)
print(response.text)This only works if the machine running the code has a static IP. If your ISP assigns you a dynamic residential IP, or you're running this from a laptop that moves between office and home Wi-Fi, whitelisting breaks the moment your IP changes — you'd need to re-add the new IP in your dashboard every time.
What is username:password authentication?
Username:password authentication (sometimes called credential-based or basic auth) embeds a login and password directly in the proxy connection string. The proxy provider checks these credentials on every request, regardless of what IP the request came from.
python
import requests
# Username:password authentication - credentials travel with
# every request, so the connection works from any network
proxies = {
"http": "http://username:password@ip.simplynode.io:10000",
"https": "http://username:password@ip.simplynode.io:10000",
}
response = requests.get("https://ifconfig.me", proxies=proxies, timeout=10)
print(response.text)Because authentication travels with the request instead of depending on network origin, this works identically whether you're running the script from your laptop, a cloud server in another country, or a teammate's machine — no dashboard changes needed.
IP whitelisting vs username:password: comparison table
IP Whitelisting | Username:Password | |
|---|---|---|
Setup | Register static IP(s) once in dashboard | Set credentials once, reuse anywhere |
Works from dynamic IPs | No — breaks if your IP changes | Yes — credentials aren't tied to origin |
Works across multiple machines/locations | Only if each IP is registered | Yes, immediately |
Credentials in code/logs | None — nothing to leak | Username/password appear in connection strings |
Best for | Servers, VPS, fixed office networks | Laptops, distributed teams, CI/CD, rotating environments |
Risk if compromised | Attacker needs your actual IP | Attacker needs the leaked credentials |
Reconfiguration overhead | Every time your IP changes | None |
When to use IP whitelisting
IP whitelisting makes sense when your traffic consistently originates from a small, stable set of IPs:
Dedicated servers or VPS with a fixed IP that isn't going to change
Office networks with a static public IP
Production environments where you'd rather not have credentials sitting in environment variables or config files
Compliance-sensitive setups where security review flags embedded credentials as a concern, even in
.envfiles
The tradeoff: every time you deploy from a new machine, spin up a new server, or your ISP reassigns your IP, you have to log in and update the whitelist before the proxy will work again.
When to use username:password
Username:password is the more practical default for most use cases:
Local development on a laptop that switches between home, office, and mobile hotspot networks
Distributed teams where different people run the same scripts from different locations
CI/CD pipelines where the runner's IP isn't fixed or known in advance
Multiple concurrent projects that need separate credentials for tracking and access control, without touching IP settings
The tradeoff: credentials need to be handled carefully — stored in environment variables or a secrets manager, not hardcoded and committed to version control.
Can you use both at the same time?
Yes. Registering a whitelisted IP doesn't disable username:password on the same account — they're not mutually exclusive. A common setup: whitelist your production server's static IP so it connects without embedding credentials, while keeping username:password enabled for local testing and any machine whose IP isn't fixed.
Security note: neither method is inherently "more secure"
IP whitelisting removes credentials from your code, but it's only as secure as the network behind that IP — anyone on that network, or anyone who can spoof it, inherits access. Username:password keeps access independent of network, but the credentials themselves need to be protected like any other secret. The right question isn't "which is more secure" in isolation, it's "where does my traffic actually come from, and can I keep that origin — or those credentials — properly protected."
FAQ
Does IP whitelisting cost extra? No. On SimplyNode, both IP whitelisting and username:password authentication are included on residential ($2.25/GB) and mobile ($4.25/GB) proxy plans at no additional charge.
How many IPs can I whitelist? You can register multiple IPs on the same account, which is useful for teams running proxies from more than one server or office location.
Does IP whitelisting work with rotating residential proxies? Yes. Whitelisting authenticates the outbound connection to the proxy gateway — it has no effect on how the gateway rotates the residential or mobile exit IPs assigned to your requests.
What happens if my whitelisted IP changes? Requests will fail with an authentication error until you update the whitelist with your new IP in the dashboard. This is the main reason username:password is the safer default for anyone without a static IP.
Can I switch between authentication methods without changing my plan? Yes. Both methods run on the same underlying proxy pool and gateway — switching is a matter of updating your connection string or dashboard settings, not your subscription.
Does authentication method affect proxy speed or success rate? No. Authentication happens before a request is routed through the proxy pool and has no measurable effect on latency or success rate — those depend on the proxy type (residential vs mobile) and target site, not on how the connection was authenticated.