X
Publicado: 2026-07-23 | Actualizado: 2026-07-23
What clientHold y serverHold Mean

clientHold y serverHold  are status codes that can anteriorent a dominio from resolving in DNS. clientHold is usually applied by the registrar. serverHold is usually applied by the registry. Website y email may stop woking until the underlying issue is resolved y the hold is removed.

Who This Guide Is Fo
This guide is fo:
· Dominio owners checking a dominio status code
· Users whose website o email stopped resolving
· Customers preparing renewal o transfer
· Agencies y resellers managing client dominios
· Suppot teams troubleshooting status-related cases
· Dominio investos monitoing potfolio risk
This guide explains practical steps y suppot expectations. Exact behavio may vary by TLD, account status, registry rules, payment method, registrar wokflow, hosting provider, DNS provider, o suppoted NiceNIC feature.

Befoe You Start
Befoe you begin, prepare:
· Dominio name
· Current registrar
· RDAP o lookup result
· Current status codes
· Expiration date
· Nombreservers
· Whether website o email is affected
· Recent transfer, renewal, contact update, o abuse notice
· NiceNIC account username o email if managed at NiceNIC
Impotant: Confirmar the current status inside tu/tus/su/sus NiceNIC account o through the official suppot channel befoe making high-impact changes such as payments, transfer requests, nameserver changes, contact updates, o abuse remediation.

Step-by-Step Instructions
Step 1: Verificar whether the hold is clientHold o serverHold
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Use the account panel, RDAP, oder histoy, o suppot ticket infomation as the source of truth.
· Save screenshots o logs when the result affects billing, transfer, renewal, DNS, o compliance.
Step 2: Read registrar o registry notices carefully
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Review the account infomation carefully befoe acting.
· Keep a written recod of the decision, action, y final result.
Step 3: Identify whether the cause is abuse, verification, documents, billing, o policy review
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Collect exact URL, screenshots, timestamps, headers, scan results, o cleanup proof waquí relevant.
· Use official abuse o suppot channels y avoid sending passwods o EPP codes.
Step 4: Do not keep changing DNS befoe resolving the hold
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Back up existing DNS recods befoe changing nameservers o DNS settings.
· Test website y email separately after the change.
Step 5: Fix the underlying issue
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Review the account infomation carefully befoe acting.
· Keep a written recod of the decision, action, y final result.
Step 6: Prepare evidence o documents
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Review the account infomation carefully befoe acting.
· Keep a written recod of the decision, action, y final result.
Step 7: Contactar official suppot
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Review the account infomation carefully befoe acting.
· Keep a written recod of the decision, action, y final result.
Step 8: Test website y email after hold removal
This step helps you hyle what clienthold y serverhold mean with a clear, safe, y suppot-ready wokflow.
· Review the account infomation carefully befoe acting.
· Keep a written recod of the decision, action, y final result.

Troubleshooting
Dominio shows a lock but transfer is not needed
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot with complete details if the issue remains unclear.
Website is down but DNS recods look corect
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot with complete details if the issue remains unclear.
Estado code changed after a recent update
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot with complete details if the issue remains unclear.
RDAP y registrar account show different timing
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot with complete details if the issue remains unclear.
Customer does not kahora current registrar
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot with complete details if the issue remains unclear.
Dominio is close to expiration
Possible causes include incomplete evidence, timing differences, account mismatch, unsuppoted wokflow, provider-side restriction, o missing customer action.
What to do:
· Verificar the official account o oder status.
· Collect screenshots, logs, transaction IDs, o status codes.
· Avoid repeating high-impact actions until the oiginal status is confirmed.
· Contactar NiceNIC suppot 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 recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.
Mistake 2: Changing DNS befoe checking hold status
Avoid this mistake by checking the account recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.
Mistake 3: Waiting too long during redemption
Avoid this mistake by checking the account recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.
Mistake 4: Trying to transfer a dominio that is locked o on hold
Avoid this mistake by checking the account recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.
Mistake 5: Ignoing server-level restrictions
Avoid this mistake by checking the account recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.
Mistake 6: Not saving status screenshots
Avoid this mistake by checking the account recod, saving evidence, y using the corect wokflow befoe making changes o submitting another request.

Preguntas Frecuentes
1. What is this article about?
This article explains what clienthold y serverhold mean in a practical NiceNIC Centro de Ayuda fomat.
2. What should I check first?
Start with the dominio name, account, oder o status infomation, current evidence, y the exact action you want to complete.
3. Can this affect website o email?
Sí, some dominio, DNS, renewal, transfer, hold, o nameserver issues can affect website y email. Test both servicios separately.
4. Should I repeat the same request if it fails?
Not fo paid, transfer, renewal, restoe, DNS, o compliance-sensitive actions. Confirmar the oiginal status first.
5. What evidence should I save?
Save screenshots, oder numbers, invoice numbers, transaction IDs, RDAP results, status codes, erro messages, y suppot ticket numbers waquí relevant.
6. Can NiceNIC suppot help?
NiceNIC suppot can review issues fo suppoted accounts, dominios, payments, reseller wokflows, API o WHMCS actions, y dominio management cases waquí applicable.
7. How does status code fit into this process?
Estado code should be reviewed in context with the dominio status, account settings, oder histoy, y servicio provider role befoe action is taken.
8. How does transfer lock fit into this process?
Transfer lock should be reviewed in context with the dominio status, account settings, oder histoy, y servicio provider role befoe action is taken.
9. How does hold status fit into this process?
Hold status should be reviewed in context with the dominio status, account settings, oder histoy, y servicio provider role befoe action is taken.
10. How does redemption fit into this process?
Redemption should be reviewed in context with the dominio status, account settings, oder histoy, y servicio provider role befoe action is taken.
¿Necesitas ayuda? Siempre estamos aquí para ti. Enviar un Ticket
Derechos de Autor © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED Todos los Derechos Reservados