Domain suspended or on hold

Your site is offline. Your registrar or the TLD registry has placed a hold on the domain, so DNS has stopped working. Contact your registrar today to find out why and ask them to lift it.

Symptom

• Your site shows as Down in DomainDash. The registry drops a held domain from its zone, so the uptime check fails. DomainDash doesn't read holds, so it won't name the hold for you
• Your site is unreachable. Visitors see "This site can't be reached" or a registrar parking page
• Running whois example.com yourself shows one or more of: clientHold, serverHold, pendingDelete, or pendingRestore in the "Domain Status" section
• DNS lookups return NXDOMAIN because the domain has been removed from the zone

What it means

Domain registries and registrars can place status codes on a domain that prevent it from operating normally. The most disruptive of these are "hold" statuses: they cause the domain to be removed from the TLD zone, which means DNS stops working and your site goes offline, exactly as it would with an expired domain.

DomainDash doesn't read or classify holds. Its domain registration check tracks the expiry date. To find the hold, run a WHOIS lookup yourself. The status code tells you who placed the hold and what lifts it. Match yours to the table below:

Status	Who placed it	Typical cause	How to resolve
clientHold	Your registrar	Billing, WHOIS compliance, abuse complaint	Contact registrar, resolve the issue
serverHold	The TLD registry	UDRP dispute, court order, legal hold	Legal advice usually required
pendingDelete	Registry	Post-expiry or post-dispute deletion queue	Emergency redemption, or accept loss
pendingRestore	Registry	Redemption in progress	Wait for registrar to complete
clientTransferProhibited	Your registrar	Normal protection against unauthorised transfers	No action needed

If the only status codes you see are clientTransferProhibited, clientUpdateProhibited, or clientDeleteProhibited, your domain is fine. These are standard protective codes that most domains carry.

Common causes

• Outstanding unpaid invoice on your registrar account
• WHOIS contact information that is inaccurate, incomplete, or hasn't been verified following a registrar request
• An abuse report or DMCA (Digital Millennium Copyright Act) takedown complaint that the registrar is acting on
• A trademark dispute filed as a UDRP (Uniform Domain-Name Dispute-Resolution Policy) complaint with ICANN
• A suspected security compromise, where the registrar detected suspicious activity on your account or domain
• Domain transfer that was flagged as potentially unauthorised, triggering a hold while the registrar investigates

How to fix

1. Check the domain status in WHOIS. Run whois example.com and look for the Domain Status field. Note the exact status codes, because they tell you whether it's a registrar-level or registry-level hold.

2. Identify the reason for the hold. Contact your registrar's support team. The WHOIS record won't tell you why the hold was placed. Ask specifically which hold is in effect and what action you need to take to have it removed.

3. Resolve the underlying issue. For billing issues: pay the outstanding invoice. For WHOIS compliance: update your registrant contact information. For abuse or DMCA complaints: respond to the complaint through the registrar's process. For UDRP or court orders: get legal advice. For security compromises: change your password, enable two-factor authentication, and report the compromise to the registrar.

4. Request the hold to be lifted. Once the issue is resolved, ask the registrar to remove the hold. The registrar usually lifts billing and compliance holds within a few hours. pendingDelete is urgent, so ask about redemption immediately. Pulling the domain back typically costs £60 to £160 on top of the renewal price, depending on the registrar.

5. Watch propagation and verify in DomainDash. After the hold is lifted, run whois example.com again to confirm the clientHold or serverHold status code is gone. DomainDash doesn't read holds, so look at the site's checks: once the domain resolves again, uptime checks pass and the site page header reads Healthy once recovery is confirmed, or Unstable while uptime for the selected timeframe (24 hours by default) is under 97%.

6. Prevent future holds. Keep billing up to date, maintain accurate WHOIS contact details, and enable two-factor authentication on your registrar account.

How to verify

After the hold is lifted:

1. Run whois example.com. The Domain Status section should no longer contain clientHold or serverHold. Standard codes like clientTransferProhibited are fine.

2. Give DNS up to an hour to come back, then run:

   dig example.com A +short @8.8.8.8

   You should see the domain resolving to an IP address.

3. Open the site in a browser and confirm it loads.

4. Open the site in DomainDash and confirm the site page header reads Healthy. It reads Unstable instead until uptime for the selected timeframe is back to 97% or more. Roughly 45 minutes of downtime in a day is enough to cause that.

Registries put a domain back in the zone within minutes of a hold being lifted, and resolvers stop saying the domain doesn't exist within about 15 minutes for .com. If it still doesn't resolve after an hour, ask the registrar to confirm the hold is gone at the registry, not only in their own system.

Related

• Domain expired — if WHOIS shows an expired domain rather than a hold status
• WHOIS lookup failed — if DomainDash can't read the WHOIS record at all
• Domain registration — how DomainDash tracks domain status and what the checks look for
• How incidents work — how DomainDash opens and escalates incidents when a domain is expiring or expired