To transfer a domain, you move its registration from one registrar to another: unlock the domain, get its authorization (EPP) code, start the transfer at the new registrar, pay (usually adding a year), and approve the confirmation email. It takes about 5–7 days for most extensions, and your DNS carries over so the site needn’t go down. A 60-day lock applies after registration or a prior transfer.
Transferring a domain is a well-trodden path — people move for better pricing, features or support all the time. It only goes wrong when a rule or a code is missed, so the trick is simply knowing the sequence before you start.
What is a domain transfer?
A domain transfer changes which registrar manages your registration. Importantly, it does not change ownership (you remain the registrant) and it does not, by itself, change where your site or email point. Think of it as switching the shop that administers your name — the name, and its settings, come with you.
Moving a domain’s registration from one registrar to another, using an authorization code, while preserving ownership and (if set up correctly) the existing DNS configuration.
Before you start: a checklist
Most failed transfers fail at the preparation stage. Confirm all of these first:
- The domain is at least 60 days old at its current registrar (and wasn’t transferred in the last 60 days).
- It is not expired or in redemption — renew first if it is close to expiry.
- Your contact email is current — approval messages go there.
- WHOIS privacy may need disabling temporarily, as some registrars require it off to read the contact email.
- The domain is unlocked and you have the authorization code (see below).
How to transfer a domain, step by step
- Unlock the domain. At your current registrar, turn off the “registrar lock” (transfer lock) for the domain.
- Get the authorization code. Request the EPP/auth code from the current registrar; it is often shown in the domain settings or emailed to you.
- Start the transfer at the new registrar. Enter the domain and the authorization code, and pay the transfer fee (usually one year’s registration).
- Approve the confirmation. Respond to the approval email, or approve within the new registrar’s dashboard. Approving promptly speeds things up.
- Wait for completion. The losing registrar releases the domain and the gaining registrar finalizes it — typically within about 5–7 days.
Note your name servers first
Before transferring, write down your current name servers and key DNS records. If you set the same name servers at the new registrar (or your DNS lives elsewhere entirely), your site and email keep working without interruption.
Rules and common gotchas
| Rule / gotcha | What to know |
|---|---|
| 60-day lock | No transfer within 60 days of registration or a previous transfer. |
| Registrar lock | Must be turned off before a transfer can begin. |
| Auth code | Required and case-sensitive; expires/regenerates at some registrars. |
| Near-expiry timing | Avoid transferring in the final days before expiry; renew first. |
| Contact email | Must be reachable; approval depends on it. |
Keeping your site and email online
The single biggest worry — downtime — is avoidable. Because a transfer moves the registration and not your hosting, your website and email stay live as long as the DNS keeps pointing where it already does. The safe approach: don’t change hosting in the same window, keep your existing name servers, and verify the DNS is identical at the new registrar before and after. Only once the transfer has settled should you make any further DNS changes.
Don’t change everything at once
Transferring the registrar and switching hosts and editing DNS all together is how outages happen. Do the transfer first, confirm the site is fine, then change one thing at a time.
After the transfer
Once complete, log in to the new registrar and: re-enable the registrar lock for security, turn WHOIS privacy back on if you disabled it, set up auto-renew, and confirm the domain’s expiry date reflects the added year. Your domain is now fully managed at its new home — same name, same site, new control panel.
★ Key takeaways
- A transfer moves the registration between registrars; ownership and DNS are preserved.
- Core steps: unlock, get the auth/EPP code, start & pay at the new registrar, approve.
- A 60-day lock follows registration or a prior transfer; it usually takes 5–7 days.
- Keep the same name servers and don’t change hosting simultaneously to avoid downtime.
Frequently asked questions
What is an EPP or authorization code?
An authorization code (also called an EPP code, auth code or transfer key) is a unique password for your domain that proves you are entitled to move it. You get it from your current registrar and give it to the new one to authorize the transfer.
How long does a domain transfer take?
For most gTLDs, a transfer takes around 5 to 7 days once initiated, though it can complete faster if you approve it promptly. The delay is built into the process to give the losing registrar time to confirm and the owner time to object if something is wrong.
Why can't I transfer my domain right after registering it?
ICANN’s policy imposes a 60-day lock after a domain is first registered or transferred between registrars. During this window the domain cannot be transferred again. It exists to deter fraud and hijacking. You must wait out the 60 days.
Will my website go down during a transfer?
It should not, if you prepare. A transfer moves the registration, not your DNS, and your existing name servers and records carry over if set correctly. Keep the same name servers, and avoid changing hosting at the same moment, to keep the site and email live.
Does transferring a domain renew it?
Usually, yes — most gTLD transfers add a year to the registration (and you pay for that year as part of the transfer). So a transfer typically both moves the domain and extends it by 12 months. Check the new registrar’s terms to confirm.