Transferring a domain to a new registrar sounds intimidating, but it is a well-defined, standardised process with a fixed set of steps — and once you know the sequence, it is routine. A domain transfer moves the registration of your domain from one registrar (the company you bought or currently manage it through) to another, without changing the domain itself. Your website and email keep working throughout if you prepare correctly. This cornerstone guide walks you through the whole transfer, start to finish.

You will learn what a domain transfer is and is not, the prerequisites that must be met before you can transfer, the exact step-by-step process, what happens to your website and email during it, how long it takes and how to track it, and the common problems and how to avoid them. By the end you will be able to transfer any eligible domain to a new registrar confidently, with no surprises.

What a domain transfer is (and isn’t)

A domain transfer is the process of moving your domain’s registration from your current registrar to a new one. A registrar is the accredited company through which you register and manage a domain, and transferring changes which registrar holds and manages that registration — but it does not change the domain name itself, its ownership, or where your website and email are hosted. You still own the same domain; you are simply managing it through a different company.

It is important to distinguish a domain transfer from things it is often confused with. It is not the same as moving your website (that is web hosting migration, a separate thing), nor the same as pointing your domain at a new host (that is changing DNS or nameservers, which you can do without transferring at all). A transfer specifically relocates the registration — the administrative record of the domain — to a new registrar.

So understanding a domain transfer correctly is the foundation: you are changing the company that manages your domain’s registration, nothing more. Your website stays on its host, your email stays where it is, and your domain remains yours — provided you handle the DNS carefully (covered below). People often transfer to consolidate a domain and hosting under one provider, to get better pricing or management, or simply to leave a registrar they are unhappy with. Whatever the reason, the process is the same standardised sequence everywhere.

The prerequisites before you can transfer

Before you can transfer a domain, several conditions must be met — these are standardised rules that apply across registrars, designed to prevent unauthorised or hasty transfers:

• The domain is at least 60 days old at its current registrar: a domain registered or previously transferred within the last 60 days is locked from transfer by an industry rule.
• The domain is unlocked: the registrar ‘transfer lock’ (a protection setting) must be turned off before a transfer can proceed.
• You have the auth/EPP code: the unique authorisation code that proves you are entitled to transfer the domain, obtained from your current registrar.
• Your contact email is current: the domain’s administrative email must be one you can access, since transfer approval emails go there.
• The domain isn’t expired or in dispute: it should be in good standing, not lapsed or subject to a hold.

These prerequisites are non-negotiable because they are enforced by the domain system itself, not just one registrar’s preference. The two you most actively control are unlocking the domain and obtaining the auth code — both done at your current registrar before you begin. The 60-day rule is a common surprise: if you recently registered or transferred the domain, you simply have to wait. Meeting all these conditions first is what makes the actual transfer go smoothly rather than bouncing back with an error.

The step-by-step transfer process

With the prerequisites met, the transfer follows a clear sequence. At your current registrar: unlock the domain (turn off the transfer lock), and obtain the auth/EPP code (sometimes emailed to you, sometimes shown in the domain settings). These two actions prepare the domain to leave.

At the new registrar: start a transfer (there is usually a clear ‘transfer a domain’ option), enter your domain name, and provide the auth/EPP code when prompted. You will typically pay the transfer fee at this point — which, for most domains, also extends your registration by a year, so it is not money lost. The new registrar then initiates the transfer request with the current registrar.

Then comes approval and confirmation: you will usually receive an email (at the domain’s administrative address) asking you to confirm the transfer — approve it promptly, as this speeds things up. The current registrar may also offer to release the domain immediately or let it run its course. Once approved, the transfer completes and the domain appears in your new registrar account. So the sequence is: unlock and get the code at the old registrar, request and pay at the new one, then approve the confirmation — a handful of clear steps in order.

What happens to your website and email during a transfer

A crucial reassurance: a domain transfer, done correctly, does not take your website or email offline. This is because the transfer moves the registration, not the DNS settings that direct your traffic — and if the DNS settings carry over unchanged, your domain keeps pointing at the same website and mail servers throughout, so visitors and email continue to reach you.

The key to keeping it seamless is ensuring your DNS records are preserved through the transfer. Ideally, your DNS configuration (the records pointing your domain at your host and mail servers) is either replicated at the new registrar beforehand or carried over, so there is no gap. The risk is not the transfer itself but a DNS reset — if the new registrar applies default DNS that does not match your setup, your site or email could break, which is why you preserve or recreate the records.

So during a properly handled transfer, your website and email keep working, because the transfer is an administrative change to registration while your DNS continues directing traffic as before. The practical safeguard is to note your current DNS records before transferring and confirm they are in place at the new registrar, so nothing points to the wrong place afterward. Handle the DNS with care and a transfer is invisible to your visitors — the whole point of doing it correctly.

How long it takes and tracking it

A domain transfer is not instant — it typically takes up to five to seven days to complete, though it can be faster if you approve the confirmation promptly and the current registrar releases the domain quickly. This built-in delay is a deliberate safeguard in the domain system to prevent unauthorised transfers, giving time for the confirmation and any objection.

You can speed it up meaningfully by approving the transfer confirmation email immediately (a slow approval is the most common cause of a transfer dragging on), and, at some registrars, by explicitly accepting/releasing the transfer from the losing registrar’s side rather than waiting for the automatic timeout. Both registrars usually show the transfer’s status in your account, so you can track its progress from ‘pending’ to ‘completed’.

So expect a domain transfer to take several days, plan for that window, and track its status in both registrar accounts. Crucially, because DNS is preserved, your site and email keep working throughout this waiting period — the transfer running in the background does not affect your live services. So the multi-day duration is not downtime; it is simply the administrative process completing while everything continues to function. Approve promptly, track the status, and it resolves within the expected window.

Common problems and how to avoid them

Most domain-transfer problems come from the prerequisites not being met, and are easily avoided by checking them first. The most common is the domain still being locked — if you forget to unlock it, the transfer is rejected, so always confirm the transfer lock is off. A wrong or expired auth code is another frequent one: the code must be exact and current, so copy it carefully and use it promptly.

The 60-day rule catches many people: if you registered or last transferred the domain within 60 days, the transfer will be blocked and you must wait out the period. An inaccessible administrative email is a subtler trap — if the confirmation email goes to an address you cannot check, you cannot approve the transfer, so update your contact email to a working one before starting. And a domain too close to expiry can complicate a transfer, so avoid transferring right at renewal time.

So the common problems — a locked domain, a bad auth code, the 60-day rule, an inaccessible email, an expiring domain — all trace back to prerequisites, and all are avoidable by verifying those conditions before you begin. If a transfer does fail, the error usually tells you which condition was not met, so you can fix it and retry. Checking the prerequisites first is the single best way to make a domain transfer go through cleanly on the first attempt, without the frustration of a bounced request.

FAQs

How do I transfer a domain to a new registrar?

At your current registrar, unlock the domain (turn off the transfer lock) and get the auth/EPP code. At the new registrar, start a transfer, enter the domain, provide the auth code, and pay the transfer fee (which usually adds a year to your registration). Then approve the confirmation email sent to your domain’s administrative address. The transfer completes in about five to seven days. Preserve your DNS records so your site and email keep working.

Does transferring a domain move my website too?

No. A domain transfer moves only the registration — which company manages your domain — not your website or email, which stay on their host. Transferring is often confused with website migration (moving the site to a new host) and with pointing DNS at a new host; those are separate. If your DNS records are preserved through the transfer, your site and email keep working exactly as before.

What do I need before transferring a domain?

The domain must be at least 60 days old at its current registrar, unlocked (transfer lock off), and in good standing (not expired or in dispute). You need the auth/EPP code from your current registrar, and access to the domain’s administrative email (approval emails go there). Meeting all these before you start is what makes a transfer go through cleanly rather than bouncing back with an error.

How long does a domain transfer take?

Typically up to five to seven days, though it can be faster if you approve the confirmation email promptly and the current registrar releases the domain quickly. The built-in delay is a safeguard against unauthorised transfers. Because your DNS is preserved, your site and email keep working throughout — the multi-day duration is not downtime, just the administrative process completing in the background.

Will my website go down during a domain transfer?

Not if you handle the DNS correctly. A transfer moves the registration, not the DNS settings that direct your traffic, so if your DNS records are preserved (replicated at the new registrar or carried over), your domain keeps pointing at the same site and mail servers throughout. The risk is a DNS reset applying defaults that don’t match your setup — so note your records beforehand and confirm they’re in place at the new registrar.

Why did my domain transfer get rejected?

Usually a prerequisite wasn’t met: the domain was still locked (transfer lock on), the auth/EPP code was wrong or expired, the domain was within the 60-day rule (registered or transferred in the last 60 days), the confirmation email went to an inaccessible address, or the domain was expired or in dispute. The error usually names the issue — fix that condition and retry. Checking all prerequisites first avoids most rejections.

The bottom line

Transferring a domain to a new registrar is a standardised, routine process once you understand what it actually is: moving your domain’s registration — which company manages it — from one registrar to another, without changing the domain, its ownership, or where your website and email are hosted. It is not website migration and not a DNS change; it is purely an administrative relocation of the registration. The process succeeds cleanly when you meet the prerequisites first: the domain at least 60 days old at its current registrar, unlocked, in good standing, with the auth/EPP code in hand and an accessible administrative email. Then the sequence is simple — unlock and get the code at the old registrar, request and pay at the new one (the fee usually adds a year to your registration), and promptly approve the confirmation email.

The reassurance that makes the whole thing low-stress is that your website and email keep working throughout, because the transfer moves registration while your DNS continues directing traffic — provided you preserve those DNS records, noting them beforehand and confirming they are in place at the new registrar so nothing resets to defaults. Expect the transfer to take about five to seven days (faster if you approve promptly), track its status in both accounts, and remember that this waiting period is not downtime — your live services run normally in the background. Nearly every transfer problem — a locked domain, a bad auth code, the 60-day rule, an inaccessible email — traces back to an unmet prerequisite, so checking those first is what turns a domain transfer from an intimidating unknown into a routine, no-surprises task that completes on the first attempt.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. To transfer a domain to a new registrar: at the old registrar, unlock it and get the auth/EPP code; at the new one, request the transfer, enter the domain and code, and pay (usually adds a year); then approve the confirmation email. It takes about 5-7 days. A transfer moves only the registration, not your site or email — preserve your DNS records so they keep working. Most rejections come from unmet prerequisites (locked domain, bad code, the 60-day rule, inaccessible email), so check those first.