IP allowlisting with a static ISP proxy, in both directions

Direction 1: a partner allowlists your proxy IP

Use this when a supplier portal, a partner API or your company’s own admin tool only accepts known addresses, and your team works from changing home or travel connections.

1. Rent one dedicated IP (buy one ISP proxy).
2. Confirm it is static and note the exit IP.
3. Send that IP to the partner for their allowlist, with the rental end date.
4. Route only that tool’s traffic through the proxy (browser profile, script or app setting).
5. Renew before the end date. Renew from your balance before the end date to ask for the same IPs; keeping an IP depends on upstream stock, and the client area shows the result before you pay.

Direction 2: we allowlist your IP to log in without a password

Use this when a tool cannot store proxy credentials. In your client area, add up to 10 of your own public IPs; connections from them are accepted without a username and password. Anyone else still needs credentials. Remove an IP from the list as soon as you stop using that connection.

Why not use a shared or rotating IP for an allowlist?

• A rotating IP changes, so the partner would have to allow a whole range, which most refuse.
• A shared IP lets other customers of the same vendor through the partner’s allowlist. That is a security risk for the partner, and a reason to refuse it. See dedicated vs shared.
• A dedicated static IP is one address used by you alone for the rental, which is what allowlists are designed for.

What can go wrong, and how to plan for it?

• The rental ends: renew before the end date and keep the date in the partner’s ticket.
• The IP fails: a replacement IP has a different address, so the partner must update the list; give them two IPs from the start if downtime is costly.
• The partner sees a consumer provider: some security teams expect a business range; tell them it is a dedicated proxy IP and give the AS number from an ASN lookup.