Why Can't I Transfer My Domain? The 60-Day Lock Decoded
By Thomas Lovas Lokoy — researched and drafted with AI assistance, then fact-checked and approved by Thomas before publishing · Editorial policy
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:
- "A pending UDRP proceeding that the Registrar has been informed of."
- "Court order by a court of competent jurisdiction."
- "Pending dispute related to a previous transfer pursuant to the Transfer Dispute Resolution Policy."
- "URS proceeding or URS suspension that the Registrar has been informed of."
- "The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request."
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:
- "The transfer was requested within 60 days of the creation date as shown in the registry Whois record for the domain name."
- "A domain name is within 60 days (or a lesser period to be determined) after being transferred."
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
| Clock | Starts when | Policy basis | Can you avoid it |
|---|---|---|---|
| New registration | You first register the name | 3.7.5 — registrar may deny | No. Wait it out. |
| Recent transfer | You moved the name to this registrar | 3.7.6 — registrar may deny | No. Wait it out. |
| Change of Registrant | You changed who the registrant is | 3.8.5 — registrar must deny | Yes, but only in advance |
Notice the difference in the third column. The first two say the registrar may deny — the policy permits it, and whether a given registrar does is set out in its own terms, so check them. 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:
- Both parties at the same registrar? Use an internal account push. The name moves between accounts without an inter-registrar transfer at all, so no transfer lock is in play. This is the fastest and safest option and it is why experienced sellers ask which registrar the buyer uses before agreeing anything.
- Different registrars? Transfer the domain to the buyer's registrar first, while you are still the registrant, then let them update the registrant details afterwards. The change of registrant then happens at their end, on a domain that is already where it needs to be.
- Must change the registrant first? Exercise the opt-out on the same form, before saving.
- Already locked? Wait. The domain still works — the lock only blocks inter-registrar transfer, not DNS, not renewal, not contact updates. Agree with the buyer in writing what happens in the interim, and make sure escrow release terms reflect the actual delivery date.
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 is today's date relative to the creation date and the last transfer date? Both are in the public registration record.
- Does your registrar offer the Change of Registrant opt-out? Ask in writing, keep the answer.
- Is there any dispute pending? A UDRP or URS proceeding the registrar knows about is a mandatory denial and it outranks everything else here. See what happens in a UDRP dispute.
- Is the domain unlocked, is DNSSEC handled, and do you have the authorisation code? These are the ordinary transfer prerequisites, and they are separate from the sixty-day question.
- Are you certain of the buyer's registrar? Get it before you agree the mechanism, not after.
What the lock does not do
Worth stating plainly, because the message on screen tends to cause panic:
- It does not stop the site working, the mail flowing, or DNS changes.
- It does not stop renewal, and it does not affect the expiry date.
- It does not stop an internal push to another account at the same registrar in most cases — though registrars differ here, so ask rather than assume.
- It does not stop you selling. It stops the domain moving registrars for sixty days, which is a scheduling problem, not a legal one.
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.
Is ICANN getting rid of the 60-day lock?
Yes, but the change is not in force yet. ICANN's Transfer Policy Review working group recommended "eliminating from the future Change of Registrant Data Policy the requirement that the Registrar impose a 60-day inter-Registrar transfer lock following a Change of Registrant" (recommendation 26.4 in its final report). The same report recommends replacing the new-registration window with a fixed 720-hour (30-day) restriction from the creation date.
Where that stands, checked on ICANN's own sites on 4 October 2026:
- The GNSO Council adopted the final report on 12 March 2025 and sent its recommendations report to the ICANN Board on 10 April 2025, according to the GNSO project page.
- The same page still lists the ICANN Board resolution, the notice of policy actions and the implementation details as "TBD".
- ICANN's current Transfer Policy still contains the 60-day Change of Registrant lock and its opt-out.
Until ICANN publishes an effective date for the revised policy, registrars apply the rules described above, so plan a sale or migration around the lock as it exists today, and check the GNSO page for the current status before you rely on a change that has not yet taken effect.
A worked example, with dates
Suppose you register a .com on 1 March 2026 and change the registrant on 10 June 2026 without opting out.
| Event | Date | What the 60 days mean |
|---|---|---|
| Domain created | 1 March 2026 | The registrar may refuse a transfer requested before 30 April 2026 (60 days after the creation date) |
| Registrant changed, no opt-out | 10 June 2026 | The registrar must refuse inter-registrar transfers until 9 August 2026 |
| Transfer to a new registrar completes | Any later date | The new registrar may refuse a further transfer for 60 days after it |
If the working group's proposed 720-hour (30-day) window from creation were adopted as recommended, the first line would end on 31 March 2026 instead; until the new policy is in force, plan on the current rules. For a sale, the table is the argument for transferring first: a transfer started on 1 June, before the change of registrant, avoids the second clock entirely. How to sell a domain name safely puts that order into a full sale checklist.
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.
Frequently asked questions
Why can I not transfer my domain for 60 days?
One of three things has happened within the last 60 days: the domain was registered, it was transferred between registrars, or its registrant details changed without an opt-out. ICANN's Transfer Policy lets the registrar refuse a transfer in the first two cases and requires it to refuse in the third.
Does changing my email address trigger the 60-day lock?
A material change to the registrant's name, organisation or email address counts as a Change of Registrant under the current policy, so it can. Many registrars offer an opt-out, which must be selected before you make the change, not after.
Can a registrar remove the 60-day lock?
For the change-of-registrant lock, only if you opted out before the change. For the post-registration and post-transfer windows, the policy lets the registrar refuse a transfer rather than requiring it to, so some registrars will allow an earlier transfer; ask yours.
Is ICANN removing the 60-day lock?
ICANN's Transfer Policy Review working group recommended removing the change-of-registrant lock, and the GNSO Council adopted its final report on 12 March 2025. The current Transfer Policy still contains the lock, so plan as if it applies until your registrar confirms otherwise.
Do country-code domains have the same 60-day rules?
Not necessarily. ICANN's Transfer Policy covers generic extensions such as .com; each country-code registry sets its own transfer rules, so check the registry's policy for the extension you hold.
Sources
Last updated:
