Why Your .COM or .NET Domain Is on serverHold and What to Do

Your .COM or .NET domain suddenly stops working. Your website won’t open, your business email may be affected, and a domain lookup shows serverHold.

What should you do first?

serverHold is a registry-level status that prevents a domain from being published in the registry’s DNS zone. It doesn’t necessarily mean the domain has been deleted or used for abuse.

Most importantly, do not assume the restriction will disappear automatically. The next step depends on why the registry applied it.

Quick Help: What to Do Right Now

If your domain is affected, start with these three actions:

1. Check your domain status.

Use NiceNIC WHOIS Lookup to confirm whether your domain actually shows serverHold.

2. Contact your registrar.

If your domain is registered with NiceNIC, sign in to submit a support ticket. If you cannot access your account, use the official NiceNIC contact page.

For domains registered elsewhere, contact the current registrar of record.

3. Provide the details needed for investigation.

Include your domain name, the exact status code, when the issue started, and any registry or registrar notifications you’ve received.

If your website or email is currently unavailable, mention that impact in your ticket.

Important: Don’t repeatedly change your nameservers or DNS records in an attempt to remove serverHold. First identify the reason for the registry-level restriction.

What Does serverHold Mean?

According to ICANN's EPP Status Code Guide, serverHold is a status controlled by the registry operator.

For .COM and .NET, the registry operator is Verisign.

When this status is applied, the domain is not activated in the registry’s DNS zone, even if nameservers have been configured.

This can affect the website, email delivery, and other services that depend on normal domain resolution.

serverHold vs. clientHold

These two statuses may have similar effects, but different parties control them.

Why the difference matters: A registrar may be able to remove its own clientHold after the applicable issue is resolved. A registry-imposed serverHold requires the registry’s restriction to be removed.

Your registrar can help investigate and coordinate the necessary steps, but it cannot simply override the registry’s decision.

For more information, read ClientHold and ServerHold Explained.

Why Were Some New .COM and .NET Domains Put on serverHold in 2016?

This article was originally published on August 1, 2016, following a NiceNIC inquiry to Verisign about newly registered .COM and .NET domains placed on serverHold.

Verisign’s correspondence referred to an operational policy update effective July 18, 2016.

The update required certain registrars covered by the policy to comply with additional verification requirements associated with China’s Ministry of Industry and Information Technology (MIIT), including real-name and domain-name verification codes.

Some affected registrations therefore required additional compliance processing.

However, the historical notice does not mean that every newly registered .COM or .NET domain is automatically placed on serverHold today.

It also does not establish a universal waiting period after which the restriction will disappear.

For a current serverHold case, the actual reason must be confirmed with the registrar and, where necessary, the registry.

Why Might a .COM or .NET Domain Be on serverHold Today?

There are several possible explanations.

Registration or identity verification

The domain may be subject to additional verification or registration-data requirements under an applicable registry policy or legal obligation.

Security or abuse concerns

A registry may apply restrictions while reviewing a security threat or suspected misuse.

Legal or compliance requirements

A court order, applicable law, or another registry-level compliance requirement may affect the registration.

Delegation or operational issues

In some situations, missing delegation information or another registry-level condition may need clarification.

The status alone doesn’t tell you which explanation applies.

A registration-data problem also doesn’t always lead to serverHold; some suspensions use registrar-level statuses instead.

Don’t treat a registry hold as proof of wrongdoing, and don’t assume every hold is a temporary technical delay.

How to Resolve serverHold: Four Steps

Step 1: Confirm the Status and Registrar

Check the domain through WHOIS or RDAP.

Look for:

• The exact EPP status code
• The current registrar of record
• The expiration date
• Available nameserver information

If you see clientHold instead of serverHold, the troubleshooting process may be different.

If you’re unsure what the result means, share the status information with your registrar.

Step 2: Check Official Notifications

Review messages in your registrar account and any notices received about the affected domain.

Look for requests involving identity verification, inaccurate registration information, security investigations, or missing documentation.

Be careful with unexpected emails asking for sensitive information.

Verify the request through the registrar’s official support channel before submitting documents or following unfamiliar links.

Step 3: Request a Specific Explanation

If the domain is managed by NiceNIC, submit a ticket asking the support team to review the registry-level status.

Your message should include the domain name and relevant evidence.

You can use this short request:

My domain example.com currently shows serverHold. Could you please help confirm the reason for the restriction, whether any verification or corrective action is required, and the next steps for registry review? My website/email is currently affected.

Replace example.com with your actual domain and describe the affected services accurately.

If the case involves an abuse or security investigation, provide the supporting information requested through the authorized private channel.

If the restriction appears to be incorrect, ask for a review and explain why, with relevant evidence.

Avoid sending passwords, private keys, or sensitive identity documents through public forums or social media.

Step 4: Complete the Requirements and Verify Recovery

Follow the applicable verification or corrective process.

Depending on the case, this might involve updating registration information, providing documentation, addressing a security issue, or waiting for a registry review after submitting the required evidence.

There is no universal guaranteed removal time for serverHold.

Once the status is removed, check that:

• The domain no longer shows serverHold.
• Its DNS delegation has been restored.
• The website opens correctly.
• Email and other affected services are functioning.

Some cached DNS information may take time to update after delegation is restored.

If your domain remains unavailable after the hold is removed, ask the registrar or DNS provider to help determine whether there is a separate configuration issue.

Common Questions About serverHold

Will serverHold disappear automatically?

Not necessarily. Some cases may be resolved after the required processing, while others need verification, corrective action, or registry review. Do not rely on waiting alone.

Can NiceNIC remove serverHold immediately?

NiceNIC can investigate the issue and help coordinate the applicable process. However, serverHold is controlled by the registry, and NiceNIC cannot guarantee immediate removal of a registry-imposed restriction.

Does serverHold mean my domain is deleted?

No. The status alone does not mean the registration has been deleted. However, the domain may be unavailable through normal DNS resolution while the hold remains.

Continue checking its expiration date and renewal requirements.

Can I fix serverHold by changing nameservers?

Changing DNS records alone will not override a registry-imposed hold.

If missing delegation information is the underlying issue, your registrar can explain what nameserver information is required. Otherwise, the reason for the hold must be addressed through the appropriate registry process.

Need Help With a .COM or .NET serverHold?

The most useful first step is to identify the reason for the restriction.

A serverHold may affect your website or email, but the status code alone doesn’t explain the complete situation.

If your domain is registered with NiceNIC:

Check Your Domain Status — Confirm the current status code.

Submit a Support Ticket — Sign in and provide the affected domain name, notifications, and relevant details.

Contact NiceNIC — Use an official contact option if you're unable to access your account.

You can also consult NiceNIC's registry-level serverHold troubleshooting guide for additional background on registry-specific review procedures.

The key is to resolve the underlying issue—not simply wait for the status to change.