The update lock: the registry refuses changes to the domain’s registration — its nameservers, its contacts, its other statuses. It protects against a hijacker pointing the domain elsewhere. It does not touch the DNS records at your DNS host: those change as usual.
WHOIS: Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited RDAP: "client update prohibited" WHOIS: Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited RDAP: "server update prohibited"
| Status | clientUpdateProhibited, serverUpdateProhibited |
| Set by | The registrar or the registry |
| Website and email | Keep working |
| Blocks | Changes at the registry: nameservers, contacts, other statuses |
| Does not block | DNS records at your DNS host, or renewing |
Check a domain’s statuses
Enter a domain: we ask its registry for every status it has, and say whether clientUpdateProhibited is one of them.
What it means
With the update lock set, the registry rejects every change to the domain except removing the lock itself. The client version is the registrar’s, which many set by default and lift automatically when you change the nameservers in their panel; the server version is the registry’s, usually part of Registry Lock and removed only through the registry’s own check.
Why it is there
- The registrar’s default protection.
- Registry Lock (the server version).
- A dispute over the domain.
What to do
- Changing A, MX or TXT records? Do it at the DNS host — this lock does not apply.
- Changing nameservers or contacts? Do it at the registrar; most lift the client lock for the change on their own. If the change is refused, switch the lock off, make it, and switch it back on.
- For the server version, ask the registrar to request the unlock from the registry.
Sources
Status meaning checked on 25 September 2026 against these official sources:
- EPP Status Codes — icann.org
- RFC 5731 — rfc-editor.org
- Prevent Domain Name Hijacking With Verisign Registry Lock Service — verisign.com