Setting a ceiling for the acquisition of an onchain TLD
There is no price list. How an organization reasons its way to a maximum it can defend internally, without anchoring on the seller.
A seller of an onchain TLD will name a price. That price reflects what the seller wants, not what the asset is worth to you. Before any conversation begins, you need a number of your own: a maximum you can defend to finance, to legal, and to the board, built entirely from your own situation. Without it, the seller’s opening figure becomes the anchor, and every negotiation from that point forward moves on the seller’s terms.
This article sets out a structured method for building that ceiling. It covers the sources of value you can quantify, the alternatives you would pursue if the acquisition failed, what waiting costs you, and how to turn a range of value into a single defensible number. It also covers who should hold that number and what to do when talks develop and new information arrives.
The method does not require a comparable sale. It does not require a market index. It requires honest answers to questions your organization can answer about itself.
Application count as reported by the trade press; expected evaluation fee from ICANN's new gTLD program pages; renewal fee from the Freename registry's terms.
Why comparables do not help
In real estate or equity transactions, comparables discipline both sides. A buyer can point to five transactions in the same street, the same sector, the same period, and argue from them. Onchain TLDs do not have that market. Transactions are private. Terms are not published. The registries that record ownership make the fact of a transfer visible on a block explorer, but the price is not part of the onchain record. There is no index, no clearing price, no assessed value.
Even if prices were published, comparables would mislead. The value of .yourbrand to your organization is not the value of .yourbrand to the previous holder or to a hypothetical third party. It is specific to your exposure, your planned uses, your alternatives, and the cost of your time. A comparable sale at a lower number would anchor you low; a comparable sale at a higher number would anchor you high. Neither reflects your situation.
The correct approach is to set aside what others have paid and ask only what the asset is worth to you. That question has a structured answer, and the sections below walk through it.
Value from protection: quantifying the exposure you remove
The first source of value is defensive. An onchain TLD that matches your brand or a key product name, held by a third party, creates a surface for misuse. On the Freename registry, issuing names under a TLD is reserved to whoever holds it, so the decision about which names exist under your brand’s string sits with someone else. Those names can receive payments, resolve in wallets that support them, identify AI agents, or point to content. A customer who meets one of them has no simple way to know that the TLD is not operated by you. The Namespace Exposure Score scores how exposed a brand is onchain; the output gives you a starting point for the protection value calculation.
To translate exposure into a number, ask three questions. First, what is the annual cost of monitoring and enforcement if you do not acquire? The UDRP is the dispute policy that lets a trademark owner challenge a bad-faith registration in the DNS through an expedited procedure. It binds registrants through the contracts that ICANN-accredited registrars use, and an onchain name is issued outside that system, so the policy does not reach it. What remains is ordinary trademark law, applied to whoever uses the name, in whichever country that use occurs. How well that works varies by country and by facts, and your own counsel decides what is realistic. For the ceiling, you only need the estimate: the annual cost of monitoring, advisory work, and the actions you would expect to take.
Second, what is the realistic cost of a brand-confusion event? Consider a fictional mid-sized manufacturer whose product brand resolves in a wallet under a TLD it does not control. If a customer sent a payment to a name under that TLD believing it belonged to the manufacturer, the response would involve customer service, communications, legal review, and management time. Your organization’s own records of past incidents, of any kind, are the right input here. Do not borrow a figure from a vendor report or a headline.
Third, how many years does the exposure last if you do not act? The answer is open-ended. A Freename TLD carries no annual renewal fee, so the holder faces no recurring cost that would lead the TLD to lapse, and has no obligation to sell or to stop issuing names. An exposure with no end date is worth more to remove than a temporary one. Multiply the annual monitoring cost by a horizon your finance team accepts and add a probability-weighted estimate of the event cost. That sum is the floor of your whole valuation: the amount the acquisition is worth even if you never use the TLD.
Value from use: what your organization would actually do
The second source of value is operational. An acquired TLD is not simply a defensive asset; it is infrastructure you can activate. The question is what you would realistically do with it in the first three years after transfer, and what that use is worth.
The capabilities of onchain TLDs that are live include payments to a name, names that resolve in wallets, websites published to IPFS (a network that stores files by their content), and identities for AI agents. Coverage is partial: onchain names sit outside the ICANN DNS root, and an ordinary browser does not open them without added support. Count only the uses that work in the software your customers and counterparties already have. Then consider which of the following apply.
Payment routing: names such as pay.yourbrand or treasury.yourbrand can replace wallet addresses for incoming payments. A readable name is harder to mistype than a long string of characters, and easier to recognize in a record, which has a value in finance and treasury work. Estimate the annual volume of wallet-based transactions you handle or plan to handle, and the cost of a single routing error or reconciliation failure.
Customer-facing names: your organization may plan to issue names to customers, partners, or internal users under the TLD. Each registration of such a name pays a fee, and under the royalty program that Freename operates, part of that fee goes to the holder of the TLD, which after the acquisition would be you. The registry advertises that part at up to half, and its current terms and activation conditions apply, so read them before you model anything. Use the Subname Revenue Calculator to build a conservative projection with stated assumptions. Treat that projection as a component of use value, not as the primary driver of the ceiling.
AI agent identity: if your organization operates or plans to operate AI agents in customer-facing or cross-organizational workflows, names under a TLD you hold can only have been issued by you, which is not true of names under a TLD held by someone else. How naming registries connect to the emerging standards for agent identity is still evolving, so this value is hard to quantify. It belongs in a qualitative section of your internal memo, not in the arithmetic.
Build the use value as a three-year net present value (the sum of future amounts, each reduced to reflect how far away it is), using a discount rate your finance team accepts. State every assumption. Here is a worked example with invented figures. Assume an organization registers 500 names in year one, each producing a royalty of one monetary unit, and 200 additional names in each of years two and three at the same royalty. Assume year one is counted at face value and each later year is divided by a factor of 1.10 per year of delay. The three-year royalty value is 500 + (200 / 1.10) + (200 / 1.21), which equals 500 + 182 + 165, or 847 monetary units, against 900 undiscounted. These figures are gross: a Freename TLD has no annual renewal fee, but taking part in the royalty program carries an annual cost set by the registry, which is not included here and must be deducted for each year of the model. If the seller’s TLD was registered under earlier terms that include the program for life, confirm with the registry before closing whether those terms pass to you. Replace the unit and the volumes with your own. The point is the structure, not the numbers: use the same model throughout, and do not revise the assumptions upward mid-process.
Sources of value: the questions to ask
The table below names each source of value and the question that draws out an honest answer. The goal is not to add all four rows into a single figure immediately. It is to make sure that each source is addressed before the ceiling is set.
| Source | What you are measuring | Key question |
|---|---|---|
| Protection | Cost of monitoring and enforcement if you do not acquire | What does the annual exposure management program cost, and what is a realistic incident cost? |
| Use: payments and names | Revenue and operational savings from activated uses | What is the three-year NPV of royalties and error-cost savings at conservative assumptions? |
| Use: identity and agents | Organizational value of a controlled namespace for agents and internal users | Which planned AI or identity programs require a verifiable named namespace? |
| Option value | Value of capabilities you do not plan to use now but may need | What would you pay to keep open a use you cannot yet commit to? |
The fourth row deserves a word, because it is the one finance teams distrust most, and with reason. Option value is what you would pay to keep a possibility open: a product line that may need names, a payment flow that is not yet approved, an agent program still in pilot. It is real, but it is also the row where enthusiasm hides. A workable rule is to admit an option only when a named person inside the organization owns the plan it depends on, and to cap the whole row at a fraction of the two use rows that you fix before you estimate it. An option nobody owns is worth nothing in the ceiling.
The alternatives and their cost
No ceiling analysis is complete without pricing the alternatives. The ceiling is the lesser of what the asset is worth to you and what the best alternative costs. If an alternative exists that achieves substantially the same outcome for less, that alternative sets an upper constraint.
For an organization that wants its own namespace, the most visible alternative is an ICANN dotBrand: a TLD delegated in the DNS and operated by the trademark owner for its own use. The comparison between a dotBrand and an onchain TLD covers the differences in detail. The two are not close substitutes. A dotBrand resolves in every ordinary browser and mail system, which an onchain TLD does not, and for a public website the DNS is simply better. A dotBrand does nothing, however, about a matching onchain TLD held by someone else. Price the ICANN route as an alternative only for the uses it can actually serve.
Where it is relevant, its cost is large and its calendar is not yours. ICANN opened an application round for new generic TLDs in 2026, the first in more than a decade, and the window closed on August 12, 2026. ICANN’s new gTLD program pages give an expected evaluation fee of USD 227,000 per application. That figure excludes legal and technical advisers and the cost of running a registry after delegation. The trade press reported 1,616 applications going forward. An organization that did not apply in that window must wait for a later round before the route is open to it again.
The ICANN route also takes time. An application passes through evaluation, possible objections or contention with competing applicants, contracting, and delegation before a single name can be used. The transfer of an onchain TLD is one transaction once the parties agree. If your exposure already exists and your use cases are ready, the time the ICANN route takes is itself an item of cost.
Other alternatives include operating under a shared sector TLD, accepting the exposure without action, or pursuing a legal enforcement strategy. Each has its own cost. Operating under a sector TLD held by someone else means you do not control issuance; the holder decides who receives a name next to yours. Accepting the exposure has the cost structure described in the protection section above. Legal enforcement without holding the TLD depends on the country and the facts, and its cost recurs for as long as the exposure does.
In your ceiling analysis, list each realistic alternative, state what it achieves relative to the acquisition, and note the cost. Where the acquisition achieves meaningfully more than the best alternative, the surplus belongs in your valuation. Where the alternative is a close substitute, it sets a hard upper constraint.
The cost of waiting
A ceiling is set at one moment, and the inputs behind it move. Waiting is itself a decision with a cost, and that cost belongs in the analysis like any other. It should be estimated, not assumed, and it is never a reason to hurry a decision.
The cost of waiting has three components. First, the exposure continues. Every month without the TLD is a month during which its holder can issue names under it. If names are being issued, the number outstanding grows, and whatever you plan to do after an acquisition becomes more complex.
Second, the holder’s position can change. A holder may receive other interest, may decide to operate the TLD, or may simply stop considering offers. Nothing obliges a holder to remain available, and a token can stay in a wallet indefinitely. The price may also move in either direction. Do not assume that waiting makes an acquisition cheaper, and do not assume the opposite; treat both as scenarios with a probability attached.
Third, your own alternatives can narrow. An alternative that depends on a window, as the ICANN route does, stops constraining the ceiling once the window has closed without an application from you. The acquisition is then compared against fewer options, and the constraint that the closed alternative placed on your ceiling falls away. Record that change in the analysis when it happens, with its date and its reason.
To quantify the cost of waiting, take the annual cost of exposure management for the period of delay, add the use value that would have been earned during that period under your own model, and add a probability-weighted estimate of any change in price. Using the worked example above, a one-year delay moves every royalty one year further out: the 847 units become 847 / 1.10, or 770, a difference of 77 units before the exposure cost of that year is added. The figure may be small. If it is, say so in the memo; a small waiting cost is a legitimate finding and supports a patient approach.
From a range of value to a single ceiling
By this point, your analysis has produced a range: a floor from protection value alone, a midpoint that adds conservative use value, and an upper bound that includes option value and the cost of waiting. The ceiling is not the upper bound of that range. It is the point at which you would genuinely stop.
The ceiling must pass two tests. First, the finance test: can you explain to a finance committee why a payment up to this amount is justified by specific, stated items of value? Each item should have a method, an assumption set, and a stated confidence level. It is a structured argument from identifiable items of value, and it should read that way. Second, the sanity test: if you paid the ceiling and the TLD turned out to generate only its protection value, with no use-case revenue and no option value realized, would the organization regret the payment? If the answer is yes, the ceiling is too high.
One practical discipline: express the ceiling as a range rather than a point, with a hard stop at the top of the range. The range gives negotiators room to move without exceeding the mandate. The hard stop is communicated once to the people who need to know it, and not again. It is not put in writing where it can be forwarded.
Keep the ceiling for the price of the TLD separate from the cost of advice. Where a desk is mandated to find and approach the holder, its fee is a fixed amount, not a share of the price, and it is paid by the organization that gives the mandate. A fee that does not rise with the price leaves the adviser with no interest in a higher number, and it lets finance approve two distinct lines: one for the asset and one for the work of acquiring it.
- Protection valueEstimate the annual cost of monitoring and enforcement without the acquisition, multiply by a reasonable horizon, and add a probability-weighted incident cost. This is the floor of the range.
- Use valueBuild a three-year NPV of payments, royalties, and operational savings at conservative, stated assumptions. Add qualitative value from identity and agent uses where applicable.
- Alternative costPrice each realistic alternative. Where the acquisition achieves more than the best alternative, the surplus is additive to the ceiling. Where the alternative is a close substitute, it sets a constraint.
- Cost of waitingEstimate the exposure cost during the delay, the use value forgone, and a probability-weighted change in price. Add this to the midpoint of your range to arrive at the upper bound.
- CeilingSet the ceiling below the upper bound, at the point that passes both the finance test and the sanity test. Express it as a narrow range with a hard stop. Communicate it only to those who need it.
Who knows the ceiling
This is a governance question, and it is easy to get wrong. The ceiling is sensitive information. If the seller or the seller’s adviser learns it, it becomes the floor of the negotiation. If too many people inside your organization know it, it will leak.
In practice, the ceiling should be held by three people at most: the executive who will authorize the payment, the in-house counsel or strategy lead who is managing the file, and the external adviser conducting the approach. The negotiator needs to know the ceiling to know when to stop; they do not need to communicate it to the seller at any stage.
Where the approach is made under a buy-side mandate, in which an organization mandates a desk to find and approach a holder, the circle stays small by construction. At Hush Partners, a single named partner stays with the file from the first note through to closing, and a standard mutual NDA applies to every exchange. That structure limits the number of people who hold sensitive information.
What the negotiator does communicate to the seller is willingness to proceed seriously and the parameters of a deal that would work: structure, timeline, and closing through escrow. The ceiling is never one of those parameters. If a seller asks directly what your maximum is, the answer is that you are working from your own valuation and that the conversation will show whether the parties are in range.
Revising the ceiling during talks
A ceiling set before talks begin is not permanent. New information arrives during the process, and a rigorous method requires that you update the ceiling when the inputs change, not when the pressure is highest.
Legitimate reasons to revise the ceiling upward include: discovery of additional use cases you had not previously modeled; loss of an alternative (for example, an application window that closes); and independent confirmation that names are being issued under the TLD at a rate that makes the exposure larger than you estimated. Each of these changes one of the inputs to the valuation. Revise the relevant input, rerun the calculation, and document the revision with its rationale.
Illegitimate reasons to revise upward include: emotional attachment to completing the deal; pressure from a timeline that feels artificial; and the appearance of a competing bidder whose interest has not been independently verified. These are negotiating dynamics, not valuation inputs. Your ceiling should not move because a seller implies urgency or hints at another offer. If the competing interest is real, it will become apparent; if it is not, paying above your ceiling would have been a mistake regardless.
Revisions should be made by the same small group that set the original ceiling, using the same method. A revision made under pressure, without updating the input model, is not a revision. It is giving way. The test is simple: can you explain the new ceiling to your finance committee with the same structure you used for the first one?
When talks break down, the ceiling survives. An asset that was worth acquiring at a certain value does not become worth less because a negotiation failed, and it does not become worth more because you were disappointed. Circumstances change on both sides. Holding the ceiling steady, and keeping the file that supports it, means you are ready to resume if the conversation reopens, without rebuilding the analysis from scratch.
The next step for your organization
If your organization has not yet conducted a formal ceiling analysis for a TLD it wants to acquire, the starting point is the exposure side: run the Namespace Exposure Score for the name in question, and separately ask your trademark counsel which enforcement options are realistic for onchain names in the countries that matter to you. Those two inputs establish the protection value floor, which is always the most defensible component of the ceiling.
Once you have a draft range, compare your method with how a TLD valuation is built. A valuation looks at the asset; your ceiling looks at your organization. The two should be able to sit side by side without contradiction, and where they diverge, the reason should be something specific to you that you can name.
If the approach to a holder has not yet begun, Hush Partners acts for organizations that mandate it to find and approach a holder, including through brand namespace recovery where the TLD matches your brand. The ceiling stays with you and the partner on the file. Closing, when the parties reach agreement, runs through onchain escrow and transfer on an aftermarket, and post-transfer activation covers putting the TLD to work afterward.
The desk is reached through the contact form on the site, and only that way. Bring the range, not the hard stop, to the first conversation.
Questions people ask
Does the method change if the TLD is a sector word rather than a brand name?
Yes, in one important respect. A sector TLD, such as .yoursector, has a different protection profile: the exposure is not brand confusion in the same direct sense, but the loss of namespace control in a sector you operate in is still a real cost. The use-value side of the analysis expands, because a sector TLD can support issuance to customers, partners, or community members in ways that a brand TLD typically does not. The royalty projection and the subname revenue model therefore carry more weight in the ceiling for a sector TLD. The method is the same; the relative weight of each component shifts.
Should the ceiling include the cost of activating the TLD after transfer?
Activation costs belong in the broader business case, but they affect the ceiling only if you have a hard budget that covers both acquisition and activation together. If the budget is unified, subtract a realistic activation estimate before setting the acquisition ceiling. If the budgets are separate, leave activation out of the ceiling calculation; conflating them produces a number that is difficult to defend to a finance committee. The free Launch Roadmap tool on the site helps scope the activation work before the acquisition closes.
What if the holder does not respond to an initial approach?
No response is information. It may mean the holder is not monitoring their wallet, that they have no interest in selling at any price, or that they are waiting to see whether interest is serious. A second note after a reasonable interval is appropriate; repeated contact is pressure, and it is not how a serious buyer behaves. If the holder remains unresponsive over a reasonable period, the ceiling analysis remains valid; the cost of waiting keeps accruing under your own model, and the organization should consider whether one of the alternatives it priced, such as monitoring and enforcement, or the ICANN route in a later round for the uses it serves, should move up the priority list. Your ceiling does not require a willing seller to be worth building; it tells you how hard to pursue one.
