How Long Does a Domain Transfer Take, and How to Make It Faster
The appraisal desk is open
Type a domain like sunsetcapital.com or a keyword like capital to see its estimated value, the sales that prove it, and matching names for sale.
Automated estimate for informational purposes only. Not financial or investment advice, and not a guarantee of sale price.
Short answer: An inter-registrar domain transfer normally completes in 5 to 7 days. Most of that is a single mandatory wait: under ICANN's Transfer Policy the losing registrar gets 5 calendar days to respond, and if it says nothing, the transfer is approved by default. Approve it yourself in the losing registrar's control panel and the same transfer can finish in a day or two. A push between two accounts at the same registrar is different and lands in minutes, because no registry transfer happens at all.
The number people actually get wrong is not the duration, it is whether the transfer can start. A 60-day lock after a registration, a previous transfer or a change of registrant will block it outright, and that lock is what turns a "one week" transfer into a two-month wait. Here is the whole timeline, what is fixed by policy, and the parts you control.
How long each kind of transfer takes
| Type of move | How long | Auth code needed? | What decides the speed |
|---|---|---|---|
| Account push at the same registrar | Minutes to a few hours | No | Nothing touches the registry, so only the registrar's own confirmation step applies |
| Inter-registrar transfer, you approve it | 1 to 2 days | Yes | You explicitly approve at the losing registrar instead of waiting out its window |
| Inter-registrar transfer, left to run | 5 to 7 days | Yes | The 5-day losing-registrar window expires and the transfer auto-approves |
| Change of registrant, then a transfer | Up to 60 days, then 5 to 7 | Yes, after the lock | A 60-day lock follows the registrant change unless the prior registrant opted out first |
| Newly registered or just-transferred name | Blocked for 60 days | Not applicable | ICANN bars a transfer within 60 days of registration or of a prior registrar transfer |
Read that table from the bottom up if you are buying a domain. The last two rows are where deals go wrong, because a buyer who assumes "about a week" and discovers a 60-day lock has a launch date problem, not a paperwork problem.
Why does a domain transfer take 5 days?
Because ICANN's Transfer Policy gives the current registrar a fixed window to object. When the gaining registrar submits the request, the registry notifies the registrar of record, which then has 5 calendar days to respond. Failure to respond within those 5 calendar days results in a default approval, and the transfer proceeds. That window exists to protect registrants against names being moved without authorization, and it is the single largest fixed block of time in the process.
The important consequence is that the 5 days is a maximum, not a minimum. It is a deadline for an objection, so an explicit approval ends it immediately. Most registrars expose this as a "pending transfers out" screen with an approve button, and almost nobody looks at it. That one click is the difference between a two-day transfer and a five-day one.
A second 5-day rule catches people out separately: your registrar must provide the authorization code within 5 calendar days of your request. Many registrars let you generate it instantly in the control panel, but if yours makes you file a ticket, that request can legitimately sit for most of a week before the transfer has even started. Ask for the auth code first, before you tell anyone a date.
The step-by-step timeline
| Step | Typical time | Who controls it |
|---|---|---|
| Check eligibility: no 60-day lock, domain not expiring within a few days | Minutes | You |
| Unlock the domain and turn off privacy if the registrar requires it | Minutes | You |
| Obtain the authorization code | Instant, or up to 5 days by policy | Losing registrar |
| Start the transfer at the new registrar and pay the fee | Minutes | You |
| Confirm the transfer email from the gaining registrar | Minutes, if you see it | You |
| Losing registrar responds, or stays silent | Up to 5 calendar days | Losing registrar, unless you approve |
| Registry completes the transfer | Usually within hours | Registry |
Five of those seven steps are yours, and each of them is measured in minutes. The two that are not yours are capped at 5 days each by policy. When a transfer takes three weeks, it is nearly always because a confirmation email went to an old address on the registrant record, and nobody noticed for a fortnight.
What actually blocks a transfer: the 60-day locks
Three events start a 60-day inter-registrar transfer lock: a new registration, a completed registrar transfer, and a Change of Registrant. The first two are widely known. The third is the one that ambushes domain buyers, and it is worth getting exactly right because most guides state it wrongly.
When the registrant details change, the registrar applies a 60-day lock. Registrars may offer the prior registrant the chance to opt out of that lock, but only before the change of registrant is requested. The new registrant can never opt out, and nobody can opt out after the fact. So if you are buying a domain and want to move it to your own registrar quickly, the opt-out has to be arranged by the seller, in advance, as part of the deal. Once the change has gone through, the 60 days are simply real.
This is the single best argument for taking an account push instead of a registrar transfer when you buy a name. A push moves the domain into your account at the seller's registrar in minutes, with no auth code and no waiting. You can move it to your preferred registrar later, on your own schedule, when the lock has expired and nothing depends on the timing.
Does my website go down during a domain transfer?
No, and this is the most common unnecessary worry. A registrar transfer moves the domain's sponsorship from one registrar to another. It does not change the nameservers, so DNS keeps resolving from wherever it resolved before, and your site and email carry on exactly as they were. Downtime during a transfer happens when someone also changes the nameservers at the same time, or when the new registrar's default DNS silently replaces the old records.
So do these two things in separate weeks. Transfer the registrar first, confirm everything still resolves, then change nameservers later if you need to. Before you touch either, write down the current records: A, AAAA, CNAME, MX, TXT and any SPF or DKIM entries. Mail is the part that breaks quietly, because a missing MX record does not produce an error page, it produces silence, and you find out when a customer mentions it a week later. Putting the domain and its mail exchanger behind continuous uptime monitoring for the fortnight around a move is the cheapest insurance there is, since the failure mode you care about is the one nobody notices.
Can a domain transfer be cancelled or sped up?
Cancelled, yes, but only while it is pending. The losing registrar can reject a transfer inside its 5-day window, and the registrant can normally cancel from either side before the registry completes it. Once the transfer has completed, it is done, and undoing it means a fresh transfer back, which starts its own 60-day lock. That asymmetry is why you should double-check the auth code and the destination account before you submit, rather than after.
Sped up, also yes, and it is mostly about removing your own delays:
- Request the auth code first. It can legitimately take 5 days to arrive. Everything else waits on it.
- Fix the registrant email before you start. The confirmation goes to the address on the domain record, not to your account login. Stale contact details are the number one cause of a stalled transfer.
- Approve the transfer at the losing registrar. Look for "pending transfers out" and approve it manually. This alone typically saves 3 to 4 days.
- Unlock and disable privacy up front. A locked domain or a privacy service that masks the registrant will cause an outright rejection, and you restart from zero.
- Do not transfer in the last week before expiry. Some registries reject it, and you risk the name lapsing mid-process. Renew first, then move.
One reassurance on the renewal question, because it stops people transferring at all: you do not lose the time you already paid for. An inter-registrar transfer requires a one-year renewal, and that year is added on top of the remaining term rather than replacing it, up to the 10-year maximum a gTLD registration can hold.
Where the transfer sits in a domain purchase
If you are transferring because you just bought the name, the transfer is the last step, not the first, and the order protects you. Money goes into escrow, the seller unlocks the domain and releases the auth code only once those funds are confirmed, you take control, and the escrow agent releases payment after you verify it. Doing the transfer before the money is secured means handing over the asset on trust, which is how private domain deals go wrong. The mechanics and the current fee tiers are on our domain escrow page, and the full handover sequence is in transferring a domain to a new owner.
Timing also matters when you are buying a name that is not for sale yet. If you are waiting on an expiring domain, the drop timeline runs 65 to 80 days before you can even attempt to register it, which is covered in our guide to domain backorders. If the name is owned and actively used, the route is a direct approach through a domain acquisition service, and there the negotiation takes far longer than any transfer will. In both cases the 5 to 7 day transfer is the fastest and most predictable part of the whole exercise.
Questions people ask
How long does a domain transfer take? Normally 5 to 7 days for an inter-registrar transfer. The bulk of that is the 5 calendar days ICANN gives the losing registrar to respond, after which the transfer approves by default. If you approve it manually at the losing registrar, it usually completes in 1 to 2 days. A push between accounts at the same registrar takes minutes.
Why is my domain transfer still pending? Almost always an unanswered confirmation email or the losing registrar's 5-day window still running. Check the email address on the registrant record rather than your account login, since that is where the confirmation goes. If both are clear, check that the domain is unlocked and privacy is off, because a rejection can look like a pending state for a while.
How long after buying a domain can I transfer it? Sixty days, if the purchase involved a change of registrant or a fresh registration. The lock is applied by the registrar under ICANN policy. The prior registrant could have opted out before the change was requested, but you as the new registrant cannot, so raise it with the seller before closing if timing matters.
Do I lose my remaining registration time when I transfer? No. The mandatory one-year renewal that comes with an inter-registrar transfer is added to the time you already have, up to the 10-year maximum. If your name had 14 months left, it will have 26 months after the transfer.
Does a domain transfer affect SEO? Not on its own. Search engines resolve your site through DNS and see no change when the sponsoring registrar changes, so rankings are unaffected. What does affect SEO is downtime or broken DNS caused by changing nameservers at the same moment, which is a good reason to separate the two operations by a week or two.
Before you move a name you have just acquired, it is worth knowing what it is actually worth on paper. Run it through a domain appraisal against real sold comparables, and if you are holding several names, domain portfolio management covers the renewal and lock discipline that keeps a portfolio from leaking value through missed dates.