Selling a geographic TLD: who buys it and how the sale runs

A TLD that names a city, a region or a country sits in a different category from one that names a brand or a sector. The asset is not portable. A buyer cannot substitute it with something adjacent, rebrand around it, or pick a synonym that works just as well. The place is the place, and only one TLD carries its exact name. That quality concentrates both the upside and the difficulty of a sale.

This article is for holders of that kind of TLD on Freename, a registry where a TLD exists as a token sitting in the holder’s wallet, who want to understand where a sale begins, who the realistic buyers are, and what determines whether a conversation leads anywhere. It is one of a series on selling by type of TLD. The general mechanics of running a file are only touched on here where they look different for a place name.

By the end you will be able to identify the two broad categories of buyer for a geographic TLD, construct the argument each needs to hear, avoid the mistake that ends conversations early, and know what sets the pace before you begin.

What makes a geographic TLD its own category

A trademark TLD is, at its core, a defensive instrument. The organization that wants it already owns the underlying mark, and the TLD is an extension of that ownership into a new namespace. The case for acquisition is internal: legal protection, brand consistency, infrastructure control. See what a trademark TLD is for that separate analysis.

A geographic TLD works differently. No organization automatically owns a place name the way a company owns its registered mark. The name of a city or a country belongs, in a meaningful cultural and political sense, to everyone and to no one. That opens the buyer pool wider in one direction, because many parties have an interest, while narrowing it in another, because legitimacy concerns arise that do not apply to a brand name.

The difference shows in the first conversation. With a trademark TLD, there is one obvious counterparty and the discussion starts from its rights. With a place name, nobody arrives with a right to assert, and in most countries a bare place name is hard to protect as a trademark at all, although the rules vary and your own counsel decides how they apply to you. What a buyer brings instead is a mandate: a public remit, a membership, or a business plan tied to the place. Your sale is a search for the party whose mandate fits the name best, and that party may not know yet that the TLD exists.

It also differs from a sector TLD such as .yoursector. A sector word can be bought by any company in that sector, anywhere, and a buyer that loses interest can be replaced by a competitor with the same need. A place has a boundary. The parties with a credible connection to it can usually be counted on a short list, and several of them answer to voters or to members.

The practical consequence: the argument for a geographic TLD almost always has to address governance, stewardship and community benefit, as well as utility and exclusivity. A buyer who ignores that takes on reputational exposure they may not have assessed.

Who has a legitimate interest in a place name

The parties with a credible reason to hold a place-name TLD fall into three clusters: public bodies, local business groups and private operators.

Public bodies include the municipality itself, its economic development agency, its tourism authority, and any publicly funded body whose remit is digital infrastructure or local identity. A city government that controls the onchain version of its own name has something specific. Only the holder of a TLD can issue names under it, so the city decides which residents, local businesses, civic organizations and official services receive one, and the result is a governed namespace that carries civic identity in a way a name under a general-purpose extension does not. The audience page for operators describes what running a TLD as a namespace involves.

Local business groups sit at the edge of the public category. A chamber of commerce, a regional trade association or a destination marketing organization may have both the budget and the mandate to acquire a place-name TLD, particularly if the acquisition can be positioned as infrastructure for member businesses. These bodies often move faster than a government, but they have their own approval processes and their own board-level sensitivities about anything that looks like speculation.

Private operators enter when the public route stalls or when no public body has the capacity or appetite to engage at all. They are covered in their own section below.

The table sets these buyer types side by side. Every file is different, and these are patterns, not certainties.

The sensitivities of geographic names and what the DNS experience suggests

On the ICANN side of the DNS, geographic names have been handled with particular caution. In ICANN’s program for new generic TLDs, an applicant for a string that matched certain place names, such as a country or a capital city, was expected to show the support or the non-objection of the relevant government or public authority. Governments, which advise ICANN through its own structures, have consistently pressed the view that place names should not be allocated without the agreement of the authorities concerned.

That history matters to your buyers. An onchain TLD operates outside the ICANN DNS root and is not subject to ICANN’s rules, so none of those requirements apply to your sale. Experienced buyers know the history all the same, and they apply their own version of the legitimacy test.

The DNS experience is instructive in a second way. When cities and regions obtained place-name TLDs through ICANN, questions followed about who should benefit from registrations, what restrictions should apply, and what should happen when a commercial operator’s interests diverged from the public interest. Those questions were about the place, not about the technology, and they travel with the name into any namespace.

The onchain context removes some frictions, since there is no ICANN application to prepare and no delegation process to wait for, but it does not remove the underlying sensitivity. A buyer acquiring a TLD that names a major city knows they will be asked, sooner or later, by journalists, by local politicians or by the city itself, on what basis they control that name. They need an answer. If you want a buyer to move past initial interest toward a real conversation, you have to help them see that the TLD comes with a governance story they can manage.

The sensitivity rises with the size and prominence of the place. A TLD naming a small municipality carries less political weight than one naming a national capital or a widely recognized destination. A country name is the most delicate case, because the only public body that matches it is a national government, the slowest and most cautious buyer of all. Calibrate your approach accordingly.

Why a public body buys slowly and needs a different file

If your most logical buyer is a municipality, a regional government or a tourism authority, accept from the outset that the timeline will not match a commercial transaction. Public bodies in most jurisdictions cannot bind themselves to an acquisition without a formal approval process. Depending on the amount and the country, that process may involve procurement rules, council or board votes, legal opinions from in-house or external counsel, and sometimes public consultation. None of this is negotiable from your side.

What you can control is the quality of the information you give them. A public body needs a file that answers the questions its lawyers will ask, which are not the questions a commercial buyer would ask. That means:

• A clean registry record, which is public and can be checked on a block explorer
• A clear account of what names, if any, have been issued under the TLD and to whom
• A plain description of what the TLD can do technically, such as website publication, payments to a name and resolution where it is supported, without overstating coverage
• A governance outline: how the namespace could be managed after transfer, what restrictions could apply to registrations, how disputes could be handled

Price needs the same care. An official who recommends the purchase must be able to explain the figure to an auditor or an elected body, so a number that arrives with its reasoning is worth more to them than a number that is merely lower. A private valuation requested before any approach gives you that reasoning in advance, and it lets the early conversation stay on governance and fit.

A public body also has to explain why it is dealing with you in particular. With a place name the answer is simple and true: there is one TLD with that exact name on the registry, and one holder. Put that fact in the file plainly, as a description of the asset. It helps the official justify a direct purchase, where their rules allow one.

The pace is also affected by budget cycles. If your approach lands after the relevant body’s budget has been approved, the earliest realistic closing may fall in the following budget period. Factor that into your expectations before you begin.

Private operators as the alternative buyer

When no public body has the capacity or appetite to engage, private operators are the realistic alternative. Two sub-types exist.

The first is an operator who wants to run the TLD as a namespace business: issuing names under it and building a community of users with a real connection to the place. Freename runs a royalty program that pays the holder of a TLD a share of each registration fee for names registered under it, advertised at up to half and subject to the registry’s current terms and activation conditions. That income is not free of cost: a Freename TLD has no annual renewal fee, but participation in the program carries an annual cost set by the registry, and where a TLD was registered under earlier terms that include the program for life, the operator should confirm with the registry before closing whether those terms pass to a buyer. This buyer needs to see a credible path to adoption. The argument for them is commercial: which businesses, individuals and organizations connected to this place might want a name under this TLD, and what the revenue model looks like. The Subname Revenue Calculator is useful here, because a projection with stated assumptions gives an operator something concrete to assess.

The second sub-type is a portfolio or strategic acquirer: a party that sees the asset as worth owning for its optionality, whether they activate it at once or hold it. These buyers tend to move quickly and impose fewer conditions. The trade-off is price: a buyer without an activation plan prices in the uncertainty of future use in a way that an operator with a clear plan does not.

Private operators do not face the governance pressure that a public body faces, but they are not immune to it. An operator who acquires a prominent place-name TLD and issues names under it carelessly can find themselves in a difficult position if the municipality or government concerned takes an interest. A well-run namespace, with documented policies, transparent criteria for issuing names and a clear dispute process, protects the operator as much as it serves the business.

That is why the choice between the two tracks is less stark than it looks. A local operator who runs the namespace well may later work with the city, or supply names to its services. For some places, the operator is the buyer that makes eventual public use possible, because it carries the cost and the learning that a public body cannot yet justify.

The argument that works for a place name and the one that backfires

The argument that works with both buyer types is a stewardship argument. Exclusivity does not need arguing: a buyer who understands onchain TLDs already knows that one TLD carries the name. What they want to know is whether the asset is clean, whether the transfer is straightforward, and whether the governance story holds.

The stewardship argument covers three things: what the TLD enables technically (payments to a name, website publication, names for local entities), who the likely users are, and what the holder has or has not done with it so far. A TLD with no names issued and a clean record is often easier to sell than one with an ambiguous history of issuance.

The argument that backfires is the one built on time pressure. A public body cannot shorten its approval path because a seller asks it to, so pressure produces defensiveness and a legal review of the seller, not a decision. A private operator may tolerate it from a counterparty it already trusts, but on a first approach it reads as a warning sign.

The same logic applies to the argument from financial return. Telling a municipality that the TLD can generate revenue is not wrong, but leading with it signals that the seller sees the city’s name first as a source of income. The revenue argument belongs in the middle of a conversation, after the stewardship and governance frame is established.

There is one more argument to leave out: the suggestion that the name could end up with a party the buyer would dislike. It is the fastest way to turn a possible buyer into an opponent, and it is not how a serious sale is run. If the place has no interest, the honest response is to thank them and close the conversation.

What weakens the asset before a sale

Several things reduce the value of a geographic TLD or make a sale harder to close, and most of them are within the holder’s control.

Unmanaged name issuance. If names have been issued under the TLD to parties with no clear connection to the place, or to parties whose association with the name would embarrass a public buyer, the asset carries reputational risk that a careful buyer will price in or walk away from. A public body acquiring a city-name TLD will look at what has been issued. Make sure the record is one you can defend.

Names that look official. A name under a place TLD that reads like a public service, such as a town hall, a police service or a tax office, is a particular problem when it was issued to someone who is not that service. It can mislead residents, and it is the first thing a public body’s lawyers will look for. If such names exist, say so at the start and explain how they came about.

Wallet ambiguity. Because the TLD is a token in a wallet, buyers and their counsel will want to understand who controls that wallet and how. If the token has moved between wallets in ways that are difficult to explain, the review stalls. The registry record is public and anyone can check it on a block explorer, so make sure what they find matches what you represent.

Resolution overclaiming. An onchain name is not part of the ICANN DNS, which means a standard browser will not open it unless support has been added. Today the places where a Freename name does resolve are Bitcoin.com Wallet, MetaMask by way of Freename’s resolver, and desktop browsers in which the Freename Web3 extension has been installed. This coverage is partial and it changes. For a place name the point is sharper than usual, because a public body thinks first of ordinary residents with ordinary browsers. State the position accurately. It rarely ends a conversation, but a misrepresentation discovered later does.

Inactivity without explanation. A TLD held for a long time with no names issued is not a problem in itself, and a Freename TLD carries no annual renewal fee, so holding it costs nothing in renewals. But a holder who cannot explain why they acquired a place name makes a buyer nervous. Have a coherent account of why you hold the asset and what you envisioned for it.

Unclear transfer mechanics. A buyer’s counsel will want to understand how the transfer works before agreeing to terms. If you cannot explain it fluently, the conversation slows. Where the sale runs through Hush Partners, closing takes place through onchain escrow on an aftermarket, which is Freename’s unless the client prefers another marketplace.

The terms a place-name buyer tends to ask for

The terms of this sale differ from a brand or sector sale in three places, all of which follow from the buyer’s accountability.

The first is the treatment of names already issued. A public buyer will want a complete schedule of them attached to the agreement, and a statement from you that the schedule is complete. It may ask you to stop issuing names from the moment discussions become serious. Agreeing to that early costs you little and removes a recurring worry on their side.

The second is conditionality. A public body often cannot sign an unconditional commitment before its approving authority has voted. Expect terms that are agreed in substance first and become binding only once approval is given. For you, that means a period in which the terms are settled but the sale is not certain, and the agreement should say how long that period can last.

The third is what happens after closing. Some buyers will ask for a short handover: an explanation of how names are issued and how the token is held. Others will want nothing further from the seller. Neither is unusual. What you should not accept without advice is an open-ended commitment about how the namespace will perform or be received.

These are commercial patterns, not legal advice. Contract and procurement rules vary by country, and your own counsel decides what you can agree to.

How long a geographic TLD sale takes and what sets the pace

A sale to a private operator who already knows onchain TLDs, with a clean asset, is the shortest case. A sale to a public body is the longest and commonly runs across more than one budget period from first approach to transfer. The main variables are not unique to geographic TLDs, but they show up more often and more strongly here than in brand or sector sales.

The first variable is the buyer’s internal approval requirement. A private operator with a single decision-maker moves faster than a tourism board that needs a mandate from its parent government body. Knowing which type of buyer you are speaking with shapes the entire process.

The second variable is the completeness of your file. A holder who arrives with a prepared package (registry record, issuance history, technical summary, governance outline, valuation) shortens the buyer’s review. A holder who assembles information reactively, one question at a time, adds delay to every stage.

The third variable is the buyer’s familiarity with onchain assets. A municipal legal team that has never reviewed the transfer of a token will need time to get comfortable with the mechanics. A private operator who has acquired TLDs before will not. You cannot solve this entirely, but clear written explanations reduce the friction.

The fourth variable, specific to geographic names, is the political calendar. A municipal body approaching an election, or a tourism authority whose leadership has just changed, may pause a transaction that was progressing well. There is nothing to do in that situation except keep the file in order and wait.

The stages of a file, from mandate to transfer, are set out on the how it works page. They are the same for a geographic TLD, but the public-body track adds an approval layer that a commercial track does not have.

What to prepare before the first approach

Most of these steps apply to any TLD sale. They carry more weight for a geographic name, where the buyer’s review is broader and the governance frame matters as much as the technical one.

1. Check the registry recordConfirm that the token is in the wallet you intend to sell from, that you know who controls that wallet, and that the public record on the block explorer matches what you will tell a buyer.
2. Document the issuance historyList every name issued under the TLD: to whom, when and on what basis. Mark any name that could be taken for an official service. If an issuance is hard to explain, address it before a buyer asks.
3. Write a technical summaryDescribe accurately what the TLD can do, including website publication, payments to a name and resolution in supported wallets and browsers, and say where coverage is partial.
4. Draft a governance outlineSketch how the namespace could be managed after transfer: who could register names, on what criteria, how disputes would be handled. It does not bind the buyer, but it shows that stewardship has been thought through.
5. Obtain a valuationA reasoned figure gives the buyer's finance and legal teams something they can defend internally, and keeps price from dominating the first conversation.
6. Map the buyersList the public bodies, tourism or destination bodies, chambers and private operators with a credible connection to the place. Order them by fit with the stewardship frame first, and by speed of decision second.
7. Prepare the confidentiality stageHave the package ready to share under a mutual NDA, so that there is no delay once a buyer signals interest.

The TLD Readiness Score is a free tool that scores how ready a TLD is to be sold, and it is a reasonable first check before you start on the list above.

If you hold a geographic TLD and want support identifying and approaching buyers, Hush Partners takes sell-side mandates for this type of asset. A single named partner stays with the file from the first note through to closing, the desk does not name the seller of a TLD, and a standard mutual NDA covers every exchange. The fee for a mandate is a fixed amount and is never calculated as a share of the price. The desk also acts for organizations that want the holder of a particular TLD found and approached. Either way, the starting point is the contact form.

Questions people ask

Is an onchain geographic TLD the same as an ICANN city TLD?

No. A city TLD delegated by ICANN is part of the DNS and opens in ordinary browsers everywhere. An onchain TLD lives in a separate namespace and needs a compatible wallet or browser extension. The two are different assets with different governance and different technical reach, and for plain reach the DNS is simply better. The comparison of an ICANN dotBrand and an onchain TLD covers the same contrast for brand names.

Can a public body be approached directly, or does an intermediary help?

A direct approach from a holder to a city government or tourism authority is possible but carries a risk. If the first contact is poorly framed, it can trigger a defensive response that makes a second approach harder. An intermediary can present the asset as infrastructure without being the party that profits from the price, which makes the governance and stewardship framing easier to deliver credibly.

What happens to names already issued under the TLD when it transfers?

Names you hold yourself under the TLD can pass to the buyer with it if the two of you agree, and names sold to third parties stay theirs. What happens beyond that depends on the registry’s terms, which you should read before you make any statement to a buyer. The transfer agreement should address the point explicitly: which names exist, what their holders can expect, and what the new holder’s policy will be. This is a legal question, and your counsel decides how to handle it in your situation.

Does the place need to be in a particular country for the TLD to be saleable?

No. An onchain TLD is not tied to a jurisdiction, and the place it names can be anywhere. Saleability depends far more on the recognition and the commercial or civic significance of the place than on its country. A well-known destination in a small country may be more saleable than a minor municipality in a large one.

What if the relevant municipality or government objects to the sale?

The transfer of an onchain TLD is a matter of onchain mechanics and private contract, and whether any public authority has a say depends on the law of the countries involved, which your counsel must assess. In practice, a buyer who is sensitive to legitimacy, as most buyers of geographic names are, will weigh any known objection. If a municipality has publicly stated an interest in the TLD or objected to private ownership, that is a material fact for the buyer’s review. Disclose it early.