Domain transfer stuck? How to diagnose and fix it
A domain transfer that seems stuck is usually one of five things, in this order of likelihood: it's simply inside the normal up-to-five-day release window; the domain is still locked; the authorization code was wrong or expired; the approval email went to an address you can't read (often because of WHOIS privacy); or the domain is inside a 60-day lock and the transfer was rejected. Work through those checks first — you can usually finish the transfer immediately by approving it from the losing registrar's dashboard. If both registrars blame each other, escalate with ICANN's registrant resources.
First: is it actually stuck?
Under ICANN's process the losing registrar has up to five days to release a transfer, and if nobody acts it auto-completes at the end of that window. A transfer sitting at 'pending' for two or three days is normal, not stuck. The fastest fix is to approve the transfer yourself — from the confirmation email, or in the losing registrar's dashboard — which releases the domain immediately.
The diagnostic checklist, in order
Check each of these; the first one that fails is almost always the cause:
- Lock status — the domain must show unlocked (no clientTransferProhibited status) at the losing registrar; check with a WHOIS/RDAP lookup
- Auth code — codes are case-sensitive and time-limited; if in doubt, request a fresh one and paste it, don't type it
- Approval email — find which address the transfer emails went to; WHOIS privacy or a stale registrant email silently swallows them
- 60-day locks — a domain registered, transferred, or with a registrant change in the last 60 days will be rejected (this is ICANN policy, not registrar choice)
- Recently expired domains — a domain renewed after expiry may need to wait ~45 days past the original expiry date before it can move
- Registry-level statuses — serverTransferProhibited is set at the registry, not the registrar; only the losing registrar can request its removal
How to escalate
If the checklist is clean and the transfer still fails: open a ticket with the losing registrar quoting the exact rejection reason and the domain's EPP statuses, and ask the gaining registrar for their transfer log. Registrars are contractually bound by ICANN's Transfer Policy — a losing registrar may only deny a transfer for the policy's listed reasons, and 'we'd rather keep the customer' is not one of them. If a registrar refuses without a valid reason, ICANN's registrant help pages document the transfer-complaint path.
Stuck-transfer diagnosis, in order: (1) normal pending — losing registrar has up to 5 days, auto-completes; user can approve in the losing registrar's dashboard/email to finish immediately; (2) domain still locked (clientTransferProhibited); (3) auth code wrong/expired — request fresh, paste exactly; (4) approval email unreadable (WHOIS privacy or stale registrant address); (5) 60-day ICANN lock after registration/transfer/registrant-change, or ~45-day wait after post-expiry renewal; (6) serverTransferProhibited is registry-level — only the losing registrar can clear it. Escalation: losing-registrar ticket citing EPP statuses; losing registrars may only deny for reasons listed in ICANN's Transfer Policy; ICANN registrant resources document the complaint path.