Written by
Hasnaat Mahmood
Hasnaat is the founder of Find Cheap Domains and writes from hands-on experience with domain registrations, renewals, transfers and DNS management.
Practical domain management experienceWhat Does clientTransferProhibited Mean on a Domain?
It means your registrar has placed a transfer lock on the domain, so another registrar cannot transfer it away while that status remains active. In most cases it is a normal security setting, not a sign that anything is wrong.
Quick answer
It is a registrar lock that blocks transfers to another registrar.
ICANN describes clientTransferProhibited as a client status code set by the registrar. While it is active, the registry rejects attempts to transfer the domain to a different registrar.
- Set at registrar level
- Blocks registrar transfers
- Usually easy to remove when eligible
If you have looked up a domain in WHOIS or RDAP and seen clientTransferProhibited, the wording can sound more serious than it is. Most of the time it simply means the domain is locked against an unauthorised registrar transfer.
My own rule is not to treat this status as a warning by itself. If I am not planning to move the domain, I would generally rather see a transfer lock in place than leave the domain unnecessarily open to an outbound transfer.
It does not mean your website is blocked.
The status is about transferring the registration between registrars. It does not, by itself, stop the domain resolving, switch off email or prevent visitors reaching the website.
The status itself
What does clientTransferProhibited actually do?
It tells the registry to reject a request to transfer the domain to another registrar.
The word client is important. In EPP terminology, client status codes are set by the registrar, while server status codes are set by the registry. ICANN lists clientTransferProhibited as one of the standard client status codes.
If another registrar tries to submit a transfer request while this status is active, the transfer should be rejected. That is why registrars commonly refer to the setting as a domain lock, registrar lock or transfer lock.
It blocks registrar transfer
The domain cannot normally be transferred from the current registrar to another until the status is removed.
It helps protect the domain
The restriction makes it harder for an unauthorised party to move the registration away without the lock first being removed.
It is not a DNS suspension
The code does not tell the registry to remove the domain from DNS. That is a different type of status, such as clientHold.
If you want the wider picture, our guide to how domain locking works explains why registrars use these restrictions and when you would normally unlock a domain.
ICANN EPP status code guideICANN's reference explains the difference between client and server status codes and what clientTransferProhibited means.Read the ICANN guide ICANN on locked domainsICANN explains that registrar lock and client transfer prohibited are commonly used terms for a locked domain.Read ICANN guidance
Why it appears
Why is clientTransferProhibited on my domain?
The most ordinary reason is simply that your registrar keeps the domain locked unless you are preparing to transfer it.
ICANN's current Transfer Policy allows registrars to set clientTransferProhibited at registration or later at the registered name holder's request, provided the relevant terms are covered in the registration agreement.
- The registrar applies a transfer lock by default. This is common as a security measure.
- You turned domain lock on yourself. Many registrar dashboards let the registrant lock and unlock a domain directly.
- The domain was recently registered or moved. You may also be subject to a separate transfer restriction, so removing the visible lock does not necessarily make the domain immediately transferable.
- The registrar has its own security workflow. Some providers require extra verification before the lock can be removed.
That last point is why I would not judge a registrar purely by whether this code is visible. A locked domain is often exactly what you want when no transfer is planned. What matters is whether you can remove the lock cleanly when you genuinely need to move the domain.
Easy to confuse
clientTransferProhibited is not the same as every other transfer restriction
Seeing a transfer-related status does not tell you the whole reason a domain cannot move.
clientTransferProhibited
A registrar-set EPP status. It blocks the transfer while active and can often be removed from the registrar account or by contacting the registrar.
60-day transfer restriction
A domain may be ineligible for transfer because of ICANN transfer rules or a change-of-registrant restriction. That is a separate question from whether the visible EPP lock is switched on.
serverTransferProhibited
This is set at registry level rather than registrar level. ICANN says it is less common and may be associated with disputes, redemption or a registry-lock service.
pendingTransfer
This means a transfer request has already been submitted and is being processed. It is not the same as a lock preventing the transfer from starting.
We have a separate explanation of whether nameserver changes trigger a 60-day transfer lock, because that is one of the easiest restrictions to mix up with an ordinary registrar lock.
Unlocking the domain does not guarantee a transfer will be accepted.
If another transfer restriction still applies, the domain can remain ineligible even after clientTransferProhibited disappears from RDAP or WHOIS.
When you want to move
How do you remove clientTransferProhibited?
Start in the registrar account where the domain is currently registered.
- Open the domain's security or transfer settingsLook for wording such as Domain Lock, Registrar Lock, Transfer Lock or Unlock Domain.
- Turn the lock offIf the registrar provides self-service unlocking, the status should be removed through that control.
- Check that no separate restriction appliesA recent registration, previous transfer or other transfer-policy condition can still prevent the move.
- Request the AuthInfo codeFor TLDs that use an auth code, obtain it only after you are sure you are transferring to the intended registrar.
- Recheck RDAP or WHOISConfirm the status has cleared before repeatedly submitting a transfer request.
Under ICANN's Transfer Policy, if the registrar does not give you a self-service facility to remove clientTransferProhibited, it must remove the status within five calendar days of your initial request. The policy also requires the AuthInfo code within five calendar days where the registrar does not provide a self-service method for generating it.
Once you are ready to move, it is worth checking the receiving registrar as well as the old one. You can compare domain transfer prices before you unlock anything, rather than leaving a domain open while you decide where it is going.
When to look closer
When should clientTransferProhibited concern you?
The status itself is usually routine. The problem is when you cannot control it or it appears alongside something you do not understand.
- You are trying to transfer and there is no way to unlock the domain.
- The registrar refuses to remove the lock without a clear policy reason.
- You see serverTransferProhibited as well and do not know why.
- The account email, password or security settings changed unexpectedly.
- You did not request an outbound transfer but receive transfer-related messages.
- The domain is locked and you no longer have access to the registrar account.
If the only thing you see is clientTransferProhibited on a domain you are not trying to move, I would usually leave it alone. Unlock it when you have a real transfer to make, complete the move, and avoid keeping a valuable domain unlocked for longer than necessary.
If you are preparing a `.com` move, our guide to how long a .com domain transfer takes explains what happens after the lock has been removed and the transfer has actually started.
My view
For most domains, clientTransferProhibited is a good status to see when you are not transferring.
The name sounds severe, but the job is simple: stop the registration being moved to another registrar until the lock is removed. I would treat it as a normal security control first, then investigate only if you cannot unlock the domain when you genuinely need to.