Why can't I find my domain in Cloudflare's transfer list?

Cloudflare Registrar only transfers domains whose DNS is already managed on an active Cloudflare zone. If the domain doesn't appear, add it as a site first, move its nameservers to Cloudflare, and wait for the zone to go active, then it becomes eligible.

Will my website or email go down during the transfer?

Not if you move DNS to Cloudflare first and verify every record. The registration transfer itself doesn't change how DNS resolves, so downtime only happens when records were missed during the earlier DNS migration step.

Do I lose the time left on my current registration?

No. The transfer fee adds a full year to your existing expiry date rather than resetting it, so any remaining time you already paid for is preserved.

How to Transfer a Domain to Cloudflare Registrar

VigilDog Team · October 6, 2026 · 6 min read

Cloudflare Registrar is popular for one honest reason: it sells domains at wholesale cost with no markup and no upsells. But a Cloudflare registrar transfer has a real prerequisite most guides gloss over, your DNS has to be on Cloudflare and active before the transfer will even start. Get the order wrong and you either can't begin or you knock your site and email offline mid-move. Here's the sequence that keeps everything up.

What Cloudflare requires before you can transfer

Cloudflare Registrar isn't a general-purpose registrar you can point at any domain. It only registers or holds domains whose DNS is already managed inside a Cloudflare account on an active zone. So the transfer is really a two-phase process: first move DNS management to Cloudflare and confirm it's serving your records, then transfer the registration itself.

There are also eligibility rules set by ICANN, not Cloudflare. A domain must be at least 60 days past its initial registration or its last transfer, and it can't be within the final days before expiry. If you recently registered or moved the domain, you'll have to wait out the 60-day lock, no registrar can override it.

Step 1: Move DNS to Cloudflare first

In your Cloudflare dashboard, add the site as a new zone. Cloudflare scans your current DNS and imports the records it can see, then gives you two nameservers to set at your existing registrar. This is the step that carries the most risk, so verify before you switch: Cloudflare's import is a snapshot and it misses records it can't detect, especially email.

Compare the imported zone against your live DNS record by record, A, AAAA, CNAME, MX, and every TXT (SPF, DKIM, verification records). Miss an MX record and email stops; miss a DKIM TXT and your mail starts failing authentication. Our DNS records explained guide covers what each type does if you're unsure what's safe to drop.

Only after the records match, update the nameservers at your current registrar to the pair Cloudflare gave you. Propagation typically completes within a few hours but can take up to 24. Cloudflare emails you when the zone goes active, wait for that confirmation before moving on.

How a domain name resolves to a server

Step 2: Unlock and get your EPP code

Back at your losing (current) registrar, prepare the domain for release:

Turn off the registrar/transfer lock (sometimes called clientTransferProhibited).
Disable WHOIS privacy temporarily if the registrar requires it, some block transfers while privacy hides the admin contact.
Confirm the admin email on file is one you can access; the transfer approval often lands there.
Request the authorization code (also called the EPP code, auth code, or transfer secret). It may be shown instantly or emailed to you.
Check the domain isn't inside the 60-day post-registration lock or a recent-transfer lock.

Step 3: Start the transfer in Cloudflare

In Cloudflare, open Domain Registration > Transfer Domains. Cloudflare lists the zones in your account that are eligible, remember, only domains with active DNS on Cloudflare appear here. Select the domain, paste the EPP code, and pay the transfer fee. That fee isn't a surcharge: it buys you a full one-year renewal added on top of your existing registration, so you don't lose the time you've already paid for.

After you submit, the losing registrar has up to five days to release the domain. You can usually speed this up by approving the transfer immediately from an email they send, or by clicking 'accept transfer' in their control panel. If you do nothing, it still completes automatically at the five-day mark. Cloudflare emails you when the domain lands in your account.

After the transfer: verify nothing quietly broke

Because DNS moved to Cloudflare in step one, your site and email should never have gone down, the registration change in step three doesn't touch how records resolve. But confirm anyway: load the site over HTTPS, send a test email, and re-check your MX and DKIM records survived the move. This is the moment small omissions from the DNS import surface.

Also confirm the domain's new expiry date and re-enable WHOIS privacy if you turned it off. Cloudflare offers free WHOIS redaction, so there's no reason to leave your contact details exposed. You can spot-check what resolves publicly with our domain expiry checker.

Don't rely on registrar reminder emails

One quiet downside of Cloudflare Registrar: it doesn't do aggressive renewal marketing, and if a card expires or an email lands in spam, a lapse can slip past you. Wholesale pricing is great; it also means fewer nag emails to save you from yourself.

That's a good reason to keep expiry and DNS health on independent monitoring rather than trusting any single registrar's notifications. VigilDog's domain and DNS monitoring tracks expiry dates, nameserver changes, and record drift across every domain you manage, so a missed renewal or an accidental DNS edit reaches you as an alert, not as a down site.