Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Domain transfer fails: status clientTransferProhibited, the domain is locked

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A transfer that the registry rejects because the domain is locked is often the status clientTransferProhibited. ICANN's EPP status page says this code "tells your domain's registry to reject requests to transfer the domain from your current registrar to another", and that the status "will help prevent unauthorized transfers resulting from hijacking and/or fraud". The same page says client codes are set by the registrar. Server codes are set by the registry and "take precedence over client codes".

Removing the client lock is a registrar action. It does not remove serverTransferProhibited, a court order, or a 60-day transfer lock. Check which status is actually set before you unlock anything.

What the status means

The Transfer Policy, updated 21 February 2024, section 5.1 says registrars may set clientTransferProhibited "upon registration or subsequent request by the Registered Name Holder", with the terms in the registration agreement and the holder's express consent. If the registrar does not provide a facility for the holder to remove it, the registrar must remove the "ClientTransferProhibited" status within five (5) calendar days of the holder's initial request.

Section 3.9 lists instances when a requested change of registrar may not be denied. Section 3.9.3 is "Domain name in Registrar Lock Status, unless the Registered Name Holder is provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request." So a lock alone is not a ground for denial when the holder has not been given that opportunity and ability.

Other denials are separate. Section 3.7.5 allows a denial in the first 60 days after creation. Section 3.7.6 allows a denial for 60 days after an inter-registrar transfer. Section 3.8.5 requires a denial when the registrar imposed a 60-day lock after a Change of Registrant and the holder did not opt out. Unlocking clientTransferProhibited does not lift those. The Policy's notes add that a registrar may apply clientTransferProhibited for the 60-day lock after a Change of Registrant, and then it must lock the name in a way that prohibits the holder from removing the lock. Section 3.8 also requires denial for a pending UDRP, a court order, a pending transfer dispute, or a URS proceeding.

serverTransferProhibited is the registry's lock. The EPP page says removing it "can take longer than it does for clientTransferProhibited because your registrar has to forward your request to your domain's registry and wait for them to lift the restriction."

Likely causes

Cause What you see How to confirm
The registrar set clientTransferProhibited The gaining registrar says the domain is locked; Whois shows that status Whois or RDDS, as below
You removed the client lock, and a 60-day lock remains The status you cleared is gone, and the transfer is still denied Compare the denial with sections 3.7.5, 3.7.6 and 3.8.5
The registry set serverTransferProhibited That server status is present The EPP page: you contact the registrar, who works with the Registry Operator
The name is in the Redemption Grace Period Transfer is prohibited by the registry, not by a client lock (Expired Registration Recovery Policy section 3.2) redemptionPeriod in the directory result

Prove the cause before changing anything

The EPP status page says you find the codes "by running a Whois lookup, which you can do by visiting http://www.internic.net/whois.html or your registrar's website", and that the codes "will be included in the search results".

Save the full result, including every status, into a dated note such as whois-example.com-2026-11-22.txt. Do this from the registrar's lookup or the InterNIC page the EPP status page names. Write down the denial text from the gaining registrar beside it.

Proceed to unlock only if the result contains clientTransferProhibited and you are the Registered Name Holder. If the result contains serverTransferProhibited, a redemption status, or you are inside a 60-day window the policy lists, removing the client status will not complete the transfer by itself.

Fix

Before you ask for the change, save the status list as it stands now, in a file of its own, for example from a command line lookup or by copying the registrar's lookup page into it.

whois example.com > /root/whois-before-unlock-example.com-2026-11-22.txt

Risk: Removing clientTransferProhibited tells the registry to stop rejecting transfers of this domain. A person who also has the AuthInfo code can ask a gaining registrar to submit a transfer. The domain can leave the current registrar. The EPP page says the status will help prevent unauthorized transfers.

If the registrar's screen has a control that removes clientTransferProhibited for this domain, use that control, for this domain only. If it does not, ask the registrar of record in writing to remove clientTransferProhibited. Section 5.1 requires removal within five calendar days of that initial request when no such facility exists. Section 5.3 says the method must not be more restrictive than the method used to change contact or nameserver details. Section 5.4 says the registrar must not refuse solely because of a payment dispute between you and the registrar.

serverTransferProhibited is a different status. The EPP page says that for it you must first contact your registrar and request that they work with the Registry Operator to remove the code.

To undo it: if /root/whois-before-unlock-example.com-2026-11-22.txt lists clientTransferProhibited, ask the registrar to set it again, or use the same facility to turn the lock back on. If the saved list did not show it, there is nothing to set back. Section 5.1 allows the registrar to set the status on the Registered Name Holder's request. Afterwards, run the same Whois or RDDS lookup and confirm the status is present before you treat the domain as locked.

Confirm the fix

  1. A fresh Whois or RDDS lookup no longer lists clientTransferProhibited.
  2. The lookup does not show a different blocking status that you still need to deal with.
  3. The gaining registrar accepts the transfer request. You still need a valid AuthInfo code; a lock and a code are separate checks.
  4. After the transfer, the lock is on again if you still want it.

What to watch afterwards

  • A 60-day creation, transfer, or Change of Registrant lock is a different denial. Read the reason the registrar of record is required to give under section 3.7.
  • serverTransferProhibited stays until the registry removes it.
  • Put the client lock back after a transfer you intended, unless you want the name left open.
  • Redemption is not a lock you clear. Section 3.2 of the Expired Registration Recovery Policy says: "During the Redemption Grace Period, the registry must disable DNS resolution and prohibit attempted transfers of the registration."

Risks and limits

  • The policy's five days apply when the registrar does not offer a facility. A panel that you can operate yourself is the facility section 5.1 points you to.
  • The Transfer Policy covers gTLD inter-registrar transfers. Country-code registries publish their own transfer rules.
  • Fees, if any, are on the registrar's own page. The Transfer Policy does not set a price for unlocking.

Sources