Skip to content

How to Transfer a Domain Name: A Step-by-Step Guide

To transfer a domain name to a new registrar, confirm the domain is eligible to move, copy its DNS settings, make sure the contact email on the registration is one you can read, unlock the domain at your current registrar, and request its authorization code. Then start the transfer at the new registrar, enter the code, pay for the transfer, and approve it if the old registrar asks. Most transfers finish within five days. Once the move is complete, check the new registration, turn the transfer lock back on, and expect the domain to stay locked against another registrar transfer for 60 days. This step-by-step guide covers each stage of moving your own domain in practical terms, including the details that cause most failed or disruptive transfers.

Transferring a domain name between registrars, shown on a keyboard

Make Sure a Registrar Transfer Is What You Need

The phrase “domain transfer” covers three different procedures. Moving a domain from one registrar (the company you pay to manage the registration) to another is an inter-registrar transfer, and it is the subject of this guide. Moving a domain between two accounts at the same registrar is usually called a push or an account change, and it needs no authorization code. Changing who owns the domain, for example after a sale, is a change of registrant. If you are moving your own domain to a new company and keeping it in your name, you need an inter-registrar transfer. Our guide to how domain transfers work explains all three, along with the ICANN Transfer Policy rules behind them.

The rules in this guide apply to generic top-level domains such as .com, .net and .org. Country-code domains follow their own registry’s rules. A .uk domain, for instance, is moved by changing its registrar tag rather than by authorization code. Check the new registrar’s instructions for any country-code domain before you begin.

Before You Start

Confirm the Domain Is Eligible to Transfer

First, confirm that the domain can move. A domain generally cannot be transferred to another registrar within 60 days of its initial registration or of a previous inter-registrar transfer. A change to the registrant’s name, organization or email address may also trigger a 60-day lock, unless the registrant opted out when the change was made. A domain that is close to expiring should be renewed before the transfer, and a domain that has already been deleted and is in its redemption period must be restored at the current registrar before it can go anywhere.

You can check the domain’s status codes in a public registration lookup. A status of clientTransferProhibited means your registrar’s transfer lock is on, which you can turn off yourself. A status of serverTransferProhibited means the registry has placed the lock, and your registrar will need to ask for it to be lifted. Our guide to domain status codes explains what each status blocks.

Copy Your DNS Settings and Decide Where DNS Will Live

This is the step most often skipped, and it is the cause of most transfer outages. Find out who hosts the domain’s DNS (the records that point the name at your website and email). If the nameservers belong to your web host or a DNS provider such as Cloudflare, the registrar transfer will not touch them, and the website and email should keep working. If the nameservers belong to the registrar you are leaving, the old registrar may stop serving those records once the domain leaves, and everything can go offline at once.

Before you start the transfer, export or write down every DNS record, including the A, CNAME, MX and TXT records. If DNS is hosted at the losing registrar, recreate those records at the new registrar or a separate DNS provider, switch the nameservers, and wait at least a day for cached answers to expire before you begin the transfer itself. Our guide to nameservers and DNS records explains each record type and how to change nameservers safely.

If the domain uses DNSSEC (DNS Security Extensions, which sign DNS records so resolvers can detect tampering) and the DNS provider is changing, plan that change separately. A signature that no longer matches the key published at the registry makes the domain unresolvable for any user behind a validating resolver. These errors are common: a 2025 study of 319,277 signed domains found that 25.6% had at least one DNSSEC error during the observation period, according to Ashiq et al., Decoding DNSSEC Errors at Scale. The usual approach is to remove DNSSEC well before changing DNS providers and turn it back on at the new provider afterward. Our DNSSEC guide explains why.

Check the Contact Email and Account Access

Then confirm that the registrant email on the domain is current and that you can receive mail there. Transfer notices, approval links and sometimes the authorization code itself are sent to that address. If it belongs to a former employee, a developer you no longer work with, or a mailbox on the domain you are about to move, change it first. Remember that changing the registrant email can trigger the 60-day lock described above, so make that change early or use the registrar’s opt-out if it offers one. Some registrars also ask you to turn off privacy protection before a transfer; many no longer require it.

Unlock the Domain and Get the Authorization Code

Next, sign in to your current registrar account and turn off the transfer lock, sometimes labeled “domain lock” or “registrar lock.” This removes the clientTransferProhibited status, which otherwise tells the registry to refuse any transfer request.

While you are in the account, request the authorization code. It is also called an auth code, an EPP code (after the Extensible Provisioning Protocol that registrars use to talk to registries) or a transfer authorization code. Some registrars display it on screen; others email it to the registrant address. Treat the code like a password, because it is one: it is unique to the domain, and anyone who has it while the domain is unlocked can request a transfer. Some registrars expire codes after a set period, so request it shortly before you plan to start the transfer.

Start the Transfer at the New Registrar

Once you have the code, go to the new registrar, often called the gaining registrar, and start a transfer for the domain. Enter the authorization code when prompted and pay the transfer fee. For most generic domains the fee includes a one-year extension of the registration, which is added to the existing expiration date, so you do not lose the time you already paid for. The gaining registrar then sends the request to the registry.

Approve the Transfer and Wait

After the request reaches the registry, the old registrar, called the losing registrar, has up to five days to act on it. Many losing registrars send an email asking you to approve or reject the transfer. Approving it usually completes the move within hours. If you do nothing, the registry generally completes the transfer automatically when the five-day window closes. If the losing registrar rejects the request, the most common reasons are a lock that is still on, a mismatched or expired authorization code, a domain inside its 60-day lock, or an unpaid balance on the account.

How Long a Domain Transfer Takes

Stage Typical timing
Moving DNS away from the losing registrar, if needed One to two days, including time for cached records to expire
Unlocking the domain and receiving the authorization code Minutes, or up to a few days at some registrars
Losing registrar’s response window after the request Up to five days; often hours if you approve the notice
Restriction on another registrar transfer after completion 60 days

ICANN’s Transfer Policy has been under review by an ICANN working group, and some of these intervals and names may change as revisions take effect. The current registrar’s transfer help page states the rules it applies today.

After the Transfer: Check, Relock and Secure

Finally, check the new registration. Confirm that the domain appears in your account at the new registrar, that the expiration date moved out by a year, and that the nameservers are exactly what you expect. Load the website and send a test email to and from an address on the domain. If you removed DNSSEC before the move, turn it back on at the DNS provider and confirm the new DS record has been published.

Then secure the domain at its new home. Turn the transfer lock back on, enable multi-factor authentication on the new account, confirm that the registrant details and renewal payment method are correct, and turn on auto-renewal. The domain is now locked against another registrar transfer for 60 days, which is a useful protection during the period when the new account is least familiar. Our guide to registrar account security lists the settings worth enabling on any new account.

If a Transfer You Did Not Request Appears

A transfer notice for a domain you did not ask to move is an emergency, because the transfer is the moment a domain is most often stolen. Reject the transfer through the losing registrar’s notice, call the registrar, ask them to relock the domain, and change the passwords on both the registrar account and the email account tied to the registration.

If the transfer has already completed, registrars have an urgent channel called the Transfer Emergency Action Contact (TEAC), and ICANN’s Transfer Policy requires a human response at the gaining registrar “within 4 hours, although final resolution of the incident may take longer,” as summarized in the ICANN Transfer Policy Review working group’s 2023 TEAC and TDRP briefing. Formal disputes between registrars fall under the Transfer Dispute Resolution Policy, which states that “a dispute must be filed no later than twelve (12) months after the alleged violation” and lets only the gaining or losing registrar file, according to the ICANN Transfer Dispute Resolution Policy. A domain owner cannot invoke either process directly, so the faster you get your registrar involved, the more options remain.

How DNAccess Helps

A domain transfer is routine when the domain is unlocked on purpose, the email is current, and the DNS has been planned. Our domain name management service moves domains between registrars for clients without gaps in DNS, email or security settings, and consolidates names scattered across old accounts. When a transfer has already gone wrong, our stolen domain name recovery service works with both registrars and the registry to get the domain back.

This article is part of the DNAccess Domain Name Basics guides, which explain how domain names, registrars and DNS work in plain English.