A domain transfer between registrars typically takes about 5 to 7 days. It can finish in a few hours if your current registrar approves the request quickly, and it can stretch longer if something blocks it, such as a 60-day lock, a wrong authorization code or an unanswered approval email. The wait is not a flaw. It is a security window, and most of it is under your control.
This guide explains where the days go, which rules add time, how to speed things up without cutting corners, and how to keep your website and email running the whole way through.
TL;DR
- Plan for 5 to 7 days for a typical .com, .net or .org transfer. ICANN policy lets the current registrar take up to 5 calendar days to respond, and silence counts as approval.
- Approving the transfer manually at the old registrar is the single biggest way to shorten the wait, sometimes to hours.
- You generally cannot transfer a domain within 60 days of first registering it or of a previous registrar transfer. A change of registrant details can trigger its own 60-day lock.
- Keep your nameservers unchanged during the transfer and your site and email keep working.
- If a transfer stalls, check the lock, the code, the approval email and the 60-day rule, in that order.
Table of Contents
- How long a domain transfer takes, step by step
- The 60-day rule, explained
- What makes a transfer slower
- How to move faster without cutting corners
- Will your website go down during a transfer?
- If your transfer is stuck
- Our perspective: treat the transfer as a scheduled change
- Moving your domain to inSave Hosting
- Frequently asked questions
- Sources
How long a domain transfer takes, step by step
The headline number hides several small waits. Here is where the time goes for a standard transfer between ICANN-accredited registrars.
| Stage | What happens | Typical time |
|---|---|---|
| Preparation | You unlock the domain and get the authorization (EPP) code from your current registrar | Minutes to a day |
| Submission | You enter the code at the new registrar and pay the transfer fee | Minutes |
| Authorization email | The current registrar sends a confirmation message to the domain holder. ICANN's policy says it must be sent no later than 24 hours after the registry request | Up to 24 hours |
| Approval window | You approve, or the current registrar waits. If it does not respond within 5 calendar days, the transfer is approved by default | Minutes if you approve, up to 5 days if you do not |
| Registry update | The registry records the new registrar | Usually within hours of approval |
Add these up and you get the figure most registrars quote: roughly 5 to 7 days when nobody intervenes, and far less when someone does. The fast path depends on one question: does your old registrar let you approve the outgoing transfer yourself? If it does, you can usually finish the same day. If it does not, the request sits until the window closes.
Two practical notes follow from that:
- Check the old registrar right after you submit. The transfer is started at the new registrar, but the old one holds the brake. The new registrar cannot speed it up for you.
- Look at the email address on the domain's contact record before you begin. The approval message goes there, and a dead mailbox is one of the most common reasons a transfer drags.
Country-code domains follow their own rules. A .co.uk, .ca or .com.au transfer can be faster, slower or handled with a different process, so do not apply .com expectations to them. This article covers the generic domains most US site owners hold.
The 60-day rule, explained
The phrase "60-day lock" covers three different situations. Mixing them up is the main reason people are surprised by a refused transfer.
60 days after you register a domain
Under ICANN's policy, a domain generally cannot be transferred within 60 days of its initial registration. If you bought a domain last month and want to move it to your hosting provider, you will need to wait out the remainder of the period. Nothing you do at either registrar changes that.
60 days after a previous transfer
The same policy applies after an inter-registrar transfer: you generally cannot move the domain again within 60 days. There are exceptions, such as an agreed transfer back to the original registrar. So if you moved a domain by mistake, ask both registrars about reversing it rather than starting a fresh transfer.
60 days after changing the registrant
This one catches business owners who are tidying up records. ICANN's Change of Registrant rules treat a material change to the registrant's name, organization or email address as a security event. It needs separate confirmation, and it can start a 60-day lock on transfers. Some registrars offer an opt-out, but they are not obliged to. Ask before you edit anything.
The lesson: correct the contact name and email first, wait out any lock, and only then start a time-sensitive transfer. Our own walkthrough of the 60-day transfer lock goes deeper on how registrars apply it.
The 60-day rule is an eligibility block, not a processing delay. A registrar may also refuse a transfer for other policy reasons, including evidence of fraud, a reasonable dispute over identity, certain unpaid registration charges, an express objection from the authorized holder, or legal proceedings. It must give you the reason.
What makes a transfer slower
Most delays trace back to a short list.
- The domain is still locked. Registrar lock is on by default at many registrars. If it is on when the request arrives, the request is denied.
- The authorization code is wrong or expired. A bad code means a failed request that you have to restart. Copy it carefully and use it only with the registrar you chose. Our guide to getting EPP codes right covers the usual pitfalls.
- The approval email never arrives. It goes to the registrant address on file. Check spam folders, and confirm the address is one you can still open.
- Outdated contact details. An old email or a retired employee's address stalls everything.
- A recent registration, transfer or registrant edit. See the 60-day rule above.
- Unpaid or expired status. A domain that has lapsed needs to be renewed first. If yours has just expired, read about the renewal grace period before doing anything else.
- A pending dispute or legal hold. These are rare, but they stop a transfer outright.
How to move faster without cutting corners
ICANN's waiting period exists so that the current holder has a chance to spot and stop an unauthorized move. So speed should come from finishing the authentication steps promptly, not from skipping the security window.
- Choose the destination registrar first. The transfer is initiated there, not at the old one.
- Confirm the registrant email works. Log in to that mailbox and make sure you can receive mail.
- Finish any contact edits early. Avoid triggering a change-of-registrant lock in the middle of a project.
- Unlock the domain and request the code in the same sitting.
- Submit the transfer and pay. Most generic transfers add a year to the registration term, but the new registrar charges a transfer fee that includes that year. Check the displayed renewal price too, not just the first-year price.
- Approve at the old registrar. Look for a pending outbound transfer in your account, or for the authorization email, and approve it.
- Watch for the confirmation. When the status changes, the old registrar should invalidate the code.
Do not start a transfer close to the expiration date. Leave yourself a comfortable margin, so a rejected code or a missed email costs you days, not your domain.
Will your website go down during a transfer?
It should not. A registrar transfer changes who administers the domain, not where it points. As long as your nameservers stay the same, DNS keeps resolving through the transfer, so visitors and email carry on as before.
The risk appears when you change several things at once. Changing nameservers, DNS records, DNSSEC or mail settings during a transfer adds a separate propagation delay and makes problems harder to diagnose. Treat them as two projects:
- Project one: move the registrar, with nameservers untouched.
- Project two: after the transfer completes, point the domain to new nameservers or a new host.
Our guides on changing nameservers without downtime and how DNS management works cover the second project in detail. If you are also changing your site's address structure, plan for search visibility too: this site migration SEO guide explains how to map URLs and protect rankings, and our piece on redirecting one domain to another covers the redirect side.
For a full checklist, see our article on transferring a domain safely and avoiding downtime.
If your transfer is stuck
When a transfer runs past the expected window, check these four things in order:
- Status and lock. Is the domain still locked at the old registrar, or showing a status that blocks outbound transfers?
- Authorization code. Generate a fresh one and resubmit if there is any doubt.
- Approval email. Search the registrant mailbox, including spam, for the message. Many registrars let you approve from the account dashboard instead.
- Eligibility. Rule out the 60-day restrictions, an unpaid balance, an identity dispute, a fraud review, a legal hold or a TLD-specific rule.
If a denial looks improper, ICANN provides a transfer-complaint route. Before going that far, our guide to fixing a failed domain transfer walks through WHOIS checks and the first hours after a failure.
Our perspective: treat the transfer as a scheduled change
We look after customer sites with SRE and DevOps engineers in the EU and US, and the pattern we see is consistent. Transfers rarely fail because the process is hard. They fail because someone started one under pressure: a domain about to expire, a contact email nobody owns, a launch date set before the 60-day window had passed.
Our advice is to put the transfer on the calendar the way you would any other change to production. Fix the contact details first. Move the registrar with nameservers unchanged. Only then move the site or the DNS. Keeping those steps apart means that if one goes wrong, you know exactly which one.
We also think renewal pricing belongs in the decision. A low first-year transfer price is easy to compare, but the figure you will pay every year afterward matters more. That is why we stress honest renewal pricing.
— Ihor
Moving your domain to inSave Hosting
If you are ready to consolidate your domain and hosting in one dashboard, you can start on our domain transfer page. If you also need a home for the site, our shared hosting and WordPress hosting plans include free migration, daily backups and free SSL, backed by a 30-day money-back guarantee. Plan details and pricing are on those pages.
Frequently asked questions
How long does a domain transfer take?
Most .com, .net and .org transfers complete in 5 to 7 days. If your current registrar lets you approve the outgoing transfer, it can finish within hours. If you do nothing, the request is approved by default after the registrar's 5-day response window.
Is there really a 60-day rule for new domains?
Yes. A newly registered domain generally cannot be moved to another registrar for 60 days. The same limit usually applies after a previous registrar transfer, and a change of registrant details can add a further lock. Wait until the period ends, then start the transfer.
Will my website or email stop working during a transfer?
Not if you leave the nameservers alone. The domain stays registered and DNS keeps resolving while the registrar changes. Downtime comes from changing DNS settings at the same time, so do that after the transfer is complete.
Can I speed up a domain transfer?
Partly. You cannot skip the security window, but you can approve the request at your old registrar as soon as it appears, use a correct authorization code and make sure the registrant email works. Those steps remove nearly all avoidable delay.
Does a transfer renew my domain?
For most generic domains, a successful transfer adds one year to the registration term, and the transfer fee covers that year. Rules differ by extension, so check the new registrar's terms for your TLD before you pay.
Sources
- ICANN Transfer Policy
- ICANN FAQs for Registrants: Transferring Your Domain Name
- ICANN Transfer Policy Implementation Update (Change of Registrant)
- DNSimple Help: What Is Domain Transfer?
- Site Migration SEO guide