Targeting by Country, City, and ASN

You connect to one hostname — <proxy-host> on port 80 — over HTTP, HTTPS (CONNECT), or SOCKS5. Targeting parameters are suffixes appended to your username, separated by hyphens. The password never changes, and neither does the endpoint.

Each suffix is a key-value pair: a short code, a hyphen, then the value. The proxy parses the suffixes at connection time and picks an exit IP matching the requested target and session parameters.

# Plain rotating request (any country)
curl -x http://user123:pass@<proxy-host>:80 https://example.com

# Same credentials, US exit IPs only
curl -x http://user123-cc-US:pass@<proxy-host>:80 https://example.com

Country targeting uses -cc- followed by the two-letter ISO country code: -cc-US, -cc-DE, -cc-BR. This is the most common filter and the safest default — country pools are large, so rotation stays healthy.

Continent targeting uses -co- with one of six codes:

• AF — Africa
• AS — Asia
• EU — Europe
• NA — North America
• OC — Oceania
• SA — South America

Country and continent are mutually exclusive — use one or the other, never both in the same username. -co-EU is useful when any European IP will do and you want the widest possible pool; -cc- is for when the specific country matters.

user123-cc-DE     # Germany only
user123-co-EU     # anywhere in Europe

City targeting uses -ct- followed by the city name: -ct-Dallas, -ct-London. Names with spaces or diacritics are normalized by stripping both — São Paulo becomes SaoPaulo, so the suffix is -ct-SaoPaulo.

Dallas      -> -ct-Dallas
São Paulo   -> -ct-SaoPaulo
New York    -> -ct-NewYork

City filters are the narrowest geographic option, and geolocation at city granularity is inherently less exact than at country level — IP databases sometimes place an address in a neighboring city or metro area. Use city targeting when your use case genuinely needs it, and fall back to country targeting when a mismatch would only be a minor inconvenience.

An ASN — Autonomous System Number — identifies a network on the internet, typically an ISP or hosting provider. An IP address is announced by a network identified by its ASN, so filtering by ASN means filtering by network operator rather than by geography. The suffix is -asn- followed by the number: -asn-13335.

Legitimate reasons to target an ASN:

• Testing how your own site or app behaves for subscribers of a specific ISP — CDN routing, latency, and DNS resolution can differ per network.
• Ad verification and content checks where a campaign or page variant is served differently depending on the viewer's carrier or provider.
• QA for region- and carrier-dependent services, confirming what a real customer of that network actually sees.
• Reproducing a bug report from a user on a particular ISP.

ASN pools vary enormously in size. A major consumer ISP contributes many residential IPs; a small regional operator contributes few. Treat ASN targeting like city targeting: precise, but narrow.

Targeting suffixes stack with sticky session parameters in the same username. -s- pins an IP to a session ID of your choosing, and -ttl- sets how long the pin lasts in seconds (default 60, maximum 86400 — twenty-four hours).

user123-cc-US-s-mysession-ttl-600

# -cc-US      exit IP in the United States
# -s-mysession   sticky session id "mysession"
# -ttl-600    keep the same IP for 600 seconds

The geo filter is applied first, then the session pin holds one IP from that filtered pool. Reusing the same session ID within the TTL returns the same IP; changing the ID gets you a fresh one that still matches the filter. This is the standard pattern for anything login- or cart-shaped, where mid-flow IP changes would break state.

The guiding rule: use the broadest filter that satisfies the requirement. Narrower targeting means a smaller candidate pool, which means less rotation variety and a higher chance of slow or failed picks in thin regions.

• No filter or continent — bulk collection of public data where location barely matters. Maximum pool, maximum rotation.
• Country — the workhorse. Localized search results, country-specific pricing and catalogs, and most market research and SEO monitoring tasks.
• City — local pack results, delivery-radius checks, city-specific ad placements. Accept the smaller pool as the cost of precision.
• ASN — ISP-specific verification and QA. The most operator-precise filter; expect pool size to track the size of the network.

Whatever you build, stay within the rules: respect each target site's terms of service, robots.txt, and rate limits. Geo targeting changes where your requests appear to come from — it does not change what you are permitted to do, and the acceptable use policy applies to every request.

Before wiring a targeted username into a job, confirm it resolves where you expect. Any IP-info endpoint works for a spot check.

1. 01Build the username with your suffix, e.g. user123-ct-SaoPaulo.
2. 02Run a request through it against an IP-geolocation endpoint and check the returned country and city.
3. 03Repeat a few times without a session ID to sample the rotation, or with -s- to confirm the pin holds.
4. 04For batch validation of generated lists, use the built-in proxy checker in the dashboard — it streams per-line results including country and latency.

If a narrow filter consistently times out or returns off-target locations, widen one level — city to country, ASN to country — and retest. Pool depth, not syntax, is usually the culprit.