Domain transfers usually take anywhere from a few minutes to 7 days, depending on the domain extension, the registrar involved, and whether the transfer is approved promptly. For most generic domains, the transfer process is often completed within 5 to 7 days if no action is needed from the current registrar. Some transfers can finish much faster when the domain is already unlocked, the authorisation code is correct, and approval emails are confirmed quickly.
If you are moving a domain to a new hosting provider or registrar, it helps to understand the steps that affect the timeline. A domain transfer is not the same as changing DNS records or pointing nameservers to a new service. DNS changes can take effect quickly, while a full transfer moves the domain registration itself to the new provider.
How long a domain transfer usually takes
The answer depends on the type of domain and the transfer method, but these are typical timeframes:
- Instant to a few hours: Some transfers are completed quickly if the gaining registrar supports fast approval and the losing registrar does not delay the release.
- 1 to 3 days: A common timeframe when both sides process the request efficiently and the domain owner confirms the transfer promptly.
- 5 to 7 days: The standard timeline for many gTLD transfers, such as .com, .net, and .org, if the transfer is not manually approved earlier.
- Longer than 7 days: Less common, but possible if the domain is locked, the auth code is wrong, contact details are outdated, or there is a dispute or registry restriction.
In practice, many hosting customers complete the administrative steps in less than an hour, but the overall transfer can still wait on registrar-level processing or policy-based delays.
What affects domain transfer time
Several technical and administrative factors can speed up or slow down a transfer. Knowing them in advance helps avoid avoidable delays.
Domain extension
Different domain extensions have different transfer rules. Generic domains such as .com, .net, and .org often follow a standard process, while country-code domains may have stricter or more varied requirements. Some registries support quicker transfers, while others require additional validation steps.
Domain lock status
Most domains must be unlocked before transfer. If the domain is still locked at the current registrar, the transfer request will not complete. In many control panels, this option appears as Domain Lock or Transfer Lock. Turning it off is usually one of the first steps.
Authorisation code
An auth code, also called an EPP code or transfer code, is required for most transfers. If the code is invalid, expired, or does not match the domain record, the transfer may fail or be rejected. Always copy it exactly as provided by the current registrar.
Registrar approval process
Some registrars approve transfers automatically, while others require the domain owner to confirm by email. If the approval message goes to an old or inaccessible mailbox, the transfer can stall until the issue is fixed.
Domain age and recent changes
Domains registered or transferred very recently may be subject to transfer restrictions. A common rule is that a domain cannot be transferred within a certain period after registration or a previous transfer. Changes to contact details or nameserver settings usually do not block transfer, but they can sometimes trigger extra checks.
Contact email access
The transfer approval email is often sent to the administrative contact on file. If that email address is not working, the transfer may remain pending. Before starting, make sure the contact details in the registrar panel are correct and accessible.
Transfer timeline by domain type
While exact timing varies, the following estimates are useful when planning a move to ITA or another hosting provider:
- .com, .net, .org: Usually 5 to 7 days, often sooner if approved quickly.
- Many UK-related and European domain extensions: Timing varies by registry; some complete in hours, others take several days.
- Country-code domains: Transfer timing depends on registry policy and may require extra steps, such as owner validation or registry-specific forms.
If the domain is part of a business website, plan the transfer carefully so it does not interfere with email routing, SSL renewal, or website availability.
Steps to transfer a domain without delays
Following the correct process is the best way to reduce transfer time. The exact names of the options may differ between registrars, but the workflow is usually similar.
1. Check eligibility
Confirm that the domain is eligible for transfer. Look for any restrictions such as:
- recent registration or recent transfer
- transfer lock still enabled
- expired domain status
- pending ownership or contact changes
- registry-level blocks
If you are moving the domain to a hosting platform with a control panel such as Plesk, confirm whether the domain is being transferred only, or whether hosting, DNS, and email will also be moved.
2. Unlock the domain
Log in to the current registrar and disable the transfer lock. In many control panels, this is a simple toggle. Keep the domain unlocked only for as long as needed to complete the move.
3. Request and verify the auth code
Request the transfer code from the current registrar. Some providers send it by email, while others display it in the account panel. Check that the code is complete and not truncated.
4. Make sure contact details are up to date
Verify the admin email address and other relevant contact fields. Transfer verification messages are usually sent there. If the mailbox uses spam filtering, whitelist registrar messages before starting the transfer.
5. Start the transfer at the new provider
Enter the domain name and auth code in the gaining registrar or hosting platform transfer form. Review the transfer summary carefully before submitting.
6. Approve the transfer email
If the process requires confirmation, approve the transfer as soon as you receive the email. This is often the fastest way to shorten the overall timeline.
7. Wait for completion and verify the result
Once the transfer is accepted, monitor the domain status in the new account. When the transfer completes, confirm that nameservers, DNS zones, and any linked services are still correct.
Domain transfer versus DNS change
It is important not to confuse a domain transfer with a DNS update.
- Domain transfer: moves the registration from one registrar to another.
- DNS change: updates where the domain points, such as web hosting or email servers.
- Nameserver change: delegates DNS management to another provider.
You can usually change DNS or nameservers without transferring the domain. In many cases, this is enough when moving a website to a new hosting platform but keeping the domain at the current registrar. If you do transfer the domain, you may still need to recheck DNS settings after completion.
How to avoid downtime during a transfer
A domain transfer should not cause downtime by itself, but service interruptions can happen if DNS or email settings are not prepared. To keep the website and mail services online:
- copy the current DNS zone before making changes
- lower TTL values in advance if you plan to change nameservers
- verify A, CNAME, MX, SPF, DKIM, and DMARC records
- make sure the new hosting account is ready before starting the transfer
- test the site using the temporary hostname or preview URL, if available
- confirm that email accounts are created before switching mail routing
If your website is managed through Plesk, review the domain’s DNS settings after transfer and confirm that the hosting subscription still contains the correct document root, SSL certificate, and mail configuration.
What to check before moving a domain to ITA
Before starting a transfer to ITA, it is good practice to prepare the domain and the associated services. This reduces the risk of waiting longer than necessary.
- the domain is unlocked
- the auth code is available and valid
- the administrative email address can receive messages
- the domain is not within a registrar transfer restriction period
- the current DNS records are documented
- mailboxes, SSL certificates, and website files are ready on the new platform
- any third-party services tied to the domain are noted, such as site verification, CDN, or external mail filtering
If the domain is attached to a managed hosting service, check whether the provider also handles DNS migration. This can save time when updating records after the transfer completes.
Common reasons a transfer is delayed
Most delays come from a few repeat causes. If your transfer has not completed within the expected time, check these first.
The domain is still locked
Even if the transfer has been submitted, the request will not progress if the domain remains locked at the current registrar.
The auth code is wrong
A single incorrect character can cause the transfer to fail or remain pending. Re-request the code if needed.
The approval email was missed
Look in spam, junk, promotions, and filtered folders. Some mail systems delay external messages or quarantine them.
The domain is expired or close to expiry
Expired domains may have different transfer behavior depending on the registry and registrar policy. In some cases, renewal must happen before transfer can proceed.
Registry restrictions apply
Certain registries enforce rules such as waiting periods after registration, ownership change verification, or additional documentation for transfer.
Contact details are outdated
If the email address on file is no longer valid, transfer approval may be impossible until the details are updated.
Can you use the domain while it is transferring?
Yes. In most cases, the domain continues to work during the transfer. Website availability depends more on DNS than on the registrar itself. If nameservers and DNS records remain unchanged, visitors should still reach the site while the transfer is in progress.
That said, avoid changing too many things at once. If you are moving both the domain and hosting at the same time, make one change at a time where possible:
- prepare the new hosting account
- copy the site and mail data
- test everything on the new platform
- transfer the domain
- update DNS or nameservers only when ready
What happens after the transfer completes
Once the transfer is finished, the domain appears in the new registrar or hosting account. At this point, review the following:
- renewal date and auto-renew settings
- domain lock status
- nameservers and DNS zone contents
- mail routing and mailbox settings
- SSL certificate status
- any redirects or subdomain records
If you manage the domain through a hosting control panel, confirm that the domain is assigned to the correct subscription and that the web root points to the right site files. For Apache-based environments, also check that virtual host settings match the intended domain configuration.
Frequently asked questions
Why is my domain transfer taking so long?
The most common reasons are a locked domain, an incorrect auth code, an unapproved verification email, or registry-specific waiting periods. If none of these apply, contact both the current and new registrar to check the transfer status.
Does transferring a domain change my website content?
No. A transfer only moves the registration. Your website files stay where they are unless you also move hosting or update DNS.
Will email stop working during the transfer?
Not if your DNS and mail records stay unchanged. However, if you are also moving hosting or nameservers, make sure MX and related records are copied correctly first.
Can I transfer an expired domain?
Sometimes, but it depends on the registrar and registry rules. In many cases, it is safer to renew the domain before starting the transfer.
Do I need to change nameservers when I transfer a domain?
No. A transfer and a nameserver change are separate actions. You can transfer the domain and keep the existing DNS setup if that is what you want.
How do I know when the transfer is finished?
You will usually receive a confirmation email from the new registrar, and the domain will appear in your account. The status may also update in the control panel.
Summary
A domain transfer can take anywhere from a few minutes to 7 days, with 5 to 7 days being common for many domains. The exact time depends on the extension, registry rules, domain lock status, auth code accuracy, and how quickly approval emails are completed. To avoid delays, unlock the domain, confirm contact details, request the correct transfer code, and start the process only when your hosting and DNS settings are ready.
If you are moving a domain to a new hosting platform, remember that the transfer itself does not move your website or email. Those services still depend on DNS, nameservers, and the configuration in your control panel. Planning these steps together helps ensure a smooth move with minimal interruption.