# What is a TLD worth? Valuing onchain TLDs > What drives the value of an onchain top-level domain: string quality, logical buyers, cleanliness, sector economics and subname revenue. Source: https://hush.partners/onchain-tld-valuation Category: Selling Published by Hush Partners. --- A holder who wants to sell an onchain TLD faces an immediate problem: there is no published price list, no index, no audited transaction history they can point to and say "mine is worth roughly this." That absence does not mean value is arbitrary. It means value must be reasoned rather than looked up, and the reasoning has a structure that holds across very different kinds of TLDs. This article walks through every driver that enters a serious valuation, explains what moves each one up or down, and is honest about where uncertainty persists even after all the work is done. By the end, you will know how to think about your own TLD before you ask anyone else to think about it for you, and you will understand what a formal [private valuation](/private-valuation) can and cannot deliver. The audience here is the holder and their advisers. Nothing below is financial or legal advice; your own counsel decides how to apply it to your situation. ## Why there is no price list, and why that is not guesswork On Freename, your TLD exists as a token sitting in a wallet, and the record that says so is public: anyone can look it up on a block explorer. What no public record tells you is what a specific buyer would pay for that specific string on a specific day. That gap is not a failure of the market. It is a structural feature of any market where assets are unique and buyers are few. Compare it to commercial real estate. A building has a measurable footprint, a rental income, a location, and a zoning classification. Appraisers use all of that, and they still reach a range, not a number, because the eventual price depends on who shows up and what they need. An onchain TLD is at least as singular. Within a given registry, the string `.yourbrand` exists once. The set of organizations that would rationally pay a material amount for it is finite, sometimes very small, and the holder rarely knows who is in it. The response to thin markets is not to abandon analysis. It is to identify every factor that a rational buyer would weigh, assess each one honestly, and express the result as a range with a stated rationale. That is what a valuation does. It replaces "I think it is worth a lot" with a documented argument that a counterparty can interrogate. ### Why comparables are thin and often misleading Buyers and sellers of conventional assets rely on comparables: earlier transactions in similar assets that set a reference range. For onchain TLDs, comparables are scarce and often misleading, for three reasons. First, much of the market is private. Many transactions close without any public statement of price, and the parties who do disclose are not a random sample. They are more likely to have a reason to speak, whether to signal success or to establish a precedent. A disclosed transaction is not a neutral data point. Second, TLDs are not fungible. The price achieved for one string tells you almost nothing about the price achievable for a different string, even if the two look superficially similar. The buyer pool, the trademark sensitivity, the sector economics, and the namespace cleanliness all differ. Applying a ratio drawn from one transaction to another asset is like valuing a building in one city by reference to a sale in a different city, a different sector, and a different period. Third, a reported price carries the context of its transaction. A trademark TLD acquired by the matching brand owner reflects that owner's specific risk calculus, not a general market price. A TLD acquired by a fund reflects that fund's portfolio thesis and return target. Neither is a reliable guide for a seller with a different asset and a different buyer profile. This does not make comparables useless. A cluster of transactions in broadly similar strings, close together in time and in the same registry, can suggest a rough floor. But the ceiling, which is where the real value discussion happens, is always specific to the asset and the buyer. ### The drivers at a glance With no list to consult, the work moves to the drivers themselves. The table shows what pushes each one in each direction, and the sections that follow take them one at a time. | Driver | Raises value | Lowers value | |---|---|---| | String quality | Short, one word, clear meaning, works as a namespace | Long, hard to spell, awkward names beneath | | Buyer pool | Several motivated buyers, high trademark sensitivity | One marginal buyer, low sector awareness | | Namespace cleanliness | No names issued, clean title, no conflicts | Many names outstanding, disputed terms, competing claims | | Sector economics | Active onchain sector, short adoption distance | Unproven sector, heavy substitution, regulatory pressure | | Subname revenue | High realistic adoption, sustainable price per name | Small addressable community, commodity pricing | | Liquidity position | Patient seller, no timing constraints | Time-pressured sale, restrictive deal structure | | Reference points | Cluster of broadly similar transactions | Unique string, no reference transactions | ## String quality String quality is the first filter. It is not the only factor, but a weak string limits everything else. The questions to ask are simple. Is the string short? Is it easy to spell in the languages of the likely buyer pool? Is it a dictionary word, a category descriptor, a coined term, or a random sequence? Does it carry a clear meaning? Does it work as a namespace, meaning that names issued beneath it read naturally? `pay.yourbrand` works. A string that produces awkward or ambiguous names beneath it will require marketing effort that a buyer will discount. Generic one-word strings tend to attract more potential buyers than coined or multi-word strings, for the same reason that plain dictionary words have long drawn the widest interest among DNS domain names. The logic is not that generic strings are inherently superior. It is that a wider set of buyers can imagine a use for them without much persuasion. A specific, distinctive string can be worth more than a generic one if the right buyer is identified, because exclusivity has its own value to a brand. But that argument depends entirely on finding that buyer. Character count matters somewhat less for a TLD than for a name registered under one, because the names issued beneath the TLD carry most of the display weight. Still, a TLD that is long, hyphenated, or hard to pronounce in the target market shrinks the plausible buyer pool. A last test is whether the string carries associations the buyer would have to manage. A word with a second meaning in another language, or one tied to a sensitive subject, is not worthless, but it narrows who can use it comfortably. A valuation records those associations rather than hoping a buyer will not notice them. ## Trademark TLD or market TLD There are two fundamentally different kinds of onchain TLD, and they are valued differently. A **trademark TLD** is a string that corresponds to a brand name, a product line, a company name, or another mark in active use. The organization that owns or uses that mark is often the only party that can use the TLD without legal and reputational risk. That concentration of demand can support a premium, but it also means there is effectively one logical buyer. If that buyer declines, there may be no second buyer at a comparable price. The page on [trademark TLDs](/trademark-tlds) describes this category in more detail. A **market TLD** is a string that functions as a generic namespace: a category term, a community descriptor, or a coined term with no single owner, such as `.yoursector`. A market TLD can be sold to operators who want to run a namespace business beneath it, to communities, or to funds that treat TLDs as digital assets. The buyer pool is broader, but no single buyer has the specific need that a trademark owner has. The valuation implication is direct. The upper bound for a trademark TLD is set by how much the matching trademark owner values control, how exposed they feel without it, and how capable they are of paying. For a market TLD, both the lower and the upper bound are set by the economics of running a namespace: how many names can realistically be issued, at what price point, and over what horizon. The category also changes what a holder should expect from the conversation. A trademark owner approached about a matching string weighs it as a matter of brand protection, and the holder's conduct is part of what they assess. A trademark protects a sign used in trade, and the rules differ from country to country, so a holder of a trademark TLD should take advice from their own counsel before any approach is made. A string that has been held quietly, with no names issued that trade on the mark, is a simpler file than one that has not. ## The number and quality of logical buyers Value is not an intrinsic property of a string. It is the intersection of what a string offers and who needs it. A rigorous valuation therefore maps the buyer side, not just the asset. For a trademark TLD, mapping is straightforward: identify the organizations that hold or use the mark, consider their size and sector, and infer their capacity to pay and their sensitivity to the risk of not holding the TLD. A large consumer brand in a sector where onchain identity has become operationally relevant has a different risk calculus than a small professional services firm with no blockchain footprint. Where the same word is used as a mark by several unrelated organizations in different sectors or countries, the pool is wider than one, and that changes the range. For a market TLD, the mapping is harder. Logical buyers include organizations wanting to operate a namespace for a community, sector funds, and individual investors who believe the string will appreciate. Each of these buyer types has a different maximum price and a different process for making a purchase decision. An institution usually needs internal approvals, a confidentiality agreement, and a structured process. A fund may move faster but will discount more aggressively for uncertainty. Knowing which type of buyer is reachable, and in what timeframe, shapes the realistic range. Quality matters as much as number. Five parties who could conceivably be interested are worth less to a valuation than two who have a clear use, the means to pay, and someone inside with the authority to decide. A pool counted generously produces a range that no negotiation will confirm. ## Cleanliness of the namespace "Cleanliness" refers to the state of the names already issued under the TLD. If the holder has issued names to third parties, a buyer acquires not just the TLD but the obligations and exposures those names carry. A buyer will want to know how many names are outstanding, on what terms they were issued, whether any of them conflict with trademarks, and whether any could be challenged by a rights holder or an authority. A TLD with no names issued beneath it is structurally clean. A TLD with a large number of names in circulation carries more complexity. That complexity is not necessarily negative, since names in circulation mean the namespace is already in use, but it requires the buyer to conduct diligence on the existing namespace before closing. The holder's own behavior matters here. On Freename, issuing names under a TLD is reserved to its holder, so the state of the namespace is the holder's record and nobody else's. A holder who issued names carefully, with clear terms and no obvious trademark conflicts, will face fewer questions than one who issued names indiscriminately. If the namespace has been kept tight, that fact should be documented and presented to any prospective buyer. If it has not, the holder should understand that a buyer will price the remediation work into their offer. Cleanliness also covers the holder's title. Because the registry record sits on a public chain, a buyer can inspect it without asking for anything. Clean title means the token has been in the holder's wallet without dispute, its history is unambiguous, and there are no competing claims. Any gap in that history will require explanation. ## Sector economics and revenue from names beneath the TLD The sector in which a TLD string sits determines both the pool of buyers and the ceiling on subname revenue. These two things are connected but distinct. ### How the sector shapes demand A TLD in a sector where onchain identity is already operationally useful, such as payments or digital credentials, has a shorter distance to travel before names beneath it generate real demand. A TLD in a sector that has not yet integrated blockchain infrastructure into its workflows requires a buyer to also fund that adoption, which they will discount into the price. Sector concentration matters too. If the logical buyers for a market TLD are all in one sector that is under regulatory pressure, illiquid, or contracting, the buyer pool shrinks and the timeline to a transaction extends. A TLD whose plausible buyers span multiple sectors is more robust. Finally, consider the competitive landscape. A TLD in a crowded generic category, where several similar strings exist onchain and remain available, faces price pressure from substitutes. A TLD that is the most natural string for its category, or the only remaining clean string in it, commands a stronger position. An honest sector analysis also states where the DNS is simply the better tool. Onchain names resolve only in wallets, browsers and applications that support them, and that coverage is partial. A sector whose users expect every name to open in an ordinary browser will adopt slowly, and a valuation that ignores this overstates demand. ### Projecting revenue from names Freename runs a royalty program for TLD holders: each time a name is registered under the TLD, part of the registration fee goes to the holder. The registry advertises that share at up to half, and its terms and activation conditions in force at the time apply. Freename charges no annual renewal fee on the TLD itself. The cost of holding is therefore low, and any revenue comes directly from activity in the namespace. For valuation purposes, the question is how to project that revenue honestly. The [Subname Revenue Calculator](/subname-revenue-calculator) on the site helps with the arithmetic. The harder work is estimating the inputs: how many names are likely to be registered under this TLD, by whom, and at what price per name. A worked example makes the structure visible. The figures are assumptions chosen for round arithmetic, expressed in abstract units, and say nothing about any real TLD or price. Assume a market TLD in an active sector, with an addressable community of 500 organizations or individuals who would want a name under it. Assume a registration fee of 100 units per name, that two in five of the addressable community register in the first two years, and that the holder's share is half, the advertised maximum. That produces 200 names at 100 units each, for a gross registration volume of 20,000 units, of which the holder receives 10,000 units over two years. Whether that figure supports any given asking price depends on the discount the buyer applies and the confidence they have in the adoption assumptions. Change the adoption to one in ten and everything else stays the same: 50 names, 5,000 units of gross volume, and 2,500 units for the holder. The gap between 10,000 and 2,500 comes from a single assumption, which is why the assumptions, not the formula, are where the real negotiation happens. Neither total includes the annual cost of taking part in the royalty program, which the registry sets and which has to be deducted from the holder's units. Some TLDs were registered under earlier terms that include the program for life, and whether those terms pass to a buyer is a question to settle with the registry before closing. The honest position on subname revenue is this: it is a genuine and distinctive feature of the onchain TLD structure, but it is a projection, not a guarantee. A buyer will stress-test the assumptions. A seller who overstates the likely adoption loses credibility across the entire negotiation. ## Liquidity and the holder's own constraints Liquidity is not a property of the TLD. It is a property of the situation. A TLD that would attract several buyers in a patient process may attract none if the holder needs to close quickly, sets strict confidentiality conditions, or insists on a structure that a buyer's legal team will not approve without a long review. The holder's constraints enter the valuation in two ways. First, they affect the achievable price: a time-pressured sale produces a lower price than a patient, structured process. Second, they affect the type of transaction that is viable. An institution buying a trademark TLD for brand protection needs time for internal approvals, even in a straightforward case. A fund may move faster. A holder who cannot match the pace of their most logical buyer will either wait for a faster buyer, who may value the asset less, or accept a discount. A holder who understands this before going to market will make a more realistic estimate of outcome. The page on [how a file moves from mandate to transfer](/how-it-works) sets out the stages, which helps in judging whether your own timetable fits them. There is one constraint the onchain structure removes. With no annual renewal fee on a Freename TLD, holding costs do not push a holder toward a sale. Patience is affordable, and a valuation can treat waiting for the right buyer as a real option rather than a cost to be minimized. The limit on patience is usually the holder's own plans, not the asset. Jurisdiction matters here too. The tax treatment of a sale varies with where the holder is established, the holding structure, and how local law classifies the asset. This is a matter for the holder's own counsel. ## How a private valuation is built A valuation is a structured argument, not a formula. The range it produces has a floor, a midpoint, and a ceiling, each resting on a different set of assumptions. The page on [how a TLD valuation is built](/valuation) describes the service; the sequence below shows the reasoning behind it.
How a TLD valuation is assembled
  1. String assessmentThe string is evaluated for length, memorability, linguistic clarity, usefulness as a namespace, and any existing associations, positive or negative, that a buyer would encounter.
  2. Buyer mappingLogical buyers are identified by type: trademark owners, namespace operators, sector funds, or strategic acquirers. Each type is assessed for capacity, need, and speed of decision.
  3. Namespace reviewThe state of names already issued under the TLD is examined: volume, terms, any potential conflicts, and the clarity of the holder's title on the registry.
  4. Sector and revenue analysisThe sector economics are assessed, and a subname revenue model is built with stated assumptions. Scenarios at low, mid, and high adoption are run, and the sensitivity of the output to each assumption is noted.
  5. Constraint reviewThe holder's timing, jurisdiction, confidentiality needs, and process constraints are documented. These affect which buyers are reachable and on what timeline.
  6. Range constructionThe floor is set by the weakest plausible buyer scenario. The ceiling is set by the strongest, assuming the most motivated buyer and the cleanest process. The midpoint reflects the most likely combination of buyer type and process quality.
  7. Rationale documentationEvery assumption is written down. The output is a document the holder can review with their adviser, not a number without a source.
The value of this process is not that it tells the holder what their TLD is worth. It is that it tells the holder what the TLD is worth *to whom*, *under what conditions*, and *with what degree of confidence*. Those qualifiers are where the real information lives. The order of the steps matters. The string and the buyers come first because they bound everything else: no revenue model rescues a string nobody has a reason to want. The constraints come late because they do not change what the asset is, only which part of the range is reachable for this holder. ## What a valuation cannot tell you A valuation is not a sale. The distance between a reasoned range and an executed transaction is the distance between analysis and a negotiation between two parties with their own information, their own constraints, and their own advisers. A valuation cannot tell you whether a specific buyer will appear, or when. It cannot predict how long the process will take. It cannot account for changes in the holder's circumstances, the buyer's appetite, or the broader market between the valuation and any offer. And it cannot force a buyer to pay the ceiling of the range. A ceiling is a theoretical maximum under the most favorable conditions, not a starting point for negotiation. Nor can it settle legal questions. Whether a string conflicts with someone's trademark, and what follows if it does, depends on facts and on national law. A valuation can flag the exposure and reflect it in the range. Only counsel can assess it. What a valuation can do is give the holder a defensible position. A holder who enters a negotiation knowing their range, their rationale, and their constraints can evaluate an offer against a standard rather than against intuition. They can explain to a buyer why a low offer is low, in terms the buyer can engage with rather than dismiss. ## What to prepare before you request a valuation A valuation is only as good as what the holder brings to it, and most of the preparation can be done alone. Before you ask anyone for a range, assemble the following: - The string, the registry, and the wallet that holds the token, so the public record can be checked. - A complete account of the names issued under the TLD, with the terms on which each was issued, or a plain statement that none exist. - Any contact you have had with an organization whose mark matches the string. - Your own constraints: timing, confidentiality, the structures you can and cannot accept. - Your adoption assumptions for names beneath the TLD, with the reasoning behind each. Working through that list surfaces gaps while they are still cheap to close. If the namespace is not clean, that is better to know before going to market than during a buyer's diligence. If your timing makes the most logical buyer unreachable, adjusting it before starting a process is worth considering. The [TLD Readiness Score](/tld-readiness-score) on the site gives a first reading of how ready a TLD is to be sold. Hush Partners prepares private valuations for [TLD holders](/holders), and the request form linked at the start of this article is where to ask for one. Every exchange with the desk falls under a standard mutual NDA. For a holder who then decides to sell, a [sell-side mandate](/sell-side-mandates) asks the desk to find a buyer. ## Questions people ask ### Does a valuation expire? A valuation reflects the state of the asset and the market when it is built. It does not expire on a fixed schedule, but it should be revisited if the namespace changes materially: if a significant number of names are issued, if the relevant sector shifts, or if the trademark landscape around the string changes. An old valuation that has not been reviewed should be read as indicative only. ### Can I use the valuation in a negotiation without disclosing it? Yes. A valuation is prepared for the holder's own use. The holder decides what to share with a counterparty and what to keep internal. In many negotiations, sharing the fact that a valuation exists, and its broad conclusion, carries more weight than sharing the full document. A counterparty who knows the holder has done the work has less reason to open with an offer they cannot justify. ### What if no buyer offers the floor of the range? Then the floor was set too high, the buyer pool is smaller than estimated, the holder's constraints are more limiting than anticipated, or all three. The right response is to review the assumptions, not to reject the process. Sometimes a careful process confirms that the right buyer does not exist yet, and patience is the correct strategy. ### Is the onchain structure relevant to a buyer's legal team? It is. The TLD is a token in a wallet, and closing runs through onchain escrow. A buyer's legal team will want to understand what rights the token conveys, how the registry governs the namespace, and how the registry's terms treat the royalty program after a transfer. These are diligence questions that a structured process addresses directly. The page on [escrow and transfer](/escrow-and-transfer) covers how closing works. ### How is value different for a TLD that already has names registered under it? A TLD with a record of registrations is no longer purely a projection. The record narrows the range of disagreement: both parties can observe actual registration volume and work from there. The key questions shift to sustainability, meaning whether registrations are likely to continue, grow, or slow, and to the quality of the namespace built under the TLD. A buyer will still discount for uncertainty about future registrations, but an active namespace with a track record is a stronger negotiating position than an unused TLD, provided the namespace is clean.