Most domain transfers finish quietly in a few days, but sometimes the new registrar simply reports "transfer rejected" with no explanation. There is no need to panic. Nearly all rejections come down to a handful of known causes, and owners can fix most of them in minutes. Start by checking the domain's current state:
whois example.com | grep -iE "status|creation date|expiry date|registrar:"
curl -s https://rdap.org/domain/example.com | jq '{status: .status, events: .events}'1. The domain is transfer-locked
The most common cause. Many registrars enable a transfer lock by default, shown in WHOIS as clientTransferProhibited, and the registry rejects any request while it is on. Remove the lock at the current registrar, wait for WHOIS to update, then restart the transfer.
2. The Auth code is wrong or outdated
Copying can add spaces, change letter case or mix up similar characters, and some registrars issue a new code on every request, invalidating the old one. Get a fresh code, paste it rather than retyping, and use it promptly.
3. The 60-day restriction has not passed
In generic zones, transfers are usually denied within 60 days of registration, a previous transfer or an owner change. You can calculate the first from the WHOIS creation date; confirm owner-change locks with the registrar. Meanwhile you can still change DNS and name servers, so the site keeps working.
4. The domain has expired or is in redemption
An expired domain moves through a grace period, a redemption period and pending deletion. Statuses such as redemptionPeriod or pendingDelete block transfers. Restore or renew the domain at the current registrar first, and renew before transferring if expiry is only days away.
5. The confirmation email never arrived
Some registrars email the WHOIS contact to confirm a transfer. If the address belongs to a former employee or a dead domain, nobody confirms and the transfer is cancelled. Privacy proxies that do not forward mail cause the same problem. Check the contact email and spam folder, and temporarily disable privacy if needed.
6. A dispute or registry lock exists
serverTransferProhibited means the registry, not the registrar, set the lock, usually because of a trademark dispute, court order or abuse investigation. It cannot be removed from a registrar panel. Registrars may also hold domains with reversed payments or open billing disputes.
7. The zone or registrar does not support the transfer
Not every registrar works with every zone. If the new registrar lacks accreditation or does not accept transfers for that zone, the request fails immediately. Country-code zones may follow entirely different rules; in .uz, changing registrars follows the registry's own procedure and may require extra documents or confirmation.
Example: a private clinic's domain
A private clinic in Fergana tried to transfer misol.com and was rejected twice. The domain was still locked, and the WHOIS email belonged to a former IT contractor. The lock was removed and the email changed to admin@misol.uz, but that edit counted as an owner change and triggered a 60-day lock. The lessons: keep contacts up to date long before a transfer, and ask whether your registrar lets you opt out of the lock when editing details.
Pre-transfer checklist
For domains in the sayt.uz cabinet, most of these items are visible on the domain page; support can confirm the rest.
- Transfer lock off, no
clientTransferProhibitedin WHOIS. - A fresh, correctly copied Auth code.
- 60 days passed since registration, transfer or owner change.
- Enough time left before expiry.
- A working contact email.
- No server-level lock or open dispute.
- The new registrar accepts transfers for your zone.