# Selling a short or acronym TLD: who buys it and how it runs > For holders of a very short TLD or an acronym: the logical buyers, the argument that works, and what sets this sale apart. Source: https://hush.partners/selling-short-or-acronym-tld Category: Selling Published by Hush Partners. --- A two- or three-letter TLD, or one that spells an acronym familiar in a particular industry, sits at an odd junction. The string is scarce by definition, which makes it easy to overestimate. It is also legible to many different parties, which makes it easy to approach the wrong ones first. A holder who starts without a clear framework can use up, in a few careless notes, the goodwill of the very organizations that had the best reason to listen. This article lays out what makes the short or acronym TLD a distinct category, who the realistic buyers are, what argument persuades them and which one reliably does not, and what you should have in order before approaching anyone. The general mechanics of a sale (mandate, valuation, outreach, escrow, transfer) are covered on the page that explains [how a file runs](/how-it-works) and are mentioned here only where they interact with what is specific to this type of asset. ## What a short or acronym TLD is, and how it differs from a trademark TLD A TLD is "very short" for the purposes of this article when its string is two or three characters, including combinations of letters and digits. An acronym TLD is a string of a few letters that spells the initials of a phrase, a profession, an institution or an industry, rather than a word in its own right. Throughout this article the example is written `.yoursector`: read it as a compact set of initials that people in one field use every day. The distinction that matters most is between an acronym TLD and a [trademark TLD](/trademark-tlds). A trademark TLD matches one organization's mark closely enough that the organization is the obvious, and often the only, party with a reason to acquire it. With a single plausible buyer, the sale looks like a private conversation about one identifier, and the process, the argument and the timeline follow from that. An acronym TLD is different because the same letters are used, informally, by many parties. The letters that stand for a professional body in one country can also stand for an industry association in another, a public program in a third and several mid-sized companies elsewhere. Several of them may feel a strong contextual interest in the string, and some may hold trademark rights in the letters for their own goods or services. Onchain TLDs exist outside the ICANN DNS root, so the UDRP, the dispute procedure that binds registrants of ICANN domain names through their registration agreements, was not written for them. Trademark law itself still applies wherever it applies, it varies by country, and your own counsel decides what it means for your string. That multiplicity of interested parties is the central fact of this type of TLD, and it shapes everything that follows. A two-letter string that carries no acronym meaning is a purer case of the same thing: it is short, it is scarce, and its meaning is supplied by whoever uses it. ## The candidate list is wide, and that changes the negotiation The first instinct of a holder with an acronym TLD is usually to build a list of every organization whose initials match the string. The instinct is right. The conclusion drawn from it is often wrong. A wide list of candidates means more possible buyers, which sounds like an advantage. In practice, it also means that each candidate's attachment to the string is diluted. An organization that knows its initials are shared with many others does not experience the letters as its own. It uses them in a context, next to a full name, a logo or a sector. Take the context away and the letters point in many directions at once. The negotiation therefore turns less on identity and more on use: what the buyer intends to do with the TLD and why the acquisition earns a place among its projects. This is the opposite of the trademark TLD situation. There, the argument is about fit: the string and the organization's name are the same thing, and the TLD extends an identity the organization already manages. For an acronym TLD, that argument fails immediately, because the buyer knows the letters are shared. The framing that works looks forward: what can this TLD enable for this specific organization, with its members, customers or systems? ### More candidates do not add up to a stronger position It is tempting to treat the length of the candidate list as a measure of demand. It is not. A list of matching initials measures coincidence, and coincidence is not intent. Most organizations on the list have never considered an onchain TLD and have no project that would use one. A few have a team, a budget line or a product that makes the string useful to them. Your real market is that small group, and the work of the sale is to find it by studying what each candidate does, not by counting how many candidates there are. The same reasoning applies to the claim each candidate could make. In a trademark TLD sale, the buyer's link to the string does much of the persuading. Here it does very little, for any of them. You should expect to carry the argument yourself, with a use case, in every conversation. ## Scarcity is an argument, not a price On the registry, each TLD exists once. It is recorded onchain as a token held in a wallet, the record is public, and anyone can check it on a block explorer. No second copy of the same string can be created on that registry. That is genuine scarcity, and it is worth stating. The mistake is to lead with scarcity as if it were self-evidently valuable. An experienced reader on the buyer's side, whether general counsel, a brand director or a technology lead, will ask at once: scarce for whom? If the acronym matches many organizations and the buyer's own use of the letters is narrow, the scarcity argument proves only that no second copy exists. It does not prove that this buyer needs the one that does. The same reader will also note the limits of the technology. Onchain names resolve outside the ICANN DNS root, so an ordinary browser does not open them without support: a compatible wallet, a resolver or a browser extension. Coverage is partial and it changes. For any use that depends on every member of the public reaching an address from any browser, the DNS is simply the better tool, and saying so early costs you nothing with a serious buyer. Scarcity lands well when it is combined with a concrete use: the string is unique, and here is what it enables for your organization, for example a payment handle such as `pay.yoursector` or a member identity such as `name.yoursector`, in a namespace where only the holder of the TLD can issue names. Scarcity alone reads as speculation. Scarcity attached to a use is the beginning of a business case. ### Why a short string without a meaning still needs a use A two-letter TLD that does not spell anything faces a version of the same challenge. The string's brevity is its appeal, but brevity without a purpose leaves the buyer asking what the acquisition would change for them. An operator running a market namespace, meaning a TLD under which names are issued to the public, finds a short TLD useful because every name issued under it is short too. A name of a few characters followed by two or three more is compact, easy to read aloud and easy to type into the wallets and applications that support onchain names. For a [namespace operator](/operators), brevity improves every name the namespace will ever issue, which is why this type of buyer can reason about a string that means nothing at all. A company or an institution sees it differently. For them, brevity helps only if the string connects to something the public already associates with them, such as a long-used abbreviation of their own name or of a product. With that connection, the TLD extends an identity that customers recognize. Without it, the TLD is a short string attached to nothing, and the conversation stalls. This difference between operator logic and corporate logic decides which type of buyer to approach first for any given short TLD. A meaningless two-letter string points to operators. A set of initials with a settled meaning in one field points to the bodies and companies of that field. ## The five buyer types and how they move The table below covers the main categories of buyer for a short or acronym TLD. The categories overlap: a trade body is sometimes also an operator, and a company sometimes asks an adviser to act for it. Pace is described in relative terms only, because it depends on each organization's own decision process. | Buyer type | Primary motive | What the argument needs | Pace | |---|---|---|---| | Company or institution with matching initials | A namespace for names it already uses | A specific use and a clear fit with its identity | Slowest: several teams sign off | | Trade or professional body | Names issued to members | Usefulness to members and a fit with its governance | Slow: committees and boards | | Namespace operator | Names issued to the public | A short string and sound namespace economics | Fastest: a commercial decision | | Fund or family office | A long-held digital asset | Scarcity, clean records, a realistic view of resale | Moderate: depends on its mandate | | Technology platform or protocol | An identity for a product or its users | A fit with the product and with what resolves | Moderate: follows the product plan | The first two rows are where acronym TLDs usually find their buyer, and they are also the slowest. The operator row is where a meaningless short string usually finds its buyer, and it is the quickest. Knowing which row your string belongs to tells you both whom to approach and how much patience the sale will ask of you. ## Avoiding the trap of contacting every match Because the search for matching initials returns a long list, the temptation is to send a note to every organization on it. This approach almost always damages the sale. Each organization you contact learns that the TLD is being offered. Some will do nothing. Some will pass the note to their counsel, who will read it with caution, as counsel should. A few will mention it to peers in their sector, because organizations that share initials often know of each other. By the time you reach the candidate with the best reason to buy, it may already have heard about the TLD second-hand, in terms you did not choose and cannot correct. A broad mailing also changes what the note says about you. A message that could have been sent to anyone with the right initials shows that you have not studied the recipient. A team that receives such a note has no reason to answer it, and a legal department may read it as an attempt to trade on its organization's name. That reading is very hard to undo later, even with a better message. ### Ranking the candidates before any note is sent The alternative is sequenced outreach, and it starts with a ranking. Three questions do most of the work. First, how central are the letters to the candidate? An organization known to its public mainly by its initials is a stronger candidate than one that uses them only in internal documents. Second, does the candidate already do something a namespace would serve? A body that issues membership numbers, a company that pays a network of partners and a platform that gives each user a handle all have a ready use for names under a TLD. An organization with no such activity would have to invent a project before it could justify the purchase. Third, can the candidate decide? An organization with a digital team and a history of adopting new tools can evaluate the proposal. One without them may like the idea and still be unable to act on it. Approach the highest-ranked candidate alone and allow a real period for an answer. If it declines, you have lost nothing, and its reasons will often improve the next note. Sequencing is not a tactic for making anyone feel hurried. Its purpose is the reverse: each party gets a considered, individual proposal and the time to assess it. Where a holder prefers not to run this work alone, a [sell-side mandate](/sell-side-mandates) places it with a desk that finds and approaches buyers on the holder's behalf. ## The use case works, and three arguments backfire with shared initials The argument that works is specific. It begins with what the buyer already does, such as registering members, paying counterparties, publishing a directory or running automated services, and shows how names under the TLD would serve that activity. It names a concrete function: `name.yoursector` as the identity of a member, `pay.yoursector` as a payment handle in the wallets that support onchain names. It states plainly what resolves and where, and what does not. The shorter and more familiar the string, the easier the case is to make, because the buyer's own public already reads the letters without explanation. Three arguments backfire, each for a different reason. The first is the investment thesis presented to a buyer who does not hold assets for return. Telling general counsel or a brand team that the TLD is scarce and may be worth more later gives them nothing they can take to a budget holder. Their job is to reduce risk and support operations. The investment framing also shows that you have not thought about their situation, which lowers their confidence in everything else you say. It belongs only in a conversation with a fund or a family office, and even there it needs clean records and a realistic account of how such an asset can be resold. The second is the claim of identity: these are your letters. With a trademark TLD that statement is simply true. With an acronym it is not, the buyer knows it, and overstating the link invites the reply that many others share it. The third is any reference to other organizations that might acquire the string. It is the argument holders reach for most readily with an acronym TLD, precisely because the list of matches is long, and it is the one to leave out entirely. It tells the recipient nothing about what the TLD would do for it. It reads as pressure, and an organization under pressure sends the file to its lawyers and stops talking. It also casts doubt on your motives in a way that follows you into every later conversation. The proposal should stand on the use it describes. If the use is not enough for this buyer, the right response is to move to the next candidate on your list, not to raise the temperature. The right order is short: what the TLD enables for this organization, why the string fits what it already does, and what you can show about the state of the asset. Then stop, and let the reader think. ## What weakens the asset before a sale Several conditions reduce what a short or acronym TLD can achieve in a sale, and some of them are within your control. The first is an entirely unused TLD. A buyer checking the asset will look at the public record. A TLD under which no name has ever been issued invites the question of whether the namespace works in practice. A modest demonstration answers it: a few names issued for your own purposes and a test of resolution in a wallet that supports them. The names you issue matter as much as their number. Names that imitate an organization on your candidate list are the surest way to end the conversation with that organization before it starts, and they should never be issued. The second is public over-promotion. A TLD that has been offered widely in public, discussed in open forums and attached to speculative price claims arrives in a negotiation already framed. The buyer has formed a view from what it has seen, and a legal team that finds loud promotion around a string resembling its initials will be wary of the whole subject. A quiet, direct approach to a short list of well-chosen candidates suits this type of asset far better. The third is a history that is hard to follow. The record of the TLD is public, so a buyer's counsel will compare your account with what the block explorer shows. Transfers between wallets that you cannot explain, or a stated history that does not match the record, lead to more questions and sometimes to a withdrawal. The [TLD Readiness Score](/tld-readiness-score), a free tool on this site that scores how ready a TLD is to be sold, is a reasonable first check before any outreach. The fourth is an open disagreement. If one of the organizations whose initials match the TLD has already written to you about the string, or objected to it publicly, that exchange will surface when a buyer reviews the file. It needs a clear explanation, and it is a point on which your own counsel should advise before you approach anyone, because trademark rules differ from one country to another. ## How long a sale of this type takes and what sets the pace No honest article can give you a number of weeks or months. What can be described is what sets the pace, and for this type of TLD nearly all of it sits on the buyer's side. The quicker sales involve a namespace operator or a technology platform, where a commercial team controls the decision and already understands what a TLD is. The discussion goes straight to the string, the economics of issuing names and the terms. The slower ones involve a company, an institution or a membership body. Legal, brand, technology and finance may each need to review the proposal, and a body governed by a board or a committee decides on that body's calendar, not yours. When the TLD would be the first onchain asset the organization holds, its teams also have to settle questions they have never faced: who controls the wallet, how the asset is recorded in the accounts, who may issue names. Each question is reasonable, and each takes a review cycle. Acronym TLDs add a delay of their own. Because the letters are shared, a careful buyer will want to understand its position relative to others who use them, and its counsel may take time over that question in more than one country. A trademark TLD rarely raises it. Expect it, and do not read the silence that accompanies it as a refusal. Your side adds time when the asset is not ready: a history that needs explaining, no evidence that the namespace works, or an open disagreement each adds at least one round of questions. Preparation before outreach is the one lever you fully control. At the end of the process, the closing itself takes place in onchain escrow on an aftermarket, as set out on the page about [escrow and transfer](/escrow-and-transfer). ## What to prepare before the first approach The preparation falls into four parts, and all of it should be complete before any candidate is contacted. **The record and its history.** Confirm that the onchain record is in order, that the wallet holding the TLD is under your control, and that you can account for every transfer since the TLD was created. A buyer's counsel will look at the block explorer, and the record should match what you say. **A use brief for each type of buyer.** Not one presentation sent to everyone, but a short document written for the logic of each category. The operator version covers the length of the string and the economics of issuing names. The company version covers identity and the functions that names under the TLD would serve. The membership-body version covers services to members and governance. For an acronym TLD, add one paragraph that states honestly which meanings of the letters you are aware of and why this recipient's use is the one your proposal addresses. That paragraph shows the care a legal reader looks for. **Evidence that the namespace works.** Issue a small number of names for your own use, test them in the wallets and browsers that support them, and write down the result, including what did not resolve. Volume is not the point. The point is to show a functioning namespace and an accurate picture of its limits. The page on [what is live](/whats-live) lists the capabilities that work, with sources, and is a sound reference for this note. **A confidentiality framework.** A substantive exchange about a sale belongs under a mutual NDA from the start, so that neither side's interest becomes known in its sector. In a file handled by Hush Partners, a [standard mutual NDA](/nda) applies to every exchange. With these four parts in place, the first conversation can be about the buyer's use of the string and not about gaps in your file. ## Where to start if you hold one of these TLDs Start with the ranking, on paper, before any contact. Write down the meanings of your string that you know of, sort the candidates by the three questions above, and decide which row of the buyer table your TLD belongs to. If the honest answer is that no candidate has a ready use for it, that is worth knowing early: the work then is to demonstrate a use, or to accept that the natural buyer is an operator. If you want a view on value before you speak to anyone, you can request a [private valuation](/private-valuation) through the form on this site. Hush Partners is a private desk for onchain TLDs, and one of the things it does is act for holders who mandate it to find a buyer. One named partner follows the file from the first note to closing, and the seller of a given TLD is never named. To put a short or acronym TLD before the desk, use the contact form on the site. ## Questions people ask ### Does a short TLD have more value than a longer one? Not automatically. Brevity helps when the buyer reasons about a namespace, because every name issued under a two-letter TLD is shorter than the same name under a longer one, and that matters to operators. For a company or an institution, value comes from the fit between the string and what its public already calls it, not from length alone. A set of initials with a settled meaning in one field can interest a buyer far more than a shorter string that means nothing in its world. ### Can an organization with a matching trademark force a transfer? The UDRP applies to domain names in the ICANN system and has no direct application to a TLD recorded on an onchain registry. That does not settle the question. A trademark owner may have other remedies under the law of a given country, depending on the mark, on how the TLD is used and on what was said when it was offered. This is information and not advice: your own counsel decides, ideally before the first note is sent. ### What happens to the royalty program when the TLD is sold? Freename runs a royalty program that pays the holder of a TLD part of each registration fee for names registered under it. The registry advertises that share at up to half, and the program depends on its current terms and on activation conditions. Holding a Freename TLD involves no annual renewal fee, but taking part in the program has an annual cost that the registry sets, so the buyer of a short string should count it against any income it expects. Some TLDs were registered under earlier terms that include the program for life, and whether such terms follow the TLD to its buyer is to be confirmed with the registry before closing. Because the program is tied to holding the TLD, the parties should check with the registry how it applies after a transfer, and the sale terms should say who receives any amount earned before closing. ### If a buyer asks whether others have been approached, what should you say? The truth. Sequenced outreach makes the truthful answer simple, because at any moment you are in discussion with one party at most. Never suggest that other organizations are interested in order to speed up an answer. Apart from being a form of pressure, it is easy to disprove among organizations that share initials and often know each other. ### Is onchain resolution good enough to support the use-case argument? It depends on the use. Bitcoin.com Wallet supports Freename names, MetaMask does so through Freename's resolver, and on desktop browsers the Freename Web3 extension is required. Outside those environments an ordinary browser does not open an onchain name, and coverage changes over time. A use that lives inside wallets and applications, such as payments to a name or identities for members, can be shown working. A use that requires any member of the public to reach an address from any browser cannot, and a buyer who needs that is better served by the DNS.