1. Trustname Support
  2. Solution home
  3. Domain Registration, Transfers & Pushes
  4. Domains with Extended Attributes
Open navigation

Understanding Geographic Restrictions for ccTLDs, aka Local Presence Requirement

Two-letter domains like .uk, .de, and .jp are known as country code top-level domains (ccTLDs). These domains correspond to a specific country, territory, or geographic location.


Geographic restrictions for ccTLDs refer to rules set by the country-code top-level domain (ccTLD) registry that limit who can register a domain based on geographic or legal presence in a specific country or territory.


What Do Geographic Restrictions Mean?

Many ccTLDs (like .fr, .de, .ca, or .au) require one or more of the following from the registrant:


  • Residential or business address in the corresponding country
  • Proof of citizenship or residency (e.g. ID, passport)
  • Local business registration or tax ID
  • Local administrative contact or agent

Examples

  • .fr (France): Requires a registrant located within the EU.
  • .ca (Canada): Restricted to Canadian citizens, residents, or businesses.
  • .au (Australia): Must have an Australian Business Number (ABN) or local presence.
  • .jp (Japan): Requires a postal address in Japan.


Why These Rules Exist?

  • To protect national digital identity
  • To ensure compliance with local laws
  • To prevent cybersquatting or misuse by foreign entities
  • In summary, geographic restrictions mean you must have a connection to the country the ccTLD represents — whether through location, nationality, or business presence — to register a domain under that extension.


Each ccTLD has its own registration rules, which are set by the local registry authority. In many cases, registration is restricted to individuals or entities located in the corresponding country. For this reason, additional documentation is often required to prove eligibility.


ccTLDs with Geographic Restrictions

ccTLDCountryRestriction Summary
.auAustraliaMust have an ABN, ACN, or local presence in Australia
.caCanadaRestricted to Canadian citizens, residents, or registered entities
.frFranceMust be based in the EU
.deGermanyRequires local administrative contact within Germany
.jpJapanRequires a Japanese postal address
.itItalyRegistrants must be EU residents or entities
.chSwitzerlandRequires a local administrative contact
.inIndiaSome subdomains (like .gov.in, .ac.in) are restricted to Indian government or academia
.noNorwayMust be a resident or registered organization in Norway
.esSpainRequires a valid Spanish ID (for individuals) or CIF/NIF (for companies)
.usUnited StatesAvailable only to U.S. citizens, residents, or organizations
.ruRussiaMust provide Russian legal/identification information
.krSouth KoreaRequires a Korean business registration or resident ID
.sgSingaporeLocal presence required for certain second-level domains (e.g., .com.sg)
.fiFinlandRegistrants must be based in EU or EEA
.cnChinaRequires Chinese business registration and real-name verification


Local Presence ccTLDs: No Privacy Protection Allowed


Please be aware that many ccTLDs do not support Whois privacy and require you to create a valid contact with accurate personal or business details. Some registries may even send physical mail to verify the address you provide. Ensuring accurate and compliant contact information is essential to avoid suspension or cancellation of your domain.


This is not an exhaustive list. Many other ccTLDs also enforce similar restrictions. Always check the registry’s official documentation or consult your domain provider before attempting to register a ccTLD with possible restrictions.


More detailed information about geographic restrictions and eligibility requirements can be found in the ccTLD supply agreements and registry policies.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article