Our Domain Stack: Cloudflare At-Cost for toolscore.net, Porkbun When DNS Has to Leave
at-cost + 0% markup, 1 hard rule the number that matters here
By Stan K.
How we run the domain behind this site: Cloudflare Registrar sells at cost with zero markup but locks every domain to Cloudflare nameservers — the rule is explicit and quoted here. When a project needs external DNS, we register at Porkbun instead: $11.81 flat .com (registration = renewal = transfer, from the official pricing API), WHOIS privacy free for life, no nameserver lock. Plus the transfer mechanics: +1 year to expiry, the 45-day trap, 60-day locks.
This site is a static Astro build served by Cloudflare Pages for $0 a month — unlimited static bandwidth, 500 builds a month included. The only line item that costs money is the domain itself, and after trying both vendors in this article across different projects, we run a two-registrar policy. It is decided by exactly one question: where is the DNS allowed to live?
The Cloudflare half: at-cost, with one hard rule
toolscore.net is registered at Cloudflare Registrar. The pricing promise, in Cloudflare’s own documentation: “You only pay what is charged by registries and ICANN… without markups fees,” and renewals are “always at or below what registries and ICANN charge us.” There are no upsells in the cart because there is no cart — DNS, DNSSEC, SSL and WHOIS redaction are included, and the catalog covers over 430 TLDs.
The hard rule, also in Cloudflare’s own documentation: “All domains acquired via Cloudflare Registrar use Cloudflare nameservers… You will not be able to change to another DNS provider’s nameservers while using Cloudflare Registrar.”
For this site, that rule costs us nothing. DNS, proxying, SSL and hosting already live in the same account; the nameservers were going to point at Cloudflare anyway. Locking them there is not a sacrifice — it is one less setting to get wrong. At-cost renewal on a domain whose every other service is free is about as boring as infrastructure gets, which is the compliment we are paying it.
Cloudflare Registrar is not a general-purpose registrar. It is a registrar for domains whose DNS lives at Cloudflare. If your project needs Route 53, corporate nameservers, or any external DNS host, a Cloudflare-registered domain cannot point there — not “inconveniently,” but by documented policy. Buy those domains somewhere else from day one.
The number we refuse to print
Cloudflare’s exact at-cost .com price sits behind a login-and-JavaScript wall; our probes got an interstitial, not a figure, so we have no verified number to publish — and we won’t borrow one from a blog. The price also moves by design: registry wholesale prices rise (Squarespace says so publicly while raising its .com, .net, .org and .xyz renewals), and an at-cost registrar passes every cent of that through. That is the honest trade. You never pay a markup, and you never lock a printed number.
When our tables need a verified flat .com figure, they use Porkbun’s: $11.81 — registration = renewal = transfer, returned verbatim by the official pricing API, with a standing −$1 first-year coupon that makes year one $10.81. One number for all three events is a rarer property than it sounds; compare Namecheap’s verified $12.08 first-year sale against its $19.98 renewal — plus 65% in year two.
The Porkbun half: where DNS is allowed to leave
Not every project lives inside Cloudflare. A client with corporate DNS on Route 53, a mail stack where DNS control is non-negotiable, a test domain that gets pointed at a new nameserver every month — for those, we register at Porkbun, for three verified reasons:
- No nameserver lock. Point the domain at any DNS host, change it whenever the project demands.
- One flat number. $11.81 for registration, renewal and transfer alike — no teaser year, no renewal cliff.
- WHOIS privacy free for life. It does not flip to a paid add-on in year two.
The full decision matrix we actually use:
| Project shape | Where we register | Why |
|---|---|---|
| Site fully on Cloudflare (Pages, Workers, proxy) | Cloudflare Registrar | At-cost with zero markup; the nameserver rule is irrelevant — DNS was going to Cloudflare anyway |
| DNS must live elsewhere (Route 53, corporate NS, mail-critical DNS) | Porkbun | No nameserver lock; move DNS freely without changing registrars |
| TLD outside Cloudflare’s 430+, or an IDN (xn—) domain | Porkbun or another registrar | Cloudflare explicitly does not support IDN domains, and unsupported TLDs simply do not appear in its search |
| The price must be citable without logging in | Porkbun | $11.81 flat is published machine-readable; Cloudflare’s figure is not |
Transfer mechanics: what moving a domain actually costs
A transfer between registrars is not free, but it is not lossy either. You pay the new registrar a one-year fee, and that year is added on top of your current expiry date. Porkbun’s documentation: “All transfers of gTLD domain names include a one year renewal of the domain.” Cloudflare’s: “a transfer adds one year to your current expiration date.” Documented exceptions: .uk and .nz transfers add no year and charge no fee, and no transfer can push a domain past the registry’s 10-year cap.
Three timing rules decide whether the move is smooth or stupid:
- The 45-day rule. Transfer a domain within roughly 45 days after a renewal and the registry does not add the extra year — you paid for a 1-year transfer fee, and the expiry clock did not move. Wait 45 days after renewing, then transfer.
- The 60-day locks. After registration (Porkbun requires the domain to have been at the current registrar “for at least 60 days”), after any transfer, and after a registrant contact change, the domain cannot move. The registrant-change lock is sometimes optional — registrars “may allow you to opt out of this,” in Porkbun’s wording — but plan as if it is not.
- The clock. The whole process usually finishes in under a day and, per Porkbun’s official wording, takes “not generally more than eight days.”
The mechanics that matter before any of this — unlock at the old registrar, EPP/auth code, DNSSEC handled carefully — are covered in the traps article.
When Cloudflare Registrar is the wrong answer
Blunt version, so nobody has to infer it from the table above:
- DNS must leave Cloudflare at any point in the project’s life. The lock makes it a non-starter; you would be transferring the domain out first, inside the 60-day-lock rules, under time pressure.
- You need an IDN (xn—) domain, or a TLD outside the 430+ catalog.
- You need a printed, quotable price. At-cost is a promise, not a number you can put in a budget — the verified flat figure lives at Porkbun.
Our total domain-layer bill for this site: one at-cost renewal a year, no privacy fee, no upsells, against $0/month hosting. The verified version of that stack for everyone else — including the TLDs that quietly cost more every year — is in the Domains hub. Start with the .io renewal creep if you want to see what the opposite philosophy costs.