Fixed address
Static and dedicated — the address never changes, so the profile's network footprint stays consistent.
Set up a dedicated static IP in fingerprint browsers
Cross-border ecommerce and advertising teams manage account environments in fingerprint browsers, and a stable, clean, controllable egress IP is a core part of each environment. This page shows how to pair AdsPower, BitBrowser, and similar tools with a dedicated static IP: connection model, verification steps, and where it applies.
How it connects: client-level egress + local direct connection
CityLink delivers dedicated static IPs through its client: once the device connects, the whole machine egresses from that fixed dedicated IP. In the fingerprint browser, set the profile to “No proxy (local direct)” — profile traffic uses the local network, which is now your dedicated static IP. AdsPower's official docs state the same: no-proxy profiles use the local network IP.
One user per IP
Never shared or recycled; the usage history is yours to control from delivery.
Fit for primary accounts
One device, one route, one egress — right for the long-term environment of your most important accounts.
Setup steps (AdsPower example)
- Connect the dedicated static IP routeConnect in the CityLink client, then confirm the machine egress on an IP-checking site.
- Create a profile with No proxyIn AdsPower, set the profile's proxy to “No proxy (local direct)”; BitBrowser and similar tools have an equivalent direct-connection option.
- Verify inside the profileUse “check proxy” or open an IP-checking site inside the profile; confirm the egress IP and region match the account's footprint. Switch the IP-lookup channel if the region displays oddly.
- Keep usage consistentFixed profile, fixed workload, regular patterns — avoid switching egress frequently.
Applicability (read first)
- This is machine-level egress: all no-proxy profiles on the same device share one egress IP. If you need many different-IP profiles running in parallel on one machine, per-profile proxy resources are required — this setup does not cover that.
- No anti-association or anti-ban guarantees: platforms weigh account, device fingerprint, and behavioral signals together; the network is only one part.
- For teams where each member needs their own fixed egress, see team dedicated nodes. Follow the target platform's terms.
Related reading
FAQ
Can one machine run several different-IP profiles at once?
This setup is machine-level egress: no-proxy profiles on the same device share one dedicated static IP. Running many different-IP profiles in parallel requires per-profile proxy resources — mention this need when selecting a plan.
What does a dedicated static IP add to an account environment?
A fixed address, one user per IP, never shared or recycled — the profile's network footprint stays consistent and its history is yours to control. Right for primary accounts.
What about teams where each member needs a fixed egress?
Consider team dedicated nodes: fixed egress per member or group with unified management. Email us with your team size to discuss.
Plan by your accounts
Tell us your platform, account count, device count, and region needs. We will recommend personal or team dedicated options based on actual requirements.