X
What clientHold and serverHold Mean
clientHold and serverHold are status codes that can prevent a domain from resolving in DNS. clientHold is usually applied by the registrar. serverHold is usually applied by the registry. Website and email may stop working until the underlying issue is resolved and the hold is removed.
Who This Guide Is For
This guide is for:
· Domain owners checking a domain status code
· Users whose website or email stopped resolving
· Customers preparing renewal or transfer
· Agencies and resellers managing client domains
· Support teams troubleshooting status-related cases
· Domain investors monitoring portfolio risk
This guide explains practical steps and support expectations. Exact behavior may vary by TLD, account status, registry rules, payment method, registrar workflow, hosting provider, DNS provider, or supported NiceNIC feature.
Before You Start
Before you begin, prepare:
· Domain name
· Current registrar
· RDAP or lookup result
· Current status codes
· Expiration date
· Nameservers
· Whether website or email is affected
· Recent transfer, renewal, contact update, or abuse notice
· NiceNIC account username or email if managed at NiceNIC
Important: Confirm the current status inside your NiceNIC account or through the official support channel before making high-impact changes such as payments, transfer requests, nameserver changes, contact updates, or abuse remediation.
Step-by-Step Instructions
Step 1: Check whether the hold is clientHold or serverHold
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Use the account panel, RDAP, order history, or support ticket information as the source of truth.
· Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance.
Step 2: Read registrar or registry notices carefully
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 3: Identify whether the cause is abuse, verification, documents, billing, or policy review
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Collect exact URL, screenshots, timestamps, headers, scan results, or cleanup proof where relevant.
· Use official abuse or support channels and avoid sending passwords or EPP codes.
Step 4: Do not keep changing DNS before resolving the hold
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Back up existing DNS records before changing nameservers or DNS settings.
· Test website and email separately after the change.
Step 5: Fix the underlying issue
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 6: Prepare evidence or documents
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 7: Contact official support
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 8: Test website and email after hold removal
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Troubleshooting
Domain shows a lock but transfer is not needed
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Website is down but DNS records look correct
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Status code changed after a recent update
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
RDAP and registrar account show different timing
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Customer does not know current registrar
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Domain is close to expiration
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Common Mistakes
Mistake 1: Assuming every lock is a suspension
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 2: Changing DNS before checking hold status
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 3: Waiting too long during redemption
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 4: Trying to transfer a domain that is locked or on hold
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 5: Ignoring server-level restrictions
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 6: Not saving status screenshots
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
FAQ
1. What is this article about?
This article explains what clienthold and serverhold mean in a practical NiceNIC Help Center format.
2. What should I check first?
Start with the domain name, account, order or status information, current evidence, and the exact action you want to complete.
3. Can this affect website or email?
Yes, some domain, DNS, renewal, transfer, hold, or nameserver issues can affect website and email. Test both services separately.
4. Should I repeat the same request if it fails?
Not for paid, transfer, renewal, restore, DNS, or compliance-sensitive actions. Confirm the original status first.
5. What evidence should I save?
Save screenshots, order numbers, invoice numbers, transaction IDs, RDAP results, status codes, error messages, and support ticket numbers where relevant.
6. Can NiceNIC support help?
NiceNIC support can review issues for supported accounts, domains, payments, reseller workflows, API or WHMCS actions, and domain management cases where applicable.
7. How does status code fit into this process?
Status code should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
8. How does transfer lock fit into this process?
Transfer lock should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
9. How does hold status fit into this process?
Hold status should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
10. How does redemption fit into this process?
Redemption should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
clientHold and serverHold are status codes that can prevent a domain from resolving in DNS. clientHold is usually applied by the registrar. serverHold is usually applied by the registry. Website and email may stop working until the underlying issue is resolved and the hold is removed.
Who This Guide Is For
This guide is for:
· Domain owners checking a domain status code
· Users whose website or email stopped resolving
· Customers preparing renewal or transfer
· Agencies and resellers managing client domains
· Support teams troubleshooting status-related cases
· Domain investors monitoring portfolio risk
This guide explains practical steps and support expectations. Exact behavior may vary by TLD, account status, registry rules, payment method, registrar workflow, hosting provider, DNS provider, or supported NiceNIC feature.
Before You Start
Before you begin, prepare:
· Domain name
· Current registrar
· RDAP or lookup result
· Current status codes
· Expiration date
· Nameservers
· Whether website or email is affected
· Recent transfer, renewal, contact update, or abuse notice
· NiceNIC account username or email if managed at NiceNIC
Important: Confirm the current status inside your NiceNIC account or through the official support channel before making high-impact changes such as payments, transfer requests, nameserver changes, contact updates, or abuse remediation.
Step-by-Step Instructions
Step 1: Check whether the hold is clientHold or serverHold
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Use the account panel, RDAP, order history, or support ticket information as the source of truth.
· Save screenshots or logs when the result affects billing, transfer, renewal, DNS, or compliance.
Step 2: Read registrar or registry notices carefully
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 3: Identify whether the cause is abuse, verification, documents, billing, or policy review
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Collect exact URL, screenshots, timestamps, headers, scan results, or cleanup proof where relevant.
· Use official abuse or support channels and avoid sending passwords or EPP codes.
Step 4: Do not keep changing DNS before resolving the hold
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Back up existing DNS records before changing nameservers or DNS settings.
· Test website and email separately after the change.
Step 5: Fix the underlying issue
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 6: Prepare evidence or documents
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 7: Contact official support
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Step 8: Test website and email after hold removal
This step helps you handle what clienthold and serverhold mean with a clear, safe, and support-ready workflow.
· Review the account information carefully before acting.
· Keep a written record of the decision, action, and final result.
Troubleshooting
Domain shows a lock but transfer is not needed
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Website is down but DNS records look correct
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Status code changed after a recent update
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
RDAP and registrar account show different timing
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Customer does not know current registrar
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Domain is close to expiration
Possible causes include incomplete evidence, timing differences, account mismatch, unsupported workflow, provider-side restriction, or missing customer action.
What to do:
· Check the official account or order status.
· Collect screenshots, logs, transaction IDs, or status codes.
· Avoid repeating high-impact actions until the original status is confirmed.
· Contact NiceNIC support with complete details if the issue remains unclear.
Common Mistakes
Mistake 1: Assuming every lock is a suspension
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 2: Changing DNS before checking hold status
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 3: Waiting too long during redemption
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 4: Trying to transfer a domain that is locked or on hold
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 5: Ignoring server-level restrictions
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
Mistake 6: Not saving status screenshots
Avoid this mistake by checking the account record, saving evidence, and using the correct workflow before making changes or submitting another request.
FAQ
1. What is this article about?
This article explains what clienthold and serverhold mean in a practical NiceNIC Help Center format.
2. What should I check first?
Start with the domain name, account, order or status information, current evidence, and the exact action you want to complete.
3. Can this affect website or email?
Yes, some domain, DNS, renewal, transfer, hold, or nameserver issues can affect website and email. Test both services separately.
4. Should I repeat the same request if it fails?
Not for paid, transfer, renewal, restore, DNS, or compliance-sensitive actions. Confirm the original status first.
5. What evidence should I save?
Save screenshots, order numbers, invoice numbers, transaction IDs, RDAP results, status codes, error messages, and support ticket numbers where relevant.
6. Can NiceNIC support help?
NiceNIC support can review issues for supported accounts, domains, payments, reseller workflows, API or WHMCS actions, and domain management cases where applicable.
7. How does status code fit into this process?
Status code should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
8. How does transfer lock fit into this process?
Transfer lock should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
9. How does hold status fit into this process?
Hold status should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
10. How does redemption fit into this process?
Redemption should be reviewed in context with the domain status, account settings, order history, and service provider role before action is taken.
Need help? We're always here for you.
Submit a Ticket
- Domain Names
- Registering Domains
- Domain Reseller
- Domain Pricing
- Whois Lookup
- Our Products
- Dedicated Server
- Cloud Server
- SSL Certificates
- Business Email
- Company Profile
- About NiceNIC
- Domain News
- Payment Method
- Legal | Disclosure Requests
- Customer Support
- Help Center
- Submit a Ticket
- Contact Us
- Report Abuse
Copyright © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED All Rights Reserved
