Why Can't I Transfer My Domain? The 60-Day Lock Decoded

The message everybody meets eventually

You go to move a domain to a different registrar and the transfer is refused. Nothing is wrong with the name, nothing is overdue, and you have the authorisation code. The registrar tells you the domain is locked for sixty days and there is nothing they can do.

They are telling the truth. This is ICANN policy, not a registrar rule, and no support agent can override it. What follows is what actually triggers it, what does not, and how to sequence a sale or a migration so it never happens to you.

Everything quoted below is from ICANN's own Transfer Policy, checked at icann.org on 6 September 2026.

The four ways a transfer gets refused

ICANN's Transfer Policy separates refusals a registrar must make from ones it may make. Section 3.8 lists the mandatory denials:

Section 3.7 lists the circumstances in which a registrar may deny a transfer, and two of those are the other sixty-day windows people hit:

So there are three distinct sixty-day clocks, and confusing them is why the answers people get online do not match the message on their screen.

The three sixty-day clocks, told apart

Notice the difference in the third column. The first two say the registrar may deny — the policy permits it, and in practice most do. The third says the registrar must deny. That is the one nobody can help you with, and it is also the only one you can do something about, provided you do it before rather than after.

What counts as a Change of Registrant

This is the part that catches sellers. A Change of Registrant is not a transfer between registrars. It is a change to who the policy considers the legal holder of the name — in practice, the registrant's name, organisation, or email address.

What normally does not trigger it: correcting a phone number, updating a postal address for the same registrant, changing nameservers, changing the administrative or technical contact, renewing.

What does: putting somebody else's name on the domain. Which is, of course, exactly what selling a domain looks like if you do it in the obvious order.

If you are unsure whether a specific edit will trigger it at your registrar, ask them before you save the form. Every registrar knows the answer for their own system, and the question costs nothing. Saving the form and finding out costs sixty days.

The opt-out, and its one hard limit

The Transfer Policy allows a registrar to let you opt out — but the timing is absolute. The policy's own wording ties the denial to whether the holder "did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request."

Prior to. Not during, not after. Once the change is processed, the window has closed and the lock runs its course.

Two practical points follow. First, the opt-out is not universally offered — the policy permits registrars to allow it, and not all of them build it. Check whether yours does before you plan around it. Second, if it is offered, it is usually a checkbox on the same form as the change itself, and it is easy to miss while concentrating on getting the new details right.

Why the lock exists, and why that is a reasonable trade

It is worth understanding the threat model, because the lock stops feeling arbitrary once you do.

The classic domain theft is: attacker gets into the registrar account, changes the registrant email to one they control, then immediately transfers the name to a registrar in another jurisdiction. Once the domain has moved and the registrant has changed, unwinding it is slow, expensive and sometimes impossible.

The sixty-day lock breaks that chain at the point where it matters. The attacker can change the details, but they cannot move the name out for two months — which is a long time for the real owner to notice, and for the original registrar to still have the authority to fix it.

The cost of that protection lands entirely on legitimate sellers doing things in the wrong order. That is a genuine cost, and it is a defensible trade.

The right sequence for a sale

If you are handing a domain to a buyer, do it in this order and the lock never appears:

Our guide to selling a domain safely covers the money side of this, and how to transfer a domain covers the registrar mechanics step by step.

The right sequence for a migration

If you are moving registrars for your own reasons — better renewal pricing, consolidating a portfolio, escaping bad support — the rule is simply: do not tidy the contact details on the way out.

Transfer first. Clean up the registrant record afterwards, at the new registrar, once you have no further move planned. It is remarkably common to update an old email address as part of "getting organised", then discover that the tidying blocked the migration it was part of.

Also check the other two clocks before you start. A name you registered last month, or moved last month, may be inside a window the new registrar cannot shorten.

What to check before you touch anything

What the lock does not do

Worth stating plainly, because the message on screen tends to cause panic:

Country-code extensions may not follow this at all

The Transfer Policy is an ICANN policy and binds the generic extensions. Country-code registries set their own transfer rules, and they vary widely — different lock periods, different authorisation mechanisms, sometimes eligibility checks on the incoming holder that have no equivalent in the generic space. If your name is on a country extension, the registry's own published rules are the authority, not this page. Our ccTLD guide covers how much these differ.

The short version

Three sixty-day clocks exist. Two of them you can only wait out. The third — the one that fires when you change who owns the name — is the only one with an escape hatch, and the hatch closes the moment you press save. Transfer first, change ownership second, and the whole subject becomes something you read about rather than something that happens to you.