Domain transfer: how long it takes depends first on which kind you mean. Moving a domain to another account at the same registrar, a push, needs no auth code and no registry hand-off. Moving it to a different registrar runs through the registry and the old registrar, and their timers set the pace. Escrow.com, which handles domain sales, puts the range at “a few minutes to up to six weeks” depending on the registrar. Registrar pages were checked on 25 October 2026.
The ICANN timers behind a registrar transfer
Under current ICANN rules, the losing registrar must send its confirmation email “not later than twenty-four (24) hours” after the registry tells it about the request. If it then fails to respond “within five (5) calendar days”, the transfer is approved by default. That is where the usual “up to five days” comes from. It is a default-approval window, not a promise that every transfer finishes in five days.
| Rule | Time |
|---|---|
| Losing registrar sends confirmation | Within 24 hours |
| No response from losing registrar | Default approval after 5 calendar days |
| Auth code and unlock, if no self-service | Within 5 calendar days of your request |
| After registration or a previous transfer | Registrar may deny for 60 days |
| After a change of registrant | 60-day lock unless you opted out beforehand |
ICANN has been reviewing the Transfer Policy; check icann.org for changes. Its plain-English summary is the registrant FAQ on transferring your domain name.
Domain transfer time by registrar
Each registrar publishes its own estimate, and they do not agree. These are their own words.
| Registrar | Stated time | Fast path stated |
|---|---|---|
| Namecheap | “30 minutes to 8 days”; old registrar releases “within up to 5-7 calendar days” | Ask the old registrar to speed up the outgoing transfer |
| GoDaddy | “Most domain transfers complete in 5-7 days” | “under 15 minutes” after you release it manually at the old registrar |
| Cloudflare | “Up to 10 days”; most registrars “within 5 business days” (.mx up to 10 business days) | Approve via the old registrar’s email or dashboard |
| Porkbun | “Five to seven days” (one page); “5 to 7 business days” (another) | Same day, “usually almost instantly”, if the old registrar allows |
| Dynadot | “1-15 days” (2026 page); “five to fifteen days” (2025 page) | Not stated |
| Spaceship | “autocomplete in 30 minutes, but no longer than 5 days max” | Not stated |
Read the GoDaddy figure carefully. Fifteen minutes is the fast path; GoDaddy itself says most take five to seven days. Dynadot’s two help pages give different ranges, so treat 15 days as its outer bound. The differences come from TLDs, business versus calendar days, and how quickly the losing registrar acts.
A push at the same registrar
A push skips the registry timers. Namecheap says that with the destination profile filled in, “the domain will be moved to it almost instantly”. Dynadot calls a push “free and quite quick”, and Spaceship’s changelog says you can “Instantly transfer domains in bulk to other accounts”. It is not always instant, though: the receiver often has to accept by email, within 72 hours at Porkbun or about a week at Dynadot. The receiving steps are in how to accept a domain push.
The 60-day locks
Two separate 60-day rules can stop a registrar transfer before it starts. First, ICANN says “Your registrar may deny a transfer request if the domain name is within 60 days of initial registration”, and the same applies within 60 days of a previous registrar transfer. “May” matters: it is the registrar’s choice.
Second, after a change to the registrant name, organisation or email, the registrar must apply a 60-day lock unless you opted out before the change. ICANN adds that “the registrar does not have to offer this option.” Its advice is practical: “you may want to consider completing the transfer process before changing your contact information.” This is also why sellers often push instead, since a push is not an inter-registrar transfer.
To see where a domain stands, check its creation date. The Domain Age Checker shows the registration date and true age for up to 20 domains, with a flag for domains that were dropped and re-registered. It will not show a change-of-registrant lock; only the registrar knows that.
What speeds a transfer up
- Unlock first. A domain with clientTransferProhibited will be rejected. Cloudflare says if “Transfer in progress” lasts more than 24 hours, check that you unlocked it. The statuses are explained in domain status codes.
- Use a fresh code. Cloudflare notes codes are “usually only valid for a limited period”, so request it when you are ready. More on getting one in domain authorisation codes.
- Approve at the losing registrar. Cloudflare, GoDaddy and Porkbun all point to the old registrar’s email or dashboard as the way to skip the wait.
- Check payment before submitting. Cloudflare warns a failed payment “can leave the transfer in a partially started state.”
- Keep the registrant email reachable. Dynadot says certain TLDs need verification emails through that address.
Timing around expiry matters too. Dynadot recommends “initiating the domain transfer at least 2 weeks before the expiration date”. If you have just renewed, Namecheap asks you not to transfer “within 45 days of the previous expiration date”, and Porkbun warns that within 45 days “your registration may not be extended for an additional year.” Cloudflare adds a step of its own: the domain must be active on Cloudflare first, which “usually takes a few minutes but can take up to 24 hours.”
Why transfers stall, and what to do
Most stalls are the losing registrar waiting out its five days. Dynadot’s advice, if you have authorised and confirmed everything, is that “we are most likely waiting for your previous domain registrar to approve the transfer.” Ask them to release it, or wait for the default approval.
A rejection is different. Cloudflare says it happens “if you declined the transfer request, or if the registrar determined the domain is not eligible”; you start a new request. Check for a 60-day lock, a dispute, or an unpaid prior period. Expiry alone is not a reason: ICANN says registrars “are not allowed to deny a transfer due to expiration or nonrenewal”, though a name in redemption must be restored first. If you believe a transfer was wrongly denied, ICANN accepts transfer complaints.
The limit here is plain: these are each registrar’s own estimates, not measured times, and a stubborn losing registrar can use all of its window.
Frequently asked questions
Why does a domain transfer take five days?
Under current ICANN rules, the losing registrar has five calendar days to respond; if it does nothing, the transfer is approved by default. Approving it yourself is usually faster.
How long does a Namecheap domain transfer take?
Namecheap says “anywhere from 30 minutes to 8 days”, depending on the TLD and how quickly your current registrar releases the domain.
Can I transfer a domain I registered last month?
Possibly not to another registrar: your registrar may deny it within 60 days of registration. A push to another account at the same registrar is a different process.
Does the transfer add a year?
Under ICANN policy a completed registrar transfer adds one year, up to ten years in total. Some country-code names work differently.
The takeaway Check the registry dates with the Domain Age Checker before you agree a timeline. If you are buying, browse aged domains on the SERPHeroes marketplace, where a push between accounts is fast, a registrar transfer typically takes up to five days, and you can follow every step on your order page.
