Also called registry-level lock
Registry lock, explained
It appears in registry data as the statuses serverTransferProhibited, serverUpdateProhibited and serverDeleteProhibited. A registrar lock, clientTransferProhibited, is different: you can switch it off from your registrar account, so anyone who takes over that account can too. With registry lock, the registrar has to forward a request to the registry and wait for it to lift the restriction, and providers verify the request through a separate, pre-agreed channel first. Not every registry or registrar offers it; Cloudflare, for example, provides it to Enterprise customers with high-profile domains.
For investors, registry lock makes sense on the few names whose loss would hurt most, such as high-value one-word or short .coms. The cost is speed: lifting the lock takes time, so plan for it before a sale closes and tell the buyer or escrow service, or the deal can stall at the transfer step. AI-generated messages and cloned voices make social-engineering attacks on registrar accounts more convincing, which strengthens the case for a lock that needs more than account access to remove.
Example. Before the sale closed, the seller asked the registrar to lift the registry lock early, so the transfer would not stall.
Free to read, no signup. The list is for news of the course itself.
Join the waitlistSources
Education, not financial, legal or tax advice. Domain investing is speculative and most domain names never sell. Read the disclaimer.
