← Back to Learning Hub

DNS Migration • Intermediate • 6 min read

EPP Domain Status Codes Explained: clientTransferProhibited and More

A reference for the EPP status codes in WHOIS: clientTransferProhibited, serverHold, pendingDelete, autoRenewPeriod, and what each one blocks or signals.

EPP domain status codes are the short labels you see in a WHOIS record, like clientTransferProhibited, serverHold, or pendingDelete, that tell you what can and cannot be done to a domain right now. They come from the Extensible Provisioning Protocol, the system registrars and registries use to manage domains, and each one either reports a state or actively blocks an operation. This guide is a plain-language reference to the codes you will actually encounter: what each means, who sets it, and what it stops.

What EPP status codes are

EPP is defined across several RFCs, with domain statuses in RFC 5731 and the grace-period statuses in RFC 3915 (both current as of November 2026). Every registered domain carries one or more status codes at all times, and they surface in WHOIS and RDAP output. Reading them tells you a lot in one glance: whether the domain is locked against transfer, frozen from updates, resolving normally, or sliding toward deletion.

The codes split into three families by who sets them and why. Client codes are set by the registrar (your provider), server codes are set by the registry (the operator of the TLD), and pending and grace-period codes describe a transition the domain is moving through.

Client codes: set by your registrar

Client codes begin with the word "client" and are controlled by the registrar, usually on the owner's behalf as a security measure. You can typically turn them on and off yourself in the registrar's control panel.

CodeSet byWhat it blocks or signals
clientTransferProhibitedRegistrarBlocks transfer to another registrar; the main anti-hijack lock
clientUpdateProhibitedRegistrarBlocks changes to the domain's details, including nameservers
clientDeleteProhibitedRegistrarBlocks deletion of the domain
clientRenewProhibitedRegistrarBlocks renewal requests
clientHoldRegistrarTells the registry to stop publishing the domain in DNS; it stops resolving

clientTransferProhibited is the one you want on by default. It is not a problem; it is a feature, the lock that stops someone who gains brief access from spiriting your domain away to another registrar. clientHold is the serious one here, because it pulls the domain out of the zone and it stops resolving entirely.

Server codes: set by the registry

Server codes begin with "server" and are applied by the registry itself. You cannot remove these on your own; they usually reflect a dispute, a legal hold, or a registry-level action, and clearing them means working through your registrar and sometimes the registry.

  • serverTransferProhibited: the registry blocks transfer, often during the first 60 days after registration or a prior transfer, or because of a dispute.
  • serverUpdateProhibited: the registry blocks all changes, frequently tied to a legal or abuse matter.
  • serverDeleteProhibited: the registry blocks deletion, protecting a domain under investigation or dispute.
  • serverRenewProhibited: the registry blocks renewal.
  • serverHold: the registry removes the domain from the zone so it stops resolving; a strong signal of a suspension or dispute.

Seeing a server-prefixed prohibition is a cue to find out why. It almost always means an external process, a UDRP dispute, a court order, or a registry compliance action, rather than something you toggled.

Pending and grace-period codes

These describe a domain in motion. The pending codes come from EPP; the grace-period codes come from the Registry Grace Period protocol (RFC 3915) but appear in the same WHOIS status list.

  • ok (also shown as "active"): no pending operations and no prohibitions. Oddly, a bare "ok" means no transfer lock is set, so it is less protected than a domain showing clientTransferProhibited.
  • inactive: the domain has no nameservers delegated.
  • pendingTransfer: a transfer to another registrar is in progress and awaiting completion.
  • pendingDelete: the domain is scheduled for deletion. After the redemption window it sits here for about five days, then drops.
  • pendingRestore: a deleted domain is being recovered during its redemption period.
  • autoRenewPeriod: a grace window, typically up to 45 days, after an automatic renewal during which the registrar can reverse the charge.
  • redemptionPeriod: the domain expired and was deleted, but can still be restored, usually for about 30 days, often at a premium fee.
  • addPeriod: the short grace window just after initial registration during which a deletion is refunded.

How to read a domain's status

  1. Pull the WHOIS or RDAP record and find the status lines.
  2. Separate them by prefix: client codes you can change, server codes you cannot, pending and grace codes describe a transition.
  3. Check for clientTransferProhibited; its presence is good and its absence is worth fixing.
  4. Treat any clientHold or serverHold as urgent, because the domain is not resolving.
  5. If you see server-prefixed prohibitions, contact your registrar to learn the underlying reason.
$ whois example.com | grep -i "status:"
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited

Why these codes matter for security and transfers

The client prohibitions are your first line of defense against domain hijacking. Keeping clientTransferProhibited, clientUpdateProhibited, and clientDeleteProhibited enabled means an attacker who briefly compromises an account still cannot move, alter, or delete the domain without first clearing the locks, which buys time and triggers alerts. The flip side is that these same locks will block a transfer you actually want, so you must lift them, and clear any 60-day registry-level serverTransferProhibited, before initiating one. For the full mechanics, our guide on transferring a domain between registrars walks through unlocking and auth codes, and the domain lifecycle after expiry explains how autoRenewPeriod, redemptionPeriod, and pendingDelete chain together.

To see the live status codes on any domain, including whether its transfer lock is on, run the name through the Valla DNS WHOIS search tool and read the status lines directly from the registry answer.

Is clientTransferProhibited a problem I need to fix?

No, it is a protective lock you generally want on. It stops a domain from being transferred to another registrar without your action, which defends against hijacking. You only remove it, temporarily, when you intend to transfer the domain yourself.

What is the difference between client and server status codes?

Client codes are set by your registrar and you can usually toggle them in your control panel. Server codes are set by the registry operating the TLD and cannot be removed by you; they typically reflect disputes, legal holds, or registry compliance actions.

My domain shows serverHold and stopped resolving. What happened?

serverHold means the registry pulled the domain from the zone, so DNS no longer answers for it. It usually signals a suspension, dispute, or compliance issue, and clearing it requires working through your registrar to resolve the underlying cause.

What does pendingDelete mean and can I still save the domain?

pendingDelete means the domain is in the final roughly five-day stage before it is released, after the redemption period has already passed. At that point it generally cannot be restored; recovery had to happen earlier, during redemptionPeriod.

Why does a status of "ok" mean my domain is less protected?

A plain "ok" status means there are no pending operations and, importantly, no transfer lock set. Because clientTransferProhibited is absent, the domain is more exposed to an unauthorized transfer than one that shows the lock, so adding the lock is worthwhile.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.