how long does a domain transfer take?.

five to seven days if you do nothing. often under an hour if you approve the confirmation email.

that gap is the entire subject. almost everything written about slow transfers describes the default path, where the delay is not a processing queue but a waiting period existing specifically so you can be asked — and which ends the moment you answer.

the clock, step by step

a gTLD transfer has a fixed shape whichever registrars are involved.

• unlock the domain at the losing registrar. instant, and entirely in your control.
• get the [auth code](/glossary/auth-code), sometimes called an EPP or transfer code. usually shown immediately, occasionally emailed, occasionally delayed by hours as friction.
• start the transfer at the gaining registrar and pay. this is where the year of renewal is charged.
• approve the gaining registrar's confirmation email. minutes, if the address on the record still reaches you.
• the losing registrar has up to five days to release it. the long part, and the part you can skip.
• the domain arrives. registry updated, nameservers usually unchanged but not always.

the five-day window is a maximum, not a duration. the losing registrar must get the chance to confirm you meant it; hearing nothing, the transfer completes automatically when the window expires. but go into your account there and explicitly approve the outbound transfer and the window closes at once. most people never do, wait five days, and conclude that transfers are slow.

the fastest possible transfer

• check the admin contact email is one you can actually read, before anything else. the most common cause of a transfer stalling to the full five days, and invisible until it costs you.
• unlock, and confirm it took. some registrars show the toggle flipped while the registry still reports clientTransferProhibited.
• handle privacy. a proxy that does not forward mail will swallow the confirmation. disable it before you begin rather than debugging it afterwards.
• use the auth code promptly. several registrars expire codes, and a stale one produces a rejection that reads like a lock.
• approve at both ends. the gaining registrar's email, then the outbound approval in the losing registrar's control panel. the second is what turns five days into minutes.

what actually makes transfers slow

a dead contact address. the registration was made years ago with an address at a company you have left. you never see the confirmation, so nothing happens until the five days run out. fix it first — but read the next point before you change anything else.

the 60-day locks. ICANN's transfer policy blocks a gTLD transfer for 60 days after initial registration and 60 days after a previous transfer. the third trigger is the ambush: a change of registrant — the owner's name, organisation or email — starts its own 60-day clock, so 'I updated the contact details so I could receive the confirmation' can lock the domain for two months. the 60-day lock has the detail, including where an opt-out exists.

a registrar that makes it deliberately awkward. unlock buried three menus deep, an auth code released only after a support conversation, a retention interstitial on the way out. legal within limits, and it varies enormously. transferring away from GoDaddy walks one of the more involved paths.

a domain close to expiry. transferring in the last days before expiry, or during the grace period afterwards, is genuinely messy — some registrars refuse outbound transfers on expired names. renew first, then transfer. the year is not wasted.

a status code you have not looked at. clientTransferProhibited, serverTransferProhibited, pendingDelete or an existing pendingTransfer will each stop a transfer, and the error you get back frequently does not say which. read the registry record with expiry check rather than trusting a dashboard.

the year you gain

a gTLD transfer includes a renewal: one year is added to the existing expiry date. you do not lose the time remaining and you do not restart the clock — the year goes on top of whatever was left.

two consequences. transferring wastes nothing, even on a domain that only just renewed. and transferring shortly before a renewal falls due is the efficient moment, because you pay the gaining registrar's price instead of the losing one's. where those prices differ the difference is renewal arbitrage, and moving the domain is how you collect it — compare registrars before deciding where it goes.

.uk works completely differently

if you are moving a .uk, none of the above applies. Nominet does not use auth codes. every registrar has an IPS tag, and changing the tag is the transfer: you request the change at your current registrar, the tag is updated, and the domain is with the new one.

the practical differences invert the usual advice. it is effectively immediate rather than a five-day wait, there is no confirmation email to approve, and no year is added — the expiry date does not move, so you renew separately whenever it falls due. there is therefore no efficiency in timing a .uk transfer near renewal. move it whenever you like.

if it has stalled

• read the registry record. expiry check shows the status codes. pendingTransfer means it is in flight and the clock is running. clientTransferProhibited means the unlock did not take.
• confirm who holds it right now. registrar lookup reports the accredited registrar from the registry rather than from whichever dashboard you are looking at, settling arguments about whether anything moved.
• check your spam folder and the privacy proxy's forwarding, in that order.
• if it was rejected, find out why. usually a lock, an expired auth code, a 60-day window, or an unpaid balance at the losing registrar. all fixable, none worth waiting out.
• restart rather than wait. a failed transfer does not queue itself. once the cause is fixed you begin again from the auth code.

one thing to do before you start

a transfer moves the registration, not your DNS. in principle nameservers carry across untouched. in practice some gaining registrars point new arrivals at their own, and if your zone is not already replicated there everything goes dark at once. export the zone file first, or at minimum write down every record — five minutes, and the difference between a transfer nobody notices and an outage in your own maintenance window.

once it lands, check the expiry date reflects the added year and that auto-renew is on. a domain arriving with auto-renew off, at a registrar you have no habit of checking, is exactly what lapses eleven months later. staged expiry alerts across every registrar you use, free for ten domains, exist for that specific failure.