What clientHold and serverHold Mean

If your domain shows clientHold or serverHold, its registry operator may stop publishing the domain in the DNS zone. This can make the website, email and other services unreachable even when the domain registration still exists.

The crucial difference is who applied the hold:

A hold is not the same as clientTransferProhibited (a transfer lock). Removing a transfer lock does not automatically remove a DNS hold.

Find out why the domain is on hold

1. Check the exact status in your NiceNIC account and via the applicable registry lookup/RDAP.
2. Look for verification reminders, expired invoices, inaccurate contact notices, registry document requests, or abuse/compliance messages.
3. Confirm the registry expiry date and whether the domain's renewal has finished processing.
4. If an official verification is outstanding, use the verified method indicated by the registrar or registry; do not follow untrusted links or send credentials through email.
5. If the domain was held for abuse or a registry review, submit the requested evidence and remediation details through the official support channel.

Do not repeatedly change DNS records when the status itself prevents delegation. Fix the hold first, then check DNS and hosting.

When should the domain work again?

Once the authorized party removes the hold, recheck the live status and authoritative delegation. DNS caches may take time to refresh. Test the real website and MX records rather than relying only on a control-panel success message.

If the underlying reason is unclear, open a NiceNIC support ticket with the domain, exact EPP status, dates, any verification case number and affected services. A registry-imposed hold may require additional review; removal cannot be guaranteed in advance.

A hold is different from a transfer lock

Troubleshooting example: If shop.example shows serverHold, changing its A record may have no visible effect, because the registry is not delegating the name normally. Resolve the underlying registry issue first. By contrast, if the domain has ordinary clientTransferProhibited status and website DNS is healthy, the lock is a security feature rather than the cause of downtime.

Once the hold is lifted, allow time for updated registry delegation and DNS caches. Check from multiple recursive resolvers rather than promising an instant return. If verification was the cause, confirm that the recipient address was genuinely authorized; do not submit credentials to an unverified verification URL.

Related NiceNIC Guides

• Why Is My Domain on ServerHold? Official Registry Checks and Next Steps
• Why Is My Domain on ClientHold and How Can I Fix It?
• Domain on ServerHold Due to Registry Email Verification
• How to Check Domain Status Before Transfer or Renewal