Using a Static IP for IP Whitelisting on APIs and Admin Panels
By the ProxyV4 Engineering Team · Updated:
A static IP for IP whitelisting gives your outbound traffic one fixed address that a partner API, firewall or admin panel can add to its allow-list. Home and office connections often get a new public IP from time to time, and each change locks you out until someone updates the list. Sending that traffic through a private static proxy gives it an address that stays the same while the proxy is active.
Why services ask for a static IP for IP whitelisting
An IP allow-list tells a server to accept connections only from listed addresses. It cuts down the traffic that can reach a login page or API at all, which is why payment providers, B2B data feeds and internal tools often ask for your outbound IP during onboarding.
The list only works if your address stays put. Many consumer and some business connections receive a new public IP after a router restart or when the provider reassigns addresses, and cloud instances without a reserved address can change too. A static outbound IP solves that: the service sees one address on every request you route through it.
- Tighter firewall rules. Cloud security groups, host firewalls and many SaaS admin settings can accept a single address written as a /32.
- Fewer interrupted sessions. Some services add a security check when a login suddenly comes from a new address.
- Clear logs. Partners can tie API calls and quota usage to one known address.
- Not a password replacement. Keep normal authentication on the service as well; an allow-list is an extra layer.
Where a fixed outbound IP is usually required
The details differ by service, but three situations come up again and again.
Partner and payment APIs (fixed IP for API allowlist)
Many partner APIs ask for your production egress addresses and reject calls from anything else, often with an HTTP 403. If your jobs run from a laptop, a home office or cloud instances without a reserved address, route the API client through the static IP and register that one address with the partner.
Admin panels and hosting consoles
Teams often restrict a CMS backend, hosting console or internal dashboard to known addresses. Remote staff rarely have fixed home IPs, so a shared static proxy gives the administrator one address to allow. Only people who should reach the panel should get the proxy line.
Databases and other non-web connections
Database ports are commonly limited to approved client IPs. These connections are not HTTP, so an HTTP proxy will not carry them; you need SOCKS5 support in the client or a tool that routes a program through SOCKS5, such as Proxifier. Check that your database client works this way before you rely on it.
Route your tools through the static outbound IP
The allow-list only sees traffic that actually goes through the proxy. Command-line tools such as curl read proxy environment variables, as covered in the curl setup guide:
export HTTPS_PROXY="http://USER:PASS@IP:PORT"
curl --max-time 15 https://proxyv4.com/api/my-ipIn code, pass the proxy to the HTTP client directly. With Python Requests:
import requests
proxy = "http://USER:PASS@IP:PORT"
proxies = {"http": proxy, "https": proxy}
response = requests.get("https://proxyv4.com/api/my-ip", proxies=proxies, timeout=10)
print("Outbound IP:", response.text.strip())Both should print the proxy's IP, not your own. Send that exact address to the service owner, not the one you see on your own connection.
Static outbound IP options compared
A proxy is not the only way to get a fixed address. Which option fits depends on what needs the address and how much you want to set up. For background, see static IP vs dynamic IP.
| Option | Setup effort | What it carries | Good fit |
|---|---|---|---|
| Private static proxy | Low, configured per tool | Traffic from apps that support HTTP(S) or SOCKS5 proxies | API clients, scripts, browsers, admin panels |
| Cloud NAT gateway or reserved IP | Higher, cloud networking | All traffic from instances in that network | Workloads already running in that cloud |
| Company VPN with fixed egress | Medium, client software | All traffic from a connected device | Staff who need several internal systems |
| Static IP from your internet provider | Depends on provider and location | All traffic from that site | A fixed office |
When a ProxyV4 private IPv4 fits, and when it does not
A private datacenter IPv4 from ProxyV4 has one tenant for the whole term, which matters for allow-lists: no other customer's traffic leaves from the address you have asked a partner to trust. The IP stays the same while the proxy is active, and renewing before expiry keeps the same address. It is available in the United States, Vietnam, Japan, South Korea, Singapore, the United Kingdom and Hong Kong, and traffic is unmetered.
Every proxy supports HTTP(S) and SOCKS5 with username and password login. On the order's page you choose HTTP only, SOCKS5 only or both on the same port; switching modes can move the proxy to a new port, so copy the ip:port:user:pass line again afterwards. Username and password is the documented way to log in to the proxy itself; if you need another method, ask support.
It is the wrong tool if the service only accepts residential or mobile connections; ProxyV4's static ISP IPs (United States and Vietnam) may suit the first case, and mobile proxies are not sold. It also does not fit jobs that need many changing IPs. IPv6 proxies are a separate product that only works on IPv6-ready sites, and if a workflow depends on UDP, ask support before ordering. Prices are per IP per month; see live prices and order a single IP to test your allow-list first.
Troubleshooting allow-list rejections
If the service still rejects you after the IP is listed, work through these checks in order.
The request is not going through the proxy
The most common cause. Some programs ignore proxy environment variables, a NO_PROXY entry may exclude the target, and a browser without proxy settings connects directly, possibly over IPv6. Run the curl check from the same machine and tool, or open the my IP tool in the browser profile you use, and confirm the exit IP is the proxy's IPv4 address.
Proxy login errors (407)
An HTTP 407 comes from the proxy, not the target: the username or password is missing or wrong. Copy the line again from the dashboard, and URL-encode special characters if the password sits inside a proxy URL.
The allow-list entry itself
Check that the entry matches the address exactly, written as a single IP or /32 where the form asks for CIDR. Some services apply allow-list changes on their own schedule, so ask the owner when a change takes effect before assuming the proxy is at fault.
Step by step
- 1
Get a static IP
Order one private IPv4 and copy its ip:port:user:pass line from the dashboard.
- 2
Confirm the exit address
Run the curl check through the proxy and note the IP it returns.
- 3
Add the IP to the allow-list
Send that address to the partner, or add it as a single IP or /32 in your firewall or admin settings.
- 4
Point your tool at the proxy
Set the proxy in the client, script or browser profile that needs access.
- 5
Test the protected resource
Make a real authenticated request to the service and confirm it is accepted.
Frequently asked questions
Will my static IP change when I renew?
No. On ProxyV4, the IP stays the same while the proxy is active, and renewing before expiry keeps the same address.
Can other users share my whitelisted IP?
No. Each private IPv4 has one tenant for the whole term, so no other customer's traffic leaves from it.
Can I use SOCKS5 and HTTP on the same static IP?
Yes. On the order's page you can choose HTTP only, SOCKS5 only or both on the same port.
What if the static IP does not connect?
A proxy that fails for a technical reason, such as not connecting or showing the wrong location, is covered by the refund policy and credited to your account balance.
Can I order just one IP to test an allow-list?
Yes. A single IP can be ordered, so you can test it with the partner or firewall before adding more.
A private IPv4 that stays yours while you renew
One tenant per IP, the same address while active and after renewing before expiry, HTTP(S) and SOCKS5, and unmetered traffic. Order one IP to test your allow-list.
Get a static IP