Geographic TLDs (geoTLDs) are generic extensions that name a city or region — such as .nyc, .london, .tokyo, .berlin, .paris and .miami — usually backed by the local authority and often requiring a local connection to register. They came mostly from ICANN's 2012 new-gTLD program and differ from country codes by being city- or region-specific. They signal local identity strongly, but the extension itself is not a ranking factor.
What makes a TLD "geographic"
A geographic TLD names a place smaller than a country — a city (.nyc, .london, .tokyo), a region (.bzh for Brittany, .scot for Scotland) or a broad community (.eus for the Basque community). Technically these are generic TLDs created in ICANN's 2012 expansion, but their value is local identity: a .nyc address says "we are part of New York City" in a way a generic .com cannot. Because cities are involved, many geoTLDs were applied for by, or with the backing of, the local government, and several impose a local-presence requirement so the namespace genuinely represents the place. They are distinct from country codes, which represent whole nations.
Geographic TLDs reference list
A selection of city and region extensions, the place they represent and typical eligibility. Many require a local connection — verify per registry.
| Extension | Place | Type | Typical eligibility |
|---|---|---|---|
| .nyc | New York City, USA | City | Local presence in NYC required |
| .london | London, UK | City | Open, with London focus |
| .berlin | Berlin, Germany | City | Local connection expected |
| .tokyo | Tokyo, Japan | City | Open |
| .paris | Paris, France | City | Local connection / Paris focus |
| .miami | Miami, USA | City | Open |
| .amsterdam | Amsterdam, Netherlands | City | Local connection expected |
| .barcelona | Barcelona, Spain | City | Local connection expected |
| .vegas | Las Vegas, USA | City | Open |
| .scot | Scotland | Region / community | Scottish connection / affinity |
| .bzh | Brittany, France | Region | Breton connection / affinity |
| .eus | Basque community | Community | Basque language / community affinity |
Eligibility reflects typical registry policy and can change; confirm via the registry before registering. All are generic TLDs delegated through ICANN — see the IANA root zone database.
When a geoTLD is the right choice
A geographic extension is a strong fit when your audience is genuinely local and that locality is part of your brand — a New York restaurant on .nyc, a London agency on .london, a Berlin startup on .berlin. The extension does three things well: it signals locality at a glance, it keeps short, memorable names available (the geoTLD namespaces are far less crowded than .com), and it aligns you with civic identity. The trade-offs are reach and eligibility — a geoTLD frames you as local, which is a feature for a neighbourhood business and a limitation for a global one, and several require you to prove a local connection. As always, the extension does not change your ranking; choose it for identity, not SEO.