Comparing Registrars Over Three Years: The Rules That Decide the Cost

Registrar comparison articles are useful for about a month. Prices move, promotional first-year rates expire, and the table you read last year is wrong.

The rules underneath the prices do not move. They are set by ICANN’s transfer policy and registry agreements, they are published, and they decide something more important than the price: whether the plan you are comparing is even executable on your timeline.

Here is the version of the comparison that does not expire.

Three separate 60-day locks, not one

Most people know there is “a 60-day rule.” What is less widely known is that there are three distinct triggers, with different strengths, and that the difference matters.

After initial registration. ICANN’s transfer policy allows a registrar to deny a transfer request within 60 days of the domain’s creation.

After a transfer. The same allowance applies within 60 days of a completed inter-registrar transfer.

After a change of registrant. This one is categorically different. When the registrant’s name or organisation changes, the registrar must impose a 60-day lock on inter-registrar transfer — and must deny a transfer during that window. The only relief is that the registrant may be offered the option to opt out before the change is applied. Skip that opt-out and you have locked yourself for two months.

That distinction has a practical consequence for consolidation projects. If you are cleaning up a portfolio — updating registrant details and moving registrars — do the transfer first, then the registrant change, or explicitly exercise the opt-out. The reverse order puts a mandatory lock on the domain you were about to move.

A transfer adds a year, up to a ceiling

A completed inter-registrar transfer extends the registration by one year, according to ICANN’s policy — subject to a limit that surprises people who have prepaid: “in no event shall the total unexpired term of a registration exceed ten (10) years.”

Two consequences for a three-year cost model:

Transfers are partly self-funding. If you transfer a domain you were going to renew anyway, the year you receive is a year you do not pay for separately. A registrar comparison that ignores this is comparing the wrong number.

Prepaying for a decade caps your flexibility. Once you are at the ten-year ceiling, transfers stop adding value, and you have locked capital into a registrar you may want to leave. The savings from a long prepay are real; so is the loss of the reason you were comparing registrars in the first place.

The auth code is a five-day obligation

The auth code — the EPP or transfer code — is the credential that authorises the move. ICANN’s policy puts a clock on the registrar: on the registrant’s first request, the registrar must provide a unique auth code and remove the client transfer lock within five calendar days.

It also documents a limit that is easy to get wrong: the auth code cannot substitute for the formal authorisation step. Providing a code is not the same as approving the transfer, and a process that assumes otherwise will stall.

If a registrar has not supplied the code within five days, that is a documented failure and there is a documented path for it — a complaint to ICANN’s Contractual Compliance function. The formal dispute process between registrars, TDRP, is available only to accredited registrars, so it is not your route.

Grace periods: what a missed renewal really costs

The renewal timeline is documented and it is more forgiving than the panic suggests — and then abruptly less forgiving.

ICANN documents a redemption grace period of 30 days after a registrar deletes a domain, during which a restore request “must be honored” — but with a documented caveat that “there may be a fee.” The amount is not set by ICANN. It is set by the registrar, which means it varies by an order of magnitude across the market and cannot be modelled from official sources.

Before deletion, there is the auto-renew grace period, and here the documented numbers are more specific: the registry agreement’s appendix specifies a 45-day auto-renew grace period, and a 5-day renew/transfer grace period.

So the sequence after a missed renewal is roughly: 45 days of auto-renew grace where the domain still resolves, then deletion, then 30 days of redemption where you can still get it back for a fee you cannot predict, then nothing.

For a three-year cost model, this suggests one thing worth budgeting: enable auto-renew and keep a valid payment method on file. The alternative is a line item whose size is decided by a party you have not chosen yet.

At-cost pricing exists, which changes the comparison

The reason registrar prices diverge so much is that domain registration is resold. One registrar documents the opposite model, and its wording is worth quoting because it establishes a floor:

Cloudflare Registrar states it charges only “what is paid to the registry for your domain”, with “No markup. No surprise fees,” and renewals “only renew at the list price set by the registry.”

That matters for method, not for shopping. If at-cost pricing exists, then the spread between registrars is markup, not cost — and a three-year comparison is really a question about how much you are willing to pay for the registrar’s interface, support, and renewal behaviour.

Whether that markup is worth paying is a legitimate question. What is not legitimate is modelling it as an unavoidable cost.

The three-year model, with the rules included

Input	Source	Verifiable?
Registry list price	Registry / at-cost registrar	Yes
Registrar markup	Compare quotes	Yes, same day
First-year promotional discount	Registrar quote	Yes — but check the renewal rate
Value of a transfer’s added year	ICANN policy	Yes, documented
Redemption fee (if you miss a renewal)	Registrar-set	No official figure exists
60-day locks affecting timing	ICANN policy	Yes, documented

The bottom row is the one that turns a spreadsheet into a plan. A three-year cost model with no calendar is not a model — it is an assumption that you will never need to move anything, on a timeline you have not checked.

The check that costs nothing

Before committing to a multi-year registration anywhere, run three questions:

1. How old is the domain? Under 60 days since creation, no transfer is possible.
2. Has it transferred or changed registrant recently? Same 60-day windows, and the registrant one is mandatory.
3. What does a restore cost if I miss a renewal? Ask, in writing. If the answer is not published, that absence is the answer.

None of those appear in a price comparison, and any one of them can invalidate the plan you were comparing. Check them first — a three-year model built on an impossible sequence is not cheaper than the alternative, it just looks that way in the spreadsheet.