ClientHold and ServerHold Explained

Views:611 Time:2026-05-12 14:00:57 Author: windy

clientHold is set by the domain registrar. serverHold is set by the registry that operates the domain extension.

Both statuses prevent the domain from resolving normally through DNS, but they are controlled by different parties. Contact the registrar first for clientHold. For serverHold, the registrar may explain or coordinate the next step, but the registry controls whether the status is removed.

ClientHold and ServerHold can both stop a domain from resolving, but they do not mean the same thing.

This guide is for:

business owners whose domain suddenly stopped resolving
agencies troubleshooting a client outage
support teams checking WHOIS or domain status data
portfolio users trying to understand a hold message
anyone who wants a plain-language explanation before contacting support

If your domain is tied to a live website or business email, understanding the hold type helps you move faster and avoid wrong assumptions.

clientHold vs serverHold at a Glance

Item	clientHold	serverHold
Who sets it?	The sponsoring domain registrar	The registry operator for the domain extension
DNS effect	The domain is not activated or published normally in DNS	The domain is not activated or published normally in DNS
Website impact	The website may stop loading	The website may stop loading
Email impact	Domain-based email may stop working	Domain-based email may stop working
Who should the owner contact first?	The current registrar	The current registrar for available information and the correct escalation path
Who controls removal?	The registrar that applied the status	The registry that applied the status
Can changing DNS records fix it?	No, not while the hold remains active	No, not while the hold remains active
Does it mean the domain was deleted?	No	No

What ClientHold means
clientHold is an EPP domain status applied by the sponsoring registrar.

When clientHold is active, the registrar instructs the registry not to activate the domain in DNS. The domain therefore does not resolve normally, which can interrupt the website, business email, APIs, verification records, and other services that depend on the domain.

The registration still exists. clientHold does not mean that the domain has been deleted or has automatically become available for registration.

The registrar controls this status, but removal normally depends on resolving the underlying issue first. The registrant cannot remove clientHold by changing nameservers or editing A, MX, or CNAME records.

What ServerHold means
serverHold is an EPP domain status applied by the registry operator that manages the domain extension.

When serverHold is active, the registry does not publish the domain normally in the relevant DNS zone. As a result, the domain may stop resolving even when the nameservers and DNS records shown in the registrar account appear unchanged.

Because serverHold is controlled at the registry level, the registrar cannot directly remove it by changing an account setting. The registrar may provide available information, collect documents, relay an appeal, or coordinate with the registry, but the registry decides whether its status will be removed.

The exact process varies by registry, domain extension, reason for the status, and evidence required.

What both statuses have in common
Both ClientHold and ServerHold can lead to the same visible problem:

the website does not load
email service may stop working
DNS queries no longer return active results

That is why the two terms are often confused. From the outside, both can look like "the domain stopped working." But the source of control is different, which changes how you should respond.

Important:
A hold status shows the domain's current technical state. It does not, by itself, disclose the complete reason, prove that a specific abuse allegation is correct, or identify which evidence was used in a review.
The domain owner should check account notices, renewal history, verification requests, support tickets, and any registry or registrar messages before assuming why the status was applied.

Common reasons a domain may be placed on hold
The exact reason must be confirmed from the domain's notices and case history. Possible causes may include:

Expiration or payment issues: The domain was not renewed or a required payment was not completed.
Registrant verification: Required contact, identity, eligibility, or email verification was not completed.
Registration data issues: Contact information may be inaccurate, incomplete, or require confirmation.
Abuse or security review: The domain may be under review for phishing, malware, spam, fraud, DNS abuse, or another reported issue.
Legal or dispute action: A court order, formal dispute, regulatory requirement, or applicable policy may affect the domain.
Registry policy: The registry may apply its own eligibility, verification, compliance, or security process.
Technical or operational issue: In limited cases, the status may relate to registry processing or another domain-lifecycle event.

The presence of clientHold or serverHold alone does not identify which of these reasons applies.

What domain owners should check first
1. Confirm the exact status
Start with a WHOIS or domain status check so you know whether the domain shows ClientHold or ServerHold.
2. Check whether the problem is registrar-level or registry-level
This tells you where the issue is sitting and who is likely to guide the next step.
3. Review recent lifecycle events
Ask whether the domain recently expired, entered a renewal issue, changed account settings, or received a status-related notice.
4. Check whether the issue may affect email too
If the domain supports business email, assume email continuity may also be affected until DNS resolution is restored.
5. Avoid making random DNS changes
A hold status is not usually fixed by changing nameservers or editing records blindly. First identify the actual cause.

Common misunderstandings
1. A hold status means the domain is gone
Not necessarily. A hold status usually means functionality is suspended, not that the domain has been deleted.
2. ClientHold and ServerHold are interchangeable
They are not. They may look similar from the outside, but they originate from different control points.
3. DNS edits will solve the issue immediately
Usually not. If the hold remains active, DNS changes alone will not restore resolution.
4. The same recovery path works for both
It often does not. The action path depends on whether the issue is at the registrar level, the registry level, or related to DNS abuse.

What the Registrar Can Do
For a clientHold case, the registrar may:

Explain the available reason or required next step
Request verification, payment, remediation, or supporting evidence
Review the response submitted by the domain owner
Remove the registrar-set status after the relevant requirements are satisfied

For a serverHold case, the registrar may:

Confirm that the status is registry-level
Share any instructions or information provided by the registry
Collect documents or remediation evidence where an escalation route exists
Forward or support an appeal when permitted by the registry process

Why this distinction matters in practice
For business owners, this is not just a technical definition.
It affects:

who you contact first
how quickly you can understand the issue
whether the registrar can resolve it directly
whether the registry is involved
how you explain the issue internally or to a client

When the terminology is clear, the next step becomes clearer too.

Why NiceNIC's explanation model is useful
NiceNIC's public explanation is useful because it frames the issue in plain language instead of assuming technical background. It also clearly separates registrar-level and registry-level control, which is the most important distinction domain owners need at the start.

That makes the page suitable not only for technical users, but also for business owners and agencies trying to quickly understand what changed and what to do next.

Conclusion
clientHold and serverHold can create the same visible outage, but they come from different control layers.

clientHold is applied and controlled by the registrar. serverHold is applied and controlled by the registry. Neither status is normally resolved by changing nameservers or DNS records.

Check the exact status, review recent notices and lifecycle events, and contact the registrar with the domain name, current status, relevant ticket number, and any requested evidence. When serverHold is involved, the registrar may guide or support the escalation, but the registry controls the final status change.

FAQ
Q: Does ClientHold mean the registrar suspended the domain?
A: Yes. ClientHold is a registrar-level status that disables DNS resolution until the issue is resolved.
Q: Does ServerHold mean the registry is involved?
A: Yes. ServerHold is applied by the registry that manages the extension.
Q: Can both statuses affect email as well as the website?
A: Yes. If the domain stops resolving, both website and email services may be affected.
Q: What should I do first if I see one of these statuses?
A: Run a domain status or WHOIS check, confirm which hold applies, then review the likely cause before making changes.

If the status is connected to an abuse report or suspension review, read How to Report Abuse to NiceNIC to understand the evidence, submission process, and follow-up timeline.
NiceNIC customers can also submit a support ticket with the domain name, status code, existing case number, and relevant supporting documents.

ICANN Accredited Registrar Since 2006

Buy and Register Your .COM Domain Today

Check .COM domain availability, register a new .COM domain, search multiple names in bulk, or transfer your existing .COM domains to NiceNIC. Built for businesses, domain investors, agencies, hosting providers, and resellers.

Check .COM Availability Bulk .COM Search Transfer .COM

Renew: $17.99 Market ~~$22.49~~ $14.99 first year

Renew: $17.99 Basic $14.99 0% off

Renew: $17.99 Super $14.99 0% off

Renew: $16.99 VIP $14.99 0% off