Geo-Targeting with Residential Proxies: Country, City, ZIP, and ASN

Geo-targeting is the ability to choose where your residential proxy exit appears on the map and the network. It is one of the main reasons teams use residential proxies at all: to see public content the way a visitor in a specific place would. This guide explains the levels of targeting, when finer targeting is worth it, and the availability trade-offs that come with narrowing the pool.

The levels of geo-targeting

Residential networks typically expose targeting at several levels of granularity:

• Country: nearly universal. You request an exit in a specific country.
• State or region: common in larger countries, letting you target a sub-national area.
• City: available from many providers, useful for local verification.
• ZIP or postcode: offered by some providers for fine local targeting.
• ASN: targeting by the network operator (the autonomous system), useful when the specific network matters.
• Carrier: rarer, letting you target a specific mobile or fixed-line carrier.

Not every provider offers every level. Country targeting you can assume; anything finer must be confirmed in the provider's documentation. Where a level is not documented, treat it as unknown rather than assuming it exists or is absent.

When finer targeting genuinely helps

Country targeting is enough for many tasks, but finer targeting matters when local variation is the point. Authorized examples include verifying that a public listing or advertisement appears correctly in a specific city, testing how a localized page renders for a particular region, checking regional availability of public content, and confirming that location-based public information is consistent across areas. In these cases, a country-level exit is too coarse to reveal the local differences you are trying to observe.

ASN targeting and why it exists

ASN targeting lets you choose exits on a particular network operator. This is more specialised: it matters when the behaviour you are studying depends on the specific network rather than just the location, or when you need to confirm that public content is consistent across different operators in the same area. ASN targeting is a power feature; most tasks do not need it, but for those that do, it is hard to substitute.

The availability trade-off

The central trade-off in geo-targeting is simple: the narrower you target, the smaller the eligible pool of exit addresses. A country may have a large pool; a specific ZIP code within it may have very few available addresses at any moment. Narrow targeting can therefore reduce availability, increase latency, or make some exits unavailable when you need them. Plan for this by targeting only as narrowly as the task truly requires, and by building tolerance for reduced availability into finely targeted work. Over-targeting is a common cause of frustration that is entirely avoidable.

How targeting is configured

Providers expose targeting differently. Common patterns include country-specific gateway endpoints, parameters appended to the username, or explicit fields in an API request. Because the syntax varies, follow the provider's documentation precisely. Here is an illustrative, provider-agnostic sketch showing the shape of a targeted request using placeholders and an authorized target:

# Illustrative only — real syntax varies by provider.
# Country target expressed via a username parameter (pattern varies):
curl --proxy "http://$PROXY_USER-country-de:$PROXY_PASS@gateway.example-provider.net:7000" \
     --max-time 30 https://example.com/

# City target (if supported and documented by the provider):
curl --proxy "http://$PROXY_USER-country-de-city-berlin:$PROXY_PASS@gateway.example-provider.net:7000" \
     --max-time 30 https://example.com/

Always confirm the exact parameter names and supported values in the provider's own docs, and test on an authorized target before scaling.

Verifying that targeting worked

Do not assume your targeting took effect — verify it. Against an authorized endpoint that reports the requesting IP's apparent location, confirm that exits appear where you asked. Build a small check into your workflow so that if a provider's targeting drifts or a value is unsupported, you notice quickly rather than collecting mislabelled data. This is especially important for finely targeted work, where a silent fallback to a broader area would corrupt your results.

Targeting and ethics

Geo-targeting does not change your obligations. Reaching a specific location lets you observe public content from that vantage point; it does not grant permission you lack, and it must serve a lawful, authorized purpose. Localization testing, regional ad verification, and authorized public-data research are legitimate uses of targeting. Using targeting to circumvent geographic access controls you are not entitled to bypass is not. Keep the purpose lawful and the targeting proportionate to the task.

Planning your targeting strategy

1. Identify the coarsest level that answers your question. If country works, do not target a ZIP.
2. Confirm the provider documents the level you need. Treat undocumented levels as unknown.
3. Plan for reduced availability when targeting narrowly, with retries and tolerance built in.
4. Verify targeting on an authorized endpoint before trusting the data.
5. Keep the purpose lawful and proportionate.

Balancing precision against availability

The recurring tension in geo-targeting is precision versus availability, and getting the balance right is largely a matter of matching targeting to the actual question. If you only need to know how something appears at a national level, country targeting gives you the largest, most reliable pool. If your question is genuinely local, accept that finer targeting means fewer exits and plan for it with tolerance and retries. A useful discipline is to start at the coarsest level that could answer your question and only tighten targeting when the coarser view proves insufficient. This avoids the common trap of over-targeting from the outset, which quietly degrades availability and latency for no analytical benefit.

As a practical habit, keep a short note of which targeting levels each provider actually supports for the regions you care about, verified against their documentation and your own checks. Because these capabilities change and are not always advertised consistently, a small maintained record saves you from rediscovering the same limitations on every project.

Summary

Residential geo-targeting ranges from country down to ZIP, ASN, and sometimes carrier, and it is central to localization testing and regional verification. Finer targeting reveals local variation but shrinks the eligible pool, so target only as narrowly as the task needs, confirm the provider documents the level you require, verify that targeting actually worked, and keep the purpose lawful. For the mechanics of rotation alongside targeting, see how rotation works, and for localization specifically, our ad verification and localization guide.