How long to wait before transferring a domain?

You've picked your new registrar, you've got your authorization code ready — and then the transfer gets denied without explanation. Nine times out of ten, the culprit is ICANN's 60-day lock rule, and it catches even experienced site owners off guard.

Under ICANN policy, your domain automatically becomes ineligible for transfer for 60 days in three specific situations. If any of these apply, the losing registrar can — and usually will — deny your request outright.

• Within 60 days of initial registration. A newly registered domain simply cannot move during its first two months.
• Within 60 days of a previous registrar transfer. Each completed transfer resets the clock, so back-to-back moves are off the table.
• Within 60 days of registrant contact changes — including changes to the registrant name, organization, email address, or Administrative Contact email. This one surprises people most often.

That third rule matters because updating your contact details is routine housekeeping — something you might do right before a move to "clean things up." Doing so can lock your domain for another two months. ICANN notes that registrars may offer an opt-out for the Change of Registrant lock, but they aren't required to, so never assume you'll get one.

Before requesting your authorization code, verify three dates in your registrar's dashboard: the domain's creation date, the date of any prior transfer, and the date of any recent contact changes. If all three are more than 60 days in the past, you're clear to proceed.

One more detail worth checking: your registrant email address. Registrars have up to 5 calendar days to deliver the Auth-Code, and it goes to the email on file — so an outdated address adds avoidable delay on top of the lock period.

Once you're eligible, timing improves dramatically. While the policy window allows up to 5–7 days for completion, transfers often finish in a few hours with a cooperative registrar — one practitioner documented a transfer completing in roughly 3 hours after proactively contacting support.

If all of this feels like homework you'd rather skip, it's the kind of detail a managed platform handles for you. At AI Business Sites, we handle domain registration and transfer logistics as part of the build process, so the timing rules become our problem, not yours. Either way, the takeaway is simple: check your dates first, fix your contact info, and the 60-day rule stops being a roadblock and becomes just a calendar item.

How Long a Transfer Actually Takes Once You Start

Once you initiate a domain transfer, the real timeline begins with two critical deadlines: registrars must provide your authorization code within 5 calendar days of request, and ICANN policy requires the transfer to complete within a 5-7 day window once started. While this window sets the outer limit, actual completion time varies significantly based on registrar responsiveness and your level of involvement.

In the worst-case scenario with no user intervention, transfers default to auto-completion after 7 days. However, proactive engagement can dramatically shorten this process—some users report transfers completing in as little as a few hours when they contact support to confirm the transfer is pending at the registry. One case study showed a transfer finishing in approximately 3 hours after proactive registrar contact, compared to the potential 7-day default delay.

The key to minimizing delay lies in monitoring and intervention. If your transfer stalls, contacting the losing registrar’s support team can push the process forward, especially if the domain is stuck in a "Pending at Registry" state. This active approach transforms what could be a week-long wait into a matter of hours, giving you control over a process that otherwise runs on a fixed timer. For businesses relying on uninterrupted online presence—such as those using managed platforms like AI Business Sites to maintain website performance during transitions—this proactive step ensures minimal disruption while adhering to ICANN’s transfer rules.

The most common cause of downtime during a domain transfer isn't the transfer itself — it's DNS mismanagement, according to domain industry experts. That means the registrar move itself is almost never what takes your website offline. The problem comes from how nameservers and DNS records are handled along the way.

The core principle is simple: DNS continues to function as long as name servers remain unchanged during the transfer, as transfer guides consistently note. If your DNS is hosted somewhere other than the losing registrar — Cloudflare, for example, or your new hosting provider — a registrar transfer is essentially invisible to your visitors. The domain moves behind the scenes while the DNS keeps resolving exactly as before.

Preparation makes the difference. The recommended zero-downtime playbook looks like this:

• Lower your DNS TTL to 300 seconds (5 minutes) 24–48 hours before switching, so cached records expire quickly instead of serving stale data
• Keep nameservers unchanged during the registrar transfer itself
• Leave old hosting live for 48–72 hours after the switch as a fallback
• Once everything is stable, raise TTL back to 3600 seconds or more for normal operation

The TTL step matters more than most business owners realize. TTL (time to live) tells DNS resolvers how long to cache your records. If it's set to a day and you switch hosts mid-cycle, some visitors may hit a dead server for up to a day. Lowering it to 5 minutes ahead of time means changes propagate almost instantly — practitioner guidance suggests allowing roughly 24 hours for that new TTL to spread before you touch anything.

Timing the fallback window matters too. Practitioners who've run zero-downtime transfers recommend letting DNS propagate for about 48 hours before initiating the move, and keeping the old hosting account active for two to three days after. If anything goes sideways, the old server is still there to catch requests.

This is also why timing your transfer matters beyond the 60-day ICANN lock. A transfer can take anywhere from a few minutes to 7 days depending on registrar cooperation — so your DNS setup needs to hold steady through that entire window.

For business owners who'd rather not babysit TTL values and propagation windows, a managed approach removes the guesswork. When AI Business Sites handles a domain move, the DNS-first strategy runs behind the scenes — nameservers stay put, records stay live, and the site never blinks. The transfer becomes a non-event, which is exactly how it should feel.

Most transfer problems come down to one thing: starting before the domain is actually eligible to move. ICANN's rules create waiting periods that trip up even experienced site owners, so a short checklist before you initiate anything saves days of frustration.

Start with the 60-day lock. A transfer restriction applies within 60 days of initial registration, within 60 days of a previous registrar transfer, and within 60 days of changes to the registrant's name, organization, email address, or Administrative Contact email, according to ICANN's domain holder FAQ. If you recently updated your contact details, check the calendar before requesting the move — some registrars allow you to opt out of the Change of Registrant lock, but they aren't required to.

Next, confirm your contact email is current. The Auth-Code, the authorization key that unlocks the transfer, is sent to the email listed on the domain, and registrars have up to 5 calendar days to provide it when requested. A stale inbox is the most common reason transfers stall at step one.

Then prepare your DNS so the site stays live while the registration moves. DNS continues to function as long as the nameservers stay unchanged during the transfer, and as NameSilo's transfer guide puts it, the most common cause of downtime is not the transfer itself but DNS mismanagement. A practical sequence:

• Lower your TTL to 300 seconds (5 minutes) 24–48 hours before switching, so DNS changes take effect quickly
• Keep the old hosting account active for 48–72 hours after the switch as a fallback
• Raise TTL back to 3600 seconds or more once everything is stable
• Monitor progress through your registrar dashboard or Whois, and contact the losing registrar's support if the transfer stalls

That last point matters more than most people expect. Transfers can take anywhere from a few minutes to 7 days, and in the worst case they auto-complete after a week with no intervention. One site owner documented how a proactive support email to the losing registrar cut the wait to roughly three hours instead of days.

Finally, understand what happens to your expiration date. A completed transfer adds one year to your domain's registration, per DNSimple's guide, so there's no need to renew first before moving.

If you'd rather not manage locks, Auth-Codes, and TTL values yourself, a managed setup handles the timing for you — it's one of the reasons business owners hand their domain and hosting to a managed platform like AI Business Sites rather than juggling the sequence alone.

The real question isn't how long a transfer takes — it's whether you have to manage any of it yourself.

When your domain lives in your name from day one and DNS is handled by a platform that manages the build, the timing rules become someone else's problem. ICANN's 60-day locks still apply after registration, a previous transfer, or a registrant contact change, but a managed platform tracks those windows so you don't have to. The transfer itself typically completes within 5–7 business days, though proactive registrar engagement can shrink that to hours.

• Domain registered in your name — not the provider's
• DNS hosted independently of the registrar so nameservers never change mid-transfer
• TTL lowered to 300 seconds 24–48 hours before any switch, then raised back once stable
• Old hosting kept active for 48–72 hours as a fallback

Ask a provider how they handle the authorization code request (registrars have up to five calendar days to deliver it), whether they pre-stage DNS on the new platform before initiating the transfer, and what monitoring they run during the 5–7 day ICANN window. If the answer involves you opening support tickets or watching Whois records, keep looking.

AI Business Sites registers the domain in your name, hosts DNS on our platform, and manages the entire transfer sequence — so the only timing you track is the launch date. Want to see how it works for your business? Book a free strategy call and we'll walk through the plan.