Why you cannot transfer a new domain for 60 days

What the 60-day rule says

The rule comes from ICANN's Transfer Policy. It covers moves of generic domains, such as .com, between registrars. The policy lets your current registrar deny a transfer requested within 60 days of the creation date in the registry record.

The same policy also allows a time-based denial in the first 60 days after a domain arrives from another registrar. In plain words: a name that is brand new, or has just moved, may have to stay put for a while.

The rule is about moving between registrars. It does not stop you changing nameservers, editing DNS records or pointing the domain at your website. Your site and email can work normally during the lock.

Why the lock exists

The lock gives the first registrar time to spot problems with a new order before the name moves on. ICANN's own review work describes the waiting period as partly a window to catch issues linked to card payments.

For an honest small-business owner, this feels like a nuisance. Think of it as a cooling-off window. If something went wrong with the order, there is time to fix it before the name leaves.

A registrant change can start a new lock

There is a second 60-day rule. When the registrant details change, ICANN's policy says the registrar must impose a 60-day transfer lock. In practice this means a change of the owner's name, organisation or email address.

A registrar may let you opt out of this lock. The opt-out must be taken before the change request, and the registrar does not have to offer it. ICANN advises the previous owner to ask for any registrar transfer before the registrant change.

This matters when you buy a domain from someone else. If the name is moving to your name and to a new registrar, order the steps carefully. Our /buy-domain/ guide explains how a purchase normally flows.

When the change-of-registrant lock does not apply

ICANN says the change-of-registrant process, and so its 60-day lock, does not apply in some cases. Examples are an expired registration, a registrar ending the registration agreement, a court order, a UDRP decision or an abuse complaint handled by the registrar.

The first rule is a permission, not a duty. A registrar may deny a transfer in the first 60 days, and some may allow it earlier. Do not count on that. Ask your registrar before you pay for a move.

A transfer can also fail for other reasons, such as a wrong authorisation code. Waiting out the 60 days will not fix those.

What about .pk and .com.pk names

The ICANN policy is written for generic domains. We did not find a published PKNIC document that states a 60-day lock for .pk or .com.pk names, so we will not claim one. Check PKNIC's own rules or ask your registrar before you plan a move.

For .pk, PKNIC fixes the registrant name at registration, and the minimum term is two years. Choose the owner name carefully at the start, because it is hard to alter later. Our /pk-domain-transfer/ page covers moves for Pakistani extensions.

If you are still choosing a name, read /register-pk-domain/ and /pk-vs-com-pk-vs-com/ first.

What to do while you wait

Use the 60 days well. Build the site, set up email and point your DNS. None of that needs a transfer.

Plan your next move early.

If you want a name that is already registered, our marketplace at /#browse holds payment in escrow until the move is done. To check a fresh name, use /domains/. For rupee prices, see /pricing/.

• Register in your own name, so no registrant change is needed later.
• Pick the right registrar the first time and avoid a move altogether.
• Keep the owner email working, since registrar messages and approvals usually go there.
• Note the creation date and add 60 days to find the earliest likely date.

Common questions