Geo-blocking is when a website limits or changes what it serves according to the visitor's country. The site reads the country from the visitor's IP address, by looking it up in a geolocation database, and then refuses the request, redirects it to another country's site, or serves a local version of the page.
This post explains the three forms, how a site decides which country you are in, and how to check what country any IP address is seen in. The examples are real: on 20 November 2026 we sent requests through QuanticData residential exits in four countries and recorded what came back.
What geo-blocking is: three forms
| Form | What the visitor gets | Typical sign |
|---|---|---|
| Block | No content | Status 451 or 403, or a page saying the service is not available in your country or region |
| Redirect | Another country's site | Status 301 or 302 to a country path or domain, such as /de/ |
| Local version | The same URL with different content | Another language, currency, price, catalogue or set of ads, with status 200 |
Only the first is a block in the strict sense, but all three come from the same decision, and the third is easy to miss, because nothing looks blocked. Status 451, "Unavailable For Legal Reasons", exists for the first case.
Sites do this for ordinary reasons:
- Licences. Films, music and sport are licensed country by country, so a catalogue differs by market.
- Law. Some services may only be offered where they are authorised, and some publishers withhold pages where a local law would apply to them.
- Markets. Prices, taxes, currencies, shipping and stock are set per country, so a shop shows each visitor its own market.
- Language. A visitor from Japan most likely wants the Japanese page.
- Security. A site with no customers in a region may refuse traffic from it.
In the European Union one kind of geo-blocking is regulated. Regulation (EU) 2018/302, in application since 3 December 2018, prohibits unjustified geo-blocking between EU customers in three situations: the sale of goods without physical delivery, the sale of electronically supplied services, and the sale of services provided in a specific physical location. Audiovisual services and transport are outside its scope, and its rule on electronic services does not cover copyright-protected content such as music, e-books and games, which is why streaming catalogues still differ between member states.
How a site decides your country
The main input is the IP address of the request. Addresses are allocated in blocks to network operators, and geolocation databases map each block to a country, a region, a city and a network. The lookup is fast and usually happens before the page is built, often at the content delivery network. Cloudflare, for example, can pass the visitor's country to the site with every request, and it shows what it sees on a public diagnostic page of its own site:
$ curl -s https://www.cloudflare.com/cdn-cgi/trace
...
ip=x.x.x.x
...
loc=DE
...
The loc line is the two-letter country that the edge server assigned to the address. A site behind such a network can write a rule on that value in one line: block it, redirect it, or pick a price list.
Three things are worth knowing about the databases:
- There are several, and each site uses its own. They are built from registry records, location lists that networks publish, measurements and corrections, in different proportions and on different update days.
- They agree on the country far more often than on the city. City data is an estimate, especially for mobile ranges that serve a whole region.
- They can disagree on a range that moved recently, or that is registered in one country and used in another. Then one site shows one country and another site shows the other, for the same address.
Our comparison of IP checkers compared goes through the databases one by one. Sites can also read other signals next to the address: the language your browser asks for, the country of your account or payment card, and, on phones, the location the app is allowed to use. Those are separate from the IP lookup, and a service with a strict reason to know where you are will compare them.
How to check what country an IP is seen in
There are two quick ways, and they answer slightly different questions.
In several databases at once. Paste an IP address, or a whole proxy line, into our proxy location checker. It shows the country, region, city and network that ipinfo.io and six more databases give for that address, side by side, each with a link to verify it. For a proxy, our server opens one connection through it and reads the exit address first. This is the check to run when one site shows a country you did not expect: the table shows which databases say what.
From the command line. Ask a lookup service through the connection you want to test. With a proxy, the answer describes the exit, which is the address websites see:
$ curl -s -x "http://PROXY_HOST:PORT" -U "USER-country-de:PASS" https://ipinfo.io/json
{
"ip": "x.x.x.x",
"country": "DE",
...
}
The page on how to check a proxy IP reads the other fields of that record. For the country as a content delivery network sees it, request the trace page shown above through the same connection.
Our test: four countries, 28 of 28 database answers
On 20 November 2026 we opened one session in each of four countries on the QuanticData Residential Basic network, by putting the country in the proxy username: USER-country-us, -de, -jp and -br. Through each one we requested the Cloudflare trace page and ipinfo.io, then pasted the exit address into the location checker, which asked seven databases.
| Country asked | CDN edge (loc) | ipinfo.io | Databases with that country | Cities named |
|---|---|---|---|---|
| United States | US | US | 7 of 7 | 3 |
| Germany | DE | DE | 7 of 7 | 4 |
| Japan | JP | JP | 7 of 7 | 3 |
| Brazil | BR | BR | 7 of 7 | 3 |
The country was the one we asked for in 4 of 4 readings at the CDN edge, and in 28 of 28 database answers, a separate run from the one on the tool page. The cities differed between databases for every exit, three or four names each (four for Germany), which is the pattern described above: rely on the country, treat the city as an estimate. The exit addresses are not published, because they belong to the residential connections that carried the test.
The same URL from four countries
With the country settled, we requested two public home pages through an exit in each of the four countries, with plain curl and without following redirects, and recorded the first response; the tables show google.com for all four and nike.com for three of them (United States, Germany, Japan).
| Exit country | google.com: language of the page |
|---|---|
| United States | en |
| Germany | de |
| Japan | ja |
| Brazil | pt-BR |
| Exit country | nike.com: first response |
|---|---|
| United States | 200, the English page (en-US) |
| Germany | 302 to /de/ |
| Japan | 302 to /jp/ |
One URL, four countries, four languages on the first site: the local-version form. On the second site, two of the three countries shown were sent to their own country path: the redirect form. Nothing was blocked, and nothing needed a login. This is what most geo-targeting on the public web looks like, and it is why a price, a search result or an advertisement checked from one country says little about another. We measured the size of the effect on 53 sites by exit country in an earlier post.
Country targeting on QuanticData proxies
A proxy with country targeting is the tool for seeing public pages as a local visitor sees them. The request leaves from an address in the country you name, so the site's own lookup returns that country and serves that market's page.
- On QuanticData residential proxies the country is a flag in the username, as in
USER-country-de, across 228 countries and territories. It is a request parameter, not a paid add-on, and state, city and network targeting use the same mechanism. - mobile proxies are targeted by country, region and city too, on 4G and 5G carrier addresses.
- The full list of markets is on the proxy locations page.
The jobs this serves are the ones where the public page is the data:
- price monitoring: the price, currency and stock a shop shows in each market.
- search result tracking: where a page ranks for a visitor in a given country or city. If you only need the results and not the browsing, the SERP API takes
countryandlocationas parameters and returns the results page as JSON. - ad verification: whether an advertisement and its landing page appear as booked in each country.
- Testing your own site: checking that your redirects, price lists and consent banners behave as intended in each market.
Before a run, paste one line into the proxy location checker to confirm the country your exits are seen in, as we did above.
Where geo-blocking is a line to respect
The examples in this post are public pages that any visitor in that country can open. That is different from a service that restricts access by country because a licence or a law requires it: streaming catalogues, betting, regulated financial services. There the block is the service keeping its obligations, and a proxy is not a way round it. Our terms do not allow that use, and a service with a strict reason checks more than the IP address anyway.
The useful question is simple: is this page offered to the public in that country? If yes, viewing it from an address in that country is market research. If the page is offered only to licensed or authorised users in that country, it is not yours to collect from anywhere.


