What no renewal fee changes for a TLD holder

Anyone who has managed DNS domains knows the rhythm. A name is registered for a period, an invoice arrives before the period ends, somebody pays it, and the name lives for another term. Miss the payment and the name starts a slide toward deletion. A whole craft has grown around that rhythm: renewal calendars, automatic renewal, registrar accounts with a card on file, and a finance line that comes back every year.

A top-level domain recorded on the Freename registry does not work that way. The TLD is a token that sits in a wallet, and the registry charges no annual fee to keep it there. Nothing falls due, so nothing lapses for want of payment.

That is a simplification, for the most part. But the renewal date did more than collect money. It was a risk, a budget line and a yearly reminder that the asset exists. This article takes each of those in turn: what goes away, what stays exactly where it was, and what a holder or a finance lead has to put in place because the invoice no longer does the remembering.

What a renewal really does for a DNS domain holder

In the DNS, a second-level domain is not bought outright. It is registered for a term through a registrar, and the right to keep it depends on paying for the next term before the current one ends. The registry behind the extension keeps the record only as long as that chain of payments holds.

The same payment carries three separate functions.

The first is the price of continuity. The fee is what you pay to keep the name.

The second is a condition. The name exists for you only while the payments continue. If the fee is not paid, the name passes through the grace and redemption stages that the registry and registrar apply, and it can end up available to someone else. The expiry risk is the direct consequence of the fee being a condition and not only a price.

The third is a signal. Every renewal produces an invoice, an email, an entry in accounts payable and a line in a portfolio report. Even an organization that pays no attention to a domain is told once a term that it holds one.

A TLD without a renewal fee loses all three at once. Losing the first two is a relief. Losing the third is the part that needs thought.

What disappears when the TLD carries no renewal fee

The expiry risk

This is the largest change. A DNS domain can be lost by an administrative accident: an expired card, a registrar account tied to the mailbox of someone who left, a renewal notice caught by a filter, a reorganization in which nobody inherited the task. None of those accidents can take a Freename TLD away from its holder, because the holding does not depend on a payment arriving. The token stays in the wallet whether or not anyone thinks about it.

The renewal calendar

With no date, there is nothing to schedule. A holder with several TLDs loses a whole class of work: tracking terms, staggering renewal dates, deciding each year which names are worth another term, and reconciling registrar invoices against the register of names.

The recurring line and its price risk

The annual line for the TLD itself goes to zero. So does the exposure to a change in that line, since a fee that does not exist cannot be raised at the next term. For a finance lead, this turns the TLD from a subscription into something closer to a one-time purchase: the cost of acquiring it is known when it is acquired, and holding it adds no registry charge for the TLD.

What the missing fee leaves exactly where it was

It is easy to hear “no renewal” as “no upkeep”. The two are different, and the table sets out the difference before the sections that follow take the remaining items one at a time.

Key custody takes the place of the expiry risk

The way to lose a DNS domain is to stop paying. The way to lose access to an onchain TLD is to lose the keys of the wallet that holds it, or to let them reach someone who should not have them. The risk has not gone. It has changed shape, and it has moved from the accounts payable team to whoever keeps the keys.

The new shape is harsher in one respect. A lapsed domain usually gives its holder a window to repair the mistake, and a registrar account can be recovered through identity checks and support. A wallet has no help desk. If the only person who knew the recovery phrase leaves, and nothing was written down and stored properly, there is no one to appeal to.

The work of custody is therefore the real upkeep of a TLD: who holds the keys, where the backup is, who else can act if that person is unavailable, and how the arrangement survives a change of staff. A wallet that requires several approvals before anything moves is the usual answer for an organization.

Registry dependence does not shrink

A token in your wallet is yours to hold and to transfer. What the token means, though, depends on the registry that issued it: the rules for issuing names under the TLD, the resolver that turns a name into an address or a website, the tools you use to manage records. Not paying the registry every year does not make you independent of it. It only means the relationship is no longer renewed by invoice.

Resolution is the plainest example. The DNS root knows nothing of an onchain name, so a browser needs added support before it can open one. For a Freename name, that support is found in three places: Bitcoin.com Wallet, MetaMask by way of Freename’s resolver, and desktop browsers running the Freename Web3 extension. The coverage is partial and it changes over time. The page on what works with onchain TLDs follows it.

Names under the TLD follow their own terms

The absence of a renewal fee is a fact about the TLD. Names issued under it are separate records with their own terms, set when they were registered. If you run .yoursector as a namespace and people hold name.yoursector, do not assume that what is true of your TLD is true of every name beneath it. Read the terms that applied to those registrations before you tell a registrant anything about renewal.

The royalty program is the one recurring cost you can choose

There is a second sense in which “nothing to pay” needs a qualification. Freename runs a royalty program through which the holder of a TLD is paid a share of the registration fee each time someone registers a name under it. The registry advertises that share as reaching up to half, and the program has activation conditions and terms that the registry can update.

Taking part is optional, and it is not free. The registry sets an annual cost for participation. So a holder can face two quite different pictures:

• The TLD alone. No annual fee, no royalty income from the program. The TLD is held, and names are issued under it by the holder, who is the only one able to do so.
• The TLD with the program. An annual cost to the registry for participation, and in return a share of registration fees for names registered under the TLD.

Some TLDs were registered under earlier terms in which the program is included for life. A holder of such a TLD has the program without the annual cost. If you are not sure which terms apply to yours, ask the registry. If the TLD is ever sold, whether lifetime terms carry over to the buyer is a point to confirm with the registry before closing, never to assume.

For someone used to DNS renewals, the important difference is what happens when the payment stops. Stop paying a domain renewal and you lose the domain. The program cost is a different kind of payment: holding the TLD does not depend on it, because the TLD carries no renewal fee. What happens to your participation if you stop paying is set by the program’s terms, and the registry is the one to confirm it.

That changes the question a finance lead asks. A renewal is paid because the alternative is losing the name. The program cost is paid only if the expected royalty income justifies it, and that depends on how many names you expect to see registered and at what prices. The subname revenue calculator helps frame that estimate. The royalty applies to registrations, and any estimate of income has to be set against the cost of the program, which the registry sets and which is not included in such an estimate.

How a finance lead budgets for a TLD with no renewal line

A DNS portfolio is budgeted as an operating cost: a count of names multiplied by their fees, plus the registrar’s services. An onchain TLD does not fit that template, and forcing it in produces one of two errors. Either someone adds a notional renewal line out of habit, or the asset gets no line at all and with it no owner.

The more useful approach is to list what the asset really costs to hold and to give each item a home.

Network fees are the charges a blockchain takes for recording a transaction. Where an action on the TLD involves one, the charge arises when you act, not with the passing of time.

Custody is the item most often left out, because it rarely arrives as an invoice. It is still a cost, mostly the time of the people who hold and test the arrangement.

The accounting treatment is for your accountant, and it varies by country and by reporting framework. The point to raise with them is specific to this asset. A DNS domain has a term, which gives a natural period over which to think about its cost. A TLD with no expiry has no such term, so whether it has a finite useful life, and how it is tested for loss of value, are questions that have to be answered on their own terms and cannot be read off a renewal schedule.

Whatever the treatment, give the TLD an entry in the asset register with a named owner, even though the amount against it for renewal is zero.

Holding a TLD for years when nothing is due

No carrying cost, so no forced decision

In the DNS aftermarket, renewal fees act as a slow pressure on holders. A portfolio of names costs money every year, and a holder who cannot place a name eventually asks whether to keep paying for it. That pressure pushes names back into circulation.

A holder of a Freename TLD faces no such pressure on the TLD itself. Time costs nothing at the registry. A holder can wait one year or fifteen without the wait showing up in an account. Three consequences follow.

First, patience is cheap. A holder who believes the TLD will matter more later is not paying to maintain that belief. Nothing about a zero holding cost makes the belief more likely to be right.

Second, an approach to a holder cannot rely on the calendar. A person who wants a TLD and hopes its holder will tire of the carrying cost is reasoning from the wrong market. If the holder is not interested, the passing of time does not change the arithmetic for them.

Third, the fact that a TLD is still held says little about how it is valued. In the DNS, a name renewed for many years shows that someone kept deciding it was worth the fee. A TLD held for the same length of time shows only that nobody moved it. Long holding is weak evidence of conviction.

What still costs something over a long hold

The registry line is zero, but a long hold is not free of cost in a wider sense. The money spent on acquiring the TLD is tied up in it. Custody has to be maintained for as long as the asset is held, through every change of staff and equipment. If the holder takes part in the royalty program on current terms, that cost does recur and is, in effect, the only carrying cost with an invoice.

A holder who intends to hold for a long time should therefore replace the question the renewal used to ask. The renewal asked “is this worth another term?” once a term, by force. Without it, the question has to be put on purpose. A TLD readiness score is one structured way to check the state of the asset, whether or not a sale is in view. If the answer to “would we acquire this again?” has become no, a holder can also request a private valuation and see what a considered exit would look like.

The forgotten TLD when no invoice reminds anyone

A forgotten DNS domain resolves itself, one way or the other. Either the invoice surfaces and someone renews, or the name lapses and leaves the portfolio. Forgetting has an end.

A forgotten onchain TLD has no such end. It remains in the wallet indefinitely.

The good news is that forgetting is not fatal. An organization that acquired .yourbrand for a project that was later shelved still holds it years afterward, provided the keys survived. There is no moment at which inattention alone handed the asset to someone else.

The bad news is that the asset and the knowledge of it can drift apart without any alarm. The ways this happens are ordinary:

• The person who set up the wallet leaves, and the handover covers their projects but not their keys.
• The wallet was created on a device that is later retired, and the recovery phrase was never stored anywhere else.
• An individual holder dies or becomes incapacitated, and the heirs do not know the asset exists or how to reach it.

In each case the public record still shows the TLD against the same wallet. What the record cannot tell an outsider, or the organization itself, is whether anyone can still operate that wallet. A TLD can look held and be unreachable in practice.

A second quiet problem concerns names already issued. If a holder issued pay.yourbrand to a partner, or set records on a name that point to a payment address or a website, those records keep doing what they were set to do after everyone has stopped looking. A payment address that the organization no longer controls, still attached to a name under its TLD, is the kind of thing a renewal review used to catch by accident. Without a review, nothing catches it.

For the holder, then, the absence of a renewal fee changes the nature of the duty. The duty used to be to pay on time. It becomes to know, at any moment, where the asset is and who can act on it.

The yearly review that replaces the renewal date

Since the invoice no longer provides the reminder, set one yourself. Pick a date, put it in the same calendar that holds your DNS renewals if you have one, and treat it as a renewal that costs time and no money. The review below fits in a short meeting for a single TLD.

1. Confirm the recordLook up the TLD on a block explorer and check that the wallet holding it is the one in your asset register.
2. Prove you can still actHave the people who are meant to control the wallet show that they can reach it, and test that the backup can be found and read by the second person named for it.
3. Update the names of the peopleCheck that everyone named as key holder, backup and owner of the asset still works in that role, and replace anyone who does not.
4. Review the names issuedGo through the names under the TLD, who holds each one, and where its records point. Correct any record that leads to an address or a site you no longer control.
5. Decide on the royalty programIf you take part, compare the income from registrations over the period with the annual cost. If you do not, ask whether your plans for the namespace have changed enough to reconsider.
6. Reread the registry termsNote any change in the registry's terms and in where names resolve, and what it means for how you describe the name to others.
7. Ask the renewal question on purposeRecord a plain answer to whether you would acquire this TLD again, and what follows if the answer is no.

Keep the output short: one page, dated, filed with the asset register. The value lies less in any single step than in the fact that a named person looked at the asset once in the period. For an individual holder, it also checks that the instructions left for family or an executor still match reality. Succession rules vary by country, and a lawyer should confirm how a digital asset is handled in an estate where you live.

Where the DNS renewal model serves a holder better

The DNS model has strengths that come precisely from its recurring nature.

A renewal relationship comes with an account, and an account comes with recovery. If a company loses the credentials to its registrar account, there are procedures to prove who it is and regain control. That safety net exists because a contracted service provider stands between the holder and the name. An onchain holder has traded that intermediary for direct control and has taken on the consequences.

A system of expiring names also cleans itself. Names nobody wants return to circulation. A namespace in which nothing expires keeps every abandoned asset in place for good, including the ones whose keys are gone. For someone looking for a particular TLD, that means an unreachable holder is a permanent obstacle, with no drop date to wait for.

Finally, DNS names resolve everywhere without any action by the user, which no onchain name can claim. Paying nothing per year for an onchain TLD is not a like-for-like saving against a DNS domain, because the two do different things. The glossary sets out the terms if the distinction between a registry, a registrar and a resolver is new to you.

None of this argues against holding an onchain TLD. It argues for knowing which protections you gave up when the invoice stopped coming, so that you can rebuild the ones you need.

A next step for holders: write the holding note

If you hold a TLD and have never written down how it is held, do that before anything else. One page is enough, and it should answer six points in plain words: the TLD and the registry it is recorded on; the wallet that holds it; who can operate that wallet and who is the backup; whether the royalty program is active and on which terms; which names have been issued and to whom; and the date of the next review.

Give the page to the person who would have to act if you could not. For an organization, that means the asset register and the security team. For an individual, it means whoever would settle your affairs, with the keys themselves stored separately from the description.

Then decide what the asset is for. A TLD that costs nothing to keep can sit idle indefinitely, and idleness is a choice like any other. Some holders build a namespace under it, some keep it as a defensive position for a brand, and some conclude at the first honest review that it would be better placed with someone else. Hush Partners works with holders at that last point: one partner follows the file under a mutual NDA, and the transfer closes through onchain escrow. The page for TLD holders describes how that works, and the contact form is the way to reach the desk. Whichever course you take, the holding note comes first, because every one of them starts with being able to show where the asset is and that you can still move it.

Questions people ask

Can a registry introduce a renewal fee later?

A registry sets its own terms and can revise them, so the honest answer is that the terms in force are the ones to read. The fact reported here is that a Freename TLD carries no annual renewal fee. Keep a copy of the terms that applied when you acquired the TLD, and reread the current ones at each yearly review.

Does a buyer of a TLD inherit the absence of a renewal fee?

The absence of a renewal fee is a feature of the TLD on that registry and does not depend on who holds it. What can differ between seller and buyer is the royalty program: if the seller held it under earlier lifetime terms, whether those terms pass to the buyer has to be confirmed with the registry before closing.

If nothing expires, how do I give up a TLD I no longer want?

You do not need to do anything for the registry’s sake, since no fee accrues. Leaving the TLD in a wallet you still control keeps your options open at no cost. If you want it out of your hands, the routes are a transfer to another party or a sale, and it is worth taking advice before choosing an irreversible one.