Domains & DNS

Domain transfer locks: why a transfer is blocked and what to check

Domain transfer locks are designed to prevent unauthorized registrar transfers. A transfer can be blocked by a clientTransferProhibited status, a recent registration/transfer restriction, account/security policy, or missing authorization—not because DNS or web hosting is broken.

Read the current status and transfer eligibility

Inspect registrar status, expiry date, registration/previous-transfer timing, registrant contact access, and any account security holds. Some TLDs have mandatory or registry-defined waiting periods; others use different transfer procedures.

Do not unlock the domain days in advance if you are not ready to initiate the transfer.

Keep DNS independent from registrar movement

A registrar transfer normally does not require changing authoritative nameservers. Preserve current DNS unless moving DNS is a separate planned step.

Save the zone and verify nameserver delegation before transfer so a later account migration does not become an emergency reconstruction.

Handle authorization codes securely

Retrieve the transfer/EPP authorization through the registrar’s secure workflow and provide it only to the intended gaining registrar. Treat it as a credential while it is valid.

Verify administrative email or approval channels are reachable before starting.

Relock and verify ownership after completion

Confirm the gaining registrar account, registrant details, expiry/renewal date, nameservers, auto-renew preference, and transfer lock after the move. Also confirm billing ownership and recovery contacts while the transfer history is fresh.

  • Check eligibility/status first.
  • Do not change DNS unnecessarily.
  • Protect the authorization code.
  • Verify and relock at the gaining registrar.
Related DotMoose serviceExplore DotMoose domains and DNS

Keep reading

Related guides.

More domains & dns →