serverHold domain status
serverHold is the registry-level counterpart of clientHold: the registry operator itself keeps the domain out of DNS, and lifting it has to go through the registry rather than the registrar.
Updated
- Set by
- Registry (server code)
- Effect
- Domain does not resolve; removal goes through the registry
- RDAP shows
- server hold
What serverHold means
serverHold works like clientHold, withholding the domain’s delegation so it does not resolve, but the registry operator sets it rather than the registrar. ICANN notes that server codes take precedence over client codes.
Because it comes from the registry, the cause sits with the registry operator: anything from missing delegation data to registry-level enforcement. A URS loss looks different: the registry locks the name with server prohibited codes and points it at a notice page, which keeps it in DNS rather than removing it.
On a domain you are watching
serverHold on a lookalike is a stronger signal than clientHold. It means the registry operator, not just the registrar, pulled the delegation. The registrant cannot undo it through the registrar alone.
Check a domain’s status codes
The lookup reads a domain’s live RDAP record and returns its current status set.
What to do about serverHold
The registrant has to contact the registrar, which works with the registry operator to resolve the underlying issue and lift the status.
Sources
Frequently asked questions
Only the registry operator, and the registrant reaches it through the registrar. ICANN advises contacting the registrar to request more information about the issue behind the status.
Sometimes. Registries can suspend names under their own abuse policies, and court or seizure orders also arrive at registry level. The code alone does not reveal the trigger; the registrar can tell the registrant why it was set.
Related tools and resources
Domain Abuse Contacts
Query RDAP records, live status codes, and verified abuse channels for any domain.
Domain monitoring
Daily monitoring for lookalike domains across 1,570 TLDs, with every match checked and explained.
How to Report Domain Abuse to a Registrar
Find the sponsoring registrar, collect required DNS evidence, and submit an actionable report.
Ongoing brand monitoring
notolens checks daily registrations across 1,570 TLDs, trademark registers, and app stores. When a lookalike domain, conflicting mark, or copycat app appears, notolens checks it, explains the risk, and hands you the records and possible next steps.