Singapore-based practical guides, tutorials and experiments in AI, computing, modelling, simulation, optimisation and quantum computing, with research notes and hands-on workflows.
Move WordPress.com Domain to Cloudflare: Cut Renewal Fees
Yes, Cloudflare cuts renewal fees in half. Messing up ICANN domain locks risks irreversible DNS downtime and lost traffic. Follow the 6-step transfer guide →
Can You Transfer a WordPress.com Domain to Cloudflare to Cut Renewal Costs?
Yes, Cloudflare cuts renewal fees in half. Transferring your custom domain eliminates retail markup, but messing up the DNS cutover order or ICANN domain locks risks instant site downtime. Follow our 5-minute migration checklist step-by-step below →
TECHUCATION · DOMAINS 2026 Moving a WordPress.com domain to Cloudflare Registrar, and what it actually costs.
My WordPress.com domain renewal notice came in at £16/year, with auto-renew switched off and the expiry only a couple of days away. That is a fine price for convenience, but the same name sits on Cloudflare Registrar at wholesale cost with no markup. This post walks through the move end to end, including the one step that quietly breaks things if you rush it, and lays out the real cost difference.
The short version: you do not “renew at Cloudflare”. You transfer the domain to Cloudflare, which extends the registration by a year in the process. The saving is real, but the order of operations matters.
1 · The cost case
Cloudflare Registrar charges exactly what the registry charges them, with zero markup, and bundles WHOIS privacy for free. Retail registrars add a margin on top. For a .net the difference looks like this:
DNS Record (Type & Name)
Target Value
Cloudflare Proxy Status
A · @
192.0.2.1
Proxied (Orange Cloud)
CNAME · www
@
Proxied (Optional www)
TXT · @
"google-site-verification=..."
DNS only (Grey Cloud)
192.0.2.1 is a reserved TEST-NET address that never routes anywhere, which is exactly what you want: the proxy intercepts the request before that IP is ever used. Then a single Redirect Rule (Rules > Redirect Rules) handles the rest:
Keep the TXT verification record as DNS only. It does not need to resolve to anything, it just needs to exist.
5 · After the transfer
Three things to settle once the registrar shows Cloudflare:
Auto-renew. Optional, but turning it on (Domain Registration > your domain) means you never repeat the two-days-from-expiry scramble. If you leave it off, set yourself a reminder a few weeks before the date.
DNSSEC. Worth enabling for the added integrity protection. Because Cloudflare is now both your DNS and your registrar, the DS record is published to the registry automatically, so it activates without you touching the registrar by hand. Give it from a few minutes up to a couple of hours to show as signed at the registry.
Registrar lock. On by default at Cloudflare, so that one is already handled.
One caution with DNSSEC: once the DS record is published, do not move nameservers away from Cloudflare or disable DNSSEC out of order. Breaking the signature chain is the classic way to make a domain go dark, because validating resolvers will reject it. As long as DNS stays on Cloudflare, you are fine.
Net result: same domain, half the renewal cost, a year added, and the registrar consolidated with your DNS. The only part that needs care is the DNS-first ordering and not over-deleting the redirect records. Everything else is a few clicks and a short wait.
Can you transfer a WordPress.com domain to Cloudflare to reduce renewal fees?
Yes. Cloudflare Registrar sells domain renewals at at-cost wholesale registry pricing (e.g. ~$9-10/yr for .com) compared to standard retail pricing on WordPress.com ($22-25/yr), cutting renewal costs in half.
Will transferring my domain away from WordPress.com break my website?
No, provided you point Cloudflare’s DNS records back to WordPress.com servers before initiating the domain transfer authorization code.
Leave a Reply