How to Transfer a Domain to a New Registrar (Step-by-Step, 2026)

# How to Transfer a Domain to a New Registrar (Step-by-Step, 2026)

There are plenty of reasons to transfer your domain to a new registrar. Maybe your current registrar raised its renewal prices. Maybe you want better DNS management. Maybe you are consolidating all your domains under one account. Whatever the reason, the process is standardised across the industry and, once you understand the steps, takes about five to ten minutes of active work plus a few days of waiting.

This guide covers the exact transfer process for standard gTLDs like .com, .net, and .org, plus special notes for .no domains and tips for transferring to Cloudflare.

Why Transfer?

The most common reasons people transfer domains:

Lower renewal prices. If you registered at GoDaddy for $2.99 and now face a $22.99 renewal, transferring to Namecheap, Porkbun, or Cloudflare saves you $8-12 per year. Over five years, that adds up.

Better features. Cloudflare's DNS is faster and more feature-rich than most registrar DNS. Some registrars offer better security features, bulk management, or API access.

Consolidation. Managing domains across three or four registrars is annoying. Transferring everything to one registrar simplifies billing, DNS management, and account security.

Free WHOIS privacy. If your current registrar charges for WHOIS privacy (GoDaddy charges $9.99/year), transferring to a registrar that includes it free saves money immediately.

A domain transfer typically costs the same as one year of registration at the new registrar (e.g., around $10-14 for a .com). That fee includes one year of registration added to your existing expiration date. So you are not paying extra — you are prepaying the next renewal at the new registrar's rate.

What Actually Happens During a Transfer

A domain transfer moves the registration record from one registrar to another. Your domain name, DNS records, and website are not affected by the transfer itself — only the registrar of record changes. However, there are some nuances:

• DNS records: If you are using your current registrar's name servers, you need to either recreate your DNS records at the new registrar before transferring, or change your name servers to a third-party DNS provider (like Cloudflare) before initiating the transfer. If you are already using third-party name servers, the transfer has zero impact on your DNS.
• Email: If your email MX records are hosted at your current registrar's DNS, the same applies. Make sure your email continues to work by verifying MX records at the new registrar or third-party DNS.
• Expiration date: The transfer adds one year to your current expiration date. If your domain expires on 2026-09-15 and you transfer on 2026-04-18, the new expiration will be 2027-09-15.

The 7-Step Transfer Process

Step 1: Check Eligibility

Before you start, verify that your domain is eligible for transfer:

• 60-day lock after registration: ICANN rules prevent transferring a domain within 60 days of its initial registration. If you just registered the domain, you have to wait.
• 60-day lock after a previous transfer: The same 60-day lock applies after a recent transfer. You cannot transfer a domain twice within 60 days.
• 60-day lock after WHOIS contact change: If you recently changed the registrant contact information, some registrars impose a 60-day transfer lock. Check with your current registrar.
• Not within 10 days of expiration: While technically possible, transferring a domain that is about to expire adds risk. Renew it first, then transfer.

Step 2: Unlock the Domain

Most registrars lock domains by default to prevent unauthorised transfers. You need to disable this lock (often called "registrar lock," "transfer lock," or "domain lock") in your current registrar's dashboard.

Where to find it: - GoDaddy: My Products → Domain Settings → Domain Lock → toggle off - Namecheap: Domain List → Manage → Domain tab → Domain Lock toggle - Hover: Domain Overview → Transfer Lock → unlock

The unlock takes effect immediately in most cases.

Step 3: Disable DNSSEC (If Enabled)

If you have DNSSEC enabled on your domain, you need to disable it before transferring. DNSSEC creates a chain of trust between your registrar and the DNS, and transferring with DNSSEC active can cause resolution failures during the transfer.

Disable DNSSEC at your current registrar, wait for the DS records to be removed from the parent zone (usually within a few hours), and then proceed with the transfer.

If you are not sure whether DNSSEC is enabled, check your registrar's DNS settings or use a tool like dnsviz.net to check.

Step 4: Get the EPP Code (Authorization Code)

The EPP code (also called an authorization code, auth code, or transfer key) is a password that proves you are the legitimate owner of the domain and authorise the transfer. Every registrar provides a way to obtain this code.

Where to find it: - GoDaddy: Domain Settings → Transfer domain away from GoDaddy → Continue → the code is emailed or displayed - Namecheap: Domain List → Manage → Domain tab → Auth Code → toggle to view - Hover: Domain Overview → Transfer → Get Transfer Code → code is emailed to the registrant

The EPP code is typically 8-16 characters long and is case-sensitive. Copy it exactly.

Step 5: Initiate the Transfer at the New Registrar

Go to your new registrar and start the transfer process:

1. Find the "Transfer" or "Transfer In" option (usually on the main page or in your dashboard) 2. Enter your domain name 3. Enter the EPP code when prompted 4. Pay the transfer fee (one year of registration) 5. Confirm your contact information

The new registrar will submit the transfer request to the registry.

Step 6: Confirm via Email

After the transfer is initiated, you will receive confirmation emails:

• From the new registrar: Confirming that the transfer has been requested. Some registrars require you to click a confirmation link.
• From the old registrar: Notifying you of the pending transfer. Some registrars ask you to approve or deny the transfer. Approve it to speed up the process. If you do nothing, the transfer will auto-complete after 5 days.

Check the email address associated with your domain's WHOIS contact — this is where these emails are sent. If you are using WHOIS privacy, the emails go to the proxy email, which should forward to your real address. If it does not, this is where transfers get stuck.

Step 7: Wait

After all confirmations, the transfer typically completes within 1 to 7 days:

• If you approve the transfer at the old registrar: usually 1-2 days
• If you do nothing and let it auto-complete: usually 5-7 days
• If there is an issue (locked domain, incorrect EPP code, expired domain): the transfer may fail and you will need to start over

Once the transfer completes, the domain appears in your new registrar's dashboard. Verify that all DNS records are correct and that your website and email are working.

Special Case: Transferring .no Domains

Norwegian .no domains are managed by Norid and follow a different process than standard gTLDs. Key differences:

• No EPP code: .no domains use a different authorisation mechanism. The transfer is initiated through the new registrar, and Norid handles the authorisation.
• Registrar must be Norid-accredited: You can only transfer a .no domain to a registrar that is accredited by Norid. Not all international registrars support .no domains.
• Norwegian identity required: The registrant must have a Norwegian organisation number or national ID. This does not change during transfer, but the new registrar must verify it.
• Transfer completion: .no transfers typically complete within 1-3 days once both registrars process the request.

Common Norid-accredited registrars for .no domains include Domeneshop, one.com, and EuroDNS.

Transferring to Cloudflare: Tips

Cloudflare Registrar has become a popular transfer destination because of its at-cost pricing. A few things to know:

• You must already be using Cloudflare's name servers. Before transferring a domain to Cloudflare Registrar, you need to add the domain to your Cloudflare account and switch your name servers to Cloudflare's. This means you should set up all your DNS records in Cloudflare first.
• The transfer process is standard — unlock, get EPP code, initiate at Cloudflare, confirm emails.
• Cloudflare does not support all TLDs. Check their supported TLD list before planning a transfer. Most common gTLDs and many ccTLDs are supported, but some are not.
• No WHOIS privacy toggle needed — Cloudflare includes WHOIS privacy automatically on all supported domains and will redact information in accordance with ICANN and local regulations.

Mistakes to Avoid

Forgetting to recreate DNS records. If you are using your current registrar's name servers, your DNS records live at that registrar. When the transfer completes and name servers change, those records do not come with you. Set up DNS at the new registrar or a third-party provider before transferring.

Letting the domain expire during transfer. If your domain is close to expiration, renew it at your current registrar before starting the transfer. A domain that expires mid-transfer creates a mess that can take days to resolve.

Not checking email. Transfer confirmations go to the WHOIS registrant email. If that email is incorrect or inaccessible, you cannot confirm the transfer and it may time out or fail.

Ignoring the 60-day lock. If you recently changed WHOIS information, registered the domain, or completed another transfer, the 60-day lock will prevent the transfer from going through. Check before you waste time on the process.

Panicking about downtime. A properly executed transfer causes zero downtime. If you set up DNS correctly at the new registrar or use third-party name servers, your website and email continue working throughout the process. The only risk of downtime is if you forget to recreate DNS records.

Domain transfers are routine operations that registrars handle thousands of times per day. Follow the steps, double-check your DNS, and the process will be smooth.