The 60-Day Domain Transfer Lock Explained
VigilDog Team · September 24, 2026 · 6 min read
You bought a domain, or you just updated the owner details, and now your registrar refuses to release it: "This domain cannot be transferred for 60 days." It feels like a hostage situation, but it's actually an ICANN policy designed to protect you. Understanding the 60 day transfer lock, and the two different events that trigger it, saves you from painful surprises during a migration or an acquisition.
What the 60-day transfer lock is
The 60-day transfer lock is a restriction under ICANN's Transfer Policy that prevents a generic top-level domain (like .com, .net, .org) from being transferred to a different registrar for 60 days after certain events. During the lock, the domain works normally, your site, email, and DNS are unaffected, but you cannot initiate an inter-registrar transfer to move it elsewhere.
It's important to separate this from unrelated 'locks' you'll see in a registrar dashboard. clientTransferProhibited (the registrar lock or 'transfer lock' toggle) is something you can turn off yourself in seconds. The 60-day ICANN lock is a mandatory hold you cannot remove; you can only wait it out.
The two events that trigger it
There are two distinct 60-day clocks, and people constantly confuse them. The first is triggered by a new registration or a completed transfer: after you register a brand-new domain, or after you move it from one registrar to another, it's locked to that registrar for 60 days. This blocks a classic hijacking pattern where a stolen domain gets bounced rapidly between registrars to shake off recovery attempts.
The second clock is triggered by a Change of Registrant (CoR), a material change to the registered owner's name, organization, or email address. Under the Transfer Policy, that change can impose its own 60-day inter-registrar transfer lock. This exists so that if an attacker seizes your account and rewrites the ownership, they still can't immediately whisk the domain away to another registrar.
- New registration → 60-day lock at the current registrar
- Completed registrar-to-registrar transfer → new 60-day lock
- Change of Registrant (owner name/org/email) → optional 60-day lock, which the registrant can decline at the time of change
The Change of Registrant opt-out most people miss
The registration/transfer lock is non-negotiable. The Change of Registrant lock, though, is different: ICANN's policy lets the current registrant opt out of the 60-day transfer restriction at the moment the change is made. Many registrars present a checkbox during the ownership-update flow, something like 'I want to be able to transfer this domain within 60 days.'
If you know you're about to migrate registrars after updating owner details, common during a rebrand or an acquisition, decline the lock during the CoR. If you miss that checkbox, you're stuck for 60 days with no override, because your registrar is following ICANN policy, not making a business decision they can reverse for you.
How to plan around it
The lock is predictable, so treat it as a scheduling constraint rather than an obstacle. If you're consolidating domains before a big launch, do your transfers well in advance, at least 60 days before you actually need everything in one account. If you're buying a domain from someone, understand that if they just registered it or just transferred it in, it can't move to you as an inter-registrar transfer until the clock expires (a push/account change within the same registrar is a separate path).
For owner-detail cleanups, batch them thoughtfully: update WHOIS/registrant data either long before a planned migration, or opt out of the CoR lock if a move is imminent. A little sequencing removes the two-month wait entirely. If you're unsure exactly when a domain's clocks reset, our domain expiry checker and the RDAP data behind it show registration and last-transfer dates that let you count forward.
Why this matters for anyone managing many domains
For a solo site owner, the 60-day lock is a one-time annoyance. For an agency or a business holding dozens of client domains, it's a recurring landmine: a registrant update on the wrong day can freeze a planned migration, and an expiry that sneaks up during a lock window leaves you with fewer options. The domains that bite you are always the ones nobody was watching. Keeping a live inventory, registrar, expiry date, transfer status, turns these locks from surprises into calendar items you plan around, which is exactly the discipline domain monitoring for agencies is built to enforce.
VigilDog tracks expiry and registration details across your whole portfolio in one place, so you always know which domains are free to move and which are still inside a lock window, no per-registrar spreadsheet required.
