Practical Steps When a Registrar Refuses or Delays an International Transfer

When a registrar refuses or delays an international domain transfer, the situation can become stressful, confusing, and potentially deal-breaking—especially if the transaction involves a high-value domain or strict contractual deadlines. Domain transfers are usually routine processes governed by ICANN policies and registry rules, but international transfers introduce jurisdictional complexity, compliance checks, language barriers, and procedural inconsistencies that can result in unexpected roadblocks. Understanding the practical steps necessary to navigate these obstacles is essential for protecting the integrity of the deal and ensuring that the transfer completes efficiently. These steps require not only technical knowledge but also diplomatic communication, documentation discipline, and the ability to escalate matters through the proper channels when needed.

The first practical step is to identify the precise reason the registrar is refusing or delaying the transfer. All domain extensions follow specific transfer rules, whether under ICANN’s global transfer policy for generic TLDs or under local laws for ccTLDs. A registrar’s refusal often stems from one of several common issues: the domain may be locked at the registry level; the WHOIS contact information might not match the data required for authorization; the buyer or seller may have recently changed registrant details triggering a mandatory ICANN transfer lock; or the domain may be subject to an internal fraud hold, compliance review, or administrative suspension. Some registrars delay transfers simply because they require additional documentation to satisfy internal policies or regulatory requirements. Before assuming the delay is arbitrary, the seller must obtain a clear explanation from the registrar. This involves contacting support, requesting case-specific notes, and asking for explicit clarification. Registrars will sometimes cite generic reasons, but persistent and clear questioning is necessary to uncover the actionable cause.

Once the reason for the delay is understood, the seller must verify whether the registrar’s actions comply with official transfer policies. For generic TLDs, ICANN’s Transfer Policy dictates which conditions allow or prevent a transfer. For example, domains cannot be transferred within 60 days of initial registration or within 60 days of a registrant information change unless the registrar provides an opt-out. Registrars often use this rule incorrectly—even when the registrant change was done through an internal “push” or when the opt-out is supposed to be available. Sellers must review the policy and determine whether the registrar’s justification aligns with ICANN rules. If the registrar is mistakenly applying the policy or misinterpreting it, the seller can cite the exact language of the ICANN policy in their escalation communication. Registrars are far more responsive when confronted with explicit regulatory text rather than general complaints.

Communication is a critical component of resolving transfer delays. Many registrars, especially those operating internationally or employing outsourced support teams, may provide incomplete or inconsistent guidance if contacted through low-level support channels. The seller must escalate the issue to higher-level support teams by explicitly requesting a review by the “compliance team,” “transfer specialist,” or “senior registrar operations staff.” The use of specific internal terminology signals that the requester understands registrar operations and is not making a generic complaint. Writing professional, concise, and technically accurate messages increases the likelihood of prompt and favorable responses. Sellers should provide a clear timeline of events, any relevant screenshots, confirmation emails, and all verification available to demonstrate that they have met transfer requirements.

If the registrar cites fraud prevention as a reason for delay—a common occurrence in international transactions—the seller must provide whatever documentation is necessary to satisfy the registrar’s compliance thresholds. Fraud holds are particularly common when buyers or sellers are from high-risk jurisdictions or when the transaction amount is unusually large. While compliance requests can feel intrusive, registrars are obligated to follow their internal anti-abuse protocols. Sellers may need to provide government identification, proof of domain ownership, or confirmation of intent. Although such verification can be time-consuming, responding thoroughly is often the fastest route to releasing the domain. In some cases, providing a notarized letter or signing a registrar-specified authorization form may be required.

When delays result from issues with the gaining registrar rather than the losing registrar, coordination between both sides becomes necessary. The buyer must contact their registrar to ensure that the transfer request was initiated properly and that the registrar has the domain listed with active status codes and correct authorization (EPP) code entry. Sometimes, gaining registrars impose additional checks on international transfers to protect their customers from scams or unauthorized transfers. The seller should verify that the buyer is following all procedural steps—such as approving the incoming transfer email and confirming any out-of-band verification required by the gaining registrar.

Technical verification is another essential step. Sellers should check the domain’s status codes through WHOIS or RDAP to ensure that the domain is unlocked and that there are no registry-level restrictions such as clientTransferProhibited or serverTransferProhibited. These status codes indicate whether the domain is eligible for transfer at the technical layer. If the domain remains locked despite the seller unlocking it, this may indicate a temporary synchronization delay between the registrar and the registry. In such cases, the seller should ask the registrar to refresh the domain’s registry sync or manually verify the lock status.

In the event that the registrar continues to refuse the transfer without legitimate justification, formal escalation becomes necessary. For ICANN-accredited registrars handling generic TLDs, sellers can file a Transfer Complaint with ICANN. This is not an aggressive action but a procedural safeguard ensuring that the registrar is held accountable to transfer policies. ICANN complaints require providing detailed documentation, including timestamps, emails, screenshots, and any explanations received from the registrar. ICANN typically reviews such complaints within a structured timeframe and contacts the registrar directly to ensure compliance. Registrars generally respond quickly when they receive communication from ICANN because failure to comply may negatively affect their accreditation.

For ccTLDs, escalation must be directed toward the registry rather than ICANN. Each ccTLD registry has its own dispute and escalation procedures. Sellers must contact the registry’s support team—often accessible only through accredited registrars or through regional registry liaison channels. The registry can verify whether the registrar’s refusal is valid under local policies. If the registrar is misapplying the rules, the registry may intervene directly or instruct the registrar to proceed with the transfer. Registries tend to take their oversight role seriously because inconsistent registrar behavior undermines confidence in the extension.

Another practical step involves restructuring the transaction temporarily to accommodate the registrar’s limitations without abandoning the deal. For example, if a registrar imposes a 60-day lock due to a recent registrant update, the seller can internally push the domain to the buyer within the same registrar instead of transferring between registrars. An internal push—where allowed—avoids ICANN transfer restrictions because the domain never changes registrars. This method requires both parties to agree to postpone the transfer-out, but it successfully transfers control and ownership immediately. When dealing with a buyer from a country where certain registrars are better supported, choosing a registrar known for smooth international processes can also simplify future transfers.

In extreme cases where the registrar behaves in bad faith—refusing a transfer with no policy basis, ignoring communication, or imposing unjustified obstacles—the seller may need to relocate their entire domain portfolio or move the domain before the sale to a registrar with a better reputation. This is more effective before completing a transaction than during one, but in some cases, the seller may have enough time before the transaction deadline to transfer the domain to a more cooperative registrar and then complete the sale from that new provider. This requires navigating the ICANN 60-day rules, but if the domain has not recently undergone a registrant change, it remains viable.

Documentation remains essential throughout this process. Keeping a detailed record of all communication, support responses, screenshots of registrar settings, and timestamps is not only valuable for escalation but also protects the seller in case disputes arise later. In the worst-case scenario, comprehensive documentation can support legal claims or arbitration decisions if the registrar’s misconduct leads to financial harm or a failed transaction.

Ultimately, practical steps for navigating registrar refusal or delay require a blend of technical verification, regulatory knowledge, clear communication, firm escalation, creative structuring, and strategic patience. Domain transfers are governed by a combination of global rules, local regulations, and internal registrar policies—and international transfers bring additional layers of scrutiny. By approaching delays methodically, understanding the rules deeply, and using the right escalation channels at the right time, sellers can overcome even the most frustrating registrar obstacles and ensure that their domain transaction moves forward smoothly and securely.

When a registrar refuses or delays an international domain transfer, the situation can become stressful, confusing, and potentially deal-breaking—especially if the transaction involves a high-value domain or strict contractual deadlines. Domain transfers are usually routine processes governed by ICANN policies and registry rules, but international transfers introduce jurisdictional complexity, compliance checks, language barriers, and procedural…