Domain Transfer: Moving a Name Between Registrars
A domain transfer moves a domain's management from one registrar to another — same owner, same registry record, new retail interface. For gTLDs the process is standardized by ICANN policy: unlock at the losing registrar, obtain the auth code, submit it at the gaining registrar with a transfer order, and confirm. Transfers typically complete within about five days, and a gTLD transfer generally adds a year to the registration (up to the 10-year maximum).
The steps that trip people up
- •The 60-day rule: gTLDs cannot transfer within 60 days of initial registration or a previous transfer, and many registrars impose a similar lock after a registrant-information change.
- •The registrar lock: clientTransferProhibited must be cleared before the auth code will work.
- •Stale contact email: transfer confirmations go to addresses on file — a dead email stalls everything.
- •Timing near expiry: transferring a domain that is about to expire is risky; renew first or allow generous margin.
Transfer vs. push
A transfer changes registrars and involves the registry, fees, and the 60-day rules. A push moves a domain between two accounts at the same registrar — instant, usually free, and no auth code required. Domain sales between users of the same registrar are commonly settled by push for exactly this reason.
Frequently Asked Questions
How much does a domain transfer cost?
Typically about the price of a one-year renewal at the gaining registrar, since a year is added as part of the transfer. There is no separate registry transfer fee for standard gTLD moves.
Does transferring a domain reset its expiry date?
No — it extends it. A gTLD transfer adds one year to the existing expiration (capped at 10 years total), so you lose nothing you have already paid for.
Can a transfer fail?
Yes: wrong or expired auth code, the domain still locked, the 60-day window, or the losing registrar rejecting for unpaid fees. Most failures are fixable and the transfer can be reattempted.