Phonova verdict: Cloudflare Registrar is excellent value for a supported global TLD already using Cloudflare DNS. Its no-markup model is real, but mandatory Cloudflare nameservers and the absence of verified .ke support make it a deliberate infrastructure choice.
Price and terms checked 2026-08-11: Registry and ICANN cost with no Cloudflare retail markup; exact registration and renewal prices vary by supported TLD.
Cloudflare Registrar: the decision in one table
| Registrations | New registrations and inbound transfers for supported extensions |
|---|
| Pricing model | Registry cost plus ICANN fee, without registrar markup |
|---|
| Nameservers | Cloudflare nameservers are mandatory while the domain remains at Registrar |
|---|
| Renewal | Auto-renew is available; multi-year pricing can use registration for year one and renewal for later years |
|---|
| Privacy | WHOIS data redacted where the registry permits |
|---|
| Kenya limitation | .ke/.co.ke were not verified in the supported-TLD list |
|---|
At-cost pricing is the advantage
Cloudflare says it charges the registry and ICANN cost rather than adding a retail margin. That can produce strong renewal value on mainstream TLDs. ‘At cost’ does not mean every extension costs the same or that premium names are universally supported.
It is no longer transfer-only
Old reviews often describe Cloudflare Registrar as a destination only for inbound transfers. Current documentation supports searching and registering new domains for listed TLDs as well as transferring existing ones.
Mandatory Cloudflare DNS is the central trade-off
Every Registrar domain must use Cloudflare nameservers. You can still create DNS records for third-party hosting, email and applications, but you cannot delegate the entire domain to another nameserver provider without transferring the registration away.
Supported TLDs, IDNs and premiums need checking
Cloudflare supports a defined extension list and does not currently support internationalised domain names. API documentation can surface premium pricing but says premium registration is not currently supported through that API. Verify the exact name before planning a portfolio migration.
Security and account ownership
Registrar security is tied to the Cloudflare account. Put the zone in a business-owned account, require MFA, use scoped member roles and keep recovery codes outside the account. A low renewal price is not useful if a former contractor owns the login.
Kenyan use case
Use Cloudflare Registrar for supported .com and other global names when Cloudflare DNS is already acceptable. Use a KeNIC-accredited registrar for .ke/.co.ke and when M-Pesa, KES billing or local registry support is required.
Questions buyers actually need answered
Can Cloudflare register a new domain?
Yes, for extensions on its current supported list.
Can I use different nameservers?
No. Cloudflare nameservers are mandatory while the domain remains with Cloudflare Registrar.
Does Cloudflare add a renewal markup?
Its documented model charges registry and ICANN cost without a retail registrar markup.
Can I register .co.ke?
We did not verify .ke or .co.ke on the supported list. Use a KeNIC-accredited registrar for that need.
Evidence boundary
This is a buying analysis, not an invented hands-on test. We verified the published offer and policies, separated introductory equivalents from money charged, and discounted claims we could not independently benchmark. Recheck the final checkout and keep an independent backup or export before moving a production service.
Sources checked
