You found a cheaper registrar — and your domain refuses to move
You compared renewal prices, picked a cheaper registrar, unlocked the domain, got the authorisation code, and filed the transfer. Then the transfer failed — or the new registrar's form told you the domain is not eligible yet. No error you can fix, no button you can press, no support agent who can override it. You have just met the 60-day domain transfer lock: ICANN's mandatory cooling-off period, and the most common reason a transfer that should take five days ends up taking two months.
This guide explains what the lock is, the three things that trigger it, how to tell from your WHOIS record whether you are actually locked (half the people who think they are locked are not), the one legitimate workaround, and the policy change ICANN approved in 2026 that will eventually cut the wait in half — but has not taken effect yet.
Rules checked November 8, 2026, against ICANN's Transfer Policy, registrar documentation from DNSimple and DreamHost, and ICANN Board records of June 7, 2026. Confirm with your registrar before timing a move.
What the 60-day transfer lock actually is
The 60-day transfer lock is a rule in ICANN's Transfer Policy that forbids moving a generic domain (.com, .net, .org, and every other gTLD) from one registrar to another for 60 days after certain events. It is enforced at the registry — the organisation that runs the extension, one level above your registrar — which is why no registrar's support team can lift it, shorten it, or make an exception. Every ICANN-accredited registrar enforces the same rule, so switching registrars does not escape it.
The lock exists for one reason: domain hijacking. If someone compromises your registrar account, they could change your contact email and immediately transfer the domain to a registrar they control, where recovering it becomes slow and expensive. The 60-day window gives the real owner time to notice the compromise and reverse it before the domain can be moved out of reach.
The change-of-registrant version of the lock took effect on December 1, 2016. The current Transfer Policy was updated in February 2024 and became mandatory for all registrars on August 21, 2025 — the same date ICANN's Registration Data Policy took full effect. Under that policy, if the Organization field in a domain's registrant contact details contains a company name, that organisation is treated as the legal owner, so keep the field accurate.
The three things that trigger the lock
For generic domains, exactly three events start a fresh 60-day inter-registrar transfer lock. Nothing else does.
Trigger | Clock starts | Can you avoid it? |
|---|---|---|
New registration | The day you register the domain | No — mandatory, no opt-out |
Completed inter-registrar transfer | The day the transfer lands at the new registrar | No — a fresh 60 days starts after every transfer |
Change of registrant (name, organisation, or email) | The day the contact change is made | Sometimes — opt out before the change, if your registrar offers it |
A new registration locks the domain to the registrar you bought it from for 60 days. This catches bargain hunters: you register a name at a registrar running a $0.99 first-year promo, decide a week later you would rather hold it somewhere cheaper long-term, and discover you cannot move it until day 61.
A completed transfer restarts the clock. Move a domain from GoDaddy to Cloudflare and it is locked at Cloudflare for another 60 days — you cannot immediately bounce it to a third registrar. This is deliberate: it stops stolen domains being laundered through a chain of quick transfers.
A change of registrant is the trap that catches the most people, because it looks like admin. Edit the registrant's name, organisation, or email address and, unless you opted out first, the domain is locked for 60 days. At some registrars, toggling WHOIS privacy on or off counts as a registrant change too, because it swaps the published email — so people trip this lock without realising they changed anything. Note the distinction: changing the registrant triggers the lock; editing the admin or technical contact alone does not, because those are not the registered owner.
Two locks, one confusion: check your WHOIS status codes
Before assuming you are stuck for 60 days, run a WHOIS lookup on your own domain and read the status codes. There are two transfer-blocking codes, and people constantly confuse them:
Status code | Who sets it | What it means | Can you clear it? |
|---|---|---|---|
serverTransferProhibited | The registry | The ICANN 60-day lock is active | No — wait it out |
clientTransferProhibited | Your registrar | The ordinary registrar lock, on by default as a safety measure | Yes — turn it off in your control panel in seconds |
If the only code you see is clientTransferProhibited, you are not stuck at all: flip the transfer lock off in your registrar's control panel and file the transfer. If you see serverTransferProhibited, that is the registry-level ICANN lock, and no support ticket will remove it. Nomlen's free WHOIS checker shows both codes plainly, with the creation and last-updated dates you need to work out when the lock clears.
When exactly does the lock lift?
Count 60 days from the trigger date, not from today — the registration date, the date the last transfer completed, or the date you changed the registrant contact details. Your WHOIS record shows the creation and last-updated timestamps, so you can work it out precisely.
Worked example: register a domain on July 1, and the lock clears on August 30 — 60 days later. There is nothing to file, no button to press, no support ticket to open. The registry drops serverTransferProhibited automatically and you can start the transfer that day. Plan around renewals by working backwards: a transfer takes up to five days to complete (ICANN gives the losing registrar five days to approve or deny, and silence counts as approval), so start at least a week before the renewal date — and make sure the 60 days have already cleared by then. Renewing a domain does not reset the clock or lock the domain: you can renew at any point, including during an active lock, without extending the wait.
What does NOT trigger the lock
Several things that feel like they should start a new 60-day clock do not: renewing the domain (never triggers a lock, never extends one); changing nameservers or DNS records (no effect on transfer eligibility); editing admin or technical contacts (only the registrant's details trigger the lock); toggling WHOIS privacy at most registrars (the exception is registrars whose privacy implementation rewrites the registrant email — check yours before toggling if a transfer is imminent; our guide to domain privacy protection covers when privacy is worth paying for); and unlocking the domain, which is a precondition for transferring, not a trigger.
The one workaround that actually works
There is exactly one legitimate way around the wait, and it only fits a specific situation: an account-to-account push at the same registrar. The 60-day lock blocks inter-registrar transfers — moving from one company to another. It does not block moving a domain between two accounts inside the same registrar, because that is not a registrar transfer at all. That is the fix when you bought a domain into the wrong account, or you are taking over a domain from a client or a previous owner who is already with the same registrar: both accounts have to live at that one registrar, and the domain does not change companies — but you get control immediately, with no 60-day wait. Most registrars offer this as a free "push" or "account change" feature.
Be blunt about the alternative: there is no paid fast-track. The lock is enforced at the registry, above every registrar. If a "domain consultant," a marketplace middleman, or a helpful-sounding stranger in a forum offers to remove the ICANN 60-day lock for a fee, they are either mistaken or scamming you — it is not technically possible for anyone to do that. Do not pay them, and do not hand them your authorisation code.
How to avoid the lock next time
The registration and post-transfer locks cannot be dodged. The change-of-registrant lock can — if you plan ahead. Most registrars let you opt out of the 60-day lock at the moment you change contact details, usually a checkbox on the confirmation step. You have to opt out before the change goes through; you cannot do it retroactively, and once the lock is in effect it cannot be shortened. Some registrars do not offer the opt-out at all — DNSimple, for example, enforces the lock with no opt-out — so check your registrar's policy before you need it.
- Transfer first, update details second. If you are both changing registrant details and moving registrars, do the transfer first — or update the details with the opt-out ticked — so you do not start a fresh 60-day clock the week before you want to leave.
- Never tidy up contact details just before a transfer. That "quick fix" to the registrant email is the most common self-inflicted lock. If the email on file still works, leave it alone until the transfer completes.
- Check the status codes before you start. A 30-second WHOIS lookup tells you whether you are waiting out
serverTransferProhibitedor just need to flip offclientTransferProhibited. - Set the reminder for day 61, not day 60, to avoid a rejection on a boundary day — and have the authorisation code ready before you start.
If the move is motivated by price, read our step-by-step guide to transferring a domain to a cheaper registrar first — and if you move domains between registrars often, the registrar-hopping playbook shows how to sequence transfers and renewals so the locks never strand you at the expensive registrar on renewal day.
What is changing: the 30-day future (approved, not yet in force)
At its March 2025 meeting (ICANN82), ICANN's GNSO Council accepted the final report of its Transfer Policy Review Working Group: 47 recommendations to modernise transfers, including a mandatory 30-day (720-hour) lock for newly registered or transferred domains, the complete removal of the 60-day change-of-registrant lock, and replacing the static auth code with a one-time Transfer Authorization Code (TAC), valid for 14 days. On June 7, 2026, the ICANN Board adopted those recommendations.
But — and this is the fact that matters for your transfer today — none of it is in force yet. As of late October 2026, ICANN has not announced an effective date, and the working group recommended an 18-month implementation window. Until ICANN publishes that date, plan for the current 60-day rules and check your own WHOIS record: the status code is the source of truth, not the calendar. If your domain is more than 30 days past its trigger date and serverTransferProhibited has already cleared, your registrar is on the new rules; if it is still showing at day 45, they are not yet. Any article telling you the lock is already 30 days is describing the approved future, not the present.
One scope note: everything above applies to generic TLDs. Country-code extensions (.uk, .de, .fr, .au) follow their own registry's rules, and many have no 60-day lock at all — the UK's .uk transfers by changing the domain's IPS tag to the new registrar, typically the same day. Our ccTLD vs gTLD guide explains which rulebook each extension follows.
FAQs
How long is the ICANN 60-day transfer lock?
60 calendar days from the trigger event: a new registration, a completed inter-registrar transfer, or a change of the registrant's name, organisation, or email address. It applies to all generic TLDs under ICANN's Transfer Policy, and it lifts automatically.
Can anyone remove the 60-day transfer lock early?
No. It is enforced at the registry, above every registrar, so no support agent at any registrar can lift or shorten it. Anyone offering to remove it for a fee is mistaken or running a scam. The only legitimate bypass is an account-to-account push within the same registrar.
Does changing my registrant email trigger the 60-day lock?
Yes, unless you opt out first. Changing the registrant's name, organisation, or email triggers a 60-day lock under the policy in force since December 1, 2016. Many registrars offer an opt-out checkbox at the moment of the change — select it before the change goes through; some, DNSimple for example, do not offer it.
Does renewing a domain trigger the 60-day lock?
No. Renewals never trigger a lock and never extend one. You can renew during an active lock without affecting the date it clears.
Does changing nameservers or DNS trigger the lock?
No. Nameserver and DNS changes have no effect on transfer eligibility. Neither does editing the admin or technical contact — only the registrant's details trigger the lock.
What is the difference between serverTransferProhibited and clientTransferProhibited?
serverTransferProhibited is set by the registry and means the ICANN 60-day lock is active — wait it out. clientTransferProhibited is set by your registrar as a default safety lock — turn it off yourself in the control panel in seconds.
Is the 60-day lock becoming 30 days?
Eventually, yes — but not yet. On June 7, 2026 the ICANN Board adopted recommendations to cut the post-registration and post-transfer lock to 30 days and remove the change-of-registrant lock entirely. As of late October 2026 no effective date has been announced, and the working group recommended an 18-month implementation window. Plan on 60 days until ICANN publishes the date.
Does the 60-day lock apply to .uk or other country-code domains?
No. Country-code domains are not governed by ICANN's Transfer Policy. The UK's .uk, for instance, transfers by changing the IPS tag to the new registrar, typically the same day, with no 60-day cooling-off period.
The bottom line
The 60-day transfer lock is not your registrar being difficult — it is a registry-level anti-hijacking rule with exactly three triggers, and two of them you cannot avoid. What you can do is stop tripping the third one: never edit registrant details in the weeks before a planned transfer, tick the opt-out box if your registrar offers it, and check your WHOIS status codes before assuming you are stuck. And keep an eye on ICANN's 2026 reforms: the 30-day lock and the end of the change-of-registrant lock are approved and coming, just not in force yet. Until they are, the calendar — counted from the trigger date, not from today — is the only thing that clears the lock.




