A domain transfer can fail before the current registrar ever receives a valid request, or it can be formally denied after the request is submitted. Those are different problems. A missing authorization code, an account validation issue, a transfer lock, a recent registration, and a documented dispute do not have the same remedy. Start with the exact failure message and the stage at which it appeared.

Transfers between registrars for generic top-level domains (gTLDs) follow a common transfer policy. A country-code extension may follow different registry rules. Do not assume that every rejection is improper or that a transfer code overrides a restriction.

Get the Actual Denial Reason

Check the destination registrar's transfer order and email notices for the exact domain and time of failure. Did its form reject the authorization code before submission, did it wait for your confirmation, or did the current registrar send a denial after a registry transfer request? Save the full message, order number, and status, but keep codes and personal details out of public posts.

Ask both registrars which party stopped the request and for the specific reason. For gTLDs, the current registrar must give the registered name holder and intended destination registrar its reason for denying a transfer on a permitted ground. A vague message such as transfer failed may be insufficient to identify whether the issue is a lock, a missing authorization, or a policy condition. Request the underlying reason in writing.

Verify that the exact domain and intended destination registrar are on the request. A typo, a request for the wrong name, or an old code can cause a failure at the gaining registrar without showing that the current registrar exercised a policy right to deny the transfer.

Check Status Codes and Important Dates

Review the domain's current registration status with the registrar. The status code clientTransferProhibited is set by the registrar, while serverTransferProhibited is set by the registry operator. Either can block a transfer request, but the route to remove it differs. A registrar lock can be an ordinary protection against unauthorized transfers. Ask the current registrar for its authorized unlock method, and do not leave the name unlocked longer than needed.

Compare the creation date, most recent inter-registrar transfer date, and any recent change of registrant. For gTLDs, a registrar may deny a transfer during the first 60 days after registration or a previous transfer between registrars. The latter restriction has exceptions for a return to the original registrar when both registrars agree or a dispute decision requires it.

A change of registrant requires a 60-day lock unless the registrar offered an opt-out and the holder used it before requesting that change. The dates and type of change matter, so ask for the specific rule applied rather than guessing from the age of the website.

Check whether the domain is expired, in redemption, or subject to a hold. Expiration alone does not justify denying a gTLD transfer. A domain registration with the redemptionPeriod status must be restored through its current registrar before it can transfer; a name with pendingDelete cannot transfer through the ordinary process.

The hold codes clientHold and serverHold stop publication of the domain's DNS delegation, which tells the DNS system where to direct queries for that name. They are different from transfer-prohibition codes and can have several causes. Ask the registrar which underlying condition affects the request rather than treating a hold as a single diagnosis.

Confirm Code and Holder Authorization

The transfer authorization code, also called an AuthInfo code, must be valid for the domain. If the destination registrar reports an invalid code, first check the copied text for altered capitalization, missing symbols, or extra spaces and line breaks. Obtain or regenerate the code through your account at the current registrar or its verified support channel if needed, then submit it only through the destination registrar's secure transfer form. Do not send the code in a public support thread.

Check the registered name holder's contact details and the destination registrar's confirmation request. A request may stall if a required confirmation never arrives, is sent to an inaccessible mailbox, or comes from a party without authority. The registered name holder has the authority to approve the transfer. A third party with a copy of the code is not automatically entitled to approve the move.

Be careful about changing registration contacts in the middle of a transfer plan. Changes to the registrant's name, organization, or email address can trigger a change-of-registrant lock. If the holder's contact details need correcting, ask the registrar how the change will affect timing and authorization. Avoid changing unrelated account data simply to make an error message disappear.

Check Payment and Dispute Restrictions

Payment problems can be a valid denial reason, but the registration period matters. For an unexpired gTLD registration, unpaid fees for a previous or current registration period can justify denial; after expiration, the rule concerns an unpaid previous period. A chargeback of a registration payment counts as nonpayment. The current registrar must place the name on Registrar Hold before denying a transfer on this ground.

Evidence of fraud, a reasonable dispute about the holder's identity, or the authorized holder's express objection can also justify denial. Ask which condition the registrar is relying on and what evidence or authorization it needs. Possession of a code does not settle an identity dispute or cancel a holder's objection.

For gTLDs, a registrar must deny a transfer when it has been notified of a pending trademark dispute under the Uniform Domain Name Dispute Resolution Policy or a Uniform Rapid Suspension proceeding or suspension. A qualifying court order, a pending dispute under the Transfer Dispute Resolution Policy, or an imposed change-of-registrant lock with no prior opt-out also requires denial. The notice should identify the actual proceeding or restriction; a generic reference to security does not explain which condition applies.

Resolve the Transfer Issue

When the failure is a removable registrar lock, use the provider's authorized unlock control or request its removal. For gTLDs, the holder must have a reasonable way to remove an ordinary transfer lock. If no self-service unlock is available, the registrar must remove that lock within five calendar days of the holder's initial request, subject to restrictions required by policy or law. If the issue is a registry-level status, ask the registrar to explain what the registry requires; a normal account toggle may not clear it.

For a recent-registration or recent-transfer rule, confirm the relevant date and wait or use a permitted option stated by the registrar. For a missing confirmation, complete the verified holder authorization. For a code error, replace the code and restart the destination process as directed.

For an expired name, ask which current status affects eligibility; renewal is not automatically a prerequisite just because the expiration date has passed. Restore a name in redemption before restarting its transfer.

A mandatory time-based lock must run its course unless a permitted exception applies. A legal or dispute restriction instead requires the resolution specified by the relevant proceeding. A support agent cannot properly remove a lawful restriction simply because the holder wants the transfer to proceed. Keep the written policy explanation and seek appropriate specialist help where a legal order or dispute is involved.

Escalate a Denial That Remains Unclear

Send the current registrar a concise record: domain, transfer order reference, denial text, relevant dates, status codes, and the steps already taken. Ask it to name the policy or registry rule behind the decision and the permitted next action. If a reseller is involved, identify the accredited registrar that handles the request. Keep all responses and avoid including the authorization code unless the provider supplies a secure channel that specifically requires it.

If you believe a gTLD transfer was improperly denied after contacting the registrars, you can submit an ICANN Transfer Complaint. A complaint is an escalation mechanism, not a guarantee that the transfer will be approved. For a country-code domain, check the relevant registry operator's rules and complaint route.