cloudflare registrar review: at-cost domains, the catch, and who it's for.

Cloudflare Registrar sells domains at the price the registry charges, with nothing added. that is the entire product, and it is why the name turns up at or near the top of so many of our renewal price tables.

it is also a narrower product than most people expect, and the narrowness is the point rather than an oversight. this is what "at cost" actually means, the four constraints that come with it, and who each one rules out.

what "at cost" actually means

every registrar selling a .com pays Verisign the same wholesale fee. the price differences between registrars are not cost differences — they are margin, which is the whole reason the spread exists.

most registrars set a low first-year price to win the search result and recover the margin at renewal, once you have a live site and no appetite for a migration project. that pattern has a name — teaser pricing — and it is the largest source of quiet overspend in a portfolio.

Cloudflare does not play that game because it is not in the domain business for domain margin. it sells DNS, security and network services; domains are a retention feature. year one and the renewal are the same number: the registry fee plus the ICANN levy where one applies. no promotional year, no renewal cliff, no coupons.

the effect over five years is larger than people expect, because the comparison that matters is total cost of ownership, not year one against year one. run a TLD through price check and the gap is usually obvious.

one disclosure: we make nothing recommending Cloudflare — there is no affiliate programme, which is part of why it is under-recommended in registrar round-ups generally. our methodology covers how the tables are built and what we are paid for.

catch one: the domain must use cloudflare DNS

the biggest constraint, and non-negotiable. a domain held at Cloudflare Registrar must use Cloudflare's nameservers. you cannot register there and run DNS at Route 53, at your host, or at whichever provider your agency standardised on.

for most people this is fine and often an upgrade — the DNS is fast, the free plan is enough to hold records, and if you were already proxying the site you are just consolidating.

it rules out real situations though: a domain whose DNS is managed by a client or a platform you do not control, anything needing a DNS feature Cloudflare does not implement, and — the one that catches portfolio holders — a pile of parked names you wanted to leave at a registrar's defaults and never think about again.

catch two: it does not support every TLD

the TLD list is a subset. the big gTLDs are there and a decent spread of newer extensions, but plenty of ccTLDs are not, and a domain Cloudflare cannot sell lives somewhere else regardless of price.

this matters more for portfolios than single sites. hold a mixture of .com, .co.uk, .de and a few niche extensions and Cloudflare might cover half, leaving accounts elsewhere for the rest — which undercuts the "consolidate everything" argument. the supported list changes, so check the current one rather than any article's version; the registrar comparison shows who covers what.

catch three: there are no add-on services

Cloudflare Registrar does one thing. no email hosting, no website builder, no paid WHOIS privacy add-on, no SSL upsell, no marketplace, no brokerage, no transfer concierge.

for one kind of buyer that is the feature — nothing to decline at checkout, no pre-ticked boxes, no renewal invoice with line items you did not choose. the opposite failure mode from registrars whose checkout is mostly upsell.

for another kind it is a genuine gap. if you relied on your registrar for mailboxes or a landing page, you now source those separately. usually cheaper and better anyway, but it is work, and pretending otherwise would be dishonest.

catch four: support is thin by comparison

plainly: Cloudflare's registrar support is documentation, a forum and a ticket queue. not a phone number and a named account manager.

for a technically confident user with a working domain that is close to irrelevant — you will contact support approximately never. for someone whose transfer is stuck, or who does not know what an auth code is, it is the difference between a bad afternoon and a bad fortnight. part of what a full-service markup buys is a person who stays on the line while you fix it. that is a real service and some people should pay for it.

it is the constraint we would weigh most heavily for anyone managing client domains. debugging your own nameserver problem is one thing; doing it while a client's site is dark is another.

who it is right for

• you already use Cloudflare DNS, so the largest constraint costs you nothing
• your portfolio is mostly common gTLDs the supported list covers
• renewal cost is the number you are optimising, not first-year cost
• you are comfortable handling a stuck transfer or a DNS problem yourself
• you want no upsells, no coupons and no annual re-shopping exercise
• you hold enough domains that a per-domain markup compounds into real money

who it is wrong for

• you need DNS at a specific other provider, or a client controls it
• your portfolio leans on ccTLDs and niche extensions that are not supported
• you buy mailboxes, landing pages or brokerage from your registrar
• you want somebody on a phone when a domain breaks
• you manage client domains where an outage is a business problem rather than an inconvenience
• you sell domains and want registrar-integrated listing tools

if you decide to move

check the current figure before transferring rather than any number in an article — the Cloudflare renewal prices page is generated from a live catalogue. moving several, work in expiry order: a transfer normally adds a year to the registration, so the one expiring soonest gets the most out of going first.

unlock the domain and get the auth code at the losing registrar first; the transfer guide covers that at the registrar people most often leave. treat DNS as a separate step — recreate every record at Cloudflare and confirm it resolves before nameservers change, because a transfer with an incomplete zone is how people take their own site down.

the verdict

Cloudflare Registrar is the cheapest sensible way to hold a domain if you were going to use Cloudflare DNS anyway. it wins on the only metric that compounds — the renewal — by declining to compete on the one that does not.

it is not a full-service registrar and does not want to be. if what you value is somebody answering the phone, the markup elsewhere is buying something real. work out which of those two people you are first, then check the live tables rather than the marketing.