Change language
English Русский Deutsch Español Français Italiano Українська Tiếng Việt Türkçe Bahasa Indonesia हिन्दी 日本語 中文
Menu
Pricing
Proxies
Solutions
Resources

What a fixed address is for

Four proxy use cases depend on an address that stays the same from one session to the next. Proxy work tends to be either wide and short-lived or narrow and repeated, and these four are the second kind.

Every scenario below is open by default. A short list of targets needs a verification step first, and each page says plainly whether it is on that list.

In short: All four scenarios run on one static ISP address: a single IP on a named internet provider’s network, kept for the period you pay for and used by nobody else while you hold it. What differs is why the address must not change and whether our Acceptable Use Policy attaches a condition. The table further down sets the four side by side.

A static address is the opposite of a rotating pool, which hands out a new address per request or per short window. A datacenter address is registered to a hosting company; a static ISP address is on an internet provider’s network. Address blocks are handed out through the five regional internet registries (IANA’s number resources page lists them), and who holds each block is public record, so a target can check the registration for itself.

These four were chosen because in each of them the address staying the same decides the outcome. The scenario pages draw on how the address types behave and on our published policies. We have measured no platform ourselves, and the editorial policy says how figures are sourced.

Where being the same visitor twice is the requirement

Account management

Accounts you own or are contracted to run, reached from an address that does not change between sessions. A condition applies to accounts you do not personally own.

Region testing

Geo testing of your own site, prices and availability: seeing them the way a visitor in another country does, repeatedly and from the same vantage point, so a difference between two runs means something changed.

Ad verification

Ad verification: checking that a campaign shows what it was booked to show, from the market it was booked in, as an ordinary viewer there would see it.

Fraud prevention

Testing your own defences: reproducing what a signup or a transaction looked like and checking what the network behind it reports.

Who these scenarios are for

Teams choosing an address type

Whether a fixed address fits work they already do, or whether a rotating pool or a datacenter address would suit it better.

Teams whose work is one of the four scenarios

Why the address must not change in that job, and whether our Acceptable Use Policy attaches a condition to it.

Which scenario is yours?

The four scenarios on the same three questions

Drawn from how a static address behaves and from the Acceptable Use Policy, whose sections the last column cites.
Why the address must not changeWhat the job needs from itCondition under the policy
Account managementPlatforms commonly compare each sign-in with the account's historyOne address per account, kept at renewalEvidence of authority over accounts you do not personally own (§2)
Region testingTwo runs compare only from the same vantage pointOne address per market, from 77 countriesNone for your own site; bypassing geo-blocking is prohibited (§5)
Ad verificationThis week's check is only useful next to last week'sAn internet provider's network in the market that was boughtNone: named as needing no prior review (§2)
Fraud preventionA rule change should be the only variable in a testA known registration to check lookups againstNone for your own rules; written authorisation to test systems you do not own (§2)

Pick the one that describes your work

Questions about these scenarios

Why these four and not the usual list?

Because in these four a fixed address on an internet provider's network decides the outcome. Broad crawling, wide data collection and market-scale scraping are real jobs, and a rotating pool serves them better. A fixed address would be the wrong sale for them, and rotating residential is not on sale here yet. Rotating Residential

Do I need approval before I start?

No. Ordering, connecting and running the service is open by default, and our acceptable use policy names ad verification, anti-fraud monitoring and testing by region as needing no prior review. Verification attaches to targets, whatever the scenario: accounts on third-party platforms you do not personally own, security testing against systems you do not own, collecting personal data, and targets in financial services, healthcare or government. Verification means confirming the point in writing; for some targets it may include identity or business verification. Acceptable Use Policy

Can one address cover several of these at once?

Technically yes, and it is usually a bad idea. Reputation is per address, so mixing an account you cannot afford to lose with exploratory work on the same IP means one job's mistake becomes the other job's problem. Separate the work that matters from the work that experiments.

What happens if an address stops working mid-project?

You ask and we replace it, free, up to 20 % of the IPs in your order per calendar month. The grounds are an address that stops responding, one whose geolocation moves outside the country you bought, or one blocked on the target you named at purchase. A replacement is a different address for the rest of the period you already paid for; it does not extend the period, and it does not apply where the address became unusable through activity the Acceptable Use Policy prohibits. Terms of Service

If a scenario fits, read its page and any condition on it before you buy. The catalogue sells addresses in 77 countries, priced per IP per period; start with one address per job. On a first order you can ask for a refund within 24 hours, once per customer and for up to 10 IPs, even after testing them against your real targets.

Sources