What Really Happens During the 60-Day Domain Transfer Lock
Anyone who has tried to move a freshly registered or recently transferred domain to a new registrar has run into it: a flat, non-negotiable 60-day waiting period during which the domain simply cannot be transferred away. It feels arbitrary, but it's a specific, deliberately designed policy with a clear original purpose — one that occasionally causes real friction for legitimate reasons unrelated to what it was built to prevent.
Where the Rule Actually Comes From
The 60-day transfer lock isn't an individual registrar's invented policy — it's mandated by ICANN (the Internet Corporation for Assigned Names and Numbers) through its Transfer Policy, which applies uniformly across essentially every generic top-level domain (.com, .net, .org, and most others) regardless of which registrar you use. The policy requires that a domain remain locked against outbound transfer for 60 days following either its initial registration or a change of registrant (an ownership change, not just an administrative update).
The Original Purpose
The rule exists specifically to combat domain hijacking. Before it was implemented, a compromised registrar account could be used to register a domain and immediately transfer it to a different registrar under attacker control, making recovery significantly harder since the domain would already be outside the original registrar's reach by the time the legitimate owner noticed anything wrong. The 60-day window creates a mandatory pause specifically during the highest-risk period right after a domain changes hands, giving a legitimate owner time to notice and reverse an unauthorized change before it can be locked into a different registrar entirely. ICANN adopted this specific policy after a wave of documented hijacking incidents in the early 2000s made clear that the previous, unrestricted transfer process was being actively exploited, and the resulting rule has remained largely unchanged since, precisely because it continues to address a genuine, ongoing security concern rather than a threat that has since faded.
What Actually Triggers a New Lock Period
It's worth being precise about what does and doesn't restart the 60-day clock, since this trips up a lot of domain owners. A registrant name change (updating the actual legal owner on file) restarts the lock. Renewing a domain does not. Updating administrative or technical contact details, changing nameservers, or enabling/disabling privacy protection does not. This distinction matters most for anyone buying a domain through a marketplace or private sale — the ownership transfer itself (updating the registrant) is what triggers a fresh 60-day hold, meaning a domain you've just purchased secondhand typically can't be moved to your preferred registrar immediately, even though you now legitimately own it.
Where This Causes Real Friction
The policy's collateral effect shows up most commonly in a few scenarios: a business acquiring a domain as part of buying another company or asset, where the new owner wants to consolidate it with their existing domain portfolio at their usual registrar immediately, but can't; a domain purchased through an aftermarket marketplace (like a drop-catch auction, discussed elsewhere on this blog, or a private brokered sale), where the buyer similarly wants immediate consolidation; and legitimate account recovery scenarios, where a genuinely compromised account's rightful owner regains access but then finds the same lock applying to their own recovery actions, since the policy can't distinguish "attacker changed the registrant" from "recovery process changed the registrant back."
What You Can Still Do During the Lock
The lock specifically blocks transferring the domain to a different registrar — it doesn't freeze the domain otherwise. During the 60-day window you can typically still renew the domain, update nameservers to point it at any hosting provider you like, modify DNS records, and change administrative contacts. For most practical purposes — actually using the domain for a website or email — the lock is invisible; it only becomes a visible obstacle for the specific act of registrar-to-registrar transfer.
How This Interacts With a Registrar's Own Cancellation Policy
A related, often-missed wrinkle involves what happens if you decide to cancel a domain outright, rather than transfer it, while a lock is in effect. Cancellation and transfer are governed by different mechanisms — the ICANN transfer lock only restricts the inter-registrar transfer process specifically, so a registrant can typically still choose not to renew, or explicitly request cancellation, even mid-lock, though doing so simply routes the domain into the standard expiration lifecycle discussed elsewhere on this blog rather than offering any shortcut around the transfer restriction. This distinction matters for anyone assuming a locked domain is somehow frozen from every kind of account action; the lock is narrower and more specific than that.
A Narrow Exception Worth Knowing
Some registrars offer a workaround specifically for the immediate-post-purchase scenario: rather than transferring the domain to a different registrar, using the same registrar's own internal account-to-account push feature to move a domain between two accounts under the same registrar's umbrella, which typically isn't subject to the ICANN inter-registrar transfer lock at all, since it isn't technically an inter-registrar transfer. This doesn't help if your target destination is genuinely a different registrar, but it's a useful option if you're willing to open or use an account at whichever registrar the domain already sits with, at least as a temporary consolidation step until the standard 60-day window has elapsed and a full inter-registrar transfer becomes possible.
The Takeaway
The 60-day transfer lock is a deliberate, ICANN-mandated security measure, not an arbitrary inconvenience or a registrar trying to trap your business. Understanding exactly what triggers it — registrant changes specifically, not renewals or DNS changes — makes it possible to plan domain acquisitions and consolidations around the restriction rather than being surprised by it after the fact.
Tags: domain transfer, ICANN policy, registrar lock