Security, Abuse & Privacy

Geoblocking

Definition

Geoblocking restricts who can reach content according to where they seem to be. A request arrives, its source IP address is looked up in a geolocation database, and a rule decides whether to serve, redirect or refuse. Country-level accuracy from a maintained database is usually quoted in the high nineties as a percentage; below country it degrades quickly, and regional or city rules are unreliable enough that few people should build on them. The obvious hole is that a VPN or proxy changes the answer in one click, so geoblocking is a way to shape ordinary traffic, not a way to keep a determined visitor out. It also has a legal dimension in the EU, where unjustified geoblocking of customers between member states is restricted by the Geo-blocking Regulation.

Why It Matters

The honest uses are narrow and worth naming. Licensing sometimes ties material to one territory; a launch may be staged country by country; abusive traffic sometimes arrives overwhelmingly from networks you have no business in, and cutting them removes a lot of noise cheaply. Set against that, a country rule is a blunt instrument that catches travellers, expatriates, remote colleagues and anyone whose connection exits somewhere unexpected. If the material genuinely must not be seen by particular people, a country is the wrong test — a password or a per-person link is the right one. Choosing geoblocking for secrecy tends to produce a false sense of safety plus a stream of complaints from the wrong continent.

How It Works

The decision happens at the edge, before any file is read. The source address is matched against a database that maps allocations to countries, giving a two-letter code such as GB or DE, and a rule matches that code to an action: serve normally, send an HTTP 403, or issue a redirect to a local version. On a CDN this usually appears either as a managed setting or as a small piece of logic in an edge function, since the choice must be made per request rather than baked into a file. Worth being plain about the limits of a static host: publishing a file is publishing it, and if the platform offers no country rule then the practical alternatives are password protection, an expiring link, or simply not making the material public. Serving different content by country also needs care with caching, because a cached copy keyed without the country will happily hand one country's page to another.

Real-World Example

A publisher holds UK-only rights to a sample chapter and puts it at chapter-one.99helpers.site for a newsletter. Country rules are not something a plain static host applies on its own, so the workable route on 99helpers is a password-protected link sent to the UK list rather than an open address filtered by country. That keeps the file off search engines and out of general circulation, which is what the rights holder actually cared about. The unrestricted marketing page stays public and is linked from the same email.

Common Mistakes

  • Using a country rule as a security control — a VPN defeats it in seconds and the material was public all along
  • Blocking a whole region to stop abuse from a handful of networks — legitimate customers disappear and nobody notices for weeks
  • Serving country-specific pages from a shared cache without varying on country — visitors get whichever version was cached first

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →