clientTransferProhibited
set by: registrar
The registrar blocks transfers to another registrar.
What it tells you about enforcement
Almost never enforcement. Most registrars set this by default on every domain as anti-hijacking protection. Reading it as "someone acted" is a common and expensive mistake — the domain is completely live.
The facts
- Set by
- registrar
- Resolves?
- Yes — this code does not by itself stop the domain resolving.
- Re-armable
- Not applicable: nothing was suspended.
- Where you see it
- The
statusarray of an RDAP record, or theDomain Statusline in whois.
Do not confuse it with serverTransferProhibited
clientTransferProhibited is set by the registrar; serverTransferProhibited is set by the registry. They look the same in a whois record and mean different things about who acted and who can undo it. Read serverTransferProhibited.
Every status code
Ordered so the two that actually take a domain out of the zone come first.
- clientHoldregistrarpulled from zone
- serverHoldregistrypulled from zone
- addPeriodregistry (automatic)
- autoRenewPeriodregistry (automatic)
- clientDeleteProhibitedregistrar
- clientRenewProhibitedregistrar
- clientTransferProhibitedregistrar
- clientUpdateProhibitedregistrar
- inactivenobody
- oknobody
- pendingCreateregistry (automatic)
- pendingDeleteregistry (automatic)
- pendingRenewregistry (automatic)
- pendingRestoreregistrar
- pendingTransferregistry (automatic)
- pendingUpdateregistry (automatic)
- redemptionPeriodregistry (automatic)
- renewPeriodregistry (automatic)
- serverDeleteProhibitedregistry
- serverRenewProhibitedregistry
- serverTransferProhibitedregistry
- serverUpdateProhibitedregistry
- transferPeriodregistry (automatic)
Definitions follow ICANN’s published status-code list. The enforcement reading is ours. Last built 2026-09-20.