Not every country domain (ccTLD) is as straightforward to sell as it looks.
Some require local presence. Some require the registrant to meet specific eligibility criteria. Others require documentation that neither you nor your client anticipated. How much of that complexity lands on you depends entirely on the registrar you work with.
For resellers helping clients expand into new markets, the ability to deliver the right country domain is often what opens the door to a broader relationship. Getting it wrong – promising a domain you can’t register, or discovering a restriction mid-sale – damages trust before it has had a chance to build.
This guide walks through the main ccTLD restriction types, what they mean in practice, and the considerations that determine whether a given country domain belongs in your portfolio.
This guide is updated to May 2026 and includes expert advice from business professionals in the domain industry with 20+ years of experience; it is not intended as a substitute of national entities and registry authorities of the countries it refers to, or other regulatory institutions.
The client conversations where ccTLDs win you the relationship
Defaulting to .com when a country domain would serve the client better is one of the most common missed opportunities in domain sales.
A ccTLD is the right recommendation when:
- The business operates primarily in a specific country or region
- Local SEO matters – ccTLDs send strong geographic signals to search engines and can significantly improve visibility in targeted markets
- Trust and credibility are critical – legal, finance, and healthcare businesses benefit from the legitimacy a local domain conveys
- The client needs to demonstrate compliance with local digital regulations such as GDPR or NIS2
A practical example: a Spain-based e-commerce store expanding into Portugal would benefit from registering a .pt domain to signal regional presence and improve local search rankings – even if their primary site runs on .es or .com.
Resellers who explain the strategic value of a ccTLD – local SEO, trust, compliance – are having a different conversation than those who just quote prices. And that conversation positions them to attach SSL, email, DNS, and security on top of the domain registration.
Before those conversations can happen, though, you need to understand what you can actually deliver.
Why your registrar choice determines which markets you can serve
Every ccTLD is managed by a national registry authority. DENIC runs .de. AFNIC runs .fr. auDA runs .au. CIRA runs .ca. Each registry sets its own eligibility rules independently of ICANN’s accreditation framework.
Being accredited with a registrar gives you access to that registrar’s TLD catalog. It does not automatically satisfy the underlying registry’s eligibility requirements. The registrar you work with determines whether those requirements are handled on your behalf or handed back to you – often mid-sale, often with a client waiting.
Restrictions fall into two broad categories: registrant eligibility (who can hold the domain) and operational requirements (what administrative contact or local presence the registry demands).
Understanding the difference before you promise a domain to a client is what protects the relationship.
The restriction types that block most reseller sales
- Local presence or domicile address: some registries require the registrant to hold a physical address within the registry’s jurisdiction at the time of registration. In some cases this must be within the country itself. In others, an address anywhere in the EU or EEA satisfies the requirement. A trustee service – also referred to as local presence or domicile address – provides that compliant address on behalf of the registrant.
- Registrant eligibility criteria: some registries require the registrant to meet specific conditions beyond address. .ca is a good example: eligible registrants include Canadian citizens, permanent residents, corporations registered in Canada, and trademark holders, among other categories. Other ccTLDs require a local tax identification number or a registered business entity in-country. These requirements need either a qualifying registrant or a trustee holding the domain on their behalf.
- Admin-C requirements: certain registries require a valid administrative contact with a local address on record. The registrant may not need to be local, but the admin-c must reflect a verifiable local contact – a common sticking point when registering European ccTLDs for international clients.
- Open registration with verification: a growing number of ccTLDs with no formal local requirements are introducing registrant verification under NIS2 compliance obligations. This does not restrict who can register, but requires contact data to be accurate and verifiable – with operational implications for high-volume portfolios.
Each restriction type has a different resolution path, and whether your registrar can resolve it for you is the question that determines what you can sell.
Open ccTLDs: the straightforward part of your portfolio
Some high-value ccTLDs carry no meaningful local presence requirement and are straightforward to offer regardless of where your clients are based.
Several European ccTLDs – like .co.uk and .nl among the most commercially significant – are open to registrants worldwide. Others, such as .eu and .es, are open to EEA-based registrants, which covers most European clients but is worth clarifying for those based outside Europe. Some ccTLDs with geographic origins have become globally adopted, making them clean additions to any catalog without restriction considerations.
The open ccTLDs are the easiest wins. The restricted ones are where the commercial differentiation sits – because they’re the domains most resellers struggle to deliver.
How trustee services expand what you can sell
A trustee service satisfies a registry’s local presence requirement by providing a physical address within the registry’s jurisdiction on behalf of the registrant. The registrant retains beneficial ownership, while the trustee provides the compliant local address the registry demands.
The practical question for resellers is straightforward: does your registrar have trustee infrastructure in place, or does the requirement come back to you?
If the registrar handles it, you can offer restricted ccTLDs to clients regardless of where they are based. If not, that complexity lands on you or your client at a point when the relationship is still forming.
Openprovider handles trustee and local presence requirements for many restricted ccTLDs within its catalog. The process is managed on Openprovider’s side – as a reseller, the main requirement is agreeing to the Domicile Terms.
For API-based resellers, trustee configuration also needs to be set up within your own systems. As registry policies change, the TLDs covered by trustee arrangements can shift, so checking current coverage before committing to a registration is always the right approach.
What to evaluate before adding a restricted ccTLD to your portfolio
- Who handles the trustee requirement? If it falls to you, you’re absorbing legal and operational responsibility outside your core service. If the registrar handles it, your role is configuration and client communication.
- Is the process built in or bolted on? Trustee arrangements requiring per-domain manual handling add friction at every registration and renewal. At portfolio scale, that overhead compounds.
- What are the renewal economics? Restricted ccTLDs often carry higher costs. Understand the pricing structure and whether it’s stable year-on-year before building it into your client offering.
- What does the client need to provide? Some registries require specific documentation from the registrant even where the registrar handles local presence. Know what’s required before you commit.
- What are the transfer policies? Transfer support varies significantly across restricted ccTLDs. If a client wants to consolidate existing domains under your management, transfer eligibility is worth checking before it becomes part of your onboarding promise.
The ccTLD mistakes that cost resellers clients and revenue
- Always defaulting to .com ignores local SEO opportunities and leaves clients underserved in markets where a country domain carries more weight.
- Not explaining trust implications means missing a meaningful conversation. In legal, finance, and healthcare sectors, a local domain signals legitimate local presence to an audience that expects it.
- Recommending on price alone creates relationships built on cost, not value. A client who later decides to rebrand will often do so with a different provider.
Pro tip: before suggesting a domain, review what the client is actually trying to achieve. A few questions about their target market and growth plans turns a commodity transaction into a consultative one.
NIS2: the compliance shift that’s changing ccTLD operations across Europe
Since October 2024, the EU’s NIS2 Directive has introduced new registrant verification requirements across European ccTLD registries. Registrars must now verify at least one means of contact per registrant, and registries are progressively rolling out email and phone verification as a result.
For resellers, two things matter. First, accurate registrant data is now a compliance requirement. Placeholder or incomplete contact data at registration creates risk for both the registrar and the reseller. Second, the rollout is uneven – implementation varies by registry and member state, and full adoption across EU ccTLDs is still developing.
Resellers with large European portfolios should expect verification to become standard across all EU registries over the coming 12-18 months.
Openprovider tracks NIS2 implementation across affected registries and publishes updates ahead of changes that affect registration and renewal workflows.
WHMCS resellers: what to configure before you scale your ccTLD offering
Expanding into new ccTLDs raises specific automation questions for WHMCS-based operations. Not every TLD is automatically configured in a WHMCS module, and restricted ccTLDs often require additional fields for trustee or domicile requirements.
Before adding a new ccTLD to your catalog, review whether additional registration fields are needed, whether trustee terms need to be agreed to at the registrar level, and whether NIS2 verification requirements affect how registrant data needs to be collected.
The Openprovider WHMCS module documentation and per-TLD knowledge base articles cover the configuration specifics.
Conclusion
ccTLD restrictions are a portfolio opportunity as much as a compliance consideration.
The instinct when a client asks for a complex country domain is often to steer them toward something simpler. That instinct costs resellers revenue.
The domains that carry the most requirements are the ones most resellers struggle to deliver – which means every restricted ccTLD request is a chance to differentiate. The right registrar removes the complexity that would otherwise turn that request into a referral elsewhere.
Openprovider gives resellers instant access to 2,000+ TLDs on one platform, including the restricted ccTLDs that most registrars either can’t offer or pass back to the reseller to manage.
Openprovider Membership goes further, giving you access to domain registrations, renewals, and transfers at cost price. That means higher margins on every domain you sell, and more competitive pricing for your clients – without compromising what you can offer them.
Many clients entering new markets will need a country domain. The reseller who delivers it is the one positioned to build the relationship that follows – and every service attached on top of that domain makes it harder to replace.Create your free Openprovider account today – no credit card required.
