Domain transfer cost: what it charges, and what actually blocks it

Moving a domain between registrars is one of the few processes in this industry with a written rulebook behind it — ICANN's transfer policy — and it still manages to feel arbitrary. It feels arbitrary because the common failures are invisible from whichever dashboard you happen to be looking at. This page names them.

What a transfer is, and what it is not

A transfer changes the registrar of record at the registry. It is a registration action, not a DNS action. Three consequences follow from that:

• On a gTLD the transfer extends the registration by a year, and that year is

part of the transfer rather than an extra charge.

• The domain keeps resolving throughout. A transfer is not a migration and does

not interrupt traffic.

• Nameservers usually travel with the domain, which makes the wrong assumption

here an expensive one: if your DNS is served by the registrar you are leaving, you need to know where the zone will live afterwards. See also: the DNS explained article.

What a transfer costs

You pay the receiving registrar. That is the answer the forum gives first — "you pay transfer fees to the 'receiving' registrar. It also adds 1 extra year to your [registration]" — and the rest of this section depends on it. The fee is not a migration charge and it is not a penalty. It is the next year of the registration, paid to the registrar you are moving to — which is why the summary above this query says the fee "includes a mandatory 1-year registration extension added to your domain's current expiration date".

The published .com prices, read on 2026-10-22:

The band the summary gives is $8 to $15 per year for .com, .net and .org.

And read the GoDaddy row twice. $0.01 is not a free transfer — it is the first year of a three-year purchase, and the other two years are $22.99 each. The same shape runs through the whole market: a transfer fee that looks free is usually a commitment priced somewhere else. For scale, .com registration across 57 registrars ranges from $3.80 to $56.00, so what you are quoted for a transfer is the price of a year, not a price for the move.

The blockers, and the remedy for each

Before you press anything

1. Confirm the domain is unlocked at the current registrar.
2. Request the authorisation code.
3. Check that the registrant email is one you actually read, and that mail to it

is not being filtered.

1. Check the expiry date. If it is close, renew and then transfer, rather than

transferring a name that is about to lapse.

1. Note where the DNS is served today and decide whether it should follow.

That is five minutes of work and it removes almost every transfer that fails.

Transferring in

Enter the domain and its authorisation code, and the transfer is submitted to the registry. Your current registrar then emails the registered contact; approving that message is what authorises the move, and it is also the fastest way to get it done. The transfer is free and it includes a one-year extension on the registration.

If the DNS should follow, repoint the nameservers only once the transfer has completed. Doing it first leaves the zone you are departing authoritative for a domain you no longer control.

Transferring out

Unlocking and requesting the code are self-serve here, and nobody has to ask permission to leave. Transferring a name away does not cancel hosting: your site and your plan are unaffected, and the DNS zone keeps answering for as long as the delegation points at it. If you intend to move DNS as well, plan the cutover rather than discovering it.

How long it takes

Plan for about five days. That window exists so the losing registrar can raise an objection and so you can cancel a transfer that was not yours, which is why nobody should promise you a move that completes on the spot. Approving the confirmation email early usually shortens it, and the domain keeps serving your site the entire time.

What does not block a transfer

• WHOIS privacy. The relay forwards the confirmation mail.
• Live traffic. A transfer is a registration change; DNS is untouched.
• An active hosting plan. Hosting and registration are separate products here,

and neither one gates the other.

• A DNSSEC-signed zone, provided the parent's trust records are handled in the

right order. See also: the DNSSEC guide.

The failures listed above are all visible before you start. The transfers that go wrong are almost always the ones where somebody skipped the five-minute check.