Quick answer: For one ordinary, nonpremium
.com, compare renewal price and operating constraints, not just the first-year banner. On October 3, 2026, Cloudflare Registrar listed $10.46 to register or renew, Porkbun $11.08, and Namecheap $18.48 to renew after a displayed $11.28 first-year sale. Cloudflare requires its nameservers; Porkbun has already announced a November.comincrease; Namecheap’s sale can change. Those facts point to different reader fits, not a permanent cheapest registrar. Sources: Cloudflare, Porkbun, Namecheap.
The worksheet assumes a US buyer registering one new, ordinary .com for one year, then keeping it for a total of five years without a transfer or optional add-ons. All amounts are USD from direct public pages checked on October 3, 2026. Premium names, other extensions, taxes, redemption, and checkout terms can change the result.
See the transaction types side by side
Scroll horizontally to read all columns.
Registrar, ordinary .com | New one-year registration | One-year renewal | Displayed transfer | Price and fee note |
|---|---|---|---|---|
| Cloudflare Registrar | $10.46 | $10.46 | $10.46 | Live public .com table; Cloudflare nameservers required. |
| Porkbun | $11.08 | $11.08 | $11.08 | Current table says listed ICANN and other fees are included; November increase announced. |
| Namecheap | $14.98 standard; $11.28 displayed sale | $18.48 | $11.48 displayed sale; $14.98 standard | A $0.20 ICANN fee may apply to affected transactions at checkout. |
These are different kinds of price. Namecheap’s displayed sale is a current offer, not its ordinary registration rate or renewal amount. Promotions can change; confirm registration and transfer prices on Namecheap’s live .com page and in checkout. The $0.20 fee is a possible addition under Namecheap’s disclaimer; it should not be silently applied to every row without seeing the actual cart. Sources: Cloudflare price table, Porkbun pricing, Namecheap .com page.
Porkbun’s current $11.08 row is especially time-sensitive. Its announcement says the .com price is expected to rise to approximately $11.81 on November 1, 2026 at 04:00 UTC. The announced amount is neither today’s checkout nor a locked future renewal. If you read this after that date, use Porkbun’s live table rather than the October figure or the estimate in the announcement.
A five-year illustration that shows the renewal effect

This illustration holds the October 3, 2026 rates constant for four later renewals; it is not a five-year quote. Porkbun has already announced a November increase. Use the formula to compare the renewal effect, then replace its inputs with the rates available when you buy:
Five-year illustration = first-year registration + four one-year renewals + applicable transaction fees + selected add-ons.
The Namecheap sale row assumes the displayed first-year sale applies to this buyer and only the first year. The standard row removes that promotional assumption.
Scroll horizontally to read all columns.
| Hypothetical rate path | Formula using October 3, 2026 posted figures | Constant-current-rate illustration |
|---|---|---|
| Cloudflare Registrar | $10.46 + 4 × $10.46 | $52.30 |
| Porkbun | $11.08 + 4 × $11.08 | $55.40 |
| Namecheap standard first year | $14.98 + 4 × $18.48 | $88.90 |
| Namecheap with displayed first-year sale | $11.28 + 4 × $18.48 | $85.20 |
The comparison reveals why first-year price alone is a weak buying rule. Namecheap’s displayed $11.28 sale is close to Porkbun’s October $11.08 registration price, but the posted renewal lines differ by $18.48 − $11.08 = $7.40 per year at those dated rates. Over four hypothetical renewals, that difference dominates a small entry-price gap. Porkbun’s announced increase will narrow that gap if it applies when you renew.
You can make the worksheet responsive to future changes without pretending to know them. If any registrar’s renewal rate were $1 higher than shown for all four renewal years, its five-year illustration would rise by 4 × $1 = $4. A different increase, a sale ending, tax, or a privacy add-on changes the inputs in a different way. Recalculate with the rate the registrar publishes when you are about to renew.
For a domain you actually own, keep a row for each transaction instead of carrying one guessed renewal rate forward indefinitely:
Scroll horizontally to read all columns.
| Your record | What to enter when the event occurs | Why it matters |
|---|---|---|
| Registration | Paid amount, term, any sale condition, and new expiry date | Separates the introductory payment from later years. |
| Each renewal | Current posted renewal, fees shown in checkout, payment date, and resulting expiry | Replaces the hypothetical fixed rate with what you actually paid. |
| Any transfer | Transfer payment, previous expiry, new expiry, and any exception noted by the registrar | Shows whether the payment bought an added year. |
| Privacy or other extras | Whether included, selected separately, or ineligible | Keeps optional services out of the base comparison until chosen. |
Set a reminder early enough to inspect the live renewal and contact details before the domain approaches expiry. If a registrar changes a price, you can update the next row without rewriting what was paid in earlier years. If you decide to transfer, the recorded expiry and past renewal date make it easier to check whether the usual extra-year rule applies.
Price is not the only constraint
Cloudflare’s registrar FAQ says domains registered there must use Cloudflare authoritative nameservers. You can still point DNS records to hosting elsewhere, but you cannot use third-party authoritative nameservers for that domain under this registrar. If your workflow depends on a different DNS provider’s nameservers, the lower listed .com renewal is not the whole decision. If you are comfortable managing DNS through Cloudflare, that constraint may be acceptable.
For an existing domain, write down the DNS records that currently make the website, email, subdomains, and service verifications work before moving nameservers. A registrar transfer and a nameserver change are distinct events, but Cloudflare’s condition can make them part of the same migration plan. The potential annual saving has little practical value if the team cannot confidently reproduce its current DNS configuration.
Porkbun and Namecheap require their own checkout and policy review, but neither is presented here as a universal service-quality winner. Porkbun publishes a flat current register/renew/transfer .com line and lists phone and chat 9 a.m.–5 p.m. Pacific daily, plus email around the clock on its pricing page. Namecheap says live chat and email are available 24/7 on its support page. Those are documented contact channels, not measured response times or evidence that a difficult transfer will be resolved faster at either company. Check the support route for your chosen registrar and the issue you may need help with before moving the domain.
Registrant privacy also needs careful wording. Cloudflare documents WHOIS data redaction where the registry permits it. Porkbun describes included privacy for participating extensions, with .com outside its listed exclusions. Namecheap’s .com page describes free privacy for eligible domains. These mechanisms and registry limits are not identical, and “privacy included” is not a promise of anonymity. Check the live eligibility and what the public registration record would show for the exact name you intend to buy.
Scroll horizontally to read all columns.
| What matters most to you | Evidence-based direction | Check before paying |
|---|---|---|
Lowest posted October .com renewal among these three | Cloudflare’s $10.46 row. | Accept its nameserver requirement and verify the live price. |
| One current price for registration, renewal, and transfer, with published phone contact hours | Porkbun’s $11.08 row. | Recheck after its announced November change. |
| An existing Namecheap workflow or a live first-year promotion | Namecheap’s current sale may reduce entry cost. | Budget its $18.48 published renewal and any fee shown in checkout. |
An existing account, DNS setup, support preference, and willingness to move later can outweigh a small current price difference. A promotional first year still needs to be judged alongside later renewals.
Treat a transfer as a new year, not a mystery surcharge
A .com transfer usually adds one year to the domain’s registration term. Cloudflare’s FAQ and Porkbun’s pricing notes describe the usual extension; exceptions can apply, including timing after a recent renewal. That means a transfer fee is generally paying for an added year. It should not be counted as a yearless penalty and followed immediately by a second charge for the same added year in a planning spreadsheet.
For example, imagine a domain with eight months left before expiry. If a qualifying transfer adds one year, the new expiry would ordinarily be about 20 months away: eight prepaid months plus twelve added months. Record the transfer payment against that added year, then schedule the next expected renewal for the new expiry. This is a timing example, not a guarantee for a particular domain; check the registrar’s current confirmation and final expiry date.
Before paying for a transfer, confirm eligibility and whether a recent renewal affects the added year. Then enter the actual new expiry in your ledger. The domain transfer guide covers authorization codes, locks and the migration checks; those steps deserve their own checklist rather than an assumption in the cost model.
For a buyer happy to use Cloudflare DNS, Cloudflare has the lowest posted October renewal of this three-way .com example. Porkbun is a close current-price alternative with a different published support-channel mix, subject to its announced increase. Namecheap can make the first year look attractive, but its displayed renewal is the dominant input in the constant-rate worksheet. Before choosing any of them, recheck the live .com row, the checkout, privacy eligibility, and the nameserver or transfer conditions that apply to your domain. The domains hub covers the wider work of registration, DNS, and renewals.
Confirm live .com renewal pricing and Cloudflare nameserver requirements.
Confirm live .com renewal pricing and the checkout total.
Sources and checking
Product terms can change. These are the sources checked for this article; follow the links to verify current details before you buy.
- Cloudflare Registrar: live domain pricing (checked 2026-10-03)
- Cloudflare Registrar: FAQ (checked 2026-10-03)
- Cloudflare Registrar: WHOIS redaction (checked 2026-10-03)
- Porkbun: domain pricing (checked 2026-10-03)
- Porkbun: Why did .com prices go up? (checked 2026-10-03)
- Porkbun: WHOIS privacy (checked 2026-10-03)
- Namecheap: .COM domain prices (checked 2026-10-03)
- Namecheap: support availability (checked 2026-10-03)
- ICANN: registrant transfer FAQ (checked 2026-10-03)
- ICANN: Transfer Policy (checked 2026-10-03)