IP Whitelist
Last updated
The IP Whitelist is an authentication method provided by 1024Proxy that allows proxy usage without username and password authentication.
In addition to the standard Username & Password Authentication method, the IP whitelist offers a more convenient and efficient authorization solution. By adding trusted public outbound IP addresses to the whitelist, the system can automatically identify the request source. As long as the request originates from a whitelisted IP, users can directly call the API and use proxy IPs without including a username or password in the request, greatly simplifying the configuration process.
✅ No username/password required Eliminates the need to expose credentials in code or tools
✅ Simpler configuration Ideal for environments with fixed servers or cloud instances
✅ Secure and controlled access Only whitelisted IPs are allowed to access proxy resources
✅ More suitable for automation Fewer parameters, lower risk of configuration errors
For users with a fixed outbound IP address, the IP whitelist is a more stable and secure authentication method.
The IP whitelist mode is particularly suitable for the following scenarios:
Avoid hardcoding usernames and passwords in code
Improve overall security
Multiple services can access proxies through the same outbound IP
Easier centralized management
Reduce authentication steps
Improve request efficiency and stability
Prevent credential leakage or misuse
Log in to the 1024Proxy user dashboard, go to the IP Whitelist page, add your public IP address to the whitelist, and save the settings.


Notes:
Only public IP addresses are supported
If your IP changes, be sure to update the whitelist in time; otherwise, the proxy will not work properly
After successfully adding an IP to the whitelist, you can configure the proxy in third-party tools such as anti-detect fingerprint browsers by simply entering the hostname and port. There is no need to provide a username or password, as the system will automatically authenticate the request based on the source IP.

Only add trusted, fixed IP addresses to the whitelist
Avoid adding dynamic IPs or public network IPs
Regularly review and remove unused whitelisted IPs
If using multiple servers, add each corresponding outbound IP separately
Last updated