To authenticate an IP address for proxy access, identify your device or server's public IP address, add it to your proxy provider's authorized IP list, and test the connection using your assigned proxy endpoint. This process is called IP authentication, IP authorization, or IP allowlisting.
Unlike username-and-password authentication, IP-based authentication allows a proxy server to recognize approved connections by their network source address. It is particularly useful for datacenter proxies, web scraping applications, automated data pipelines, and servers operating from stable networks.
However, successful authentication requires more than entering an IP address. You must identify the correct public-facing IP, understand how your network routes traffic, and verify that requests actually pass through the proxy.
In this guide, we'll explain how IP authentication works, walk through setup on ProxiesThatWork, demonstrate practical connection tests, and troubleshoot common authorization problems.
IP address authentication is a network access-control method that determines whether a connection originates from an approved IP address.
When a client attempts to connect to a proxy server, the server checks the source IP against an authorized list.
If the IP matches an approved entry, the connection can proceed, subject to other applicable restrictions. If it does not match, the proxy can reject the request.
The process follows four basic steps:
For example:
Your Application
Public IP: 198.51.100.25
|
v
Proxy Authentication
Is 198.51.100.25 authorized?
|
Yes / No
/ \
Allow Reject
|
v
Proxy: 203.0.113.10:8080
|
v
Destination Website
The IP addresses above are documentation examples, not working proxy endpoints.
IP authentication is particularly convenient for unattended automation because applications do not need to supply a proxy username and password with each connection.
However, an authorized IP identifies an approved network origin, not necessarily a specific person or individual device.
You must authorize the public IP address from which your device or application connects to the proxy, not the proxy server's own IP address.
Understanding this distinction prevents one of the most common configuration errors.
A private IP address identifies a device within a local network. A public IP address identifies the internet-facing connection used to communicate with external systems.
| IP address | Type | Should you authorize it? |
|---|---|---|
192.168.1.100 |
Private LAN address | No |
10.0.0.25 |
Private network address | No |
172.16.0.10 |
Private network address | No |
198.51.100.25 |
Example public source address | Yes, if it represents your actual egress IP |
203.0.113.10 |
Example proxy endpoint | No |
Private addresses are useful within internal networks, but they generally cannot identify your connection to an external proxy provider.
Your public IP may not belong directly to the machine running the application.
For example:
The correct address is the public source IP actually observed by the proxy service.
Before configuring IP authentication, determine which public address your system uses for outbound connections.
Open a public IP lookup service such as https://api.ipify.org from the computer that will use the proxies.
The service displays your current public IP address.
This method is straightforward for desktop users, but the result can differ from the address used by a separate application, server, or network connection.
On Linux or macOS, open a terminal and run:
curl -4 --noproxy '*' https://api.ipify.org
Example output:
198.51.100.25
The -4 option requests IPv4 connectivity. The --noproxy '*' option prevents cURL from using a proxy for this particular check.
This helps identify your direct public connection even when proxy-related environment variables are configured.
On Windows PowerShell, use:
curl.exe -4 --noproxy "*" https://api.ipify.org
Using curl.exe explicitly avoids ambiguity with PowerShell commands or aliases.
Important: Run this test from the machine or deployment environment that will actually connect to the proxy. Checking your laptop's IP does not identify your remote server's IP.
For simple home networks, the public IP lookup may be sufficient.
Production systems require an additional check because application traffic can leave through different network interfaces or gateways.
If several devices share one router, they commonly share the same public IPv4 address through network address translation (NAT).
Authorizing that public IP may allow all eligible devices using the same outbound connection to reach the proxy service.
That also means IP allowlisting alone cannot distinguish individual users sharing the authorized connection.
For applications running on AWS, Azure, Google Cloud, or another cloud platform, identify the network's actual outbound IP.
Depending on the deployment, this may be:
Do not assume the cloud instance's public IP is always its outbound IP.
For reliable production operation, consider using a controlled, stable egress address.
If your application routes traffic through a VPN, the proxy may see the VPN's exit IP rather than your internet provider's address.
Check the public IP while the VPN is active and confirm the application's actual route.
Changing VPN servers may require updating the authorized IP list.
ProxiesThatWork provides HTTP/HTTPS datacenter proxies with IP-based authentication.
Once you have identified your public source IP, configure authorization through your account.
For example:
Authorized IP Address
198.51.100.25
Status: Authorized
This is an illustrative configuration, not an exact dashboard screenshot.
The account interface may vary, so follow the available IP authorization controls.
If several application servers have separate public egress addresses, authorize the necessary addresses within your account's supported limits.
Avoid adding IP addresses that do not need proxy access.
For an introductory walkthrough of these account settings, see our guide to authorizing your IP for ProxiesThatWork.
Once your source IP is authorized, configure your application with the proxy endpoint supplied in your account.
A typical HTTP proxy endpoint uses this format:
PROXY_HOST:PORT
Example:
203.0.113.10:8080
For applications that require a proxy URL:
http://203.0.113.10:8080
Replace the example address and port with your actual assigned proxy details.
With IP authentication, the connection is authorized through the source IP. No proxy username or password is required for that authentication method.
An HTTP proxy can often handle HTTPS destination requests using the HTTP CONNECT method.
For example:
Application
|
HTTP Proxy Connection
|
CONNECT example.com:443
|
TLS Connection
|
HTTPS Website
The proxy URL may therefore begin with http:// even when the destination uses HTTPS.
Do not change the proxy URL scheme to https:// unless the proxy endpoint explicitly supports TLS connections between the client and proxy.
For a broader introduction to endpoints, connection formats, and initial testing, read our datacenter proxy setup guide.
Testing confirms whether your authorized IP can successfully establish a proxy connection.
First, check your direct public IP:
curl -4 --noproxy '*' https://api.ipify.org
Next, send a request through your assigned proxy:
curl --proxy http://203.0.113.10:8080 \
--connect-timeout 10 \
--max-time 20 \
https://api.ipify.org
The expected result is the public exit IP used by your proxy, rather than the original direct connection.
Some providers restrict particular destinations. If the IP-check service is unavailable through your proxy, use another permitted test endpoint.
A successful test establishes that:
A successful connection does not prove that every destination website will accept your requests or that all proxies in a larger pool work correctly.
Test one proxy first, then expand validation to additional endpoints.
Python applications can use IP-authenticated HTTP proxies through the requests library.
Install the library if necessary:
pip install requests
Then create a simple connection test:
import requests
proxy = "http://203.0.113.10:8080"
proxies = {
"http": proxy,
"https": proxy
}
try:
response = requests.get(
"https://api.ipify.org?format=json",
proxies=proxies,
timeout=20
)
response.raise_for_status()
print("Proxy connection successful")
print("Proxy exit IP:", response.json()["ip"])
except requests.exceptions.ProxyError as error:
print("Proxy connection failed:", error)
except requests.exceptions.Timeout:
print("Proxy request timed out")
except requests.exceptions.RequestException as error:
print("Request failed:", error)
Replace the example endpoint with your assigned proxy address.
Because authorization occurs through the application's public source IP, the configuration does not include proxy credentials.
If the Python test fails but cURL succeeds, investigate:
A successful terminal test is useful, but production applications should also be tested inside their actual runtime environments.
IP authorization errors can resemble ordinary proxy connectivity failures.
Identifying where a request fails is more useful than repeatedly changing proxy addresses.
| Problem | Possible cause | Recommended action |
|---|---|---|
| Proxy authentication failure | Source IP not authorized or incorrect authentication configuration | Verify the actual public IP and account settings |
| HTTP 407 | Proxy requests authentication | Confirm the authentication method expected by the provider |
| HTTP 403 | Access denied by proxy or destination | Identify which service returned the error |
| Connection refused | Incorrect endpoint, closed port, firewall restriction, or unavailable service | Verify host, port, and network connectivity |
| Connection timeout | Network routing, firewall, or endpoint availability problem | Test reachability and review connection timeouts |
| Works locally but not in production | Different public egress IPs | Check the server's outbound address |
| Stopped working after reconnecting | Public IP changed | Update the authorized IP |
| HTTP 429 | Rate limit imposed by proxy or destination | Identify the source and adjust permitted request volume |
An HTTP 407 response means a proxy requires authentication that has not been successfully provided.
However, different providers may reject unauthorized source IPs differently. A rejected connection may appear as an authentication error, access denial, connection closure, or another provider-specific response.
Do not assume every 407 error can be fixed by adding credentials, particularly when the service uses IP-based authentication.
For deeper troubleshooting:
curl -v \
--proxy http://203.0.113.10:8080 \
--connect-timeout 10 \
https://api.ipify.org
Verbose mode can help reveal connection failures, HTTP proxy responses, and HTTPS tunnel establishment.
Avoid publishing full diagnostic logs without reviewing them for sensitive information.
IP authentication depends on the source address remaining authorized.
If your internet provider assigns a new public IP, your existing allowlist entry may no longer match.
This commonly affects residential broadband, mobile connections, and networks using dynamically assigned addresses.
For example:
Previous source IP:
198.51.100.25
New source IP:
198.51.100.80
Result:
New source IP requires authorization
To restore access, confirm your current public IP, update the approved address in your proxy account, and repeat the connection test.
For unattended scraping or automation, a stable cloud egress IP can reduce the need for frequent updates.
A dedicated NAT gateway or controlled outbound network can also make authorization easier when multiple applications share infrastructure.
Both methods can restrict proxy access, but they rely on different controls.
| Feature | IP authentication | Username/password |
|---|---|---|
| Access requirement | Approved public source IP | Valid proxy credentials |
| Best suited for | Stable servers and controlled networks | Clients using changing networks |
| Proxy password required | No | Yes |
| Main operational concern | IP changes and shared egress | Credential exposure and rotation |
| Works with automation | Yes | Yes, when supported |
Neither method is automatically more secure in every environment.
IP authentication avoids sending proxy passwords, but a shared outbound IP can represent multiple devices. Credential authentication distinguishes clients using secrets but introduces credential-management obligations.
Our comparison of IP whitelisting and username/password authentication explores these trade-offs in greater detail.
ProxiesThatWork's published proxy plans list IP authentication. Do not assume username/password authentication is included unless explicitly supported by your service configuration.
For business applications and automated workloads, IP authentication should be managed as part of network security and deployment operations.
Use stable outbound IP addresses. Unpredictable egress routing can cause intermittent authentication failures, especially across containers and cloud environments.
Follow least-privilege access. Authorize only the source addresses necessary for active applications. Remove retired servers and obsolete network entries.
Document your egress configuration. Maintain an internal record connecting approved addresses to applications, owners, and environments.
Secure the underlying systems. IP authorization is not a substitute for firewall policies, user authentication, operating system security, and appropriate application permissions.
Monitor failures. Track repeated connection denials, unexpected source-IP changes, and sudden increases in proxy authentication errors.
Test infrastructure changes. Revalidate access after VPN changes, cloud migrations, NAT gateway replacements, or network reconfiguration.
Avoid uncontrolled retries. Repeatedly retrying an unauthorized connection does not correct the source-IP mismatch. Stop the job, diagnose the configuration, and retry after correcting it.
Teams using proxies through desktop applications can also consult our browser proxy configuration guide.
Find your public source IP address, add it to your proxy provider's authorized IP list, save the configuration, and send a test request using the assigned proxy endpoint. The proxy checks the connecting source IP against the approved list.
Yes. In proxy networking, IP authentication commonly refers to authorizing connections based on an allowlist of public source addresses. IP allowlisting is the more precise term because an IP address alone does not establish an individual user's identity.
Authorize your public outbound IP. Private addresses such as 192.168.1.100 generally do not identify your connection to an external proxy provider.
No proxy username or password is normally needed when the service authorizes connections exclusively through source-IP allowlisting. Other services may use credentials or additional controls, depending on their configuration.
Many proxy systems support multiple authorized source IPs, subject to account rules and limits. This is useful when running applications across different servers, networks, or environments.
The two systems may have different public outbound IP addresses. Check the server's actual egress IP and confirm that it is authorized.
Your public IP may have changed, the authorization entry may have been removed, or the application may now use a different outbound network. Incorrect proxy settings and connectivity failures can also produce similar symptoms.
IP authentication restricts access by network origin, but it does not independently encrypt traffic or guarantee that every device using an authorized address is trustworthy. Secure network configuration and appropriate transport protections remain important.
Yes, when the provider supports it. The source IP used to access the proxy service and the proxy exit IP used to reach websites are separate concepts. Rotating exit IPs does not necessarily require changing the authorized client IP.
IP authentication is a straightforward way to control access to proxy infrastructure, particularly for servers, automated crawlers, and applications with predictable outbound network addresses.
The most important step is identifying and authorizing the correct public source IP. Once that is configured, test the connection, verify the proxy exit address, and monitor your environment for changes that could interrupt access.
At ProxiesThatWork, we provide HTTP/HTTPS datacenter proxy infrastructure with IP authentication to support legitimate data collection, monitoring, development, and automation workflows.
Explore our datacenter proxy plans to find a configuration suited to your workload and connection requirements.
With the right authorization settings, network controls, and validation procedures, proxy authentication can remain reliable even as your applications grow.
Rowan is a digital privacy advocate and web automation expert. With a background in software development and network analysis, Rowan helps users understand how proxies and anonymity tools can improve both security and efficiency online.