Buying a domain through Cloudflare
I found buying a domain through Cloudflare convenient because it keeps the name and the DNS work in one place.
Less switching between services
My domain is rezarosli.com. I bought it through Cloudflare. A domain is the address people remember. DNS connects that address to the service that answers it. Keeping both in the same account is the convenience that appeals to me: the registration and the next step towards putting a site online belong to one workflow.
For this site, that leads naturally into the Cloudflare Pages setup. It is still useful to distinguish buying a name from hosting the website; they solve different problems.
The benefits I look for
Cloudflare says its Registrar charges registry and ICANN costs without a markup, including renewals. It also provides WHOIS redaction by default and a DNSSEC activation option. The appeal is straightforward pricing and domain administration alongside DNS. Registry prices can still change; “at cost” does not mean a domain’s price is fixed forever. Cloudflare Registrar documentation
The constraint to understand
Domains registered through Cloudflare must use Cloudflare nameservers while they remain with its Registrar. That is a real tradeoff: registration and DNS are closely coupled. It does not mean the website itself must be hosted on Cloudflare, but moving DNS to another provider would require a different registration arrangement. Registration requirements
The content of this website remains separate from that decision. My Jekyll source and build produce static files; the domain gives those files a memorable public address.