goJumboGPT

Internet How the web works under the address bar

Why can't I transfer my domain for 60 days?

The three 60-day transfer waits in ICANN's policy today, how Cloudflare, GoDaddy and Namecheap apply them, and the adopted 30-day rule that is not in force yet.

8 min read How we write

The short answer

  • You cannot transfer a domain for 60 days because ICANN's Transfer Policy lets a registrar refuse a move within 60 days of registration or of the last transfer, and requires a 60-day lock after a change of owner details.
  • The first two waits are a "may" in ICANN's text, but some registry contracts make the 60 days after creation binding, so registrars such as Cloudflare and GoDaddy apply them to everyone.
  • The lock after a change of the owner's name, organization or email is the one you can sometimes avoid: Namecheap opts you out in its agreement, and GoDaddy applies it only if you chose it.
  • On 7 June 2026 ICANN's Board adopted rules that make the waits a mandatory 720 hours (30 days) and drop the change-of-owner lock, but they are not in force and no date has been set.
  • If you plan to change the owner email and move registrars, move first and edit afterwards, so one edit does not add a fresh 60-day wait.

Your domain is inside one of three 60-day waits in ICANN's Transfer Policy, the rule book for generic endings such as .com and .org. A registrar may refuse to move a name for 60 days after it was first registered. It may also refuse for 60 days after the name last moved to a new registrar. And when the owner's name, organization or email address changes, the registrar must lock the name for 60 days, unless it let the owner opt out first. In June 2026, ICANN's Board adopted changes that cut the first two waits to 30 days and scrap the third, but they are not in force and have no date.

What a domain transfer and the 60-day lock are

A domain name is the name you rent, such as example.com, the part of a web address that decides where a link goes. The registrar is the company you pay for it, such as GoDaddy or Cloudflare. The registry keeps the master list for one ending. ICANN writes the rules that registrars and registries of generic endings must follow.

A domain transfer means moving the name from one registrar to another. ICANN calls this an inter-registrar transfer. You keep the name. You start the move with a transfer code, called the AuthInfo code, from your current registrar.

The 60-day lock is a period when the name cannot make that move. In ICANN's words, the domain "is ineligible for inter-Registrar transfer for a period of time."

The three 60-day waits in the current rules

The current Transfer Policy has bound registrars since 21 August 2025. It lists the reasons a registrar may refuse a transfer and the reasons it must. The 60-day waits sit in both lists.

  1. Within 60 days of creation. A registrar may deny a transfer "requested within 60 days of the creation date" shown in the domain's public record. The clock starts when the name was first registered, not when you bought it.
  2. Within 60 days of the last transfer. A registrar may deny a transfer when the name moved to a new registrar in the past 60 days. There is one exception: a move back to the original registrar, if both registrars agree or a dispute ruling says so.
  3. Within 60 days of a Change of Registrant. A Change of Registrant is a "material change" to the owner's name, organization or email address. A material change is anything more than fixing a typo. After one, the registrar "must impose a 60-day inter-registrar transfer lock." But it "may allow the Registered Name Holder to opt out" before the change is made.

The first two waits are a "may". The third is a "must", softened by the opt-out. That difference explains most of the confusion online.

A new postal address or phone number on its own is not a Change of Registrant. Neither is pointing the name at new servers, a DNS setting that decides where the name lands.

Why registrars call it an ICANN requirement

Cloudflare's transfer guide says your domain must have been "registered at least 60 days ago and has not been transferred in the last 60 days (ICANN requirement)." ICANN's text says only "may". The gap is explained in ICANN's 2025 review: a 60-day wait after creation is "currently specified in some Registry-Registrar Agreements" and some registry contracts. So for many endings the registry makes it binding, and registrars apply it to every name. GoDaddy's transfer page sets the same 60 days after a new registration or a transfer. Expect the full 60 days.

The Change of Registrant lock is where companies differ.

  • Namecheap builds the opt-out into its registration agreement. By accepting it, you "explicitly opt out" of the lock that would follow a change of owner details.
  • GoDaddy treats it as a choice: the lock applies only "if the current registrant opted to apply a 60-day lock when approving the changes."
  • Cloudflare will not accept a name whose registrant name, organization or email changed in the last 60 days.

Why wait at all? The working group's reasons: time to catch a stolen credit card used to buy a name, time for a trademark owner to file a complaint, and an end to rapid registrar hopping, "a practice associated with domain theft."

A new domain, walked through

Take a .com registered at GoDaddy on 2 December 2026, which the owner wants to move to Cloudflare. Under the current rules:

  • 2 December 2026: the name is created. Both registrars say no transfer within 60 days.
  • 31 January 2027: day 60. The transfer can start.
  • Suppose the move completes on 5 February 2027. A new 60-day wait starts at Cloudflare.
  • 6 April 2027: 60 days after that transfer, the name could move again.

Now suppose the owner had changed the registrant email at GoDaddy on 20 January, before the move. GoDaddy would block the transfer only if the owner chose the lock. Cloudflare would refuse the name until 60 days after the change, which is 21 March. One email edit would delay the move by seven weeks. Making the change after the move avoids this.

Had the rules ICANN adopted in June been in force, the name could move 720 hours (30 days) after creation, on 1 January 2027, and the email change would add no lock.

The waits by registrar, today and after the change

Each row shows what that body's own page says. A dash means the page does not say.

Rule or registrarAfter first registrationAfter a transferAfter a change of owner name, organization or email
ICANN Transfer Policy, in force todayRegistrar may refuse for 60 daysRegistrar may refuse for 60 days, except a move back to the original registrarRegistrar must lock for 60 days, unless it let the owner opt out beforehand
Cloudflare (receiving)Not accepted within 60 daysNot accepted within 60 daysNot accepted within 60 days of the change
GoDaddy (sending)No transfer out within 60 days, or 120 days for a name bought in a bundleNo transfer out within 60 daysLocked only if the owner chose the lock when approving the change
Namecheap--Opt-out built into the registration agreement
ICANN rules adopted June 2026, not yet in forceRegistrar must block for 720 hours (30 days)Registrar must block for 720 hours, and may lift it early on a specific request with a reasonable basisNo lock

What changes when ICANN's new rules take effect

On 7 June 2026, the ICANN Board passed resolution 2026.06.07.04. It adopted all 47 recommendations of the Transfer Policy Review working group, whose final report came out in February 2025. Three replace the waits.

  • Recommendation 3: the registrar must block a transfer for 720 hours from the creation date. Registry contracts that say 60 days would have to change. A "may" becomes a "must".
  • Recommendation 18: the same 720-hour block after a move between registrars. It may be lifted early only on a specific request with a reasonable basis, such as completing a documented sale.
  • Recommendation 26.4: the 60-day lock after a Change of Registrant goes, and so does the opt-out text.

The group used hours instead of days "to avoid ambiguity." The same package renames the AuthInfo code the Transfer Authorization Code (TAC). It must still be issued within 120 hours, and it will be valid for 336 hours, or 14 days.

None of this applies yet. The Board told ICANN's chief executive to implement them "subject to prioritization." The policy text still has to be drafted with an Implementation Review Team. As of 19 November 2026, ICANN had published no effective date. The last update gave registrars a year, from 21 August 2024 to 21 August 2025, to comply. Until a date appears, the 60-day rules stand.

What this answer does not cover

ICANN's policy covers generic endings. Country endings such as .uk set their own transfer rules. Some registrars add limits: GoDaddy holds a name bought in a bundle for 120 days after registration. A registrar must also refuse a transfer during a domain dispute or under a court order, whatever the date. An expired name can usually still move, but GoDaddy says not once it is in redemption, and what happens after a domain expires covers that clock. Moving a name between accounts at one registrar is not a transfer, though new owner details can still trigger the Change of Registrant lock. This page is general information, not legal advice.

What to do if your transfer is blocked

  1. Find which wait you are in. Check the creation and last transfer dates in your registrar account. Count 60 days from the later one. If neither fits, look for a recent owner change.
  2. Ask about the Change of Registrant lock. It is the only wait some registrars treat as optional, so ask what yours allows.
  3. Change owner details after the move, not before. If you must change them first, opt out of the lock where your registrar offers it.
  4. Protect the owner email. Transfer messages go to it, so lock down that email account, keep its recovery options current, and turn on two-factor sign-in at your registrar too.
  5. Distrust urgent transfer emails. A warning that your domain must move or be lost has the shape of a scam with a link and a deadline. Sign in to your registrar directly.

Common questions

Can I transfer a domain I just bought from someone else?

It depends on when the name was first created, not when you bought it. If the name is older than 60 days and has not moved registrar in the last 60, the creation and transfer waits do not apply. The change of owner details from the sale can still trigger the 60-day Change of Registrant lock, unless your registrar opted you out.

Does renewing a domain restart the 60-day lock?

No. Renewal is not one of the reasons ICANN's Transfer Policy gives for refusing a transfer. The waits count from three events only: the creation date, the last move between registrars, and a material change to the owner's name, organization or email address. Renewing, changing DNS servers or updating a phone number alone starts none of them.

Can my registrar remove the 60-day lock early?

For the lock after a change of owner details, some will, because ICANN lets registrars offer an opt-out and practice varies. The wait after creation is often fixed by the registry's contract, so registrars rarely lift it. Under the rules adopted in June 2026, a registrar may lift the new 30-day post-transfer block early, but only on a specific request with a reasonable basis.

When does the 30-day domain transfer rule start?

No date has been set. ICANN's Board adopted the 720-hour rule on 7 June 2026, but the policy text still has to be drafted with an Implementation Review Team. As of 19 November 2026, ICANN had published no effective date, so the 60-day rules still apply. Watch ICANN's Transfer Policy page for the update.

Why does my registrar say ICANN requires 60 days?

Because in practice it often does. ICANN's policy says a registrar may refuse a transfer within 60 days of creation, but ICANN's 2025 review notes that some registry contracts specify a 60-day post-creation restriction. Where the registry's contract makes it binding, the registrar has no choice, and most apply the same wait to every name.

Sources