BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Transfer Time Expectations by Registrar: How Long a Domain Transfer Really Takes, What Drives the Clock, and the Numbers Side by Side in 2026
The honest answer to “how long does a domain transfer take” is five to seven days for the typical transfer, and the registrar guides converge on that number for a reason. It is not a billing window. It is the ICANN Transfer Policy clock, plus a handful of things the buyer controls and a handful they do not.
This guide gives the realistic timeline, decomposes what drives it, and then does the thing a single registrar’s help page cannot: it lays the time expectations out registrar by registrar, side by side, so the variance is visible instead of vague. Each window cited here traces back to ICANN’s published Transfer Policy or to the registrar’s own help documentation, not to a guess.
It also covers the case no competitor page touches. When a domain is acquired from an aftermarket source, the transfer clock interacts with the 60-day eligibility lock in a way that catches buyers out. SEO Domains operates the curated marketplace where aged and expired domains are screened before they are priced, so the lock status and transfer readiness are read up front, before the clock matters.
How long does a domain transfer take?
A domain transfer between registrars typically takes five to seven days from start to finish. That band is the ICANN Transfer Policy clock at work, and it is consistent across Network Solutions, Name.com, Namecheap, NameSilo, and Dynadot. When both parties approve quickly, the same transfer can finish within hours. When a lock, a wrong contact email, or an unanswered approval gets in the way, it can run past seven days.
The five-to-seven-day number is the single fact every guide on this topic agrees on, which makes it reliable as a planning baseline. Network Solutions, Name.com, Namecheap, NameSilo, Dynadot, and IONOS all state the same band in their help documentation. The reason they agree is that the band is not a registrar choice. It is built into the policy that governs every inter-registrar transfer of a generic top-level domain.
What the band hides is the variance underneath it. Two transfers of the same .com can finish hours apart because one mechanic, covered below, can be triggered or skipped. The job of this page is to make that variance legible: the floor, the ceiling, and the levers that move a transfer from one end of the band to the other.
The floor, the ceiling, and the typical case
The realistic spread runs from under an hour to multiple weeks, with five to seven days as the centre of the distribution. The floor is reached when the losing registrar releases the domain immediately on request. The ceiling is reached when a 60-day lock, a verification failure, or a stalled approval blocks the clock from starting or running. The typical case sits in the middle, where the transfer is left to auto-complete on the policy timer.
This is the same end-to-end move documented step by step in the Inter-registrar domain transfer walkthrough. This page is the timing companion to that walkthrough: not how to do it, but how long each part takes and why.
The 60-day eligibility locks: when the clock cannot even start
Before any transfer timeline applies, the domain has to be eligible. ICANN’s Transfer Policy imposes a 60-day lock after a domain is first registered, after a prior inter-registrar transfer, and, at the registrar’s discretion, after a change of registrant. While a lock is active, the transfer clock cannot start at all, which turns an expected one-week transfer into a multi-week wait if the lock is discovered late.
The leading timing shock is not a slow transfer. It is a transfer that cannot begin. A domain registered three weeks ago is not eligible to move, and no amount of preparation changes that until day 60. The eligibility lock sits in front of the five-to-seven-day clock, and it is the first thing to check before any timing estimate means anything.
| Trigger | Lock length | What it blocks |
|---|---|---|
| New registration | 60 days from the registration date | A freshly registered domain cannot move to a new registrar until the 60 days pass |
| Prior inter-registrar transfer | 60 days from the last transfer | A domain that just moved registrars cannot move again until the 60-day window closes |
| Change of registrant | Up to 60 days, at registrar discretion | Certain registrant-detail changes can trigger an optional 60-day transfer lock |
The full mechanics of these locks, including how the change-of-registrant lock can be waived at registrars that allow it, are covered in ICANN’s 60-day transfer rule. For timing purposes the rule is simple: confirm eligibility first, because a lock is the difference between a seven-day transfer and a seven-week one.
What really drives transfer time
Transfer time is driven by six factors: the losing registrar’s release speed, the authorization code, transfer and registry locks, the accuracy of the administrative contact, the TLD and its registry rules, and the gaining registrar’s processing. Three of these are inside the buyer’s control and three are not, and knowing which is which is the difference between a transfer that finishes on day one and one that drifts to day seven.
The five-to-seven-day band is an average of these forces pulling in different directions. Network Solutions frames the same drivers as registrar policies, status locks, contact details, and TLD rules. The decomposition below adds the one the field leaves implicit: who controls each factor, and therefore which delays can be removed and which have to be waited out.
Inside your control (removable delay)
Unlocking the domain at the losing registrar, obtaining and entering a valid authorization code, and keeping the administrative contact email current so the approval request reaches a live inbox. Get these right before you start and the clock runs clean.
Outside your control (waited-out delay)
The losing registrar’s policy on how fast it releases, the gaining registrar’s processing queue, and TLD or registry rules that add their own steps. These set the floor and ceiling of the band regardless of how prepared you are.
The authorization code and the locks
The authorization code, also called the auth code or EPP code, is the credential the gaining registrar needs to prove the transfer is authorised. An invalid, expired, or missing code is one of the leading reasons a transfer never starts. The full mechanics of obtaining and using it are in EPP code (auth code) explained. Alongside it sits the transfer lock, which has to be released before the code will be accepted. The lock-and-unlock timing is covered in Transfer locking and when to unlock.
The contact email is a hidden timer
The administrative contact email is where the approval and confirmation messages land. If that address is out of date, the transfer can stall silently because nobody sees the request to approve. Registration contact data now lives behind RDAP, the Registration Data Access Protocol that replaced WHOIS as the standard ICANN lookup on 28 January 2025, so verifying the contact is current is a quick check that prevents a slow failure.
Auto-approval versus the 5-day wait: the mechanic behind the variance
The single mechanic that explains the bulk of transfer-time variance is the losing registrar’s 5-day window. Under ICANN’s Transfer Policy, once a transfer is requested the losing registrar has up to five calendar days to act. If it explicitly approves or the owner approves on its side, the transfer completes within hours. If nobody acts, the transfer auto-completes when the 5-day window expires. That choice, approve now or wait out the timer, is the difference between a same-day transfer and a five-to-seven-day one.
This is the lever the single-registrar guides mention only in passing. The losing registrar is not slow by default. It is holding the domain for a defined window during which the rightful owner can confirm or cancel the move, a safety feature against hijacking. The window can be closed early by an explicit approval, or left to run to its end.
Fast path: explicit approval
The losing registrar offers an approve or release option, or the owner clicks an accept link in the confirmation email. The 5-day window closes immediately and the transfer completes within hours. This is how a transfer finishes the same day.
Default path: auto-complete on the timer
Nobody approves on the losing side, so the transfer waits for the 5-day window to expire and then completes automatically. Add the gaining registrar’s processing and this is the five-to-seven-day case the field describes as typical.
Namecheap and other registrars expose this directly: their help documentation explains that approving the transfer from the losing account, instead of waiting, completes it without the multi-day hold. The takeaway for timing is that the fastest transfer is one where the buyer has access to both accounts and approves on the losing side, collapsing the 5-day window to zero.
The transfer timeline, stage by stage
A transfer moves through five stages: preparation on day zero, the transfer request, the losing registrar’s authorization window of up to five days, completion at the gaining registrar, and DNS propagation as a tail of up to 48 hours. Only the authorization window and propagation consume real waiting time. The rest is same-day work the buyer controls.
Laying the stages out in order shows where the days really go. The preparation and request stages are fast and controllable. The authorization window is the bulk of the wait. Propagation is felt by the user but is not part of the registry transfer itself. The figure below maps each stage to its duration and to whether the buyer can shorten it.
Preparation. Unlock the domain, obtain the authorization code, confirm the administrative contact email is current, and disable privacy if the registrar requires it. Controllable, same-day work. Source: registrar transfer guides, cross-validated.
Transfer request. Start the transfer at the gaining registrar, pay the transfer fee, and enter the authorization code. The gaining registrar emails the confirmation request. Controllable, minutes.
Authorization window. The losing registrar has up to five days to act. Explicit approval closes it in hours; no action lets it auto-complete at the end. This is the bulk of the wait. Source: ICANN Transfer Policy.
Completion. The registry moves the domain to the gaining registrar and the domain appears in the new account. The transfer is now done at the registry level.
DNS propagation. If nameservers change with the transfer, the new records spread across resolvers worldwide. Not part of the registry transfer, but the last thing the user perceives as the move completing.
Transfer time expectations by registrar, side by side
The five-to-seven-day band is the same everywhere because the policy is the same, but registrars differ on how fast they release a domain, whether they offer an instant-approve option, and how their queue is structured. The table below sets the published expectations side by side. Every entry is the registrar’s own documented timing, not an invented figure, and the same policy floor applies to all of them.
This is the comparison a single registrar’s help page cannot give, because it can only describe its own service. Reading the field across pages shows that the differences are at the margins, the fast-approve path and the release speed, while the policy floor of the 5-day window and the 60-day lock binds every provider equally.
| Registrar | Published typical time | Fast-approve path | Timing note |
|---|---|---|---|
| GoDaddy | 5 to 7 days | Owner can accept the transfer to skip the wait | Documents the standard window with an option to approve early from the account |
| Namecheap | 5 to 7 days | Approve from the losing account to complete sooner | Help docs state approving rather than waiting completes the transfer faster |
| Cloudflare | Up to 5 days, often less | Auto-processes once authorization clears | Community and docs note many transfers clear well inside the window |
| Squarespace (former Google Domains) | 5 to 7 days | Standard policy timing | Inherited the Google Domains base; standard inter-registrar window applies |
| Dynadot | 5 to 7 days | Release on request available | Help docs describe the same band with a release-on-request option |
| NameSilo | 5 to 7 days, faster with approval | Accept the transfer to expedite | Documents typical durations and the common delay causes explicitly |
| Network Solutions | 5 to 7 days typical | Approval and processing on days 1 to 7 | Publishes a day-by-day timeline matching the policy window |
The pattern across the table is the point. No registrar can move faster than the policy floor when the transfer is left to auto-complete, and every registrar can be fast when the losing side approves explicitly. The registrar matters less than whether the fast-approve path is used. Choosing a provider on transfer speed alone is the wrong optimisation, because the speed is in the buyer’s hands more than the registrar’s.
Transferring a domain you just acquired: the aged-domain timing case
Transferring a domain bought from an aftermarket source adds one timing factor the standard guides ignore: the 60-day eligibility lock interacts with the moment of acquisition. If the domain was recently registered or recently transferred to the seller, the buyer inherits the remaining lock period. Reading the lock status before purchase is the single diligence step that prevents a multi-week surprise on a domain that was supposed to move in a week.
When a domain changes hands through a marketplace, the transfer to the buyer’s account can take one of two forms. An account push inside the same registrar moves it in minutes, covered in the Intra-registrar account push walkthrough. An inter-registrar transfer to the buyer’s preferred registrar follows the full five-to-seven-day path. The choice between them is explained in Push vs transfer: when each makes sense, and it is the first timing decision on any acquired domain.
This is where sourcing from a screened catalogue changes the timing. When the lock status, the registrar of record, and the transfer readiness are read before a domain is listed, the buyer knows on day one whether the move is a minutes-long account push or a week-long inter-registrar transfer. SEO Domains operates that curated marketplace, where aged and expired domains are checked for transfer readiness alongside their backlink and authority profiles. Browsing screened inventory on the SEO Domains marketplace means the transfer-time question is answered before purchase, not discovered after it.
The post-move tasks that follow once the domain lands in the new account, from nameserver setup to monitoring the inherited profile, are collected in the Post-transfer checklist for aged domains.
Why is my transfer taking so long? Delays, causes, and fixes
A transfer runs past the expected window for a short, repeatable list of reasons: an active 60-day lock, a still-locked domain, an invalid or expired authorization code, an unanswered approval at a stale contact email, privacy or registrar holds, or a registry-side delay on certain TLDs. Each has a specific fix, and the list resolves to one habit: complete the controllable preparation before starting the clock.
The top follow-up question to this topic, confirmed across the live results, is “why is my domain transfer taking so long”. The answer is rarely a single broken registrar. It is one of the drivers from earlier in this guide sitting unresolved. The table consolidates them as a scannable reference: the symptom, why it stalls the clock, and the move that clears it.
| Symptom | Why it stalls the clock | The fix |
|---|---|---|
| Transfer rejected before it starts | An active 60-day lock from a recent registration or prior transfer | Confirm eligibility first; wait out the lock or check the exact end date |
| Authorization code not accepted | The domain is still locked at the losing registrar | Disable the registrar transfer lock, then re-enter the code |
| Code keeps failing | The auth code is expired, mistyped, or has hidden whitespace | Request a fresh code and paste it without leading or trailing spaces |
| Stuck waiting for approval | The confirmation email went to a stale administrative contact | Update the contact email in RDAP, then resend the transfer approval |
| Privacy or hold blocking the move | WHOIS or RDAP privacy, or a registrar account hold, is active | Disable privacy if required and clear any account hold before starting |
| Domain past expiry mid-transfer | An expired domain cannot be transferred until it is renewed | Renew the domain first, then initiate the transfer |
| Slower than the band on a country TLD | Some registries add their own steps beyond the ICANN gTLD policy | Check the registry rules for that TLD and plan for the extra step |
When a transfer fails outright instead of running slow, the full diagnostic walkthrough is in Transfer failures: common causes and fixes. For a contested transfer where the dispute itself drives the delay, see Handling a transfer dispute.
Transfer-time frequently asked questions
The five questions buyers raise when they search for how long a domain transfer takes, answered against the ICANN Transfer Policy and the published registrar timing.
Q1How long does a domain transfer take on average?
Five to seven days for the typical inter-registrar transfer, a band that Network Solutions, Name.com, Namecheap, NameSilo, and Dynadot all publish. The figure is the ICANN Transfer Policy clock, chiefly the losing registrar’s window of up to five days, plus the gaining registrar’s processing. With an explicit approval on the losing side, the same transfer can finish in hours.
Q2Why do I have to wait 60 days to transfer my domain?
ICANN’s Transfer Policy locks a domain for 60 days after it is registered, after a prior inter-registrar transfer, and optionally after a change of registrant. The lock is an anti-abuse measure that prevents rapid churning of a domain between registrars. While it is active the transfer clock cannot start, so a domain registered last week is not eligible to move until day 60.
Q3Can I speed up a domain transfer?
Yes, by clearing everything inside your control before you start, then approving on the losing side. Unlock the domain, obtain a valid authorization code, confirm the administrative contact email is current, and disable privacy if the registrar requires it. Then approve the transfer from the losing account instead of letting the five-day window run, which collapses the bulk of the wait to minutes.
Q4Does transfer time differ by registrar?
The typical band is identical across registrars because the ICANN policy floor is identical. What differs is whether a registrar offers an instant-approve path and how quickly the losing side releases the domain. GoDaddy, Namecheap, Cloudflare, Dynadot, NameSilo, and Network Solutions all document the same five-to-seven-day window with their own fast-approve options, so the lever is the approval path, not the brand.
Q5How long after buying a domain can I transfer it?
It depends on the domain’s lock status at the moment of purchase. If it was registered or transferred within the last 60 days, the remaining lock period carries to the buyer, so the move waits until the lock lifts. If the domain is outside any lock, an inter-registrar transfer follows the standard five-to-seven-day path, while an account push at the same registrar can complete in minutes. Reading the lock status before purchase removes the guesswork.
Source a domain that transfers fast and clean
Transfer time is governed by policy windows and a short set of controllable steps, but the cleanest fast transfer starts before the clock: with a domain whose lock status, registrar of record, and transfer readiness are known up front. A screened catalogue answers the transfer-time question at the point of purchase. SEO Domains operates that curated marketplace.
The transfer-readiness check is part of sourcing
Everything in this guide points to one practical conclusion. The variance in transfer time is mostly knowable in advance: the 60-day lock, the registrar of record, and the contact accuracy are all readable before a domain is acquired. When that read happens during sourcing, the buyer starts the transfer already knowing the path and the timeline, instead of discovering a lock after the deal closes.
What a screened listing tells you before you buy
A domain sourced from a curated catalogue carries its transfer facts alongside its authority profile, so the timing is priced in before purchase, not discovered after it. The signals that decide how fast it moves are read up front:
- The current registrar of record and whether an account push or a full inter-registrar transfer applies.
- The lock status, including any remaining portion of a 60-day eligibility lock.
- The registration and last-transfer dates that determine when the next move becomes eligible.
- A clean administrative contact and registration history with no hold that would stall an approval.
A domain that passes these checks moves on the predictable path. One that does not is the multi-week surprise this guide exists to prevent. Reading them before purchase is the difference between a planned transfer and an improvised one.
