Which one do you need
Two different products are called a dedicated IP
One is an add-on to a consumer VPN: a fixed address for the device you browse from, so banks and CAPTCHAs stop treating you as a stranger. The other is an address for a machine that makes outbound calls on its own, so a partner can put one entry on an allowlist and leave it there. They solve unrelated problems and are bought by different people.
One question tells you which
Is the address for a device a person sits at, or for a server that runs without anybody signed in?
A person's device — laptop, phone, a work machine reaching a corporate resource — is the VPN answer. Buy it from NordVPN, Surfshark or ExpressVPN. It costs a few dollars a month on top of a subscription, installs as an app, and you are done today.
A server, container, CI runner or cluster calling somebody else's API is the other answer, and it is what this site sells. There is no person to sign in, the address has to apply to everything the machine sends, and the partner on the far end needs it to be yours alone and to never change.
What the VPN products actually say they are for
Their own descriptions make the distinction more plainly than ours would.
- NordVPN
- “A dedicated IP is a unique IP address that belongs only to you. It is an additional VPN feature for a more consistent online experience.”
- Surfshark
- “Surfshark's Dedicated IP is a fixed IP address that is unique to you. It works on unlimited devices with all connection protocols.”
- ExpressVPN
- “Get a dedicated IP address with our VPN. Avoid CAPTCHAs, easily access work resources, and more at fast, reliable speeds.”
Quoted from each vendor's own page on 2 August 2026. Check them before relying on this — they are their pages and they can change them.
Browsing, devices, CAPTCHAs, reaching work resources. Not one of them describes a server making API calls at three in the morning, because that is not what they built.
The difference in one table
| VPN dedicated IP | AnchoredIP | |
|---|---|---|
| Bought for | A person and their devices | A server, cluster or CI runner |
| Set up by | Installing an app and signing in | One WireGuard config file |
| Applies to | The device running the app | Everything the machine sends |
| Machines behind one address | The devices you sign in on | Any number, via the tunnel |
| Who holds the address space | The VPN provider | Us, registered at the RIPE NCC |
| Reverse DNS | Not offered | Yours to set |
| Typical use | Banking, CAPTCHAs, remote access | A partner's API allowlist |
When a VPN dedicated IP is the right purchase
If the address is for you rather than for your infrastructure, buy theirs. You want it on a laptop or a phone, you want it working in a few minutes, you want an app with an on switch, and you do not want to think about routing. All three do that well and cost less than we do for that job.
The same is true of a web host's dedicated IP if what you need is a fixed address for a site living on their servers. Buying it where the servers already are is the simpler answer, and we would only be adding a hop.
What you get here instead
An IPv4 address leased to you alone out of space registered to us at the RIPE NCC and announced from our own autonomous system, AS41800, with a valid ROA. It arrives over a WireGuard tunnel to machines you already run, and it does not change — not when you redeploy, not when you add nodes, not when you move cloud provider. Reverse DNS is yours to set. Any number of machines can sit behind one address.
You can check the network exists independently of anything we say: bgp.he.net/AS41800 and PeeringDB.
Questions people ask first
- Is AnchoredIP a VPN?
- No. A VPN exists to change where your traffic appears to come from and to hide it from the network in between, for a person using a device. AnchoredIP exists to make a server's outbound traffic always come from one address that a partner has put on an allowlist. The transport is WireGuard in both cases, which is why the two get confused, but the product is an address and its reputation, not privacy.
- Can I use a NordVPN dedicated IP for my server or API integration?
- It is built for a device a person uses: you install their app, sign in, and the address applies to that session. On a fleet of containers, a CI runner or a Kubernetes cluster there is nobody to sign in, no app to install per pod, and no way for a partner to be sure which of your machines the traffic came from. That is the job this site exists for.
- I just want to stop seeing CAPTCHAs on my laptop. What should I buy?
- One of the three above. Genuinely — that is what they are for, they are cheaper than we are for that job, and you will be set up in minutes with an app rather than a config file. We would be the wrong purchase.
- What is the difference between a dedicated IP and a static IP?
- "Static" means the address does not change. "Dedicated" means nobody else uses it. A hosting provider's static IP is usually both, but it is tied to that provider's server, so it is gone the day you move. What we lease is static, dedicated, and yours across whatever you run it on.
- Does a web host not already give me a dedicated IP?
- For inbound traffic to a site you host there, often yes, and if that is the whole requirement then buying it from them is simpler. It is tied to their infrastructure: it covers the machines in their account, not a Kubernetes cluster somewhere else or a laptop, and it does not follow you to another provider.
- Do I have to move my servers to use AnchoredIP?
- No. Nothing moves. The address is delivered over a WireGuard tunnel to machines you already run — EC2, a pod, a VPS, a bare-metal box — and their default route is left alone.
If it is the server one you need
Seven days on a real address out of the same range paying customers are in, so you can put it in front of the partner whose allowlist started all this and watch it be accepted. No card, and nobody to talk to.