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, clientHold and clientTransferProhibited can coexist. The first prevents publication of the domain’s delegation in DNS; the second blocks transfers to another registrar without itself stopping DNS resolution. By contrast, ok indicates that no pending operation or prohibition is set and cannot coexist with any other EPP domain status.

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 set by the registrar and instructs the registry not to publish the domain’s delegation in its DNS zone. The domain’s own DNS zone may still exist at its DNS provider, but normal public resolution will fail once relevant cached data expires. This can make the website unreachable and prevent email delivery because senders cannot resolve the domain’s MX records.

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

First confirm that the hold has been removed, then check that the registry’s parent zone publishes the domain’s delegation again. Verify that the delegated nameservers serve the expected A, AAAA, CNAME and MX records where configured, and compare results through recursive resolvers. Registry publication delays and cached positive or negative answers can cause recovery to appear at different times; a correct answer obtained directly from the DNS provider alone does not prove that public resolution has recovered.

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 set by the domain registry and prevents publication of the domain’s delegation in the registry’s DNS zone. As relevant cached DNS data expires, the website and email can become unreachable even while the hosting server and the domain’s own DNS zone are 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. Follow the stated remediation requirements rather than making unrelated DNS changes. If the site is compromised or serving harmful content, contain the incident promptly; do not wait for the hold to be removed.
4. If an abuse allegation is involved, securely preserve relevant logs and copies of affected content for review where lawful. Keeping evidence does not require leaving harmful content publicly accessible.
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.

A registrar transfer normally leaves the nameserver delegation recorded at the registry unchanged, but DNS hosting is a separate service. Confirm that the existing DNS provider will continue serving the zone after the transfer, especially if DNS was bundled with the old registrar. Transfer locks, an invalid authorization code or eligibility restrictions can prevent a request from reaching pendingTransfer; once that status is present, check the approval and completion process with both registrars. 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.
• Confirm with both registrars that the request is pending and ask for its expected completion time.
• Review any transfer notices, the new registrar’s panel and the spam folder. Follow the applicable approval or rejection procedure; not every transfer requires a manual approval click.
• If the request is unauthorized, use the registrar’s rejection or cancellation procedure and contact the current registrar immediately. Do not assume that applying a transfer lock cancels an existing request.
• 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; revoke unauthorized access. If an unauthorized transfer has already completed, urgently ask the previous registrar to begin the applicable recovery or dispute process and retain the notices as evidence. For a transfer you initiated, confirm the contact information, nameserver delegation and DNS service at the new registrar after completion.

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 indicates a post-deletion recovery stage under the registry’s redemption grace process. It often follows deletion after non-renewal, but expiry is not the only route into this state. Recovery requires a restore request through the registrar rather than an ordinary renewal alone.

During this stage, the domain is not delegated in DNS, so website and email service through the domain will fail once relevant cached data expires. For gTLDs covered by ICANN’s redemption grace requirements, the redemption period is 30 days; other extensions can follow different rules. The registry’s lifecycle rules govern the recovery window, while the registrar provides the restore procedure, customer-facing fee and any earlier processing cutoff. Confirm the exact deadline rather than assuming the registrar can extend it.

Safe steps during redemptionPeriod

1. Find the exact status and confirm the recovery deadline and processing cutoff with the registrar.
2. Ensure you can authenticate to the domain account or complete the registrar’s account-recovery procedure.
3. Confirm the restore conditions and fee in writing, including whether renewal is included or must be requested separately.
4. Back up accessible DNS records, web configuration and email settings, but do not delay a time-sensitive restore if those backups are unavailable.
5. After the restore completes, verify the expiration date, complete any required renewal, and check the parent delegation, 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 for process details and account-specific warnings. Then check the domain’s RDAP record through the relevant registry or a registration-data lookup service. RDAP is the primary public registration-data protocol for gTLDs; WHOIS availability varies, particularly across country-code extensions. RDAP can display equivalent status labels with spaces: client hold, server hold, pending transfer and redemption period. These correspond to the EPP-style names used here. Public registration data can identify statuses and the registrar, but may not disclose the reason for a restriction or the registrant’s private details.

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?

No. Changing nameservers does not remove serverHold; the registry must lift the status before the domain’s delegation can be published again. Ask the registrar for the reason and removal conditions. Nameserver corrections may still be needed separately if the configuration is wrong.

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, an RDAP record or a WHOIS record where available.
• 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