---
title: "What is geo-targeting for proxies?"
url: https://proxy.wiki/glossary/geo-targeting/
type: Glossary Term
author: "proxy.wiki editorial"
published: 2026-08-19
updated: 2026-10-21
site: proxy.wiki
topics: ["Proxy fundamentals"]
license: CC BY 4.0; quote freely with attribution to https://proxy.wiki/
---

# What is geo-targeting for proxies?

> Asking a proxy service for an exit in a particular country, region, city or network. The site you visit then judges your location with its own data.

Two separate judgements are involved, and neither is a measurement. The provider picks an exit it believes is in the place you asked for. The site you visit then decides for itself where the request came from. Both beliefs come from geolocation data assembled from registry records, routing, latency measurements and feeds that networks publish about themselves, and two sources can disagree about the same address.

## How you ask for a location

There is no standard. Most services take a parameter in the proxy username or map locations to ports, and the syntax differs between providers, so confirm it before writing integration code. The shape is usually something like this placeholder:

```
# Ask for a German exit, then check what you got
curl -s -x http://user-country-de:pass@gw.example.net:8000 https://api.ipify.org
```

Country codes are where a quiet mistake hides. Geofeeds and most location APIs use ISO 3166-1 alpha-2, in which the United Kingdom is `GB`. `UK` is only an exceptionally reserved code; RFC 8805 says parsers may accept codes from that set, which means some will and some will not. Send `GB`.

## Choosing how narrow to go

| Targeting level | What it buys | Check before relying on it |
| --- | --- | --- |
| Country | Local prices, catalogues, search results and consent flows | Whether the provider refuses or substitutes a neighbour when the country has no free exits |
| Region or state | Regional content and tax-dependent pricing | The code format: ISO 3166-2 codes such as US-AL, or names |
| City | Local listings and delivery areas | Two independent lookups per exit: city is free text in the geofeed format, so spelling and granularity vary |
| Network ([ASN](/glossary/asn/)) or carrier | One operator’s view of a service | Pool depth: one network is also one classification decision |

Every step down shrinks the [pool](/glossary/proxy-pool/) you draw from. A thin pool fails in two ways that look alike from your side: more failures as the same few exits are reused, and quiet substitution, if the provider widens your request rather than refusing it. Ask which one your provider does. They are different products, and the difference only shows when the location is scarce.

## Where the location data comes from

A network can publish where its addresses are used in a geofeed, a CSV format defined in RFC 8805: prefix, country, region, city, and a postal code field the RFC now deprecates because it is too precise. These lines are the RFC’s own examples:

```
192.0.2.0/25,US,US-AL,,
192.0.2.5,US,US-AL,Alabaster,
192.0.2.128/25,PL,PL-MZ,,
2001:db8::/32,PL,,,
```

RFC 9632 adds a way for a registry record to point at the feed, so a database can find it. Feeds are voluntary, and databases weigh them against everything else they know.

Registry data is a different thing again, and the two get confused. Looking up 1.1.1.1 through Team Cymru’s IP-to-ASN service returned `13335 | 1.1.1.1 | 1.1.1.0/24 | AU | apnic | 2011-08-11 | CLOUDFLARENET - Cloudflare, Inc., US`. The AU is the country on the APNIC allocation record. The AS name says a US company. The address itself is anycast and answered from many countries. Team Cymru’s documentation is explicit that registry country codes often differ significantly from where an address is actually used.

## When the site disagrees with the exit

Sites rarely trust the address alone. Your `Accept-Language` header, the browser’s timezone and any account settings all say where you are, and a contradiction between them and the exit is more informative than either signal by itself. Set them together. The [IP check on the tools page](/tools/) shows the country two location sources give your current address and flags when your language settings name a different one.

Verify with several draws, not one. A single answer from a rotating endpoint describes one [exit](/glossary/exit-node/), not the pool. The [curl guide](/guides/how-to-use-a-proxy-with-curl/) has a section on checking the exit country, [what is a proxy server?](/guides/what-is-a-proxy-server/) covers what a website sees besides your address, and the [proxy type guide](/guides/residential-vs-datacenter-proxies/) lists the targeting questions worth asking before you buy.

## Frequently asked questions

### Why does my exit show a different country from the one I selected?

Either the database you checked disagrees with the one your provider uses, or the pool had no free exit there and the provider served a nearby location instead. Check the address in two independent sources before concluding which.

### The address is in the right country but the site shows the wrong one. Why?

The site is using other signals as well: your Accept-Language header, the browser timezone and account settings. When those contradict the address, the contradiction is itself a signal. Set them to match the exit.

### Should I ask for UK or GB?

GB. It is the ISO 3166-1 alpha-2 code that geofeeds and most location APIs use. UK is only exceptionally reserved, and RFC 8805 leaves it to each parser whether to accept it.

## Sources

1. [RFC 8805: A Format for Self-Published IP Geolocation Feeds](https://www.rfc-editor.org/rfc/rfc8805.html)
2. [RFC 9632: Finding and Using Geofeed Data](https://www.rfc-editor.org/rfc/rfc9632.html)
3. [Team Cymru: IP to ASN mapping, and why registry country is not geolocation](https://www.team-cymru.com/ip-asn-mapping)
4. [ISO 3166-1 alpha-2: GB as the assigned code, UK exceptionally reserved](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)
