A common frustration: everything is ready to move a domain to another registrar, the transfer code is in hand and the lock is off, yet the request is rejected. Very often the reason is that the domain is still inside a 60-day restriction period. The rule is widely used in generic zones to prevent domain theft and rushed, uncontrolled transfers. Knowing when it starts and ends makes transfers easy to plan.
When the restriction applies
ICANN's Transfer Policy for .com, .net, .org and other generic zones covers several situations, each starting its own 60-day window during which a registrar may deny a transfer. In practice most registrars and registries use this right, so treat it as effectively mandatory.
- Initial registration. A domain usually cannot move to another registrar within 60 days of being registered.
- Previous transfer. After a transfer, the domain cannot move again for 60 days.
- Change of registrant. A material change to the owner's name, organisation or email triggers a 60-day transfer lock. Some registrars let you opt out at the time of the change.
The third case often catches people off guard: renaming the organisation in WHOIS or changing the owner email may count as an owner change. Finish the transfer first, then update contact details.
Why the rule exists
It is mainly protection against hijacking. If an attacker took over an account, changed the owner email and moved the domain at once, the real owner would struggle to get it back. The lock keeps the domain in place long enough for the owner to notice. It also limits fraud with stolen cards: if a payment is reversed, the registrar can only recover the domain while it still holds it.
Calculating the date
Look at the WHOIS dates. For a new registration use the Creation Date; for a transfer or owner change use the transfer date your registrar shows. Then add 60 days:
whois example.com | grep -iE "creation date|updated date|expiry date"
# Linux (GNU date): add 60 days to a date
date -d "2026-09-20 +60 days" +%F
"Updated Date" changes with any edit, including name server changes, so it does not always mark an owner change. Confirm the exact date in your registrar panel or with support, and leave a few days of margin.
Example: a new online shop
A Tashkent clothing shop bought misol.com on a promotion in September. Three weeks later the owner wanted domain, hosting and email in one place and tried to transfer, but the request was denied because 60 days had not passed. The right move is to wait: point DNS records at the new hosting now, launch the site and email immediately, and move the domain itself later. Changing name servers or DNS is not a transfer and can be done at any time. Many owners confuse the two and delay their launch for no reason, when only the registrar move has to wait.
What you can do during the lock
The lock only restricts changing registrars. You can still change name servers, add DNS records, issue SSL certificates and renew the domain; for domains at sayt.uz all of this happens on the domain page in the cabinet. Use the time to prepare: check the contact email, make sure enough registration time remains and set up an account at the new registrar. If you plan to sell the domain, think about the order of steps, since changing the owner first may trigger a new lock.
Rule changes and country-code domains
ICANN has been revising its Transfer Policy, and the new version is expected to change some of these periods and the owner-change lock. Check ICANN's official materials or your registrar for the exact effective date, as older articles may be outdated. Country-code zones, including .uz, are not directly governed by this ICANN policy; their transfer rules come from the zone's own registry, so ask support for the exact conditions before moving a .uz domain.