Transferring a domain moves administrative control from one registrar to another; it never touches your ownership, DNS zone, or website content. You need three things before you start: access to the registrant email on the WHOIS or RDAP record, the domain unlocked at the losing registrar, and an authorisation code (often called an EPP or auth code). Get those three sorted and most transfers finish within a week, usually adding one renewal year to gTLDs like .com in the process.

TL;DR:

• Most domain transfer failures stem from skipping steps like unlocking the domain, obtaining the auth code, or approving confirmation emails, not technical faults.
• You should verify that your WHOIS contact email is accessible, remove domain locks, and export DNS records before initiating a transfer to prevent downtime.
• The 60-day ICANN lock applies after registration, transfer, or contact changes, and you must meet specific criteria such as resolving status codes and TLD rules to transfer a domain.
• Getting the authorization code requires accessing your registrar’s dashboard and confirming the removal of transfer prohibitions; a lost access to email or code expiry can delay the process.
• Most gTLD transfers complete within one week, but active confirmation or registrar delays can shorten or extend this timeframe; monitoring the transfer status is essential.

Table of Contents

• Domain transfer process: the step-by-step checklist
• What are the eligibility rules before you transfer a domain?
• How do you get the auth code and unlock the domain?
• How to start a domain transfer with the gaining registrar
• How long does a domain transfer usually take?
• Why was my domain transfer denied, and how do I fix it?
• How do you keep your website and email running during a transfer?
• Change of registrant vs. inter-registrar transfer: what’s the difference?
• Why businesses hand transfers to a managed IT provider
• How Ctasystems handles your domain transfer
• Sources
• FAQ

Domain transfer process: the step-by-step checklist

Most failed transfers trace back to skipping a step, not to some obscure technical fault. Work through these in order:

1. Confirm your registrant contact details. Log into your current registrar and check the WHOIS or RDAP email is one you can actually access.
2. Export your DNS records. List every A, MX, CNAME, and TXT record, plus any third-party services (email, CDN, verification tags) that depend on them.
3. Remove locks and request the code. Ask the losing registrar to lift clientTransferProhibited and issue the authorisation code.
4. Start the transfer at the new registrar. Paste the code, pay the transfer fee, and submit the request.
5. Approve the confirmation emails. Both registrars will usually send a Form of Authorisation (FOA); approving it promptly speeds things along, as Cloudflare’s transfer guide notes.
6. Re-lock the domain once the transfer completes, and verify your DNS resolved correctly.

Pro Tip: Screenshot your DNS records before you touch anything. Registrars occasionally strip custom records during migration, and a screenshot saves you from reconstructing an MX record from memory at 11pm.

What are the eligibility rules before you transfer a domain?

ICANN’s transfer policy imposes a default 60-day lock after a domain is registered, transferred between registrars, or has its registrant contact changed. There are opt-out provisions in some cases, but assume the lock applies unless your registrar tells you otherwise.

Before requesting anything, check for:

• Status codes that block transfers, such as clientTransferProhibited, a registry lock, or a domain sitting in redemption after expiry.
• TLD-specific quirks. .uk domains follow Nominet’s registrar procedures, which differ slightly from generic TLD rules.
• Proximity to expiry. Transferring a domain that’s days from lapsing risks it dropping into a grace period mid-transfer.

A quick but easy-to-miss fact: the 60-day rule triggers on a contact change alone, not just a transfer or new registration, according to ICANN’s own registrant FAQ. Update your WHOIS details for an unrelated reason and you can accidentally lock yourself out of a transfer you were planning that same week.

How do you get the auth code and unlock the domain?

The authorisation code (also called EPP code or, for .uk domains, a Transfer Authorisation Code) is a unique string tied to your domain that proves you control it. Most gTLD codes are 8 to 32 alphanumeric characters, following the complexity guidance in RFC9154.

To get yours:

• Log into your current registrar’s dashboard and look for “Get Auth Code” or “Transfer Lock” under domain settings.
• Expect delivery to the registrant email on file, not to any address you type in on the spot.
• Registrars must remove clientTransferProhibited and supply the code within a reasonable window once you request it, under ICANN policy.
• If you’ve lost access to the registrant email, you’ll need to update contact details first and then wait out the resulting 60-day lock, or pursue a documented change-of-registrant instead.

How to start a domain transfer with the gaining registrar

Once you have the code, the rest happens on the new registrar’s side. You’ll paste the auth code into a transfer request form, and payment typically covers one year of registration on top of whatever term remains.

A few things worth deciding before you click submit:

• Nameservers. You can switch to the new registrar’s nameservers immediately or leave DNS exactly where it is and only move registrar functions. Leaving DNS untouched is the safer default if email or a website is live.
• Expiry behaviour varies by TLD. Many gTLDs add a year on transfer completion; some ccTLDs don’t extend expiry at all, so check your specific registry’s rules.
• The FOA confirmation. Both the gaining and losing registrar are obliged to send a Form of Authorisation, and the transfer generally won’t proceed until you (or the losing registrar, by inaction) confirm it.

How long does a domain transfer usually take?

Most gTLD transfers complete within about a week, according to Cloudflare’s documentation, largely because the registry operator holds a period during which the losing registrar can issue a NACK (a formal rejection) before the transfer auto-approves.

If the losing registrar actively confirms the transfer rather than staying silent, it often completes in a day or two instead of running the full window.

• Check progress through your gaining registrar’s dashboard, which usually shows a status like “pending” or “in progress.”
• You can also query the domain’s RDAP or WHOIS record directly to see which registrar currently holds it.
• Renewal behaviour on completion depends on the TLD, as AWS’s Route 53 documentation explains, so don’t assume every transfer resets your expiry date the same way.

Why was my domain transfer denied, and how do I fix it?

Denials are almost always fixable once you know the cause. Work through this list:

1. Check the status code. If clientTransferProhibited is still active, ask the losing registrar to remove it.
2. Verify the auth code hasn’t expired. Codes can time out or get invalidated by an earlier failed attempt; request a fresh one.
3. Confirm WHOIS details match. A mismatch between the registrant name on file and the name used in the transfer request is a common rejection trigger.
4. Clear any outstanding balance with the losing registrar. Unpaid renewal fees are a frequent, easily overlooked blocker.
5. Ask for the denial reason in writing. ICANN policy requires registrars to state why a transfer was refused, and that written reason is your strongest tool if you need to escalate to the registry or ICANN’s compliance team.

How do you keep your website and email running during a transfer?

Website and email outages during a transfer are almost always self-inflicted, caused by DNS records not being copied across rather than any fault in the transfer mechanism itself.

• Export every DNS record from the losing registrar and recreate them at the gaining registrar before the transfer finalises, a step hostingguider.com’s transfer guide flags as the single most common cause of post-transfer downtime.
• If your DNS is hosted separately from your registrar (Cloudflare, for instance), leave your nameservers pointed there throughout. There’s no need to touch them at all.
• If DNSSEC is enabled, disable it before initiating the transfer and re-enable it once the domain lands at the new registrar, since mismatched DNSSEC records are a known cause of transfer failures.

Pro Tip: If you’re mid-migration on a wider project rather than just moving a domain, a structured site migration checklist helps you sequence DNS changes so search rankings and email continuity survive the move together.

Change of registrant vs. inter-registrar transfer: what’s the difference?

A change of registrant updates who legally owns the domain, while an inter-registrar transfer moves which company manages it. They’re separate actions with separate consequences, and confusing them costs people weeks.

• A change of registrant commonly triggers the same 60-day inter-registrar lock described earlier, even though no transfer took place.
• If you need to do both (sell a domain and move it to a new registrar), complete the inter-registrar transfer first where your registrar allows it, or use a registrant opt-out if one’s offered.
• Registrars are expected to process a confirmed change-of-registrant request within roughly one day of receiving the necessary confirmations under ICANN policy.

Why businesses hand transfers to a managed IT provider

Most transfer failures happen because nobody currently at the business has the registrant email, the auth code, or the DNS export saved anywhere sensible. Staff turnover alone accounts for a fair share of “we don’t actually know who owns this domain” moments.

A managed transfer removes the guesswork: someone handles the EPP exchange, fixes WHOIS mismatches, migrates DNS without breaking email, and confirms the domain resolved correctly afterwards. Experienced managed IT providers have run this exact sequence enough times to know where it usually goes wrong.

— Will

How Ctasystems handles your domain transfer

If you’ve read this far and thought “I don’t have time to babysit an FOA email for a week,” that’s precisely the gap a managed transfer closes. A managed domain transfer service typically handles EPP code retrieval, WHOIS corrections, DNS migration, and post-transfer verification as part of a wider hosting and domain management offering, helping to keep your website and email live throughout.

This suits SMEs without a dedicated IT contact, organisations that don’t currently hold registrar access for a domain they depend on, and anyone who simply can’t afford downtime on a live business email address. Rather than juggling auth codes and lock settings between two registrar dashboards, you hand the whole sequence off to a team that does it routinely. Get in touch through the Ctasystems site to arrange a domain transfer or review your wider hosting setup.

Sources

Verify policy directly: ICANN’s transfer policy, Nominet’s .uk guidance, and Cloudflare’s practical walkthrough.

• How to Transfer a domain – Registrar Resources – Nominet
• How to transfer a domain name — Cloudflare

FAQ

How long does a domain transfer usually take?

Most gTLD transfers complete in five to seven days, largely governed by the registry’s five-day window for the losing registrar to reject the request, as Cloudflare explains. Active confirmation from the losing registrar can shorten this to a day or two.

How does a domain transfer work?

You unlock the domain at your current registrar, obtain the authorisation code, and submit that code to the new registrar along with payment. Both registrars send confirmation emails, and once approved, the registry updates its records to reflect the new sponsoring registrar.

Do I have to wait 60 days to transfer a domain?

Only if the domain was registered, transferred, or had its contact details changed within the last 60 days, under ICANN’s Inter-Registrar Transfer Policy. Outside that window, there’s no mandatory waiting period for a standard transfer.

Will I lose my email if I transfer my domain?

Not if you handle DNS correctly. Email breaks only when MX records aren’t copied to the gaining registrar or when nameservers get switched unnecessarily; leaving DNS untouched, or exporting every record first, keeps mail flowing throughout the transfer.