Domain Status Codes Explained: ClientHold, ServerHold and More

If your website will not open or you cannot send and receive email even though the domain does not appear to have expired, checking only the hosting server may send you in the wrong direction. Status codes such as clientHold, serverHold, pendingTransfer and redemptionPeriod can show that the problem is at the domain registration layer.

These are not HTTP response codes. Unlike a web server response such as 404 or 503, domain status codes describe the domain’s state with its registrar and registry. Identify the exact code first, then apply the action that matches that code.

What do domain status codes show?

Domain status codes are standard states used in the Extensible Provisioning Protocol, or EPP. EPP supports domain creation, renewal, transfer and status changes between registrars and registries. Panels may display the codes with different capitalization or add a plain-language explanation.

A domain can have several statuses at the same time. For example, ok can indicate that no special restriction is present, while clientTransferProhibited can show that a transfer lock is enabled. Those two statuses do not affect website availability in the same way.

Separate these three layers during diagnosis:

• Registrar: The company through which you manage the domain. Payments, contact verification and account actions are handled here.
• Registry: The central system for a particular top-level domain. A registry can apply a status such as serverHold.
• DNS and hosting: DNS determines where the domain points, while hosting runs the website application and related services.

If a hold is active, repeatedly changing DNS records usually will not solve the problem. First establish why the hold exists and what must happen for it to be removed.

What is clientHold?

clientHold is a status applied by the registrar. The domain may still have a DNS zone, but the registrar can prevent the domain from being published or resolved through the normal DNS path. As a result, the website may not open, email delivery may stop because MX records cannot be used, and DNS queries may return an unexpected result.

The reason depends on the registrar. Common possibilities include an overdue payment, unverified contact details, an abuse review, a missed document request or an account-security action. The code itself does not confirm the exact cause. Look for that explanation in the registrar’s notification or support case.

How to diagnose clientHold

1. Sign in to the registrar account and confirm the exact spelling of the status.
2. Check messages sent to the account email address, including the spam folder and support tickets.
3. Review payment, automatic renewal, contact verification and document requests.
4. Check the domain status and restriction explanation before changing DNS records.
5. If necessary, open a support request containing the domain, account-owner details and status code. Do not send a password or identity document through an unsafe channel.

Make the narrowest correction that addresses the stated cause. If the issue is an unverified email address, complete that verification. If payment failed, review the payment method and renewal process. Changing nameservers does not remove a registrar hold.

Verify the domain after clientHold is removed

DNS changes may not appear at every resolver at the same time. First confirm in the registrar panel that the hold has been removed. Then check the authoritative nameservers and the A, AAAA, CNAME and MX records.

For the website, test the HTTPS connection and the application response separately. For email, test sending and receiving separately. A successful website test does not prove that email is working.

What is serverHold?

serverHold is a restriction applied by the domain registry. The domain may be removed from registry-level DNS resolution, so the website and email can become unreachable even while the hosting server is operating normally.

The practical distinction is that the registrar applies clientHold, while the registry applies serverHold. The first symptom can look similar: the domain does not resolve or produces an unexpected result. A browser error alone cannot reliably distinguish the two statuses.

Possible causes vary by top-level domain and registry rules. They can include an abuse report, a legal request, a verification process or a policy review. Ask the registrar for the exact reason; the registrar normally communicates with the registry when needed.

What to do when serverHold is active

1. Confirm that the status is really serverHold, not clientHold or a transfer-lock status.
2. Ask the registrar’s support team for the reason, required documents and expected sequence of actions.
3. Complete the requested compliance step before changing content or DNS configuration.
4. If an abuse allegation is involved, preserve relevant content and server logs. Keep the evidence for review instead of deleting it.
5. After the hold is removed, verify the registrar panel, DNS resolution and application services in that order.

If you cannot access the registry directly, work through the registrar. Restarting the hosting server or disabling WordPress plugins will not restore access when the domain is held at registry level.

What does pendingTransfer mean?

pendingTransfer means that a request to transfer the domain to another registrar is being processed. The request may be waiting for approval, rejection or completion. This status alone does not mean that DNS resolution has stopped.

During a transfer, the domain will often continue using its existing nameserver information at the current registrar. A missed approval email, transfer lock, EPP authorization code or registration-period issue can affect the process. The guide on transferring a domain without downtime explains related planning considerations.

What to check during a pending transfer

• Confirm that you actually initiated the transfer.
• Check whether the transfer lock was removed at the current registrar.
• Review the approval email, the new registrar’s panel and the spam folder.
• If the request is unauthorized, reject it and contact the current registrar immediately.
• Unless necessary, do not start another operation, such as a nameserver change, at the same time.

If you did not initiate the transfer, do not simply wait. Change the registrar password, enable two-factor authentication and review the account for unknown users or API access. After the transfer completes, confirm the contact information and DNS records at the new registrar.

A transfer can also affect email if nameservers, DNS records or account ownership are changed incorrectly. Review the separate guidance on why domain transfers break email before moving an active mail service.

What is redemptionPeriod?

redemptionPeriod means that the domain has entered a recovery stage after the renewal period and other waiting stages that apply to many extensions. The domain may no longer be available through the ordinary renewal screen. A special restore process may be required.

During this stage, the domain can lose website and email service. The recovery period depends on the extension’s rules and the registrar’s process. The registrar determines whether a restore fee applies, how much it costs and when the deadline falls. Do not assume a universal fee or number of days.

Safe steps during redemptionPeriod

1. Find the exact status and recovery deadline in the registrar panel.
2. Prepare access that proves you control the domain account.
3. Confirm the restore conditions, how restore differs from ordinary renewal and any applicable fee in writing.
4. Before starting the operation, back up the DNS zone, web configuration and email records.
5. After the restore completes, renew the domain and check the nameservers and DNS records.

Moving to a new domain while the old one is in redemptionPeriod is not the same as recovering the old domain. Consider your brand, search visibility and email continuity, and ask the registrar about the recovery possibility and deadline before waiting.

How do you verify a domain status?

Start with the registrar panel. It can include current process details and account-specific warnings. Then check a suitable WHOIS or RDAP record. A separate explanation of how to read domain registration data is available in the guide on checking domain ownership with WHOIS.

Review clientHold, serverHold, pendingTransfer, redemptionPeriod, clientTransferProhibited and serverTransferProhibited together. Transfer-lock statuses restrict transfers; hold statuses can directly affect DNS availability. Do not treat similar words as the same problem.

Separate DNS and service tests

After confirming the status, test DNS resolution. Check whether the A or AAAA record points to the expected IP address, whether MX records identify the correct email provider and whether the authoritative nameservers are correct. Results during an active registry restriction may not represent the state you will see after the restriction is removed.

For the website, verify that the HTTPS certificate matches the domain and that the application returns the expected response. For email, test more than webmail login: send to another address and receive a message from outside the domain. Do not assume that messages rejected during a hold will be delivered automatically later; review the sender’s error and queue logs.

Keep domain status codes separate from HTTP status codes. A 404 or 503 from the website can indicate an application or web-server problem, while clientHold or serverHold can prevent the request from reaching that server at all.

Frequently Asked Questions

Is clientHold the same as a domain lock?

No. clientHold can affect DNS use. clientTransferProhibited restricts transfer to another registrar. Both statuses can exist on the same domain.

Will changing nameservers fix serverHold?

Usually not. Until the registry removes the hold, new nameserver information may not be published. Ask the registrar for the reason and removal conditions before making configuration changes.

Does pendingTransfer take the website offline?

Not by itself. Existing DNS and hosting may continue to work during the transfer. An unauthorized or incorrect request is still an account-security and ownership risk that needs prompt attention.

Can someone register the domain after redemptionPeriod ends?

The release process depends on the extension and registry timing. Ask the registrar for the recovery deadline before the final stage; once the domain is released, registration is not guaranteed.

Checklist and next step

• Confirm the exact status in the registrar panel and, if possible, a WHOIS or RDAP record.
• For clientHold, check payments, contact verification and account notifications.
• For serverHold, request the registry restriction reason and required documents from the registrar.
• For pendingTransfer, confirm who started the transfer and where approval stands.
• For redemptionPeriod, confirm the deadline, restore conditions and DNS backup.
• After the status changes, test DNS, the website and email separately.

Start by checking the domain’s current status, the registrar notifications and the domain-owner email address. Until the code is clear, avoid broad DNS or hosting changes. Complete the narrow action at the correct layer, then verify the result again.

Emre