How Long Does a Domain Transfer Take?
The standard timeline for domain transfers (5-7 days for most TLDs), the step-by-step process, what causes delays, how to speed it up, and what can go wrong.
A domain transfer typically takes 5 to 7 days for .com, .net, and most generic TLDs. Some transfers complete in as little as a few hours. Others drag on for two weeks. The difference comes down to how the registrars involved handle the approval process and whether anything goes wrong along the way.
If you have a transfer coming up -- or one stuck in limbo right now -- this guide walks through the entire process, explains why it takes as long as it does, and covers what you can do to speed things up.
The Standard Transfer Timeline
For a typical .com or .net domain transfer between two major registrars, the timeline looks like this:
Day 1: Initiate the transfer. You unlock the domain at your current registrar, get the authorization code (also called an EPP code or transfer key), and submit the transfer request at the new registrar.
Day 1-2: New registrar processes the request. The gaining registrar sends a transfer request to the registry. Some registrars do this immediately. Others batch transfer requests and process them once or twice a day.
Day 2-3: Approval emails sent. The registry or the losing registrar sends a confirmation email to the domain's administrative contact. This email asks you to approve or deny the transfer.
Day 3-5: Waiting for approval. If you click the approval link promptly, the transfer can move forward within hours. If you miss the email or it lands in spam, the transfer sits in a pending state.
Day 5-7: Transfer completes. Once approved (or after the auto-approval window expires), the registry moves the domain to the new registrar. DNS settings are updated, and the domain appears in your new registrar's dashboard.
That is the typical path. But several factors can extend or shorten this window.
The Transfer Process Step by Step
Understanding each step helps you identify where delays happen.
Step 1: Prepare the Domain
Before you start, there are a few things to check at your current registrar.
Unlock the domain. Most registrars apply a transfer lock by default. You need to disable this in your domain settings. The lock is a security feature that prevents unauthorized transfers, but it will block your legitimate transfer too if you forget to remove it.
Check the 60-day lock. ICANN policy requires a 60-day transfer lock after initial registration or a previous transfer. If you registered or transferred the domain within the last 60 days, you cannot transfer it again yet.
Disable WHOIS privacy (if required). Some registrars require you to temporarily disable WHOIS privacy protection before initiating a transfer. Others handle it automatically. Check your registrar's documentation.
Get the authorization code. This is a unique code tied to your domain that proves you have permission to transfer it. You generate it from your current registrar's dashboard. The code is typically valid for a limited time (5-14 days depending on the registrar).
Step 2: Initiate at the New Registrar
Go to your new registrar, start a domain transfer, enter the domain name, and provide the authorization code. You will usually pay the new registrar a transfer fee, which includes a one-year registration extension.
Step 3: Confirm the Transfer
After the new registrar submits the transfer request, you will receive confirmation emails. The exact flow varies:
- Some registrars send an approval email to the domain's admin contact. Click the link to approve.
- Some registrars send emails from both the gaining and losing registrar. You may need to approve on both sides.
- If no action is taken, most transfers auto-approve after 5 days.
Step 4: Wait for Completion
Once approved, the registry processes the transfer. This usually takes a few hours but can take up to 24 hours during busy periods or for certain TLDs.
Step 5: Verify and Configure
After the transfer completes, log in to your new registrar and verify that:
- The domain appears in your account
- Name servers are set correctly
- Auto-renewal is configured
- WHOIS privacy is re-enabled (if desired)
- Contact information is accurate
If you are changing name servers as part of the transfer, see this guide on how to change nameservers to avoid DNS-related downtime during the transition.
Why Transfers Take 5-7 Days
The timeline is not a technical limitation. A domain transfer is essentially a database update -- changing the registrar of record in the registry. That could happen in seconds. The multi-day process exists for security reasons.
ICANN's transfer policy requires a 5-day window for the losing registrar to approve or deny the transfer. This gives the domain owner time to notice and cancel an unauthorized transfer attempt. The losing registrar can approve it early, which shortens the window, but they are not required to.
Email-based confirmation adds latency. The approval process relies on emails reaching the domain's administrative contact. If that email address is outdated, if the email lands in spam, or if the domain owner does not check email regularly, the approval sits pending until the auto-approval timer expires.
Registrar processing times vary. Some registrars process transfer requests in real time. Others batch them. The difference between a registrar that processes requests hourly and one that processes them once per day can add 24 hours to your transfer.
How to Speed Up a Transfer
You cannot bypass the ICANN-mandated waiting period, but you can avoid the delays that stretch a transfer beyond the minimum.
Approve the transfer immediately. The single biggest time-saver. Watch for the confirmation email and click the approval link as soon as it arrives. Check spam folders. If you approved on the gaining side, check whether the losing registrar also sent a confirmation.
Verify your admin email is current. Before initiating the transfer, make sure the email address on the domain's WHOIS record (or the registrar account email used for transfer notifications) is one you actively monitor. An approval email sent to an old address you never check will sit there until the 5-day auto-approval kicks in.
Unlock the domain before you start. Initiating a transfer on a locked domain wastes time. The transfer will fail, and you will need to unlock and restart.
Get the auth code fresh. Do not request the authorization code weeks in advance. Some expire. Get it right before you initiate the transfer at the new registrar.
Choose registrars with fast processing. Some registrars are known for faster transfer processing. Cloudflare, for example, processes transfers quickly and sends clear approval emails.
What Can Go Wrong
Most transfers go smoothly, but when they do not, these are the usual culprits.
Transfer Denied by Losing Registrar
The losing registrar can deny a transfer for specific reasons: the domain is locked, the auth code is wrong, the domain was registered or transferred within the last 60 days, or there is an active dispute on the domain. Fix the underlying issue and resubmit.
Approval Email Never Arrives
If the administrative contact email is invalid or the email gets filtered as spam, you will not see the approval request. The transfer will eventually auto-approve after 5 days, but if the losing registrar actively denies it (some do when they do not receive approval), the transfer fails entirely.
Expired Authorization Code
Auth codes have a limited lifespan. If you wait too long between getting the code and submitting the transfer, the code may expire. Generate a new one and try again.
Domain in Redemption or Pending Delete
You cannot transfer a domain that has expired and entered the redemption or pending delete phase. You need to renew it first (which may involve redemption fees) and then wait for any post-renewal lock to clear before transferring.
For a broader understanding of the domain lifecycle and what these phases mean, see our domain registration lifecycle guide.
WHOIS Privacy Blocking the Transfer
Some registrars replace your administrative contact email with a privacy proxy address when WHOIS privacy is enabled. If the transfer approval email goes to a privacy proxy that does not forward it correctly, the transfer stalls. Disable WHOIS privacy before initiating the transfer if your registrar requires it.
Country-code TLDs have different rules
The 5-7 day timeline applies to generic TLDs like .com, .net, and .org. Country-code TLDs (.uk, .de, .au, .ca) often have different transfer procedures and timelines. Some are faster (UK transfers can complete in hours), while others require additional paperwork. Check the specific registry's transfer policy for your TLD.
Transfer Timeline by TLD
| TLD | Typical Transfer Time | Notes | |-----|----------------------|-------| | .com, .net, .org | 5-7 days | Standard ICANN process | | .uk | Minutes to hours | Tag change system, very fast | | .de | Usually 1-3 days | Handled by DENIC | | .au | 1-3 days | Varies by registrar | | .io | 5-7 days | Standard ICANN-style process | | .eu | Up to 5 days | Managed by EURid |
During the Transfer: Does Your Site Go Down?
A domain transfer changes which registrar manages your domain. It does not inherently change your DNS settings. If your name servers stay the same, your website and email continue working throughout the transfer with no interruption.
Problems arise when:
- The losing registrar removes your DNS records during the transfer (rare but possible with some registrars)
- You change name servers as part of the transfer and there is a propagation delay
- The domain briefly enters a state where DNS queries return stale or no data
To be safe, keep your existing name servers in place until the transfer completes and the domain is fully settled in your new registrar. Then make DNS changes separately.
If you are monitoring your domain expiry dates and want to make sure a transfer does not accidentally let a domain lapse, tools like Domain Expiry Watcher can alert you to upcoming expirations.
References
Track your domain transfers and expirations
Keep tabs on every domain in your portfolio. Get alerts before anything expires or needs attention.
Try Domain Expiry Watcher