If you have tried to transfer a domain and been told you cannot yet, the 60-day transfer lock is very often the reason. It is an industry-wide rule — not one registrar’s policy — that prevents a domain from being transferred to a new registrar for 60 days after certain events, most commonly registration or a previous transfer. Understanding exactly when it applies, and when it does not, saves you the frustration of planning a transfer only to find it blocked. This guide explains the rule in full.

You will learn what the 60-day lock is and why it exists, exactly which events trigger it, what it does and does not block, how to check whether your domain is subject to it, what your options are while it is in effect, and how to plan around it. By the end you will know precisely where your domain stands with respect to the 60-day rule and how to work with it rather than against it.

What the 60-day lock is

The 60-day transfer lock is a rule that prevents a domain from being transferred to a different registrar for a period of 60 days following certain events. It is not a setting you can toggle off like the ordinary transfer lock, and it is not specific to one registrar — it is an industry-wide policy applied across the domain system, so it holds no matter which registrar manages your domain or which one you want to move it to.

The rule exists as an anti-fraud and anti-abuse measure. Domain hijacking and fraudulent registrations are real risks, and a common tactic in such schemes is to rapidly transfer a domain between registrars to obscure control or frustrate recovery. By imposing a 60-day cooling-off period after registration or transfer, the rule makes such rapid movement impossible, giving a window in which fraudulent activity can be detected and reversed and preventing a stolen domain from being quickly spirited away.

So the 60-day lock is a mandatory, system-wide waiting period designed to protect domain owners and the domain system from abuse. Because it is a policy rather than a toggle, you cannot disable it — if your domain is within a 60-day window, you genuinely have to wait it out before transferring. Understanding it as a fixed rule, not a registrar obstruction, sets the right expectation: the question is never how to bypass it, but simply when the 60 days are up.

Which events trigger it

The 60-day lock is triggered by specific events, and knowing them tells you whether and when your domain is affected:

• New registration: when you first register a domain, it cannot be transferred to another registrar for 60 days.
• A previous transfer: after a domain is transferred between registrars, it is locked from transferring again for 60 days.
• A change of registrant (in some cases): a change of the domain’s registered owner can, depending on the circumstances, trigger a 60-day transfer lock as well (an ICANN policy around registrant changes).

The two you will most often encounter are new registration and a prior transfer — both start a fresh 60-day clock during which the domain stays put at its current registrar. The registrant-change trigger is worth knowing about because updating the domain’s owner details can, in some cases, start a lock you did not expect, so it is wise to avoid changing registrant information right before a planned transfer. In each case the mechanism is the same: the event starts a 60-day period, and the domain simply cannot transfer until that period elapses.

What it does and doesn’t block

It is crucial to understand that the 60-day lock blocks only one specific thing: transferring the domain’s registration to a different registrar. It does not block the many other things you might want to do with your domain, which is a common source of confusion — people assume a locked domain is frozen entirely, when in fact only registrar-to-registrar transfer is prevented.

Specifically, while the 60-day lock is in effect, you can still change your domain’s DNS records and nameservers freely — meaning you can point the domain at a different web host or mail server without any restriction. So if your goal is to move your website to a new host (rather than move the domain’s registration), the 60-day lock does not stand in your way at all; you simply update the DNS, which the lock does not touch. You can also renew the domain, edit contact details, and manage it normally at its current registrar.

So the 60-day lock is narrow: it stops a registrar transfer, nothing else. This distinction matters enormously in a migration context, because most people who think they are blocked actually want to move their hosting, not their domain registration — and hosting moves happen via DNS, which is unaffected. So before worrying about the 60-day lock, ask whether you actually need to transfer the domain’s registration at all, or whether a DNS change achieves your real goal without any wait.

How to check if your domain is affected

To know whether your domain is subject to the 60-day lock, you check when it was last registered or transferred, since the lock runs for 60 days from that event. If either happened within the last 60 days, the lock is in effect; if both were more than 60 days ago, the domain is free to transfer (assuming the other prerequisites are met).

You can find these dates in your domain’s registration record: a domain’s public registration information includes its creation/registration date and its last-updated or last-transfer date, and your registrar account also shows when you registered or transferred the domain. Comparing those dates to today tells you immediately whether a 60-day window is still running and, if so, roughly when it ends.

So checking is a matter of finding your domain’s registration and transfer dates (in your registrar account or its public registration record) and counting whether 60 days have passed since the most recent triggering event. If they have, you are clear to transfer; if not, the record tells you when the window closes. This quick check, done before you plan a transfer, tells you whether the 60-day rule applies to you and removes the guesswork about why a transfer might be blocked.

Your options while it’s in effect

If your domain is within a 60-day lock and you want to move it to a new registrar, your primary option is simply to wait until the 60 days elapse, at which point (with the other prerequisites met) the transfer can proceed normally. There is no legitimate way to bypass the rule, since it is a system-wide policy, so waiting is genuinely the answer for a registrar transfer.

But often you have better options depending on your actual goal. If what you really want is to move your website to a new host, you can do that right now via DNS, without waiting, because the lock does not block DNS changes. If you want to use a new provider’s services while the lock is in effect, you can point your domain there via DNS and complete the formal registrar transfer once the 60 days are up — getting the practical benefit immediately and the administrative move later.

So while the lock is in effect, your options are: wait it out for a registrar transfer (the only path for that specific action), or, far more often the real solution, achieve your underlying goal through DNS now if it is really a hosting move you are after. Reframing ‘I can’t transfer my domain’ as ‘what am I actually trying to accomplish?’ usually reveals that the 60-day lock is not the obstacle it first appears, because the thing you want to do is a DNS change the lock never restricted.

Planning around the rule

Knowing the 60-day rule lets you plan domain moves so it never catches you off guard. The main planning principle is timing: if you know you will want to transfer a domain to a new registrar, avoid doing anything that starts a fresh 60-day clock in the run-up — in particular, do not transfer it to an intermediate registrar first, and be cautious about registrant-detail changes right before a planned transfer, since those can trigger the lock.

For a newly registered domain you intend to move, simply plan for the 60-day wait from registration — or, better, register it directly with the registrar you ultimately want it at, avoiding a transfer (and its lock) entirely. When consolidating domains or hosting, sequence the moves so that any needed registrar transfers happen after their 60-day windows have cleared, while doing the hosting/DNS changes (which are unrestricted) whenever suits you.

So planning around the 60-day rule comes down to anticipating the triggers and sequencing accordingly: do not start clocks you will have to wait out, separate the unrestricted DNS/hosting moves (do them anytime) from the registrar transfers (schedule them clear of any 60-day window), and where possible avoid unnecessary transfers altogether by registering domains where you want them. Handled with this foresight, the 60-day lock becomes a known, plannable constraint rather than a surprise blocker — you work with its timing instead of running into it.

FAQs

What is the 60-day domain transfer lock?

It’s an industry-wide rule (not one registrar’s policy) that prevents a domain from being transferred to a different registrar for 60 days after certain events — most commonly registration or a previous transfer. It’s an anti-fraud measure that stops domains being rapidly moved to obscure control. It’s a fixed policy, not a toggle you can disable, so if your domain is within a 60-day window you have to wait it out for a registrar transfer.

What triggers the 60-day transfer lock?

Three events: registering a new domain (locked for 60 days from registration), transferring a domain between registrars (locked for 60 days after the transfer), and, in some cases, a change of the registered owner (registrant), which can also start a 60-day lock. New registration and a prior transfer are the most common. Avoid changing registrant details right before a planned transfer, since that can start an unexpected lock.

Does the 60-day lock stop me changing hosts?

No. The 60-day lock blocks only transferring the domain’s registration to a different registrar — it does not block DNS or nameserver changes. So you can point your domain at a new web host or mail server freely while the lock is in effect. If your real goal is moving your website to a new host, the 60-day lock doesn’t stand in your way at all; that happens via DNS, which the lock never touches.

How do I check if my domain is under the 60-day lock?

Check when your domain was last registered or transferred — the lock runs 60 days from that event. Find the dates in your registrar account or the domain’s public registration record (which shows the creation date and last-updated/transfer date). If the most recent triggering event was over 60 days ago, you’re clear to transfer; if within 60 days, the window is still running and the dates tell you when it ends.

Can I bypass the 60-day transfer lock?

No — it’s a system-wide anti-fraud policy, not a registrar setting, so there’s no legitimate way to disable or bypass it. For a registrar transfer, you simply wait until the 60 days elapse. But often you don’t need to: if your real goal is a hosting move, you can do that now via DNS (which the lock doesn’t restrict) and complete the formal registrar transfer later once the window clears.

Why can’t I transfer my newly registered domain?

Because of the 60-day lock: a newly registered domain can’t be transferred to another registrar for 60 days after registration, as an anti-fraud safeguard. You have to wait out the period. To avoid this in future, register a domain directly with the registrar you ultimately want it at, rather than registering one place and transferring — that sidesteps the transfer (and its lock) entirely.

The bottom line

The 60-day domain transfer lock is one of the most common reasons a transfer is blocked, and understanding it removes the confusion entirely: it is an industry-wide rule — enforced across the whole domain system, not by any single registrar — that prevents a domain from being transferred to a different registrar for 60 days after a triggering event, most often a new registration or a previous transfer (and, in some cases, a change of registrant). It exists as an anti-fraud safeguard, making the rapid registrar-hopping that hijackers and fraudsters rely on impossible, and because it is a fixed policy rather than a toggle, there is no way to disable it — if your domain is within a 60-day window, a registrar transfer genuinely has to wait until the period elapses.

The single most important thing to understand, though, is how narrow the lock is: it blocks only registrar-to-registrar transfer of the registration, and nothing else — crucially, it does not block DNS or nameserver changes, so you can point your domain at a new web host or mail server freely while the lock is in effect. This matters enormously because most people who feel blocked by it actually want to move their hosting, not their domain registration, and hosting moves happen through DNS, which the lock never touches. So check your domain’s registration and transfer dates to see whether a window is running, and then ask what you are really trying to accomplish: if it is a hosting move, do it now via DNS; if it is a genuine registrar transfer, simply time it clear of any 60-day window, avoid starting fresh clocks in the run-up, and where possible register domains where you want them to avoid unnecessary transfers. Handled with that foresight, the 60-day rule is a known, plannable constraint rather than a surprise.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. The 60-day transfer lock is an industry rule that blocks transferring a domain to a new registrar for 60 days after registration, a prior transfer, or (sometimes) a registrant change. It’s a fixed anti-fraud policy — you can’t disable it, only wait it out. But it blocks ONLY registrar transfers, not DNS/nameserver changes, so you can still move your website to a new host via DNS anytime. Check your domain’s registration/transfer dates to see if a window is running, and plan registrar transfers clear of it.