How Long Does a Domain Transfer Take? Real 2026 Timelines

So you've decided to move your domain to a cheaper registrar — now the only question is: how long will you be stuck waiting? Search any registrar's help center and you'll get the same two-word headline: "5–7 days." That's technically true for a .com moving between registrars, but it's also the least useful answer possible. A transfer can finish in under 24 hours if you do it right, or drag on for weeks if one small thing is wrong. And here's the part nobody tells you: most of the delay happens before the transfer clock even starts.

This guide gives you the real, stage-by-stage timeline, a checklist for the under-24-hour "fast lane," and fixes for every stall we've seen — so you never sit refreshing a transfer status page again.

The short answer: transfer timelines by scenario

Scenario	Realistic timeline	Why
.com / .net / .org between registrars	5–7 days (can be under 24 hours)	ICANN gives the losing registrar a 5-day approval window
Same registrar, new account (account push)	Minutes to a few hours	No ICANN process — it's an internal account change
ccTLD (.uk, .de, .ca)	24 hours to ~10 days	Each registry runs its own rules; no ICANN 5-day rule
Transfer with everything pre-approved	Same day	You approve the release at the old registrar yourself

The headline number everyone quotes — 5–7 days — comes from one ICANN rule: after the transfer is requested, the current registrar has 5 calendar days to respond. If it does nothing, the transfer is approved automatically on day 5. That's the default path. Everything faster than that requires someone — usually you — to act.

Where the days actually go: the 5 stages

Stage 1 — Preparation at the old registrar (0–2 days, often the longest part)

Before any clock starts, you must: unlock the domain (it shows as clientTransferProhibited in WHOIS while locked), confirm your registrant email is one you can actually access, and request the auth code (also called AuthInfo or transfer code). ICANN's policy says the registrar must provide the code within 5 calendar days of your request — most give it instantly, but some registrars drag their feet, and that's where "my transfer took forever" stories usually begin.

Stage 2 — Submit at the new registrar (minutes)

You enter the domain and auth code at the gaining registrar and pay the transfer fee. That fee includes a 1-year renewal at the new registrar's current rate — it's not a separate charge on top. Note: a transfer can't push your total registration beyond 10 years.

Stage 3 — The ICANN 5-day approval window (up to 5 calendar days)

The registry notifies your old registrar. Your old registrar can approve it, reject it, or ignore it. Silence = approval on day 5. This is the window you can collapse yourself — most registrars let you log in and manually approve the transfer-out, which ends the wait immediately.

Stage 4 — Registry processing (hours to ~1 day)

Once approved, the registry moves the domain. This is usually fast — hours, not days.

Stage 5 — Verification at the new registrar (minutes to hours)

The domain appears in your new account. Your website and email keep working throughout — a registrar transfer doesn't touch your DNS or nameservers unless you change them yourself.

Why most transfers take longer than the headline number

In our experience, delays almost never come from Stage 3–4. They come from Stage 1:

• Wrong registrant email. Approval emails go to the registrant contact on file. If that's an old work address, the transfer dies quietly.
• Domain still locked. One missed toggle and the transfer request is rejected on day 0.
• Slow auth code. Some registrars take the full 5 calendar days ICANN allows.
• 60-day locks. A domain can't transfer within 60 days of registration, a previous transfer, or a change of registrant. This is the #1 "why was my transfer rejected?" reason.
• Near-expiry domains. Some registrars won't release a domain within 7 days of expiration without manual approval — start your transfer before the last week.

The fast lane: how to finish a transfer in under 24 hours

This is the part the 5–7-day articles skip. Do all of this and your transfer can complete the same day:

1. Unlock the domain at your current registrar and check WHOIS shows no clientTransferProhibited status.
2. Confirm the registrant email is yours, and turn off registrar WHOIS privacy if your old registrar requires it for the transfer (some do).
3. Request the auth code, and keep it somewhere safe — codes expire.
4. Submit the transfer at the new registrar with the exact code (copy-paste; typos are a classic stall).
5. Immediately log back into your old registrar and approve the transfer-out manually. This is the single biggest time-saver — it skips the 5-day auto-approval wait entirely. GoDaddy, for example, can complete a transfer in as little as 15 minutes once the old registrar releases the domain.

Pre-transfer checklist (copy this)

• ☐ Domain is unlocked
• ☐ Registrant email is current and reachable
• ☐ Auth code obtained and saved
• ☐ Domain is older than 60 days, and no transfer or registrant change in the last 60 days
• ☐ Domain expires more than 7 days from today
• ☐ You know where to approve the transfer-out at your old registrar
• ☐ You've compared the new registrar's renewal price (not just the transfer price) — see our renewal price comparison

Timelines by domain type

gTLDs (.com, .net, .org)

The standard 5–7 day path described above. Fast lane (manual approval at the old registrar): under 24 hours.

ccTLDs (.uk, .de, .ca, .mx)

Each country registry sets its own process — the ICANN 5-day rule doesn't apply. Some are faster (.uk changes can process within 24–48 hours); others are slower (some TLDs like .mx can take up to 10 days, per Cloudflare's transfer troubleshooting docs). Check the specific registry's process before you start.

Same-registrar account push

Moving a domain between two accounts at the same registrar isn't a transfer at all — it's an internal push, usually instant to a few hours, and it doesn't add a renewal year.

5 reasons transfers stall — and how to fix each

1. "Transfer rejected — domain locked." Fix: unlock it at the old registrar, wait for WHOIS to update (allow up to 24 hours for some registrars), then re-submit.
2. "Invalid auth code." Fix: request a fresh code — old ones expire. Copy-paste it exactly; leading/trailing spaces break it.
3. "Transfer blocked by 60-day lock." Fix: wait it out, or change the registrant contact back and wait 60 days. Check the exact date the lock lifts in WHOIS.
4. "No approval email received." Fix: check spam, confirm the registrant email, and ask the old registrar to re-send. Some registrars require you to approve inside their panel instead of email.
5. "Stuck beyond 7 days with no reason." Fix: contact the old registrar — they hold the release. If WHOIS still shows locked after unlocking, allow up to 5 hours (some registrars up to 24 hours) for the change to propagate.

The money angle: a transfer is also a renewal

Because every registrar transfer includes a 1-year renewal at the new registrar's current price, timing a transfer is timing a renewal. Today, 1 November 2026, the Verisign .com wholesale price rose from $10.26 to $10.97 — registrars pass increases like this on over time, so the renewal price you see today at a budget registrar may not be the price in six months. Transferring now locks in a year at today's rate, and you don't lose any time you've already paid for — the year is added to your existing expiry date.

Run the numbers before you move: use our free domain renewal calculator to compare 5-year costs across registrars, and read our step-by-step guides to transferring to Porkbun or getting out of GoDaddy.

FAQ

How long does it take for a domain to transfer, exactly?

For a .com between registrars: 5–7 days by default (the ICANN 5-day approval window), or under 24 hours if you manually approve the release at your old registrar. Same-registrar account pushes take minutes to hours.

Will my website or email go down during the transfer?

No. A registrar transfer only moves the registration — your nameservers and DNS stay exactly as they are unless you change them yourself.

Can I speed up a domain transfer?

Yes — approve the transfer-out at your current registrar immediately after submitting. That's the difference between 15 minutes and 5 days. Everything in the fast-lane checklist above also removes the pre-clock delays.

Does transferring a domain extend it?

Yes — a transfer between registrars adds one year to your expiry date at the new registrar's renewal price. (It can't push you past 10 years total.) An account push at the same registrar does not add a year.

What if my transfer is stuck past 7 days?

Contact your old registrar first — the release is in their hands. Ask specifically whether there's a hold, lock, or failed auth code on the domain.

Bottom line

Plan for 5–7 days, aim for under 24 hours by approving the release yourself, and do the 10-minute pre-transfer checklist before you submit. Almost every "my transfer took three weeks" story is a Stage 1 problem — wrong email, forgotten lock, or a slow auth code — not the transfer itself. If you're moving mainly to pay less, start with our transfer vs renew comparison and the renewal audit checklist so the move actually saves you money.