Proxy Geolocation & Targeting

Proxy geolocation is the geographic location associated with a proxy’s exit IP address. Geo targeting is the selection of proxy IPs by country, region, city, or another supported area. It lets a customer choose where requests should appear to come from when a website uses their source IP to determine location.

Geography is one of the properties offered by Proxy Services. It matters for viewing national versions of websites, collecting local search results, testing regional content, and accessing services with geographic restrictions. The useful degree of precision depends on the task: a country can be enough for one application, while another needs a particular city or network.

The location of the exit IP

The address entered into a proxy application is not always the address that a destination website receives. In a simple setup, they may be the same. In a service with a gateway, the application connects to an entry server, and that server forwards the request through a selected exit. The destination receives a connection from the exit IP.

This allows one gateway to provide exits in several countries. Its own IP may be associated with a country different from the one selected for the request. Looking up the gateway address therefore does not establish the location of the exit being used.

The exit’s physical location and its location in an IP database are also separate facts. An IP address contains no country name or geographic coordinates. Databases associate addresses with places using information about the networks that use them. A city label is an estimate or classification, rather than a position reported by a GPS receiver.

Some services offer a virtual location, where the advertised IP geography differs from the physical location of the server. This can matter when a customer needs an actual network presence in a country, rather than only a country label. It also explains why a nearby label alone cannot promise a short connection delay: the traffic still follows a physical route through the gateway and exit to the destination.

Country, region, and city

Geographic targeting narrows the set of eligible exits. Selecting a country leaves the service free to choose among its matching addresses there. Adding a region narrows that set; adding a city narrows it further, where those filters are supported.

With a fixed proxy, the location is generally chosen when the address is allocated. A pool service can instead apply location settings when selecting an exit for a connection. Changing that selection asks the service for a different matching exit; it does not move an existing server to another country.

For example, choosing Canada can allow exits across the country. Ontario narrows the request to one province. Toronto asks for a particular city within that province. A request that only needs a Canadian IP gains no additional country-level benefit from restricting the choice to Toronto; it simply gives the service fewer matching exits to choose from.

Selection detail and location accuracy are different properties. A service may offer a city field even though another database places the same IP in a nearby municipality. An address associated with a large metropolitan area may not be located precisely enough to distinguish its districts. A postal code or a point shown on a checker’s map likewise does not establish the street address of the proxy device.

ASN and ISP targeting

A geographic filter answers where an exit is classified. An ASN filter selects the network associated with the IP. ASN means Autonomous System Number: it identifies a network, or group of networks, operated under a common routing policy on the internet.

This can be useful when a task depends on a particular broadband or mobile operator. For example, a regional service may be available to customers of one network, or a tester may need to compare how a site responds to connections from different operators. Selecting the city alone leaves the network unspecified.

ASN does not sit below city in a geographic hierarchy. One network can serve several cities and countries, and one city contains addresses from many networks. Where a service supports combined filters, “Toronto plus the selected network” means the exits that meet both conditions. Some products support only certain combinations, so the presence of separate city and ASN options does not mean they can always be used together.

ISP targeting usually presents a provider name instead of asking the customer to choose an ASN directly. The relationship is not necessarily one company to one ASN: a provider can operate several networks. An ISP name is therefore a product’s network selection label, whose exact coverage depends on how that product groups addresses. It should also be distinguished from the product category called ISP proxies.

Choosing a familiar operator does not by itself give an address a good reputation or guarantee acceptance by a website. The filter selects a network characteristic; the site still evaluates the connection according to its own rules.

Available locations and available IPs

A targeting menu describes what a service can select. The pool determines what it can actually supply. These are especially different in networks of residential or mobile devices, where exits may become unavailable as devices disconnect or their connections change.

A service may cover a country well while having few available exits in a particular town. Adding a network requirement can reduce that set again. The matching pool can even become empty although the country, city, and network each appear separately among the service’s supported options.

When no matching exit is available, a request may fail. A service that keeps the requested restriction must wait for a match or return an error. A fallback to a broader selection, if the product offers it, changes the condition being met. A successful connection through another city does not satisfy a requirement for the original city merely because the request completed.

The pool’s advertised total size does not resolve this question. That number may describe addresses across many countries and a period of time. It does not tell a customer how many suitable IPs are online in the required location now, or how many distinct addresses will be supplied during a run.

Availability also depends on the kind of supply. A residential pool may have local exits in a country missing from a provider’s fixed datacenter stock, but the service may charge by traffic and cannot keep a disconnected device online. A fixed ISP product may suit a task requiring a lasting address if the necessary location is available. Neither a network category nor a targeting label creates stock where the provider has none.

The price of a service also depends on more than geographic detail. It may be based on traffic, allocated IPs, or another resource; some products include detailed targeting, while others charge for it. A more detailed dropdown does not establish a universal ranking from cheap country targeting to expensive city targeting.

Random and mixed locations

Labels such as random and mixed describe different arrangements across services. They need to be read together with how the IPs are allocated.

• A location assigned at purchase. The customer receives a fixed proxy in a country chosen by the seller. The initial choice was random; the proxy does not necessarily change countries afterwards.
• A fixed list covering several countries. Each IP has its own location. The application’s choice of an address from that list determines which exit it uses.
• A rotating pool with several allowed countries. New exit selections can come from different countries, subject to the service’s selection and session rules.

A random IP can also be selected within one chosen country. That is compatible with strict country targeting: the address changes, while the country requirement stays the same.

Mixed coverage does not promise an even share of traffic from every country. The result depends on available exits and the selection method. A task comparing several national markets needs a defined selection for each market; a general mixed pool does not by itself produce a balanced comparison.

Keeping the location and keeping the IP

A fixed geographic requirement can survive many IP changes. A rotating service configured for a city can select different addresses that all match that city. Conversely, an allocated static proxy can keep the same address throughout its use. Geographic targeting and address retention are separate choices.

This difference becomes visible during a sequence of related requests. A task that requires the same country may tolerate a replacement exit there. An application that associates a session with one IP may be affected even if the replacement belongs to the same city and network.

A sticky session asks a service to reuse a selected exit for related requests. Its lifetime still depends on the product’s rules and the exit remaining available. If that exit disappears, the service may replace it or return an error. A city filter cannot turn a temporary residential connection into a permanently assigned IP.

The selected location and the website’s decision

The location used to select a proxy and the location used to assess it can come from different sources. A provider may classify its pool with one dataset while a destination site uses another. MaxMind, a widely used supplier of IP geolocation data, is one such source; it is not the only one. The distinction between data suppliers and the checkers that display their results is explained in IP Geolocation Databases & Checkers.

Registration records add another layer. Regional Internet Registries, including RIPE NCC and ARIN, maintain records of IP address resources. Operators can update registration information and publish geographic information about their ranges, but this does not require every geolocation company to adopt the same country or city. The registration record, physical exit, provider’s label, and database estimate can consequently disagree. Proxy Geolocation Mismatch explains how that disagreement develops and why replacing an IP with another from the same range may leave the result unchanged.

Even an exit recognised as being in the intended country cannot determine every regional decision a website makes. Account information, a previously selected region, or location shared by the device may affect the result. The proxy changes the source IP of the connections sent through it; other information can still reach the site. Website Location Detection explains that wider flow of information.

The useful choice is therefore the level that matches the task. Comparing national content can leave the service free to use many exits across a country. Studying local results can justify a city restriction. A network-specific task adds a separate operator requirement, and a long session adds a requirement to retain the address. Each choice asks for a particular property of the proxy service; greater geographic detail alone does not supply the others.