Porkbun

Domains · Registrar

The registrar I use when I want straightforward domain ownership and renewal pricing without mixing the registrar with the rest of the stack.

Why it earns a place

Why I use it

I prefer keeping domain ownership boring. Porkbun can be the registrar while Cloudflare handles nameservers, DNS, redirects, Pages, and mail routing. That separation makes migrations easier.

Use cases

Best for

Registering domains without tying them to a website builder
Keeping renewal management separate from hosting
Pointing nameservers to Cloudflare
Managing a portfolio of product and subdomain names

Start small

Quick start

01
Register the domain
Enable account security immediately and verify the contact email. Keep renewal enabled for domains that would be expensive to lose.
02
Delegate DNS to Cloudflare
Create the zone in Cloudflare, then replace Porkbun nameservers with the Cloudflare pair. From that point, edit DNS in Cloudflare rather than in both places.
03
Leave ownership at the registrar
Changing nameservers does not move the domain registration. Porkbun remains where you renew/transfer ownership; Cloudflare becomes where traffic is configured.

Repeatable workflows

Things I come back for

New subdomain

You normally do not create a new domain in Porkbun. Add a DNS record or custom-domain mapping in Cloudflare for the existing domain.

1
Keep the registered root domain where it is.
2
Add the subdomain to the destination host or project.
3
Create the corresponding DNS record in Cloudflare and verify HTTPS.

Transfer later

Unlock the domain and request the authorization code only when you genuinely want to change registrar; DNS hosting and registrar choice are separate decisions.

1
Confirm the destination registrar supports the TLD and transfer.
2
Unlock the domain and request the authorization code.
3
Start the transfer, then confirm DNS remains pointed at the intended provider throughout.

Reference

Links