How to set up proxies for your task
Every provider setting gives something and costs something. More filters mean a more precise exit but fewer devices in the pool: more repeats, timeouts and blocks. Pick only what your task really needs.
| Setting | What it gives | What it costs | When to use |
|---|---|---|---|
| Country | Exits in the right country, geo matches the profile and ads. | Smaller pool than “any country”. | Almost always for accounts and geo tasks. For scraping without geo you can skip it. |
| Region / city | Matches the profile's city or local results. | Much smaller pool: more IP repeats and timeouts. City geolocation is imprecise. | Only if the site really checks the city (delivery, local ads). |
| ISP / ASN | The same operator: a stable network picture for the account. | Smaller pool, sometimes by a lot. | If the platform watches ISP changes or you need a specific operator. |
| Device OS | The network fingerprint's system matches the antidetect profile. | Narrows the pool a lot; better without city and region. | Antidetect where the site checks the system (social networks, marketplaces). |
| Rotation on every request | Maximum different IPs, fewer blocks on bulk requests. | No session: an account sees a new IP at every step. | Scraping, price and SERP checks, pool estimation. |
| Sticky session | One IP per profile, like a real person. | The longer the session, the more likely the device goes offline and the IP changes. | Accounts, sign-ups, antidetect. Match the duration to your working session. |
| SOCKS5 protocol | UDP works (WebRTC, some apps). | Not every tool supports it. | Antidetect and anything that needs UDP. |
| HTTP protocol | Supported everywhere, easy to connect. | UDP doesn't work. | Scraping and scripts without UDP. |
| Provider gateway (server) | Less latency on every request. | Nothing, if you pick the nearest. | Always pick the one nearest to you or the exit country. |
| Threads (concurrency) | More requests per minute. | Overload raises timeouts and blocks. | Increase gradually and watch success under load. |
Ready sets for tasks
Sticky session per profile · the profile's country · SOCKS5 · device OS as in the profile · city and ISP only if the platform checks them.
Rotation on every request · country only if results depend on it · HTTP or SOCKS5 · no city, ISP or OS so the pool stays maximal.
Rotation or a short sticky session · the needed country and city if required · remember the city narrows the pool.
Good/bad thresholds are guidance for residential proxies, not a standard. The report holds no credentials or IPs. A repeat test may differ: residential pools change. How we test
Check your providers
Paste proxy lines; the report is ready in a few minutes.