clientHold Status: What It Means and How to Remove It

What is the clienthold status on a domain?
The clientHold status is an EPP code that tells the registry not to activate your domain in the DNS. As a result, the domain does not resolve, so your website stays offline and your email stops arriving. Your registrar usually sets it, and your registrar is also the one who can remove it.
EPP is the standard protocol that registrars and registries use to talk to each other. Every domain carries one or more status codes. Most of them are harmless, but the clienthold status cuts off access completely. Therefore, if you see it in WHOIS or RDAP output, the problem is in the registration status and not in your DNS settings.
This article covers the clienthold status only. We cover expired domains in a separate guide, and domain selection is a different topic as well. Here we help you read the status correctly, find the cause, and approach your registrar with the right next step.
First, it helps to see the picture clearly. Many owners blame their hosting provider for days. In reality, the clienthold status is a registration decision that has nothing to do with your server. The fix therefore lives with your registrar.
Why do my website and email stop working under clienthold?
A browser first asks the DNS for the IP address of your domain. When the clienthold status is active, the registry does not publish the domain in its DNS zone. The query gets no useful answer. The browser then usually shows a "site can't be reached" style warning.
Email stops for the same reason. Sending servers look up the MX record of your domain through the DNS. If they cannot find it, messages bounce or wait in a queue. Meanwhile your hosting may be perfectly healthy, which makes the problem confusing.
So do not call your hosting provider first. Check the registration status of the domain instead. If you see a similar warning, also keep the difference in mind from our guide to the DNS_PROBE_FINISHED_NXDOMAIN error, because both problems look alike at first glance.
What is the difference between clientHold and serverHold?
Both statuses keep the domain out of the DNS, but a different party sets each one. According to the ICANN EPP status codes page, the registrar sets clientHold, while the registry operator sets serverHold. The result looks the same: the domain does not resolve.
That difference decides who you talk to. For clientHold, your first contact is always your registrar. For serverHold, you also write to your registrar first, because contact with the registry usually runs through them.
- clientHold: set by the registrar, often tied to payment, verification, or a policy issue.
- serverHold: set by the registry, which often signals a higher level review.
- Under both, the DNS zone is not published, so the site and email stop.
In short, note which one you see and quote it exactly when you write to your registrar. The support team can then route your request to the right queue quickly.
How do you check the clienthold status of a domain?
You can read the status in two ways: WHOIS and RDAP. RDAP is the newer, structured successor of WHOIS. The ICANN domain lookup tool shows the status lines of your domain. You can also use our WHOIS lookup tool to get the same information.
- Enter the full domain name, for example example.com, in the lookup tool and run the query.
- Find the "status" lines in the output.
- Look for the term clientHold. In RDAP output, the same status often appears with a space, as "client hold".
- Write down the registrar name and contact channel from the same output.
- Query the DNS records separately with the DNS lookup tool. Under clienthold, no records come back.
This check takes only a few minutes, so do it first. It also gives you solid evidence before you contact the registrar. A screenshot with the date makes the conversation faster.
One detail matters: some lookup tools show cached data. Therefore, query with two different tools to be safe. Also, the status in your registrar panel and the one you see from outside can differ briefly. If the gap is large, tell the support team about it.
Is clienthold the same as clientTransferProhibited?
No. The clientTransferProhibited status is a normal lock that blocks unauthorized transfers to another registrar. The ICANN EPP status codes page describes it as protection against hijacking and fraud. Most healthy domains carry it, and it does not affect your site.
Many people panic when they see the word "prohibited" in WHOIS output. Your domain, however, works fine with that code, unlike a domain under the clienthold status. The codes that really matter are clientHold and serverHold, because they stop the DNS.
- clientTransferProhibited: blocks transfers, and the site keeps working.
- clientHold: stops publication in the DNS, so the site and email stop.
- Do not judge from the first code alone. Read the whole status list.
So read every line in the output separately. A domain can carry several statuses at the same time.
Why does a domain end up in clienthold status?
According to the official description, clientHold typically appears during legal disputes, non-payment, or when a deletion is pending. In practice, the causes fall into three groups, because registrars act for three main reasons. Each one has a different fix, so you need to find the cause first.
- Unverified registrant contact data: the registrar can suspend the domain when nobody answers the verification email.
- Payment or billing trouble: if a renewal or service fee stays unpaid, the registrar can suspend the domain.
- Terms of service violation or a complaint: the registrar can pause the domain to review it under its own policy.
Emails and panel notices from your registrar usually tell you which cause applies. Those messages may sit in a spam folder. Therefore, search every folder of the registrant email address.
Besides these three, the registrar's own security review can also trigger a hold. If a suspicious login happened on your account, the registrar may pause the domain as a precaution. In that case, reset your password right away and turn on two step verification.
Can an unanswered verification email stop a domain?
Yes, and this is one of the most common silent causes. Under ICANN's rules on registration data accuracy, registrars may need to verify the registrant's contact details. If verification is requested and nobody answers, the registrar can suspend the domain under its own policy.
For example, the usual triggers are a new registration, a change of registrant name or email, and a transfer to a new registrar. After such a change, the email is easy to miss. It goes to the registrant address, which may be old or rarely checked.
The deadline and the process vary by registrar. For that reason we give no numbers here; read the timeline on your registrar's help page. After you click the link, many registrars lift the hold themselves, but the timing differs from system to system.
If the registrant email no longer works, tell your registrar immediately. The address used for verification must be reachable.
How do you tell a payment hold from a policy hold?
The domain detail page in your registrar panel usually shows a warning badge. The emails from your registrar also hint at the cause. Comparing the order of the invoice reminder and the suspension notice tells you quickly whether payment is the cause.
If the panel shows a problem invoice, payment is the likely cause. If billing is clean and no verification email is waiting, a policy issue or complaint becomes more likely. For example, someone may have reported your domain for hosting harmful content.
| Symptom | Likely cause | Your first step |
|---|---|---|
| A verification email arrived, but you did not click it | Registrant verification | Open the link and tell the registrar |
| An unpaid invoice exists | Payment hold | Pay it and send the receipt to the registrar |
| No notice, and the panel is empty | Unclear; possible review | Open a support ticket with the registrar |
| The site showed a malware warning before | Security review | Clean the site first, then write to the registrar |
What should you do right away to remove the clienthold status?
Stay calm and work step by step, because rushing causes mistakes. ICANN's official guidance is clear: if you want the domain to resolve, contact your registrar and ask them to remove the status. The steps below are the practical version of that process.
- Confirm the status with WHOIS or RDAP and take a screenshot of the output.
- Log in to your registrar panel and read the warnings and invoices on the domain page.
- Search every folder of the registrant email for a verification message, and open the link.
- Complete any pending payment.
- If you cannot find the cause, open a support request, and write it as described in the next section.
- Keep the conversation in one channel until the status is gone, and save every reply.
However, do not skip any step. If you open a ticket before you find the verification email, the team may ask you for the same information again. That way you lose a full day for nothing.
Remember one thing during the process: you do not remove the hold yourself, the registrar does. Your job is to give the registrar what it needs, quickly and completely. Attaching the required documents to the first message cuts the back and forth.
How do you write to your registrar?
Keep your message short, specific, and complete, because that speeds up the review. Support teams receive many requests every day. A clear message reaches the right team faster.
- Write the full domain name and state that the lookup shows clientHold.
- Add information that proves you own the account, such as the account email.
- Describe in order what you did about verification or payment.
- Ask clearly what caused the hold and which step lifts it.
- Politely stress that your site and email are down, so the matter is urgent.
Also use only the official channels of your registrar. Make sure a phone line or chat belongs to the real company. Never try to speed things up by entering someone else's account or sending forged documents. Registrars treat that as circumventing their systems, and it puts your domain at greater risk.
How long does DNS take to recover after the hold is lifted?
When the registrar lifts the hold, the domain returns to the registry's DNS zone. After that, caches around the world refresh. This refresh time is not fixed. It depends on the TTL values of your DNS records and on your internet provider's cache.
So the site may not open on your connection while it opens on another. Do not misread this. Testing from a different network or with mobile data shows whether the problem is local or global.
- Try opening the site on mobile data.
- Clear your browser cache or use a private window.
- Check the DNS records with the DNS lookup tool. If records come back, the domain is live again.
- If needed, flush your device's DNS cache.
We do not promise an exact wait, because it varies by registrar and by cache. However, some fluctuation after the hold is gone is normal. A low TTL can speed up the switch, but you cannot change it during the hold. So plan ahead and review your TTL values in a calm period.
What if the site still does not open after the hold is gone?
First, separate what is still a domain problem. If WHOIS no longer shows clientHold and DNS records resolve, the remaining issue sits in the server or CDN layer. After you close the domain layer, move to the next one.
- Confirm that the server responds with the "is it down" checker.
- Check that the domain points to the right name servers. During a hold, a default setting may have changed in the registrar panel.
- If you use a CDN, check that service. For example, our Cloudflare error 522 guide explains a typical server timeout.
- Check that your SSL certificate is valid.
- Tell your hosting provider that the domain resolves but the server does not answer.
This order points you and the support teams in the right direction. Closing the domain layer before you contact the hosting provider also prevents needless back and forth.
How does the clienthold status affect your email flow?
Because the domain does not resolve, the MX record is also invisible. Incoming messages often wait on the sender's server and bounce after a while. The retry window depends on the sender's server settings. So some messages are not lost, but others may bounce.
After the hold ends, some pending messages may arrive on their own. Senders must retry the bounced ones. A short note to key customers reduces the worry about lost messages.
If you use email on your own domain, the guide on business email on your own domain explains a setup that softens such outages. Also send yourself a test message after the hold ends, to try both incoming and outgoing mail. For other email issues, such as a logo missing from an Outlook signature, see our separate guide.
Do .tr domains handle the clienthold status differently?
The EPP explanation in this article applies to general domain extensions. The registration and suspension rules for .tr domains can differ. Registration, verification, and objection procedures follow the rules of the relevant registry and the registrar. Therefore, if you face a similar problem on a .tr domain, rely on the official help pages of your registrar.
Also, .tr domains have their own restrictions, which we explain in our guide to the .tr domain restrictions. As long as you know that rules differ by extension, you will not apply the wrong rule to the wrong domain.
Here is a practical tip, because the rules differ: note the extension of your domain first. Then read the registration policy for that extension. That way you know which rules you rely on when you talk to your registrar.
How do domain status codes compare?
The table below puts the three most common statuses side by side. The definitions follow the explanations on the ICANN EPP status codes page. You can use the table as a quick checklist when you read your own output.
| Status code | Who sets it? | Does it affect the site? | How to resolve |
|---|---|---|---|
| clientHold | Registrar | Yes, the domain does not resolve | Fix the cause with the registrar and have it removed |
| serverHold | Registry | Yes, the domain does not resolve | Write to your registrar first and ask for details |
| clientTransferProhibited | Registrar | No, the site works | Ask for removal only if you plan a transfer |
If you meet a code that is not in the table, read its definition on the ICANN EPP status codes page. That way you rely on the official meaning instead of guessing.
Could another problem be mistaken for clienthold?
Not every site that fails to open has a clienthold status, though. A wrong DNS record, an expired domain, a server failure, or a CDN error can cause the same symptom. Therefore, diagnose in order. Otherwise you spend hours in the wrong place.
| Symptom | Likely source | Where to look |
|---|---|---|
| The domain does not resolve at all | clienthold status or a deleted registration | WHOIS or RDAP status line |
| The domain resolves, but the site does not answer | Server or CDN timeout | Hosting and CDN status pages |
| A certificate warning appears | Expired or misconfigured SSL | An SSL check tool |
| The domain looks expired | Renewal was missed | The expired domain guide |
If your domain stopped because it expired, our guide to an expired domain shows the right path. If the resolution problem comes from elsewhere, review your DNS records too. In short, identify the layer first, then go to the fix.
Which services stop while the domain is on hold?
However, the impact is not limited to the website. Everything tied to the domain stops. So when a hold notice arrives, list your own dependencies. Knowing which services run on this domain helps you measure the damage fast.
- The website and all subdomains do not open.
- Email addresses on the domain cannot receive messages.
- Ad campaigns with landing pages on the domain break, so consider pausing them.
- Application links and webhook calls that use the domain do not answer.
- Certificates and verification records tied to the domain cannot be checked.
Each item on this list also hurts the customer experience in its own way. Therefore, think about the whole chain, not only the website.
Does the clienthold status hurt your search visibility?
It can, because search engines cannot reach your pages. After a short outage, most sites recover. If the outage drags on, crawling and indexing get harder. We cannot measure the effect in advance and we give no guarantee, but the right actions reduce the risk.
- Get the hold removed as soon as possible, because every extra day adds risk.
- Check that the homepage and key pages open the moment the status clears.
- Confirm that your sitemap and robots file are reachable.
- Watch the crawl errors in your search console for a few days.
Example scenario: a small service site becomes unreachable during a hold. Its pages return errors and visitors cannot arrive. When the hold ends, the pages open again and crawling starts to normalize. However, a longer outage can mean a longer recovery, so speed matters. Moving to a new domain is a separate risk, since you can lose redirects and rankings.
What if the registrar does not respond?
First, make sure your request went through the right channel. Most registrars offer a ticket system, live chat, and an official phone line. If your request stays unanswered, collect the timeline and send a reminder through the same channel. Then look for the registrar's official complaint or escalation route.
- Save the ticket number and date.
- Reply to the existing ticket instead of opening a new one.
- Call the official phone or chat channel and quote your ticket number.
- Use the registrar's complaint or manager contact channel.
- If there is still no reply, look at the registrar's compliance and complaint processes.
None of these steps guarantees a result. Still, steady and documented follow-up is the most reliable way to keep the process moving.
How do you prevent a clienthold status in the first place?
Most prevention comes from boring but effective habits. Make sure the registrant email stays reachable. Also add your registrar's sender address to your safe list so its messages do not land in spam.
- Keep the registrant contact data current, and use an address that survives staff changes.
- Send renewal and billing notices to more than one person.
- When you change registrant data, look for the verification email the same day.
- Tie the domain to a shared company address, not a personal mailbox.
- Review your WHOIS output once a year.
So think this way when you pick the name as well. Our guide on how to choose a domain name also touches the long term management of a domain. A good habit is to look at the registration output before a problem appears.
What should you do if a legal dispute is involved?
According to the official description, clientHold can also apply during a legal dispute. In that case, the registrar usually acts only on the relevant authority or after the parties agree. So you may not get a quick answer from support.
At this stage, keep all official correspondence calm and organized. If you received a trademark, arbitration, or complaint notice, compare it with the documents your registrar sent you. If you are in the middle of a legal process, talk to a lawyer; this article is not legal advice.
You can still protect business continuity. For example, open a temporary channel such as a social media account or a backup email address to inform customers. Be careful, though: registering a second domain with the same brand while the first is on hold can create a new dispute.
Should you trust a paid domain recovery promise?
No. When a domain is suspended, people appear on social media and in search results who promise to get it back for sure. We cannot give such a guarantee, and nobody can. The registrar decides, and the registry decides when needed.
- Do not hand account details or the domain authorization code to unofficial middlemen.
- Avoid forged documents or someone else's account; these methods count as circumventing systems.
- Never try to get around a hold by opening a new account or a new registration.
- Pay only through the official panel of your registrar.
The healthy path is simple: the official registrar channel, honest documents, and clear writing. It takes patience, but it keeps the risk of losing your domain as low as possible.
When should you get expert help?
If your registrar conversation moves forward but rebuilding your site, email, and DNS takes time, outside support makes sense. After the hold ends, reconfiguration, SSL checks, and redirect tests need technical knowledge.
At Talha Aslan and team, we first separate whether the issue comes from the domain, the server, or the content. Then, once your site is back, we build a checklist to protect your search visibility. We are not a domain registrar, so we cannot lift a hold; that decision rests only with your registrar.
If your site needs a rebuild, you can review the scope on our web design service page. Otherwise, the steps above point you to the right registrar support in most hold cases.



