serverHold
registry pulled it from the zone
The registry has removed the domain from the zone. It sits above the registrar and the registrar cannot lift it.
What it tells you about enforcement
The REGISTRY acted, which is the strongest outcome short of deletion. In our one observed case a registry set serverHold roughly an hour after simultaneous filings went to every party in the chain — while the registrar never responded at all.
The facts
- Set by
- registry
- Resolves?
- No — the domain is not in the zone and does not resolve.
- Re-armable
- Only the registry can lift it. The registrar cannot.
- Where you see it
- The
statusarray of an RDAP record, or theDomain Statusline in whois.
Do not confuse it with clientHold
serverHold is set by the registry; clientHold is set by the registrar. They look the same in a whois record and mean different things about who acted and who can undo it. Read clientHold.
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.