A transfer workflow that works reliably for .com or .net domains cannot necessarily be applied unchanged to a ccTLD. The registry rules may differ, the authorization mechanism may use different terminology or procedures, and a rejection that looks like an API error may require operational review rather than a code change. For teams building domain registration or management features on a registrar API, knowing that distinction from the first line of integration code can save significant debugging time.
The name.com API supports domain operations across a wide range of TLDs, with infrastructure that already accounts for the transfer complexity described here. This guide maps where ccTLD transfer policies diverge from the gTLD baseline, covers the authorization mechanisms and eligibility requirements you'll encounter by TLD, and gives you a practical framework for diagnosing transfer failures before you debug the wrong layer.
By the end, you'll be able to distinguish a programmatic problem you can fix in your integration from an operational issue that requires registrar, registry, or other support.
Lock periods that don't follow the standard
The 60-day transfer restrictions in ICANN's Transfer Policy are not a universal rule for all TLDs. The policy applies to gTLDs, while each ccTLD manager establishes its own transfer rules, and those rules can look quite different from what your transfer code assumes. They can differ in how they handle transfer eligibility, authorization, waiting periods, and other restrictions.
ccTLD | Registry | Transfer Restriction / Lock Behavior |
|---|---|---|
| The current legacy process uses Nominet’s IPS tag system. Nominet has announced a transition to its standardized transfer process, including Secure Transfer Authorisation Codes (TACs), scheduled for 9 February 2027. | |
| Uses an AuthInfo procedure for provider transfers. The domain holder can change providers at any time, and a matching AuthInfo results in an immediate transfer. | |
| A domain cannot be transferred if it was registered or transferred within the previous 60 days. CIRA also requires domains to remain eligible under its Canadian Presence Requirements and may conduct Registrant Information Validation. | |
| A domain cannot be transferred if it has been registered for less than 60 days or will expire in less than 15 days, among other restrictions. CNNIC’s rules also require the registrar to verify the domain holder’s identity and willingness before issuing a transfer code. | |
| Transfers use an authorization code. Suspended domains generally cannot be transferred, and special procedures apply to domains that are blocked, reserved, under dispute, or otherwise locked. |
Some ccTLDs have no equivalent to the standard gTLD transfer restriction at all. Others impose restrictions tied to domain age, registrant changes, eligibility requirements, or other registry-specific conditions. The table below maps representative examples to what actually governs transfer timing.
TLD-specific transfer mechanisms
ccTLD registries can implement transfer workflows differently from the standard gTLD model. Some still use authorization codes, but the terminology, source of the code, and surrounding registrar procedures can vary by TLD.
.uk and Nominet's transfer model - Currently, .uk domains, including .co.uk, .org.uk, and other second-level domains, remain on Nominet's legacy registry platform, where inter-registrar transfers use the IPS tag system. Nominet is scheduled to transition .uk to its new registry platform on 9 February 2027. Under the future system, transfers will use Secure Transfer Authorisation Codes (TACs), which are valid for 14 days. The current and future transfer processes therefore use different mechanisms and registrar procedures.
.de and DENIC - DENIC uses an AuthInfo procedure for provider transfers. The domain holder obtains an AuthInfo from the current provider and provides it to the new provider, which submits the provider-change request to DENIC. If the AuthInfo matches, the transfer is completed immediately. DENIC also has technical requirements for .de nameserver configuration, but these should not be confused with the authorization mechanism for the provider transfer.
.eu and EURid - .eu transfers also use an authorization code, but the code can be obtained through several channels. The registrant can request it from the current registrar, generate one through the My .eu platform, or request an emergency code directly from EURid if the other options are unavailable. This means that the code is not necessarily something the losing registrar alone must generate.
For an API-driven transfer workflow, these differences affect the design before a transfer request is submitted. If a TLD requires registrar-specific actions or provides multiple ways to obtain authorization, the application needs to account for those requirements or confirm that the registrar's API and support infrastructure handle them.
Registrant eligibility and TLD-specific requirements
Some ccTLDs tie domain eligibility to national presence, citizenship, residency, legal status, or other criteria. These requirements can affect transfers, particularly when the transfer involves a change of registrant or when the registry requires eligibility to be maintained. The exact requirements and when they are checked vary by TLD.
.ca and CIRA - CIRA's Canadian Presence Requirements (CPR) define the categories of individuals and organizations eligible to hold .ca domains. These include Canadian citizens and permanent residents, qualifying Canadian organizations and institutions, and certain trademark and government entities. CIRA also conducts Registrant Information Validation (RIV), and domains subject to an RIV review can be locked against transfer while the review is underway. Developers should therefore distinguish the general eligibility requirements from specific transfer restrictions and validation procedures.
.eu and EURid - EURid's eligibility rules cover EU/EEA citizens and residents and organizations established in the EU/EEA, with specific provisions applying to different categories of registrants. A transfer can be affected if the resulting registration does not satisfy the applicable eligibility requirements.
The implication for developers is straightforward: a transfer can have valid authorization credentials and still encounter a TLD-specific eligibility or validation issue. Before building a transfer flow for a ccTLD with eligibility requirements, verify the current registry policy and determine which requirements are relevant to the transfer scenario.
Diagnosing transfer failures: programmatic vs. operational
When a ccTLD transfer fails or stalls, the first question to answer is where the problem sits. Two broad categories require different responses.
Programmatic or registrar-workflow issues are problems your application or registrar can potentially detect and correct without registry-level intervention:
- The authorization code is incorrect, invalid, or otherwise unusable
- The domain is subject to a registrar-level transfer lock
- The domain is within a TLD-specific transfer restriction or waiting period
- Required information for the transfer is missing or invalid
- The transfer request does not meet the TLD's procedural requirements
Operational or registry-side issues require action outside the application and may involve registrar support, documentation, validation, or registry intervention:
- A TLD-specific eligibility or validation requirement has not been satisfied
- The domain is subject to a registry-level hold or restriction
- A TLD requires documentation or identity verification that cannot be completed through the normal transfer request
- The transfer requires a registrar-specific or registry-specific procedure that the standard workflow does not cover
The decision tree below provides a practical way to triage a failed transfer: check the request and domain state first, identify any TLD-specific restriction or requirement, and then determine whether the issue can be resolved through the application or registrar workflow or requires operational support.
The important distinction is that a problem requiring human intervention does not necessarily mean contacting the registry directly. The registrar or API provider is generally the appropriate first point of contact and can determine whether registry involvement is required. Similarly, an API error does not always identify the underlying policy issue, so developers may need to combine the API response with the domain's current state and the relevant TLD's transfer rules.
Pre-transfer checklist for ccTLD transfers
Treat this as a pre-flight check, not a universal requirement list. Requirements vary by TLD, so cross-reference each item against the relevant registry policy before initiating a transfer.
Confirm the TLD's transfer mechanism - Does the TLD use an authorization code, a registry-specific code, or a tag-change process? Does the authorization need to be requested through the registrar rather than generated by the registrant directly?
Check for transfer restrictions or waiting periods - Is the domain subject to a TLD-defined restriction? Has it been registered, transferred, or has its registrant information changed recently?
Confirm registrant eligibility where applicable - Does the gaining registrant meet any local-presence, citizenship, organizational, or other eligibility requirements that apply to the TLD or transfer scenario?
Verify required registrant and contact information - Is the information current and complete, and does the TLD or registrar require any additional information or validation for the transfer?
Check for TLD-specific holds, restrictions, or documentation requirements - Does the domain have a registry-level restriction, or does the transfer require identity verification, documentation, or another TLD-specific procedure?
Confirm both registrars support the transfer workflow - Are the gaining and losing registrars able to handle the relevant ccTLD and its required transfer procedure? Not every registrar supports every ccTLD.
For any ccTLD where a specific transfer step is unclear, check the registry's current policy documentation rather than inferring from gTLD behavior.
Frequently asked questions
What is a ccTLD transfer?
A ccTLD transfer moves a country-code domain, such as .uk, .de, or .ca, from one registrar to another. The process is governed by the relevant ccTLD manager and its policies rather than ICANN’s gTLD Transfer Policy, so authorization methods, restrictions, eligibility requirements, and procedures vary by TLD.
Do all ccTLDs require an EPP auth code to transfer?
No. ccTLDs use different authorization mechanisms and transfer procedures. For example, .de uses an AuthInfo procedure, while .uk currently uses Nominet’s IPS tag system and is scheduled to move to Secure Transfer Authorisation Codes (TACs) in February 2027. Before implementing a transfer workflow, check which mechanism applies to the specific TLD.
Why was my ccTLD transfer rejected?
A transfer can fail because of an authorization problem, registrar-level lock, TLD-specific restriction, missing information, eligibility requirement, or another registry-specific procedure. Check the domain’s current status and the TLD’s transfer requirements first, then contact the registrar or API provider if the cause is not apparent.
How long does a ccTLD transfer take?
There is no universal ccTLD transfer timeline. Some transfers can complete immediately once the required authorization is accepted, while others involve waiting periods, additional validation, or registrar-specific procedures. Check the relevant registry’s current transfer policy rather than applying the standard gTLD timeline.
Building ccTLD transfers into your integration
ccTLD transfers require you to account for rules that don't necessarily exist in the standard gTLD transfer workflow. Authorization mechanisms, transfer restrictions, eligibility requirements, and operational procedures can all vary by TLD. The key is to identify those differences before treating a failed transfer as an application problem.
Before implementing or troubleshooting a ccTLD transfer, check the registry's current policy and confirm how your registrar or API provider handles the required workflow. If a transfer fails, use the framework in this guide to determine whether the issue is in your application, the registrar workflow, or a TLD-specific operational process before escalating.
Summary
A ccTLD transfer doesn’t follow the gTLD rules your code expects. Compare lock periods, authorization mechanisms, and eligibility requirements across .uk, .de, .ca, .au, and .eu, then use a triage framework to separate integration bugs from registry issues before you debug the wrong layer.
name.com supports domain operations across a wide range of TLDs. We also provide API partners with registrar infrastructure and support for domain-management workflows. To explore our API, visit the name.com API documentation.
