serverHold: What It Means & How to Fix It
serverHold is the registry-level kill switch: per ICANN, this status is set by your domain's registry operator, and your domain is not activated in the DNS. The name stops resolving everywhere — website, email, APIs, everything.
Because it's imposed by the registry rather than your registrar, it usually signals something more serious than the registrar-level clientHold.
What serverHold means
The registry has removed the domain's delegation from the TLD zone. The registration record still exists, but DNS resolution fails globally. One benign case exists: per ICANN, if you never provided delegation information (nameservers), the domain simply isn't activated yet — some registries use serverHold rather than inactive for undelegated names.
The non-benign cases: abuse enforcement (malware, botnets, phishing flagged at registry level), TLD policy violations (for example, a ccTLD's residency or documentation requirement not met), court orders, and unresolved verification issues escalated past the registrar.
Is it good or bad news?
If the domain was resolving yesterday and shows serverHold today, treat it as a serious incident. ICANN's guidance: if you provided delegation information, this status may indicate an issue with your domain that needs resolution — contact your registrar to request more information.
Registries don't suspend domains casually. Expect the cause to be policy- or abuse-level rather than a billing hiccup.
Monitor every domain status automatically
Sourdough pulls live RDAP status for every domain you track and flags anything unusual — holds, locks, redemption — before it becomes a problem. 7 days free, then $10/mo. $0 due today.
How to fix it
- •Contact your registrar first — registrants can't open tickets with the registry directly. Ask them to find out from the registry why the hold was placed.
- •If the domain was never delegated, simply provide nameservers through your registrar and the hold lifts once delegation is set.
- •For abuse-related holds, remediate the flagged issue completely, then have the registrar present evidence to the registry.
- •For TLD policy issues (common with ccTLDs), supply whatever documentation the registry requires.
- •Court-ordered holds only lift when the legal matter does.
serverHold vs clientHold
Both take the domain out of DNS; the difference is who pulled the trigger and how hard reinstatement is. clientHold is registrar-set and often clears the same day; serverHold is registry-set and typically involves a longer, evidence-based path. The full comparison is on the serverHold vs clientHold page.
Frequently Asked Questions
How serious is serverHold?
On a previously working domain, very. It means the registry operator — not just your registrar — removed the domain from DNS, which usually reflects abuse findings, TLD policy violations, or legal action. Start the registrar conversation immediately.
Can my registrar remove serverHold?
Not directly. Only the registry that set it can remove it. Your registrar's role is to relay the cause, pass along your remediation or documentation, and request the lift.
Does serverHold mean I lost my domain?
No — the registration still exists and you're still the registrant. But the domain won't resolve until the underlying issue is resolved and the registry lifts the hold.