Introduction

Transferring a domain from GoDaddy to Cloudflare Registrar means moving the domain registration management from GoDaddy to Cloudflare. After the transfer, Cloudflare becomes your registrar, and you will renew/manage the domain from Cloudflare instead of GoDaddy.

This is different from only using Cloudflare DNS/CDN. Cloudflare requires the domain to be added to Cloudflare and active on Cloudflare nameservers before you can start the registrar transfer. Cloudflare’s current documentation says the active work is around 30 minutes, but the full transfer can take up to 10 days depending on the current registrar. Most transfers include a one-year extension, while some ccTLDs behave differently. (Cloudflare Docs)

Why Transfer from GoDaddy to Cloudflare?

Many website owners move domains to Cloudflare because Cloudflare Registrar offers domain registration and renewal at cost, without retail markup. Cloudflare also tightly integrates DNS, CDN, SSL/TLS, DNSSEC, security, and performance features in one dashboard. (Cloudflare)

Typical benefits include:

1. Lower renewal pricing for many TLDs.
2. Cloudflare DNS management in the same place as CDN/security.
3. Free WHOIS privacy/redaction where supported.
4. Easy DNSSEC management after transfer.
5. Fewer add-ons and upsells compared to many traditional registrars.

Important Before You Start

Before touching anything, confirm these points.

1. Your domain must be eligible for transfer

Cloudflare says you should confirm that:

• Your domain was registered at least 60 days ago.
• Your domain has not been transferred in the last 60 days.
• You have not changed the registrant name, organization, or email in the last 60 days.
• Your current registrar account is active.
• The domain is not expired, or if expired, it should be renewed first.
• The domain uses standard characters; Cloudflare does not support domains with non-Latin characters such as IDNs. (Cloudflare Docs)

ICANN’s current Transfer Policy still allows denial of transfer in several 60-day-lock situations, including recent registration, recent transfer, or a 60-day lock after change of registrant where the holder did not opt out. (ICANN)

2. Avoid changing registrant contact details before transfer

Do not change the domain owner name, organization, or registrant email just before transfer unless you clearly know the lock impact. A registrant information change can trigger a 60-day transfer lock. Cloudflare also warns that registrant name, organization, or email changes within the last 60 days can block transfer. (Cloudflare Docs)

3. If the domain recently expired and you renewed it, wait carefully

Cloudflare recommends waiting at least 45 days after the original expiration date if the domain recently expired and you renewed it; otherwise, the registry may not add the extra year during transfer. (Cloudflare Docs)

4. Cloudflare must become your authoritative DNS

This is one of the most important points. Cloudflare Registrar requires the domain to use Cloudflare authoritative DNS in full setup mode. You cannot keep another DNS provider as authoritative DNS while the domain is registered with Cloudflare. (Cloudflare Docs)

That means before transferring the registrar, you must:

1. Add the domain to Cloudflare.
2. Copy/verify DNS records.
3. Change GoDaddy nameservers to Cloudflare nameservers.
4. Wait until the domain becomes Active in Cloudflare.

Overall Transfer Flow

The safest sequence is:

1. Audit current DNS records in GoDaddy.
2. Add the domain to Cloudflare.
3. Verify DNS records inside Cloudflare.
4. Disable DNSSEC at GoDaddy if enabled.
5. Change GoDaddy nameservers to Cloudflare nameservers.
6. Wait for Cloudflare status to become Active.
7. Unlock the domain in GoDaddy.
8. Turn off GoDaddy Domain Privacy / Domain Protection if required.
9. Get the authorization code from GoDaddy.
10. Start transfer in Cloudflare.
11. Approve transfer from GoDaddy.
12. Verify DNS, SSL, email, and renewal settings after transfer.

Step 1: Audit Existing DNS Records in GoDaddy

Before changing nameservers, open your current DNS zone in GoDaddy and make a backup.

Check these records carefully:

This is critical because Cloudflare’s DNS scan is helpful, but not guaranteed to find every DNS record. Cloudflare specifically warns that automatically scanned records may not include all existing records, so you should review your web host’s required DNS configuration to avoid downtime. (Cloudflare Docs)

Recommended backup format:

Domain: example.com
Current Registrar: GoDaddy
Current DNS Provider: GoDaddy
Current Nameservers:
- nsXX.domaincontrol.com
- nsYY.domaincontrol.com

Important Records:
A     @        192.0.2.10
CNAME www      @
MX    @        mail provider value
TXT   @        SPF value
TXT   selector._domainkey DKIM value
TXT   _dmarc   DMARC value
Code language: CSS (css)

Step 2: Add the Domain to Cloudflare

Log in to Cloudflare and add your domain.

Typical path:

Cloudflare Dashboard
→ Add a site / Add domain
→ Enter your domain name
→ Select plan
→ Continue
Code language: PHP (php)

Cloudflare will scan your DNS records and import detected records. Review every record manually. Pay special attention to email records like MX, SPF, DKIM, and DMARC, because website downtime is bad, but email downtime is often worse.

Cloudflare says the domain must be added and active before you can enter the authorization code for transfer. You cannot proceed with the registrar transfer while the Cloudflare zone is still pending. (Cloudflare Docs)

Step 3: Review DNS Records in Cloudflare

Inside Cloudflare:

Domain
→ DNS
→ Records

Compare Cloudflare records with your GoDaddy DNS backup.

Check at minimum:

Website records

A     @
CNAME www

Email records

MX
TXT SPF
TXT DKIM
TXT DMARC

App verification records

google-site-verification
facebook-domain-verification
MS=msXXXX

SSL-related records

CAA
_acme-challenge

For the first migration, I usually recommend setting important website records to DNS only first if you want simple troubleshooting. After confirming the site works, you can enable Cloudflare proxy for web records where appropriate.

Step 4: Disable DNSSEC at GoDaddy If Enabled

This is a big one. If DNSSEC is enabled at GoDaddy and you change nameservers to Cloudflare without disabling/removing the old DS records, DNS resolution can fail.

Cloudflare says DNSSEC should be disabled before changing nameservers because DNSSEC signatures tied to the old provider may no longer match after moving to Cloudflare. Cloudflare recommends waiting at least 24 hours after disabling DNSSEC before changing nameservers. (Cloudflare Docs)

In GoDaddy, the current help flow is:

GoDaddy Domain Portfolio
→ Select domain
→ DNS
→ DNSSEC
→ Turn Off DNSSEC
→ Remove

GoDaddy says DNSSEC is turned off immediately, but it may take up to 90 minutes to reflect in the account, and DNS updates can take longer globally. (GoDaddy)

Step 5: Change GoDaddy Nameservers to Cloudflare

Cloudflare will give you two assigned nameservers, usually like:

alice.ns.cloudflare.com
bob.ns.cloudflare.com
Code language: CSS (css)

Do not copy random Cloudflare nameservers from another domain. Use only the nameservers assigned to this exact domain in your Cloudflare account.

In GoDaddy:

GoDaddy Domain Portfolio
→ Select your domain
→ DNS
→ Nameservers
→ I’ll use my own nameservers
→ Enter Cloudflare nameservers
→ Save
Code language: PHP (php)

GoDaddy’s current documentation says that changing nameservers changes where DNS is managed, and it warns that incorrect nameserver changes can break website or email connections. (GoDaddy)

Step 6: Wait Until Cloudflare Shows “Active”

After changing nameservers, go back to Cloudflare and check the domain status.

Cloudflare Dashboard
→ Your domain
→ Overview

You need to wait until the zone becomes:

Status: Active
Code language: HTTP (http)

Cloudflare says this usually takes a few minutes but can take up to 24 hours. Also, Cloudflare will not allow you to enter the authorization code until the domain is active. (Cloudflare Docs)

If it stays pending for more than 24 hours, check:

1. Did you enter the correct Cloudflare nameservers in GoDaddy?
2. Did you remove old nameservers?
3. Is DNSSEC disabled at GoDaddy?
4. Did you accidentally use Cloudflare nameservers from another domain?
5. Is the domain locked by a registry-level issue?

Step 7: Unlock the Domain in GoDaddy

Now prepare the domain for transfer away from GoDaddy.

GoDaddy says you can transfer a domain away by following its transfer checklist, and manual preparation includes unlocking the domain, turning off Domain Privacy, and fully downgrading Domain Protection to none. (GoDaddy)

In GoDaddy:

GoDaddy Domain Portfolio
→ Select domain
→ Transfer
→ Transfer to Another Registrar
→ Review checklist
→ Continue with transfer
Code language: JavaScript (javascript)

If GoDaddy shows a lock or protection issue, resolve it before continuing.

Common GoDaddy-side blockers:

GoDaddy specifically notes that domains cannot be transferred within 60 days of new registration, transfer, or certain contact info changes, and domains that are part of a bundle cannot be transferred within 120 days of new registration. (GoDaddy)

Step 8: Get the Authorization Code from GoDaddy

The authorization code is also called:

• Auth code
• EPP code
• Transfer key
• Authorization key
• AuthInfo code

GoDaddy’s current process is:

GoDaddy Domain Portfolio
→ Select domain
→ Transfer to Another Registrar
→ Continue with transfer
→ Complete identity verification if required
→ Click here to see Authorization Code
→ Copy to Clipboard
Code language: JavaScript (javascript)

GoDaddy says it will also send the auth code to the registrant email address on the domain. (GoDaddy)

Important: Request the auth code only when you are ready to use it. Cloudflare notes that authorization codes are often valid only for a limited period. (Cloudflare Docs)

Step 9: Start the Transfer in Cloudflare

Once the domain is active in Cloudflare and you have the GoDaddy auth code:

Cloudflare Dashboard
→ Domain Registration
→ Transfer Domains
→ Select your domain
→ Enter authorization code
→ Confirm contact information
→ Confirm payment
→ Submit transfer

Cloudflare says for most generic TLDs like .com, .net, and .org, the transfer price includes a one-year extension from the current expiration date. Country-code domains may follow different rules; for example, .uk transfers do not add an extra year or charge a transfer fee. (Cloudflare Docs)

Cloudflare will collect registrant contact information because ICANN requires accurate contact details, although Cloudflare redacts this information from public WHOIS by default. (Cloudflare Docs)

Step 10: Approve the Transfer from GoDaddy

After you submit the transfer in Cloudflare, GoDaddy may send an approval email or show an approval option in the GoDaddy dashboard.

Cloudflare says the previous registrar will usually email you to confirm or approve the transfer. Most registrars process transfers within five business days, although some TLDs can take up to 10 business days. (Cloudflare Docs)

Cloudflare’s blog also notes that approving from the previous registrar can speed up the transfer; otherwise, the registrar may wait up to five days. (The Cloudflare Blog)

Step 11: Monitor Transfer Status in Cloudflare

In Cloudflare:

Cloudflare Dashboard
→ Domain Registration
→ Transfer Domains

Common statuses:

Cloudflare says if “Transfer in progress” stays for more than 24 hours, you should verify the domain is unlocked at the current registrar. (Cloudflare Docs)

Step 12: Final Checks After Transfer Completes

After the transfer completes, verify everything.

DNS check

Confirm these still work:

dig example.com
dig www.example.com
dig MX example.com
dig TXT example.com
dig TXT _dmarc.example.com
Code language: CSS (css)

Website check

Open:

https://example.com
https://www.example.com
Code language: JavaScript (javascript)

Check:

1. Homepage loads.
2. SSL certificate is valid.
3. Login works.
4. Admin panel works.
5. Forms work.
6. API endpoints work.
7. Redirects work.
8. No mixed-content errors.

Email check

Send test emails:

1. Gmail to domain email.
2. Domain email to Gmail.
3. Reply back.
4. Check spam folder.
5. Validate SPF, DKIM, and DMARC.

Cloudflare SSL/TLS check

Recommended starting point for most normal websites:

Cloudflare
→ SSL/TLS
→ Overview
→ Full or Full (strict)

Use Full (strict) only when your origin server has a valid SSL certificate.

DNSSEC after transfer

Once the domain is fully transferred and stable, you can enable DNSSEC from Cloudflare. Cloudflare says DNSSEC can be re-enabled through Cloudflare after transfer. (Cloudflare Docs)

Troubleshooting

Problem 1: Cloudflare does not allow me to enter the auth code

Reason: The domain is not active on Cloudflare yet.

Cloudflare requires the domain to be added, nameservers changed, and the zone active before the authorization code can be entered. (Cloudflare Docs)

Fix:

1. Check nameservers in GoDaddy.
2. Confirm Cloudflare assigned nameservers are entered correctly.
3. Disable DNSSEC at GoDaddy.
4. Wait up to 24 hours.
5. Re-check Cloudflare status.

Problem 2: Transfer rejected because domain is locked

Reason: GoDaddy or the registry still shows transfer lock.

Cloudflare says if WHOIS/RDAP shows clientTransferProhibited, the domain is still locked. Even after unlocking, propagation may take up to 5 hours, and some registrars may take up to 24 hours. (Cloudflare Docs)

Fix:

1. Unlock domain in GoDaddy.
2. Disable extra protection locks.
3. Wait a few hours.
4. Retry transfer in Cloudflare.

Problem 3: Transfer rejected because GoDaddy privacy/protection is still active

Cloudflare specifically says that if transferring from GoDaddy, make sure Domain Privacy and Domain Protection are fully disabled; GoDaddy may reject the transfer if either remains active. (Cloudflare Docs)

Fix:

1. Go to GoDaddy Domain Portfolio.
2. Open the domain.
3. Remove/downgrade Domain Protection.
4. Turn off privacy if required by GoDaddy’s transfer checklist.
5. Restart transfer.

Problem 4: Invalid or expired authorization code

Cloudflare says authorization codes are usually valid only for a limited period. If rejected, request a fresh code and check for trailing spaces or line breaks when copy-pasting. (Cloudflare Docs)

Fix:

1. Generate a fresh auth code in GoDaddy.
2. Copy carefully.
3. Paste into Cloudflare.
4. Avoid extra spaces.

Problem 5: DNS stopped working after nameserver change

Most common causes:

1. Missing DNS records in Cloudflare.
2. DNSSEC still active at GoDaddy.
3. Wrong Cloudflare nameservers entered.
4. Cloudflare proxy enabled for something that should be DNS-only.
5. Missing MX/TXT records for email.

Fix:

1. Compare GoDaddy DNS backup with Cloudflare DNS.
2. Add missing records.
3. Disable old DNSSEC/DS records.
4. Temporarily set web records to DNS-only for troubleshooting.
5. Check DNS propagation.

Best-Practice Checklist

Use this as your operational checklist.

Before migration

• Domain is older than 60 days.
• Domain was not transferred in the last 60 days.
• Registrant contact details were not recently changed.
• Domain is not expired.
• GoDaddy account login works.
• Cloudflare account email is verified.
• Cloudflare payment method is added.
• DNS records are backed up.
• Email records are documented.
• DNSSEC status checked.

Cloudflare setup

• Domain added to Cloudflare.
• DNS records reviewed.
• Missing DNS records added.
• Cloudflare nameservers copied.
• DNSSEC disabled at GoDaddy if enabled.
• GoDaddy nameservers changed to Cloudflare.
• Cloudflare zone status is Active.

GoDaddy transfer preparation

• Domain unlocked.
• Domain Privacy disabled if required.
• Domain Protection downgraded/removed if required.
• Authorization code copied.
• Transfer eligibility confirmed.

Cloudflare transfer

• Transfer started in Cloudflare.
• Auth code entered.
• Contact information confirmed.
• Payment confirmed.
• GoDaddy approval completed.
• Transfer status monitored.

After transfer

• Website works.
• SSL works.
• www and root domain work.
• Email sending/receiving works.
• SPF/DKIM/DMARC verified.
• Auto-renew checked in Cloudflare.
• DNSSEC enabled in Cloudflare if required.
• GoDaddy billing/renewal checked to avoid unnecessary future charges.

FAQ

Will my website go down during transfer?

Normally, no — if DNS is copied correctly before changing nameservers. The risky part is not the registrar transfer itself; the risky part is missing DNS records during the move from GoDaddy DNS to Cloudflare DNS.

Can I transfer to Cloudflare without changing nameservers?

For Cloudflare Registrar, practically no. Cloudflare requires the domain to use Cloudflare authoritative DNS in full setup mode. (Cloudflare Docs)

How long does the transfer take?

Cloudflare says active work is about 30 minutes, but total transfer time can take up to 10 days depending on the current registrar. Most registrars process the release within five business days after a successful request. (Cloudflare Docs)

Does Cloudflare charge for transfer?

Yes, for most TLDs, you pay the transfer/renewal cost, and the domain receives a one-year extension. Cloudflare says domains are priced at cost with no markup, and most transfers include a one-year extension. (Cloudflare Docs)

Do I need to disable DNSSEC?

If DNSSEC is enabled at GoDaddy, yes, disable it before changing nameservers. Cloudflare warns that old DNSSEC signatures can cause DNS resolution failure after nameserver changes. (Cloudflare Docs)

Can I transfer an expired domain?

GoDaddy says expired domains can be transferred until they are in redemption. Cloudflare recommends renewing at the current registrar first if the domain has expired. (GoDaddy)

Conclusion

The correct way to transfer a domain from GoDaddy to Cloudflare is not to start with the auth code. The safest method is:

Backup DNS
→ Add domain to Cloudflare
→ Verify DNS
→ Disable DNSSEC
→ Change GoDaddy nameservers to Cloudflare
→ Wait for Active status
→ Unlock domain in GoDaddy
→ Get auth code
→ Start transfer in Cloudflare
→ Approve transfer
→ Verify website, email, SSL, DNSSEC

The biggest mistakes are missing DNS records, forgetting DNSSEC, trying to enter the auth code before Cloudflare is active, leaving GoDaddy protection/privacy enabled, or changing registrant contact details before transfer. Follow the checklist, and the transfer should be smooth.

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I have worked at Cotocus. I share tech blog at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow , and SEO strategies at Wizbrand.

Do you want to learn Quantum Computing?

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at WIZBRAND

Rajesh Kumar DailyLogs