# What happens to the names under a TLD when it changes hands
> A TLD can carry names issued to other people. When the TLD is sold, those names raise questions for the seller, the buyer and the people who hold them.
Source: https://hush.partners/names-under-a-tld-when-it-changes-hands
Category: Onchain today
Published by Hush Partners.
---
A TLD transfer is simple at the token level. One wallet sends the token, another receives it, and the registry record updates. What the registry record does not show is the texture of commitments that may have built up under the TLD: names issued to other people, promises made to those people about what those names would do, and in some cases fees collected from them. The new holder owns the TLD. The question is what else comes with it.
This article takes each of the three parties in turn (the seller, the buyer and the person holding a name under someone else's TLD) and then looks at what the sale terms can do to protect all three. If you are in the middle of a transfer, or advising one, the goal is for you to leave this page knowing where your exposure sits and what questions to settle before closing.
The analysis applies to onchain TLDs recorded on a registry such as Freename, where the TLD is a token in a wallet and names beneath it are issued by the holder. When a TLD moves, names the seller itself holds beneath it can be handed over with it if the two parties agree, while names sold to third parties stay with the people who bought them. What the new holder may then do about those names depends on the registry's own terms and on what the parties agree, and both must be checked directly. Nothing here is legal advice; your own counsel applies it to your facts.
## Why names under a TLD can belong to third parties
On an onchain registry, a TLD holder occupies a position that has no clean analogy in the traditional domain name system. In the DNS, a registry operator and the registrars that sell names are separate parties, tied together by contract and ICANN policy. On Freename, issuing is reserved to one party: nobody but the wallet holding the TLD can create a name beneath it. Nothing obliges the holder to keep those names for itself. A name can be issued to a customer, a member, a partner or a stranger, who then uses it as their own.
This matters because a TLD can gather a namespace over time. A holder who runs an active community, a brand program, or a commercial market beneath their TLD may have issued a large number of names to people whose only relationships are with the TLD holder and the registry. Those name holders may have paid fees, configured wallets, built websites, or embedded `pay.yoursector` into payment flows. They rely on a name that sits beneath a token that is about to move to a new wallet.
The question of what rights those name holders have is one for your counsel. The question of what the registry's terms provide for issued names is one to put to the registry. The question of what the seller promised, and what the buyer agrees to take on, is one that the sale terms must address.
## The seller's position: what was promised
The seller created the namespace, and the seller is the only party who knows its full shape. That includes:
- **Representations about durability.** Did the seller tell name holders their names would never be withdrawn? An operator has an obvious reason to say so, because durability is what makes a name worth paying for.
- **Representations about function.** Did the seller say names under the TLD would resolve in specific wallets, support payments to `name.yoursector`, or serve websites? Functional promises can be harder to hand off than ownership.
- **Fee structures.** Did the seller collect one-time fees, subscription fees, or recurring fees from name holders? If fees were collected for a period that extends past the transfer date, the seller may have an obligation it cannot fulfill by transferring the TLD token.
- **Revenue participation.** Freename operates a royalty program: a portion of every registration fee paid for a name under a TLD goes to that TLD's holder. The advertised portion is up to half, and it depends on the registry's current terms and on activation conditions. A seller earning royalties on an active namespace is selling an income-producing asset. That income has a cost attached: a Freename TLD carries no annual renewal fee, but taking part in the royalty program does carry an annual cost, set by the registry. Some TLDs were registered under earlier terms that include the program for life, and whether those terms follow the TLD to its buyer is a point to confirm with the registry before closing. The buyer needs to know that; so does any adviser modeling the value of the TLD.
Sellers often underestimate how much of this is written down nowhere. Promises made in a community chat, a welcome message, or a terms page that has since changed are still promises. Before a sale process opens, a seller should audit the namespace: how many names exist, under what terms they were issued, and what commitments were made to the people who hold them. The [TLD Readiness Score](/tld-readiness-score), a free tool that scores how ready a TLD is to be sold, is a reasonable first check before that audit.
## The buyer's position: an inherited namespace
A buyer acquires the token. The token carries control of the TLD at the registry level, including the exclusive ability to issue new names. What it does not carry is a clean slate.
The names already issued under the TLD are held by other people. The buyer did not issue them, made no promises to their holders, and may not even know how many there are. Yet the buyer now controls the TLD those names sit under. Ownership of those names does not travel with the token: a name sold to a third party remains that party's, and only the names the seller itself holds can pass to the buyer, if the two agree on it. Whether a TLD holder can change, withdraw or reassign a name that has already been issued is not a question this article can answer in general. It depends on the registry's terms and on the agreement between the parties. Read the terms, and put the question to the registry in writing if they leave room for doubt.
From a purely practical standpoint, a buyer who does not inventory the namespace before closing is taking on an unknown liability. A worked example makes this concrete.
**Worked example.** Assume a TLD has 400 names registered under it at the time of sale. Assume the seller charged a one-time fee of USD 50 per name, so total registration revenue was USD 20,000. Assume the seller's terms stated that names were "permanent" and "non-revocable." Assume the buyer pays USD 60,000 for the TLD (an invented figure for the example, not an indication of value). The buyer now controls a TLD under which 400 people hold names they were told are permanent. If the buyer wishes to change the pricing structure, restrict the namespace, or rebrand the TLD, it faces a namespace full of prior commitments it did not make. The gap between what the buyer wanted and what it received is not a registry problem; it is a due-diligence problem.
A buyer who works through a structured process, whether by mandating a desk for a [buy-side acquisition](/buy-side-acquisition) or by insisting on a namespace disclosure from the seller, will catch this before closing. A buyer who accepts a token transfer without that disclosure carries the risk alone.
What follows the closing is also shaped by what the namespace contains. [Putting the TLD to work after the transfer](/post-transfer-activation) is a different project for a buyer who takes over an active namespace than for one who acquires a blank TLD.
## The position of someone holding a name under a TLD
If you hold a name under a TLD someone else owns, you depend on a token in another person's wallet. That is always true, including before any sale is contemplated. A transfer simply brings the question to the surface.
Your name is recorded onchain, and that record can be read on a block explorer by anyone. What the record does not show is the relationship between you and the TLD holder: what was promised, what fees you paid, what uses you have built on top of the name. Those facts live in whatever agreement or communication you had with the original holder.
When the TLD changes hands, the original holder's commitments may or may not pass to the buyer. Whether they do depends on the registry's terms, on what the sale terms say and, ultimately, on what your counsel advises. What you can do practically:
- Locate the terms under which you acquired the name. If there was a written agreement, a terms page, or any documented representation, keep a copy.
- Look up the TLD on a block explorer to see which wallet now holds it.
- Contact the new TLD holder or their operator if you have concerns about continuity of service.
- If your name is tied to a material function (wallet payments to `pay.yourbrand`, a website, an AI agent identity), assess how much that function depends on the TLD staying configured as it is.
The best time to ask these questions is before a sale is on anyone's mind. When you take a name under another person's TLD, ask what the issuer's terms say about a change of TLD holder, and whether the registry's terms say anything about issued names in that event. An issuer who has thought about it will have an answer. An issuer who has not is telling you something about how much weight to place on the name. The more your organization builds on a name, the more that answer matters: a name used for a campaign page carries less exposure than a name printed on invoices as a payment address.
The distinction between a TLD and a name under it, set out in the [glossary](/glossary), matters here in practice. You hold a name. The TLD holder controls the layer above it. Those are different positions, and seeing the structure clearly is what lets you assess your own exposure accurately.
A brand that wants a wider view than a single name can use the [Namespace Exposure Score](/namespace-exposure-score), a free tool that scores how exposed a brand is onchain.
## What the public record shows and what it does not
The registry record of a Freename TLD is public. It shows the wallet that holds the TLD token. A block explorer, a tool that reads directly from the blockchain, displays that record to anyone who looks. After a transfer, the record shows the new holder's wallet.
The record of a name under a TLD is public in the same way, and shows the wallet that holds that name. What the record of a TLD transfer tells you about the names beneath it is narrower than it seems: it tells you who holds the TLD now, not what the new holder has agreed to do about them.
What the public record does not show:
- **What promises were made.** The blockchain does not record the seller's terms, marketing representations, or private communications with name holders.
- **What fees were paid, and for what.** Onchain transactions show transfers of value, but interpreting what a payment was for requires offchain context.
- **What the name is used for.** A name may resolve to a wallet, point to a website, serve as an identity for an AI agent, or sit dormant. The record does not tell you which of these someone depends on.
- **Whether the name holder has a contractual right to continuation of service or to a refund.** Those are legal questions, not registry questions.
This gap between the public record and the commercial reality is why due diligence cannot stop at the blockchain. An adviser on either side of a TLD transfer will want offchain documentation: the seller's terms, a full list of issued names, and any communications with name holders about durability or function.
The exposure tends to be most layered for [operators](/operators) who run a market TLD as a namespace, because their business is the names themselves.
## Why an empty namespace is simpler to transfer
Most of the complications described above disappear when the TLD being transferred has no names issued under it. There are no third-party holders to consider, no prior promises, no fees collected in advance, and no constraints left by an earlier issuing policy.
A blank TLD transfers as a simple asset. The buyer knows what it is getting: the TLD token and the ability to issue names under it on terms of its own choosing, within the registry's rules. Activation starts from zero, which usually asks fewer decisions of the buyer than taking over a namespace and working out how to treat the people already in it.
This is one reason a TLD that was held but never activated and a TLD with an active namespace are different things to buy. The active namespace may represent real value (a community, royalty income, an established audience) but it also represents complexity that the sale terms must resolve. Neither is inherently better; they are different assets that call for different diligence.
For a seller who has issued nothing and is considering a sale, the reasoning is short: a buyer will assess the TLD on its potential, with nothing to untangle. For a seller who has built an active namespace, there is more to show a buyer, and more to disclose.
Between the two sits a common case: a namespace that is nearly empty. A handful of names issued to the seller's own wallets, to affiliates or to early supporters looks trivial, and often is. It still needs the same treatment in miniature. Names the seller issued to itself can move with the TLD or stay with the seller, whichever the two sides agree, and a seller who keeps `pay.yourbrand` after selling `.yourbrand` has kept something the buyer almost certainly assumed it was buying. Names given to supporters raise the question of what was said when they were given. A seller can settle much of this before a process opens, by agreeing with each of those holders what will happen to their name and by writing it down. A short, documented list is close to an empty namespace for diligence purposes. A short, undocumented one is not.
## What terms of sale can say about existing names
The sale agreement is the instrument that allocates the namespace risk between seller and buyer. Left silent, that risk falls wherever the applicable law puts it, and how the law treats onchain names varies by country and is not settled everywhere. A thoughtful agreement does not leave it silent.
The terms can address:
**Seller representations and warranties.** The seller represents that the namespace disclosure is complete and accurate; that no names were issued under terms inconsistent with the transfer; and that the terms under which fees were collected from name holders do not stand in the way of a sale. If the namespace turns out to differ from what was described, the buyer has a claim against the seller.
**Indemnification.** If a name holder makes a claim against the buyer arising from a promise the seller made, the seller indemnifies the buyer. This is a familiar mechanism in any transfer of a business that includes customer commitments.
**Continuity obligations.** The seller may be required to notify name holders of the transfer and to introduce the buyer. This reduces the risk of name holders being surprised by a change in who controls the TLD.
**Buyer obligations toward existing name holders.** The buyer may agree to honor the seller's terms for existing name holders for a defined period. This protects name holders and limits the seller's residual liability.
**Carve-outs.** If there are specific names or name holders that either party wants to treat differently (names held by the seller's own affiliates, for example, or names issued free as part of a promotion), the agreement can address each category explicitly.
**The registry's terms.** The agreement can record which version of the registry's terms both parties relied on, and what each understood them to provide for issued names. If that understanding proves wrong, it is better to have written down whose risk it was.
Getting these terms right is the work of counsel. What a structured process contributes is the information that makes the terms meaningful: a complete namespace inventory, documented prior terms, and a clear record of what was and was not issued before signing. The transfer itself, [onchain escrow and transfer at closing](/escrow-and-transfer), moves the token. It does not settle any of these questions, which is why they belong in the agreement that precedes it.
## The three parties: what each wants and what each risks
The interests of seller, buyer and name holder are not identical, and a negotiation that ignores one of the three tends to produce a deal that either fails or leads to claims after closing.
| Party | Primary interest | Principal risk |
| --- | --- | --- |
| Seller | Clean exit, full price, no residual liability to name holders | Undisclosed terms leading to claims from the buyer or name holders |
| Buyer | Known namespace, freedom to activate or rebrand | Commitments to name holders that constrain future use of the TLD |
| Name holder | Continuity of the name, its function and its terms | A new TLD holder who has not agreed to the seller's promises |
Any real transaction has more variables. The pattern holds, though: disclosure by the seller, diligence by the buyer and notice to name holders serve all three at once. A transfer done properly is not zero-sum.
## After the transfer: honoring, renegotiating, or leaving alone
Once the TLD has transferred, the new holder faces a practical choice about the names beneath it. The registry's terms govern what is technically possible, and they must be checked; the sale agreement governs what the buyer has committed to; counsel advises on what is legally sound. Within those constraints, three postures are available.
**Honoring the prior terms.** The buyer treats existing names as it found them: the same function, the same fee structure, the same access. This is the lowest-friction path and the one most likely to satisfy name holders. It is also the path that preserves whatever community or commercial value the namespace already had.
**Renegotiating.** The buyer approaches name holders to agree new terms: a new fee structure, new terms of use, or a new technical configuration. Renegotiation requires the consent of name holders and takes time. Where the prior terms were silent on a successor's ability to change them, agreement is the safer route, since a unilateral change may expose the buyer to claims. Whether the registry's terms permit what the buyer has in mind for existing names is a separate question, to be checked before any conversation with name holders begins.
**Leaving alone with a review period.** The buyer does nothing immediately and sets itself a fixed period to assess the namespace and decide on a strategy. This suits a buyer who acquired the TLD mainly for its own brand purposes and for whom the existing namespace was a minor consideration. During the review period, the buyer leaves the names as they are. At the end of it, the buyer has the information to make a considered decision.
None of these postures requires the buyer to accept unlimited liability for the seller's prior representations. That is what the indemnification provisions in the sale agreement are for. But the posture does affect the relationship between the new TLD holder and the people who built something under that TLD, and in a namespace whose value depends partly on trust, that relationship deserves care.
Whatever the posture, tell name holders which one it is. Silence after a change of TLD holder is read as a fourth posture, and rarely a reassuring one. A short notice that says who holds the TLD now, what stays the same, what is under review and how to raise a question costs little, and it replaces speculation with a statement the buyer has chosen.
## Getting a transfer to closing with the namespace resolved
Preparing a TLD for sale means inventorying the namespace, documenting the prior terms and working out what a buyer needs to know. A seller can do that work before mandating a sale process, or an adviser can help structure it. A TLD that reaches a buyer with a complete namespace disclosure is easier to price, easier to review, and less likely to cause friction after closing.
Hush Partners acts for holders who want a buyer found, under [sell-side mandates](/sell-side-mandates), and for organizations that want a holder found and approached. A standard mutual NDA applies to every exchange on a file, one named partner stays with it from the first note through closing, and closing takes place through onchain escrow on an aftermarket. The terms about existing names remain a matter for the parties and their counsel.
If you are a seller, the concrete next step is the inventory: every name issued, to whom, on what terms, with what promises. If you are a buyer, it is the request for that inventory, and a careful reading of the registry's terms on issued names, before any price is agreed. If you hold a name, it is finding the terms you were given and keeping them. And if your organization has [received a note](/received-a-note) from the desk about a TLD, that page explains what the note means and what answering it involves.
## Questions people ask
### If I hold a name under a TLD and the TLD is sold, do I lose my name?
There is no general answer. What a new TLD holder can do with a name already issued depends on the registry's terms, and what the new holder has agreed to do depends on the sale terms. Your counsel, working from the terms under which you acquired the name, is the right person to advise you on your position.
### Can a buyer disregard what the seller promised to name holders?
This is a question for counsel, and the answer depends on the country, the nature of the promises, and what the sale agreement says. An agreement that deals with existing names answers it between seller and buyer. Without such provisions, the allocation of risk follows general contract and property law, which varies by country.
### Does a TLD transfer affect the royalty income from names registered under it?
The royalty program is defined by the registry's current terms and activation conditions, so read them, and ask the registry how a change of holder is treated, before relying on that income in a price. Set against it the annual cost of taking part in the program, which the registry fixes, unless the TLD was registered under earlier lifetime terms that the registry confirms will carry over to you. The sale terms should also say who is entitled to any royalties earned before closing and not yet paid out.
### Is there a public way to see all names registered under a TLD before buying?
Name records are public, but how easily they can be gathered for one TLD depends on the tools the registry provides. Even a full list of names says nothing about the terms on which each was issued, because those terms are offchain. Ask the seller for the inventory as part of due diligence.
### Does an empty TLD still need namespace diligence?
Less, but not none. Confirm that nothing was issued, both with the seller and against the public record. Then ask what the seller said in public or in private about what the TLD would become. Announcements can create expectations in a community before a single name exists. If there were none, an empty TLD is the simplest one to transfer.