Cloudflare Registrar

What Cloudflare Registrar actually is

Cloudflare Registrar sells domain names at wholesale cost. Registration, transfer and renewal are priced at or below what the registries and ICANN charge Cloudflare, with no markup at renewal and no add-on products attached to the checkout. In an industry where the standard business model is a cheap first year followed by inflated renewals and a checkout screen full of privacy, email and hosting upsells, that positioning is genuinely unusual — and it is the entire review. The question is not whether the pricing is good. It is what you give up to get it.

Two structural constraints define the product. First, every domain registered or transferred through Cloudflare Registrar must use Cloudflare nameservers. You cannot keep the domain at Cloudflare and point it at another provider's DNS. Second, the account model assumes you are a Cloudflare user: a verified account email is required, and ICANN's registrant verification rules apply, with unverified registrations risking a hold. Within those constraints the registrar is a full participant in the domain system — registrations, transfers, renewals, auto-renew on by default, multi-year terms up to ten years for most TLDs — and the price list is public.

That public price list deserves the emphasis our database entry gives it. Cloudflare publishes a per-extension table of registration, renewal, transfer and restore prices, which is more transparency than most registrars offer. On it: .com is $10.46 for registration, renewal and transfer alike, with a $40.00 restore fee; .ca is $9.19; .co.uk is $5.30 with free transfers; .ai is $80.00 across registration, renewal and transfer; .app renews at $14.20. The critical column is renewal: the .com price is the same in year one and year ten, which is exactly where competing registrars make their margin.

New registrations are supported, not just transfers — the older "transfers only" description of this product is out of date, and Cloudflare's own documentation walks through searching and registering new domains directly in the dashboard, with term selection and contact management built in. What is not supported: internationalized domain names. You cannot register domains containing non-ASCII characters, which is a real limitation for markets where those domains matter.

Pricing: what you really pay

You pay the registry price. There is no subscription, no account fee, and no minimum commitment — a single .com at $10.46 per year is a complete transaction. Restore fees are the one genuinely punitive number on the sheet ($40.00 for .com), and they apply when a domain lapses into redemption, which is standard across the industry rather than a Cloudflare quirk. The practical advice is trivial: keep auto-renew on and a working payment method attached.

Compare that to the market. Typical registrar pricing for .com lands between $12 and $20 at renewal after a discounted first year, and privacy protection is often a separate line item at $5 to $15 per year. Over a ten-year horizon, a $10.46 flat price versus a $15.99 renewal price is roughly $55 saved per domain — for a portfolio of fifty domains, that is a real annual number, and it compounds every year. We consider at-cost domain pricing one of the few genuinely unambiguous wins available in infrastructure, precisely because it has no asterisks: the same price at registration, renewal and transfer.

Privacy: Cloudflare does not sell WHOIS privacy as an upsell product, and gTLD registrations carry the standard ICANN-mandated redaction of personal contact details. Where registrars monetize privacy as an annual add-on, Cloudflare treats it as part of registration. That is worth money in aggregate even though it never appears as a line item.

What the pricing does not include is anything beyond the domain. Hosting, email, SSL and site builders are not part of this product — Cloudflare sells CDN, WAF and Pages separately, and those are reviewed on their own pages here. If you want a domain plus bundled hosting from one invoice, this is not that product; it is deliberately just a registrar.

Performance & infrastructure

Domains are not served, so the usual infrastructure metrics do not apply. What matters instead is DNS resolution and registration reliability, and here the pairing with Cloudflare DNS is the point: nameservers are Cloudflare's, answers come from the 330-plus city anycast network, and DNSSEC can be enabled with the DS record handled in the same account. For the common case — a domain used for a website behind Cloudflare's proxy — the combined stack is fast, free to operate at the DNS layer, and managed from one dashboard.

Registration operations themselves run against the registry system with the standard EPP lifecycle: transfer locks, auth codes, auto-renew, grace periods and redemption. Nothing unusual, and Cloudflare's documentation is explicit about the flows, including the ICANN verification requirements that can put a domain on hold if the registrant email goes unverified. We would flag that as the one operational trap: an unverified email address can trigger a hold and parking nameservers until verification completes, which is ICANN policy rather than Cloudflare behavior, but it still lands on your site.

Reliability of the resolution layer follows Cloudflare's track record and concentration profile, which we have covered in detail in our Cloudflare DNS review. The short version: excellent operational record, public status page, and a single-vendor concentration risk that you manage by keeping a zone export and a documented way to move nameservers quickly if you ever need to.

Where it falls short

The nameserver requirement is the big one. It is a reasonable product decision — Cloudflare Registrar exists to feed the Cloudflare ecosystem — but it forecloses architectures where DNS lives at a separate vendor for redundancy or policy reasons. If your organization requires DNS hosting independent of your registrar, this registrar will not fit.

Internationalized domain names are unsupported. For brands and projects that need domains with non-ASCII characters, that is disqualifying, and it is worth checking before you plan a migration. Premium domains are priced at their registry premium rates, so the at-cost promise applies to standard registrations only — the wording on Cloudflare's own site is "at or below what registries and ICANN charge us," and premium pricing follows the registry's list.

Support is account-based like the rest of Cloudflare: ticket support for paying customers, community and documentation for everyone else. For a domain registrar that is usually acceptable — domains rarely need urgent support until they desperately do — but teams managing large portfolios should know that escalation paths are thinner than at registrars that sell managed domain services at higher prices.

Finally, the product surface is narrow by design. No backorder marketplace, no brokered acquisitions, no aftermarket, no bulk portfolio management tooling beyond the API. For domain investors and large portfolio operators, specialized registrars still offer tooling this one does not. For everyone else, those omissions are the reason the price is what it is.

One caveat on how to use the price sheet in your own decision: prices move as registry pricing moves, and Cloudflare's table reflects current wholesale rates rather than a fixed promise for future years. What the at-cost model guarantees is the structure — no markup layer between you and the registry — not a specific number in 2030. For budgeting a long-lived portfolio we would plan on registry price inflation, which applies to every registrar equally, rather than on any one vendor's current table.

Who should pick this

Our pick in /category/domain-registrars for anyone already using or willing to use Cloudflare DNS, which is most people reading this site. The combination of at-cost renewal pricing, free privacy, a public price sheet and first-class DNSSEC integration is the closest thing to a free lunch we have found in infrastructure. Small businesses, developers and portfolio owners running standard gTLDs should simply move renewals here and stop paying renewal markup elsewhere.

Who should skip it: organizations that require DNS at a separate vendor from the registrar; anyone needing IDN registrations; domain investors needing aftermarket tooling; and buyers of premium domains who should price the registry premium directly against competing registrars before transferring. If you are comparing registrars on price alone for standard extensions, run the ten-year math — Cloudflare wins it almost every time, and the price sheet lets you verify that yourself before you commit.

Key takeaways

• At-cost pricing: registration, renewal and transfer at registry wholesale — .com is $10.46 across all three.
• Full price sheet published per extension, including restore fees ($40.00 for .com).
• New registrations are supported now, not just transfers; most TLDs allow terms up to ten years.
• All domains must use Cloudflare nameservers — a hard constraint that rules out split-vendor DNS setups.
• No IDN support; premium domains follow registry premium pricing.
• No upsold privacy add-ons; standard ICANN contact redaction applies to gTLD registrations.

Sources

• https://pricing.registrar.cloudflare.com/
• https://www.cloudflare.com/domains/
• https://developers.cloudflare.com/registrar/
• https://developers.cloudflare.com/registrar/get-started/register-domain/
• https://www.cloudflare.com/network/
• https://www.cloudflare.com/about/