How to Transfer a Domain: A Step-by-Step Guide to Moving Between Registrars

26 June 2026
by: Sebastian Vance
in: Domain Name
Tags: domain transfer, domains, transfer domain
note: no comments

Moving a domain from one registrar to another sounds intimidating, but the process is methodical and predictable once you understand what is actually happening. A domain transfer changes who manages your registration record — nothing more. It does not touch your website, your email, or your DNS unless you let it. In this guide, I will walk you through every prerequisite, the exact sequence of steps, and the single mistake that causes most “my site went down” panic posts after a transfer.

Table of Contents

This article is part of our complete guide to domain names, where you can see how registration, DNS, and ownership fit together as a system.

Key Takeaways
• A domain transfer moves your registration between registrars — it does not move your hosting, website, or email.
• Most prerequisites are simple: wait out the 60-day rule, unlock the domain, get the EPP/auth code, disable WHOIS privacy temporarily, and confirm your admin email works.
• Transferring usually adds a year to your registration, so your remaining time stacks rather than disappears.
• The transfer takes roughly 5 to 7 days, but you can often approve it manually to speed things up.
• Set or verify your DNS at the new registrar before you transfer to avoid downtime — this is the number one cause of post-transfer outages.

What does it actually mean to transfer a domain?

Transferring a domain means moving the registration of that domain from one registrar to another. A registrar is the company that holds your domain record and bills you for it — the business you log into to renew the name and manage its settings. When you transfer, you are changing which company sits in that role.

It is critical to separate three things that often get confused:

Registration — who manages and renews the domain. This is what a transfer changes.
DNS — the records (A, MX, CNAME, and others) that tell the internet where your website and email live. DNS can be hosted at your registrar, your web host, or a third party.
Nameservers — the servers that publish your DNS records. Whoever controls your nameservers controls where traffic goes.

A transfer touches the first item only. Your website and email follow DNS and nameservers, which are independent of who your registrar is. Keep that distinction in mind and the rest of this process becomes far less scary.

What do you need before you transfer a domain?

Before you initiate anything, confirm you meet the prerequisites. Skipping these is the most common reason a transfer gets rejected at the starting line.

The 60-day rule has passed. ICANN policy locks a domain from transfer for 60 days after it is first registered and for 60 days after any prior transfer. If you registered or moved the domain recently, you simply have to wait out the window.
The domain is unlocked. Registrars apply a “transfer lock” (sometimes called registrar lock or clientTransferProhibited) by default to prevent unauthorized moves. You must turn this off in your current registrar’s control panel.
You have the EPP/authorization code. Also called the auth code, transfer key, or EPP code, this is a password-like string that proves you own the domain. You request it from your current registrar, and it is often emailed to your admin contact.
WHOIS privacy is temporarily disabled. Many transfers require your contact details to be readable during the process. Turn privacy off before you start; you can turn it back on once the transfer completes.
Your admin email is valid and accessible. Approval messages are sent to the administrative contact on the domain. If that mailbox is dead or unmonitored, the transfer can stall or expire.

Run through this checklist deliberately. Five minutes of preparation prevents days of waiting and re-trying.

How do you transfer a domain step by step?

Here is the full sequence. The labels differ slightly between providers, but the order is the same everywhere.

Confirm eligibility. Verify the 60-day window has passed and that the domain is not expired or in a redemption period.
Verify your DNS first. Before anything else, check where your DNS is hosted and confirm your records are correct. (More on why this matters in the next section.)
Unlock the domain in your current registrar’s dashboard.
Disable WHOIS privacy temporarily so your contact details are visible during the transfer.
Request the EPP/auth code from your current registrar and copy it exactly — these codes are case-sensitive.
Start the transfer at the new registrar. Enter the domain name and the auth code, then complete payment for the transfer (which usually includes a year of registration).
Approve the transfer. You will typically receive a confirmation email from one or both registrars. Approving it manually can speed the process up considerably.
Wait for completion. The transfer finalizes automatically, usually within 5 to 7 days.
Re-enable WHOIS privacy and re-lock the domain at the new registrar once the move is confirmed.
Verify your site and email are still resolving correctly.

That is the entire process. Notice that DNS verification sits near the very top — that placement is intentional.

The insight most guides bury: transferring a domain does not move your website or email. Those services follow your DNS and nameservers, which are independent of your registrar. The number one cause of “my site went down after I transferred” is people assuming the transfer carries their DNS records along with it. It does not. If your DNS was hosted at the old registrar and you did not replicate those records (or keep external DNS in place), your nameservers can change during the move and your A and MX records vanish — taking your website and email with them. Set up or verify your DNS records at the new registrar, or confirm your domain still points to your external DNS provider, *before* you transfer. Treat DNS as a separate, prior task, not a side effect of the transfer.

What happens to your remaining registration time?

This is the question I get most often, especially from people researching a 5 year domain registration transfer or any multi-year setup. The good news: you almost never lose the time you already paid for.

For most generic top-level domains (.com, .net, .org, and many others), the gaining registrar adds one year of registration as part of the transfer. That new year stacks on top of your remaining time rather than replacing it.

Scenario before transfer	What the transfer adds	Result after transfer
5 years remaining	+1 year	6 years remaining
1 year remaining	+1 year	2 years remaining
Expiring next month	+1 year	Roughly 1 year + the leftover month

So if you had five years left and you transfer, you generally end up with six. Your existing time is preserved and extended — it does not reset and it does not get forfeited. The exact handling can vary by TLD (a few country-code domains behave differently), so it is always worth confirming with the gaining registrar, but the stacking rule is the standard for the common extensions.

How long does a domain transfer take?

A typical domain transfer takes about 5 to 7 days from start to finish. Much of that is a deliberate waiting period built into the system as a security measure — it gives the registrant a window to cancel an unauthorized transfer.

You can usually shorten this. If your current registrar sends a confirmation or “release” email, approving it manually tells the system to proceed immediately instead of waiting for the full auto-approval window to expire. When both registrars and the domain owner act promptly, a transfer that would take a week can sometimes complete in a day or two.

A few things that slow transfers down:

Leaving the domain locked (the transfer cannot even begin).
An incorrect or expired auth code.
An unmonitored admin email, so approval requests sit unanswered.
Trying to transfer inside the 60-day restriction window.

How do you avoid downtime during a transfer?

The mechanics here follow directly from the unique insight above. A transfer does not move your DNS, so the way to avoid downtime is to make sure your DNS is correct and stable before you start.

Two safe approaches:

Keep your DNS external. If your nameservers point to a third-party DNS provider or your web host, the transfer of the *registration* will not disturb those records. Confirm the nameservers stay set to your existing provider after the move.
Replicate your records first. If your DNS lives at your current registrar, copy every record — A, AAAA, CNAME, MX, TXT — into the new registrar’s DNS (or an external provider) *before* you transfer. Then point the nameservers there. When the registration moves, your traffic already has a stable home.

The golden rule: DNS first, registration second. Get your records resolving correctly from their new home, confirm they work, and only then move the registration. Done in that order, your visitors and email never notice a thing.

Transfer vs. pointing nameservers: which do you actually need?

People often want to “move” a domain when what they really need is to point it somewhere new. These are different operations:

	Transfer the domain	Point the nameservers / change DNS
What it changes	Who registers and bills for the domain	Where your website and email traffic go
Do you switch registrars?	Yes	No
Requires an auth code?	Yes	No
Typical time	5 to 7 days	Minutes to set, up to 48 hours to propagate
Adds registration time?	Usually +1 year	No
Use it when	You want a new registrar (better pricing, consolidation, support)	You only need to connect your domain to a new host or service

If your goal is simply to connect a domain you already own to a new website or host, you do not need a transfer at all — you just update your DNS or nameservers, which is faster and carries no waiting period.

What are the most common transfer failures?

Most rejected transfers come down to one of a handful of fixable issues:

Domain still locked. The single most common cause. Unlock it and retry.
Wrong or expired auth code. Re-request a fresh code and paste it carefully; these are case-sensitive and sometimes contain easily-confused characters.
Too recent. Inside the 60-day window after registration or a prior transfer, the system will refuse.
WHOIS privacy still on. Some gaining registrars cannot read the contact details they need; disable privacy first.
Pending expiration or redemption. A domain that is expired or in redemption usually has to be renewed or restored before it can move.
Unanswered approval email. The transfer quietly times out if no one approves it. Watch your admin inbox.

For context: people transfer domains between all kinds of registrars — from a budget registrar to a host that bundles services, or to a DNS-focused provider like Cloudflare when they want at-cost registration. The transfer mechanics are identical regardless of the names involved; only the dashboard labels change.

Make your next transfer effortless with DarazHost

DarazHost makes domain transfers simple. You get transparent transfer pricing that extends your registration (so your remaining years stack, not reset), free WHOIS privacy, and easy DNS setup so nothing breaks during the move. Because you can keep your domain, hosting, and email together in one place, there is no juggling separate accounts — and our 24/7 support will walk you through the auth code and unlock steps if you get stuck. If you have ever lost a weekend to a stalled transfer, this is the calmer way to do it.

Frequently asked questions

Will my website go down when I transfer my domain? Not if you prepare your DNS first. A transfer moves only the registration, not your DNS or nameservers. As long as your records are correct and stable at their new (or existing external) home before you start, your site and email keep working throughout.

Do I lose the time left on my registration when I transfer? No. For most common TLDs, the gaining registrar adds a year, and that year stacks on top of your remaining time. Five years left typically becomes six after the transfer.

Why can’t I transfer my domain — it keeps getting rejected? The usual culprits are a domain that is still locked, a wrong or expired auth code, an attempt inside the 60-day restriction window, or WHOIS privacy still enabled. Work through those four and the transfer almost always goes through.

How do I get my EPP or authorization code? You request it from your *current* registrar through their control panel. It is often emailed to your administrative contact. Copy it exactly, because the code is case-sensitive.

Can I speed up a transfer that says it will take 7 days? Often, yes. If your current registrar sends a release or confirmation email, approving it manually tells the system to proceed immediately rather than waiting for the full auto-approval period.