clientHold
registrar pulled it from the zone
The registrar has told the registry to remove the domain from the zone. It stops resolving, but the registration itself is untouched.
What it tells you about enforcement
The REGISTRAR acted. This is a real suspension and the usual successful outcome of an abuse report. It is also reversible by the same registrar, so treat it as held, not finished.
The facts
- Set by
- registrar
- Resolves?
- No — the domain is not in the zone and does not resolve.
- Re-armable
- Yes — the same registrar that set it can lift it.
- Where you see it
- The
statusarray of an RDAP record, or theDomain Statusline in whois.
Do not confuse it with serverHold
clientHold is set by the registrar; serverHold 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 serverHold.
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.