What Is a Domain Transfer?
A domain transfer is the process of moving a domain name's registration from one registrar to another while keeping the same domain and ownership. It typically requires unlocking the domain, obtaining an authorization code (EPP or auth code), and approving the transfer, after which the new registrar takes over renewals and management. Transfers are governed by ICANN rules, usually take a few days, and do not by themselves move your website or email, only the registration.
- Authorization
- Requires an EPP/auth code from the current registrar (ICANN)
- Typical duration
- Often 5-7 days for most gTLDs to complete (ICANN)
- 60-day rule
- Domains generally cannot transfer within 60 days of registration or a prior transfer (ICANN)
- What moves
- Registration only; website files, DNS, and email must be handled separately
What is a domain transfer? #
A domain transfer moves the management of a domain name from your current registrar to a new one without changing the domain itself or who owns it. Your registrar is the company where you registered and pay for the domain, and transferring means switching that relationship to a different provider, perhaps for better pricing, service, or to consolidate domains in one place. The domain name, your ownership, and typically your website and email keep working throughout if handled correctly, because a transfer only changes which company holds the registration record and bills you for renewals. The process is standardized under ICANN rules for most common extensions and involves a few verification steps to prevent unauthorized moves. It is important to understand that a domain transfer is distinct from moving your website's files or changing your DNS; those are separate tasks. Confusing them is a common source of downtime. Our /services/domains-dns-email service manages transfers cleanly, and /services/website-migrations coordinates the whole picture when you are moving hosting at the same time.
What is the difference between a domain transfer and a website migration? #
This distinction trips up many business owners, and getting it wrong causes outages. A domain transfer changes only the registrar, the company that manages your domain registration and renewals. A website migration, by contrast, moves your actual website files, database, and content from one hosting server to another. And changing DNS updates where your domain points, directing visitors and email to specific servers. These are three separate things that people often lump together. You can transfer a domain to a new registrar while your website stays on the same host, or move your website to new hosting without ever transferring the domain, simply by updating DNS. Understanding which task you actually need prevents unnecessary risk. If you only want cheaper renewals, you need a domain transfer alone. If you want a faster host, you need a migration and a DNS change, not necessarily a transfer. Our /services/website-migrations service handles hosting moves, /services/domains-dns-email handles registrar transfers and DNS, and we coordinate all three when a project involves more than one. See /wiki/what-is-dns for how pointing works.
What are the requirements to transfer a domain? #
Several conditions must be met before a domain can transfer, mostly to prevent theft. First, the domain must be unlocked at the current registrar; a registrar lock, or transfer lock, is a security setting that blocks transfers and must be disabled. Second, you need the authorization code, variously called the EPP code, auth code, or transfer secret, which the current registrar provides and which proves you are authorized to move the domain. Third, the domain generally cannot be transferred within 60 days of its initial registration or a previous transfer, an ICANN rule that prevents rapid churning. Fourth, the domain should not be expired or in a redemption period, and administrative contact details must be reachable because approval emails are often sent there. Finally, domain privacy sometimes needs to be temporarily lifted so verification can occur. Meeting these requirements up front makes the transfer smooth. Our /services/domains-dns-email team gathers the auth code, unlocks the domain, and confirms eligibility before starting, so the transfer proceeds without the frustrating rejections that come from missing a prerequisite.
How does the domain transfer process work step by step? #
The process follows a predictable sequence. First, at your current registrar, you unlock the domain and request the authorization code, which may arrive instantly or after a short delay. Second, at the new registrar, you initiate the transfer by entering the domain and the auth code and paying the transfer fee, which usually includes a one-year renewal. Third, both registrars verify the request; you typically receive an approval email that you must confirm, and the losing registrar may offer a window to accept or decline. Fourth, once approved, the transfer completes, commonly within five to seven days for most extensions, and the new registrar becomes responsible for the domain. Throughout, if your DNS settings are preserved, your website and email keep working uninterrupted, because the transfer moves registration, not hosting. A critical best practice is to note your existing DNS records before transferring, in case they need to be re-entered at the new registrar. Our /services/domains-dns-email team documents DNS first, then executes each step, so nothing breaks. For hosting moves alongside, we add /services/website-migrations.
Will a domain transfer take my website or email offline? #
It should not, if done correctly, but the risk is real when DNS is not preserved. A transfer moves the registration, not your hosting or DNS, so as long as your DNS records remain intact and pointed at the same servers, your website and email continue functioning during and after the move. Problems arise when the new registrar resets DNS to its own defaults, wiping the records that point your domain to your website and email, which can knock both offline. That is why documenting all existing DNS records, the A records, CNAMEs, MX records for email, and any TXT records for authentication, before transferring is essential, so they can be recreated immediately if reset. Email is especially fragile here because MX and authentication records are easy to overlook. A careful transfer confirms DNS continuity at every step. Our /services/domains-dns-email team captures your full DNS zone before starting and verifies it after, ensuring your website stays up and email keeps flowing. If a botched transfer has already caused an outage, /services/website-rescue can restore service quickly by rebuilding the missing records.
What are common problems during a domain transfer? #
Several issues commonly derail transfers. The domain may still be locked, causing immediate rejection until you disable the registrar lock. The auth code may be wrong, expired, or not yet issued, so the new registrar cannot verify authorization. The 60-day rule may block a recently registered or transferred domain. Approval emails sent to an outdated administrative contact may go unseen, stalling the process. Domain privacy may hide the contact needed for verification. The domain may be too close to expiration, risking loss during the transfer window. And DNS may be reset at the destination, taking the site or email offline. Most of these are avoidable with preparation: unlock early, get the correct code, confirm contact details, check eligibility, and document DNS. When a transfer stalls or breaks something, quick diagnosis matters. Our /services/domains-dns-email team anticipates these pitfalls, and if something has gone wrong, /services/website-rescue troubleshoots stalled transfers and restores any services affected by DNS resets, getting your business back online while the registration completes.
Why transfer a domain in the first place? #
Businesses transfer domains for several practical reasons. Consolidation is common: if your domains are scattered across multiple registrars, moving them to one provider simplifies management, renewals, and billing, reducing the chance a domain lapses because a renewal notice went to a forgotten account. Cost is another driver, since renewal prices vary between registrars. Better service and security features, such as stronger account protection, cleaner dashboards, or included privacy, motivate moves too. Sometimes a transfer accompanies a change of web agency or hosting provider, bringing the domain under the same roof as the rest of your web presence for easier coordination. And acquiring a domain from a previous owner involves a transfer to your own account. Whatever the reason, the goal is smoother, safer management of a critical business asset. Our /services/domains-dns-email service often consolidates clients' scattered domains into one well-secured account, and when clients move to us for /services/managed-hosting or a /services/website-redesign, we can bring the domain along so everything, registration, hosting, and email, is coordinated in one place.
How do you keep a domain secure before, during, and after transfer? #
Domains are valuable targets, and a transfer is a moment of heightened risk, so security discipline matters throughout. Before transferring, ensure your registrar account uses a strong password and two-factor authentication, since an attacker who controls your account could hijack the transfer. Keep the registrar lock on except during the actual transfer window, and re-enable it immediately afterward. Guard the auth code like a password, sharing it only with the legitimate new registrar. Watch for phishing emails that impersonate registrars and try to trick you into approving a fraudulent transfer or revealing your code; verify any transfer message independently. After the move, confirm the domain shows in your new account, re-enable the lock and privacy, and verify DNS and email still work. These practices protect one of your most important business assets from hijacking. Our /services/website-security and /services/domains-dns-email teams apply these safeguards on every transfer, and our companion entry /wiki/what-is-domain-privacy explains the privacy layer that also helps shield your domain from the scams that often target it.
FAQ
Will transferring my domain take my website offline?
Not if done correctly. A transfer moves registration, not hosting or DNS, so your site and email keep working as long as DNS records are preserved. Outages happen when the new registrar resets DNS. Our /services/domains-dns-email team documents your full DNS zone before transferring and verifies it after, so nothing breaks during the move.
How long does a domain transfer take?
Most common domain extensions complete in about five to seven days under ICANN rules, though some finish faster once you approve the confirmation email. Delays usually come from missed approval emails, locked domains, or wrong auth codes. Our /services/domains-dns-email team prepares each prerequisite in advance so the transfer proceeds without avoidable hold-ups.
What is an EPP or auth code?
It is the authorization code your current registrar provides to prove you are allowed to transfer the domain. Also called an auth code or transfer secret, the new registrar requires it to initiate the move. Guard it like a password and share it only with the legitimate destination registrar, since it controls the transfer.
Why can't I transfer a domain I just registered?
ICANN rules generally prohibit transferring a domain within 60 days of its initial registration or a previous transfer, to prevent rapid churning and abuse. You must wait out this window before the domain becomes eligible. Our /services/domains-dns-email team checks eligibility first so a transfer is not rejected for this reason.
Is a domain transfer the same as moving my website?
No. A domain transfer changes only your registrar. Moving your website means migrating files and databases to new hosting, and pointing your domain means updating DNS. These are separate tasks. Our /services/website-migrations service handles hosting moves and /services/domains-dns-email handles registrar transfers, coordinated together when a project needs both.
How do I keep my domain safe during a transfer?
Use a strong password and two-factor authentication on both registrar accounts, guard the auth code, and watch for phishing emails impersonating registrars. Keep the registrar lock on except during the transfer window and re-enable it afterward. Our /services/website-security and /services/domains-dns-email teams apply these safeguards on every transfer.
Was this helpful?