Domain registration and transfer durations

Wondering how long it takes for a domain registration or transfer to complete? It depends on the TLD.

This article explains the two categories of TLDs and what determines the lead time.

Why durations vary

A domain transfer goes through a registry — the organisation that runs the TLD (e.g. Verisign for .com, SIDN for .nl). Each registry sets its own rules for how a transfer is approved and how long it takes.

For generic TLDs the process is largely standardised by ICANN. For country-code TLDs every registry has its own rules.

Before you start

Three preconditions apply to nearly every TLD. Sorting them out before requesting the transfer is what most often determines whether the move is quick or slow.

Auth code

You need the authorisation code (also called EPP code or transfer token) from the current registrar. The losing registrar generates it on request; sometimes it's available self-service in their control panel, sometimes you have to ask their support.

Without the right code, the gaining registry will reject the request.

A few TLDs use a different mechanism — most notably .uk uses an IPS tag instead of an auth code, where the current registrar changes the tag to point at the new one. Treat it as the equivalent step.

Transfer lock

A domain can be locked against transfer for two reasons:

• Newly registered or recently transferred. For gTLDs, ICANN policy locks a domain for 60 days after registration and again for 60 days after any transfer. The lock can't be waived — wait it out.
• Registrar lock toggled on. A separate setting in the current registrar's control panel. Turn it off before requesting the transfer.

Contact email

The transfer flow sends notifications and approval requests to the registrant's email address on file with the registry. If that mailbox is stale (former employee, defunct forwarder), the transfer can't be approved.

Check and, if needed, update the registrant email at the current registrar before initiating.

Generic TLDs

Generic TLDs — .com, .shop, .app, .site, .work, .online, and most other non-country-coded TLDs — follow the same flow:

1. The gaining registrar submits the transfer with the auth code.
2. The losing registrar receives a notification (the Form of Authorization, or FOA) and has up to 5 days to respond.
3. They explicitly approve → the domain moves immediately.
4. They don't respond within the window → the transfer auto-completes.
5. They explicitly reject → the transfer is cancelled. Rejection has to be for a permitted reason (e.g. the domain is locked, the auth code is wrong, registration is too recent).

So 6 days, end-to-end, is the realistic worst case for a generic TLD that's set up correctly. Most transfers land sooner — often the same day — when the losing registrar processes the FOA quickly or offers a one-click approval to the registrant.

Country-code TLDs

Country-code TLDs — .nl, .be, .es, .fr, .uk, and others — run on their own registry rules. Each registry decides:

• What unlocks the transfer. Common variants: an auth/EPP code (.com-style, used by .be and many others), an IPS tag change (.uk), a registry-issued token (.nl), or registrant verification against a national ID/business register (.fr and some others).
• How approval works. Some registries auto-approve once the technical preconditions are met; others require the registrant to actively confirm via the registry's portal; a few need a signed paper form.
• How long the registry takes to process the request once everything is in.

There's no single per-TLD duration list — the canonical answer lives in each registry's own documentation. If you need a firm timeline for a specific country TLD, contact Cyberfusion support.

When forms are involved

Some TLDs require you to supply forms or identity documents before the transfer can start. The transfer clock doesn't tick until those are in.