Domains
Domain renewal and transfer cost planner
Project several years of renewals across a portfolio, with the increase you expect compounding, and see which names cannot be transferred yet.
Free, no accountIn your browser
One per line: name, what a year costs you now in US dollars, the next renewal date, and - if you want the transfer lock checked - the date it was registered or last transferred.
How far ahead to add it up.
What you expect prices to rise by each year. It compounds: year three pays the rise twice.
Transferring compares both totals and checks the 60-day lock.
Leave this blank for today. Set a day, as 2027-01-31, to price the plan as it will stand then.
Result
Nothing to price yet
Paste your domains with what each costs you a year and the total is projected as you type.
What this is
This domain renewal cost calculator takes the prices and dates you already know for your own names - what a year costs you now, when each one renews, when each was registered or last moved - and projects the next few years of it, compounding whatever yearly increase you expect, with a side-by-side total for transferring the lot somewhere cheaper and a flag on every name ICANN's rules will not let you move yet.
A renewal budget is a compounding problem, not a multiplication one. Ten domains at $12.98 is $129.80 this year, but at 8% a year it is not ten times five years of $12.98 over five years: each rise lands on the price the last rise produced, so the gap between the flat figure and the real one is the number worth seeing before a budget is signed off.
A transfer is not a price comparison either. A transfer-in fee buys a registration year rather than replacing one, so the honest comparison is one transfer fee plus four renewals at the new price against five renewals at the old one - which is what the two totals here are.
ICANN's Transfer Policy also puts a 60-day window after registration, and after a previous registrar transfer, in which the registrar of record is allowed to refuse a transfer outright. A plan that moves a name bought last month is not a cheaper plan; it is a plan that cannot be carried out yet, which is why the second date on each line is worth pasting.
How to read the result
Read the two totals in the facts block first: what staying put costs across the years you asked for, and - when you are planning a transfer - what moving costs, with the difference spelled out as a saving or a cost rather than left as a subtraction.
The year-by-year table shows where the compounding bites: year one is the cheapest row and the last row is the one your future self is budgeting for. Every row is rounded to whole cents before it is added up, so the total is the sum of prices you could actually be charged.
The by-domain table carries the lock column. "Clear" means the second date you gave is more than 60 days old, "locked until" names the first day a transfer can be requested, and "no date given" means you did not give this tool enough to say - it is not a clearance.
This planner covers only the cost half of running a portfolio; our guide Holding a domain portfolio: renewals, status codes and the names that attack yours covers where it fits alongside tracking expiry dates, reading EPP status codes and checking for lookalike domains against the same list.
Common mistakes
What goes wrong most often, and how to tell.
- Budgeting the renewal price you paid at signupA first-year promotional price is not the renewal price, and a renewal budget built from the promotional one under-reads every year after this one. Put what a renewal actually costs on the line, which is the figure on the registrar price list rather than the figure on the receipt.
- Planning a transfer for a name registered last monthThe registrar of record may refuse any transfer requested inside 60 days of the creation date or of a previous transfer. A migration plan that includes a name bought three weeks ago needs two phases, not one, and finding that out at the registrar is slower than finding it out here.
- Treating the transfer fee as a replacement for a renewalA transfer-in adds a year to the registration rather than consuming one, so comparing a transfer fee against a renewal fee one-for-one double-counts a year. The comparison here puts the transfer in year one and the new registrar's renewal price in every year after it.
- Leaving the increase at zero because nobody announced oneRegistry wholesale fees and registrar margins have both moved repeatedly, and a zero in that box turns the total into a floor rather than a forecast. Even a conservative two or three percent tells you more about a five-year commitment than a flat line does.
Questions
What people ask about this tool.
- Year one is the price you entered, year two is that price plus the increase, year three is year two plus the increase again, and so on - each year is worked out from the year before it and rounded to whole cents, so the total is the sum of real prices rather than a smooth curve.
- ICANN's Transfer Policy lets the registrar of record refuse a transfer requested within 60 days of the domain's creation date or within 60 days of a previous registrar transfer, and it keeps both of those windows out of the refusals that are not permitted. In practice a name under 60 days old stays put.
- No, and nothing can honestly: there is no public feed of current registrar renewal pricing, only published price lists that change without notice. Every figure here is the one you typed, read and shown as US dollars - there is no conversion, so a line written as €29.50 is reported as having no price rather than counted as $29.50 - and your list is never sent anywhere.
- Because a transfer-in price and a renewal price at the same registrar are rarely the same number, and the transfer only covers the first year. One price prices year one, the other prices every year after it, which is the only way the two totals are comparable.
- Yes. Put a date in the "Project from" box and the lock windows, the past-renewal flags and the date in the summary are all measured from that day instead of today, which is how the worked examples below stay true whenever you read them.
Sources
Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.
- ICANN, “Transfer Policy” read 13 October 2026
Use it from the API
The same check, as one request.