Transfer Prohibited? How to Actually Transfer Your Domain
A rejected domain transfer almost always traces to one of three blocks: a registrar lock you can remove in a minute, a registry lock that takes a request cycle, or an ICANN-mandated 60-day restriction that nobody can remove. Diagnosing which one you're facing is the whole game.
Start with an RDAP or WHOIS lookup and read the status codes.
Block 1: clientTransferProhibited — removable in minutes
This registrar-set lock is the default state at most registrars and the most common transfer blocker. Log in to the losing registrar, find the domain's lock setting ("Transfer Lock" / "Domain Lock"), and turn it off. While you're there, request the transfer authorization code — the gaining registrar needs it to start the transfer.
Block 2: serverTransferProhibited — a registry request cycle
If RDAP shows serverTransferProhibited, the registry set the block and the registrar toggle won't clear it. If it's a registry lock service you purchased, run its verified unlock procedure. If you never requested it, ask your registrar why it's there — legal disputes and redemption states are the usual causes, and the code stays until the registry lifts it. Either way, removal routes through your registrar and takes longer than a client-side unlock.
Monitor every domain status automatically
Sourdough pulls live RDAP status for every domain you track and flags anything unusual — holds, locks, redemption — before it becomes a problem. 7 days free, then $10/mo. $0 due today.
Block 3: the 60-day rules — wait them out
ICANN's Transfer Policy imposes two waiting periods that no unlock removes: no transfer within 60 days of the initial registration, and no transfer within 60 days of a previous inter-registrar transfer. Separately, after a change to registrant contact information, many registrars apply a 60-day transfer lock — some let you opt out of that one before making the change, so if a contact update is coming, ask first.
If your transfer is rejected and the domain was recently registered, transferred, or had its registrant details changed, this is your answer. Plan the transfer for after day 60.
The full pre-transfer checklist
- •Confirm the domain is more than 60 days past registration or its last transfer.
- •Remove clientTransferProhibited at the losing registrar; verify in RDAP that the status is gone.
- •Get the authorization (auth/EPP) code from the losing registrar.
- •Make sure the registrant email on file is one you can read — transfer confirmations may go there.
- •Don't change registrant contact data right before transferring — it can trigger a fresh 60-day lock.
- •Initiate at the gaining registrar, then approve explicitly at the losing registrar to skip the up-to-five-day pendingTransfer wait.
- •After completion: re-lock the domain, verify nameservers survived, and note the new expiry date — gTLD transfers typically add a year.
Frequently Asked Questions
Why is my domain transfer being rejected?
Check RDAP status codes first: clientTransferProhibited means unlock at your registrar; serverTransferProhibited means a registry-level block. If neither is present, you're likely inside a 60-day window after registration, a prior transfer, or a registrant contact change.
Can I bypass the 60-day transfer lock?
The post-registration and post-transfer 60-day restrictions come from ICANN policy and can't be waived. The 60-day lock after registrant contact changes is registrar-implemented, and some registrars offer an opt-out at the time of the change — but not retroactively.
Does transferring a domain risk losing registration time?
No — for gTLDs a successful transfer typically adds a year to the existing term (up to the 10-year cap). Time you've already paid for carries over.