Transferring a domain from one registrar to another is a routine process, but it follows rules that can delay or block it if you are not prepared. For most generic top-level domains (gTLDs) such as .com, .net and .org, the rules come from ICANN's Transfer Policy. Country-code TLDs often have their own procedures. This article explains the common gTLD process; always check your registrars' current instructions.
Transfer between registrars versus change of account
A registrar transfer moves the domain to a different registrar. A change of account (sometimes called a push or internal transfer) moves it between two accounts at the same registrar, which is usually faster and does not involve the steps below. If buyer and seller use the same registrar, an account change is often the simplest option.
Step 1: Check eligibility
A domain may be ineligible for transfer in several situations:
- it was registered, or transferred to a new registrar, within the last 60 days;
- it is close to or past expiry, or in a redemption period;
- it is subject to a dispute or a legal lock;
- the registrant contact was recently changed and the registrar applied a 60-day transfer lock afterwards, which registrars may do under the policy unless the registrant opted out where that option is offered.
Policies are revised from time to time, so treat these as typical conditions and confirm the current rules with your registrar.
Step 2: Unlock the domain
Most registrars place a transfer lock on domains by default. In the domain's status this appears as clientTransferProhibited. You must remove it in the current registrar's control panel before a transfer can start. Some domains also carry registry-level locks for added security, which must be removed through the registrar.
Step 3: Get the authorization code
The authorization code, also called an auth code, EPP code or transfer key, proves that the transfer is authorized by the domain holder. Request it from the current registrar; it is usually shown in the control panel or sent by email. Treat it like a password and share it only with the gaining registrar.
Step 4: Start the transfer at the new registrar
At the gaining registrar, enter the domain name and the authorization code and pay the transfer fee. For most gTLDs, a transfer includes a one-year renewal added to the existing expiry date, so you do not lose remaining registration time, with some exceptions near expiry.
Step 5: Approve or wait
The losing registrar may send a notice asking you to approve or reject the transfer. If you take no action, many transfers complete automatically after a few days, commonly up to five. Approving the request speeds things up.
Keeping DNS working during the transfer
A registrar transfer changes who manages the registration, not necessarily where DNS is hosted. If your domain uses the old registrar's DNS service, those records may stop working when the transfer completes. Before starting, either move DNS to a provider independent of the registrar, or recreate the records at the new registrar and plan the nameserver change.
After the transfer
- Re-enable the transfer lock at the new registrar.
- Check contact details, auto-renew and the new expiry date.
- Verify DNS, email and any services that depend on the domain.
- Note that a new 60-day restriction on further transfers typically applies.
Transfers when selling a domain
When a domain is sold, the auth code or account change should only happen after payment is secured, often through an escrow service. The seller unlocks the domain and provides the code; the buyer initiates the transfer; escrow releases funds after the buyer confirms control.
Key takeaways
- Check the 60-day and expiry restrictions before starting.
- Unlock the domain and obtain the authorization code from the current registrar.
- Most gTLD transfers add a year to the registration.
- Plan DNS continuity separately from the registration transfer.