# The holder says no: the options that remain
> A refusal is an answer, not always the last one. What an organization can do next, and what it should not.
Source: https://hush.partners/when-the-holder-says-no
Category: Acquiring
Published by Hush Partners.
---
A refusal lands, and the instinct is to treat it as a wall. It rarely is. A holder who does not reply has made a different calculation from one who replies "not for sale at any price," and both are different again from one who says "not at that number." Reading which kind of refusal you have received is the first and most useful thing you can do. Everything that follows depends on it.
This article maps the main kinds of refusal, explains what each one tends to suggest, and then works through the options in increasing order of cost and complexity. By the end, you should be able to choose a path that keeps your position intact and your options open, without making things worse.
The context throughout is an onchain TLD, a top-level domain recorded as a token on a blockchain, held privately by a party that is not your organization. The principles borrow from the wider domain aftermarket, but the onchain environment has its own dynamics, and those are the ones addressed here.
## Reading the refusal before responding to it
Four patterns cover almost every response you will encounter.
| Kind of refusal | What it looks like | What it tends to suggest |
|---|---|---|
| No reply | Silence after one or more notes | Holder did not see the note, does not recognize the channel, or is deliberately holding options open |
| Not for sale | A clear statement that the TLD is not available at any price | Strong attachment: personal, commercial or strategic; may change if circumstances change |
| Not at that level | Counter or decline tied to price | An economic gap; the holder is willing in principle |
| Not to you | Willingness to sell, but not to this buyer | Identity concern: competitive risk, reputational risk, or a preference for a different kind of buyer |
Each pattern calls for a different next step. Treating a price refusal as a flat refusal wastes time. Treating a "not to you" as a price problem wastes goodwill and may harden the position.
### No reply
No reply is the most ambiguous. On Freename, a TLD is recorded as a token held in a wallet; the registry record is public and can be checked on a block explorer. The holder may be an individual who looks at that wallet infrequently, a fund that holds the TLD as a portfolio asset, or an operator running an active namespace. Each is reached through different channels and has different motivations. Silence often means the note did not arrive in a form the holder recognized, not that the holder considered it and declined.
Silence therefore tells you more about the channel than about the holder. Before you draw any conclusion, ask whether the note could be verified by the person who received it: who sent it, on whose behalf, and how to answer safely. An unsolicited message about a valuable asset looks, from the holder's side, much like the many unwanted messages every wallet owner receives. One further note through a channel the holder can verify is reasonable. After that, silence is treated as a no for the time being.
### Not for sale
A flat "not for sale" is the clearest answer and the one to take most literally. The holder has plans for the TLD, or values holding it more than any sum you are likely to offer. Nothing in that answer is a negotiating position, and reading it as one is the most common misjudgment at this stage. What it does leave open is time: plans change, and a holder who was treated correctly when declining is easier to speak with later.
### Not at that level
A price refusal (a counter at a number your organization cannot reach, or a stated minimum that you did not meet) is the most commercially tractable. It confirms that a transaction is possible. The gap is the problem, and gaps can be addressed in more than one way.
### Not to you
A "not to you" refusal is the most delicate. It usually means the holder has identified who is approaching, or has made a reasonable inference, and sees a reason not to transfer to that particular buyer. That reason is worth understanding before any further step is taken.
## Waiting, and how to wait usefully
Waiting is a legitimate strategy, and for many organizations it is the right one. Circumstances that make a holder immovable at one moment change: financial pressure, shifting priorities, a new ownership structure, a change in what the holder is building under the TLD. None of these can be predicted with precision, but they can be observed.
Useful waiting is not passive. It means maintaining a record of your interest, your valuation reasoning, and the terms you were willing to accept, so that when circumstances shift you can move without delay. It means being ready to re-approach cleanly, without the awkwardness of a party who has forgotten what was said before.
It also means deciding, internally, what the TLD is worth to you now and what it would be worth if the holder's position or the onchain environment changed. A valuation done at this point gives you an anchor for that later conversation. Without one, you start from scratch when the window opens.
Waiting costs something, and that cost belongs in the decision. Unlike a DNS domain, a Freename TLD carries no annual renewal fee, so there is no expiry to wait for and no lapse that returns the TLD to the registry. A holder can keep it indefinitely at no carrying cost. Waiting is therefore a bet on a change in the holder's circumstances or intentions, never on the calendar. If your plans depend on a namespace within a fixed period, waiting alone is not a plan, and the alternatives discussed below deserve attention in parallel.
One caution: waiting does not mean leaving a channel open in an ambiguous way. If you have received a clear refusal, acknowledge it, close the exchange politely, and stop. Re-opening it later as a fresh inquiry is legitimate. Keeping it technically alive with occasional nudges is not. Rules on persistent unwanted contact vary by country, and your own counsel should advise on the line in your situation.
## Monitoring what happens under the TLD
While you wait, the TLD does not stand still. A holder may begin issuing names under it, activate a royalty program, build a community, or let it sit unused. All of these developments are relevant to your decision.
On Freename, the holder of a TLD is the only party who can issue names under it. The registry's royalty program gives the holder a share of each registration fee for names registered under that TLD, advertised at up to half, subject to the registry's current terms and activation conditions. Holders therefore have a commercial reason to open the namespace instead of leaving it idle. A TLD that begins attracting registrations is likely to become more expensive to acquire and more embedded in its holder's plans. A TLD that sits dormant may indicate a holder who has not yet found a use for it and may be more open to a conversation than the original refusal suggested.
Because the record is public, all of this can be observed without contacting anyone. The difficulty is doing it consistently: a check made once after the refusal and never again tells you little. [Namespace Watch](/namespace-watch) is the desk's service for monitoring the names of a brand onchain, and for an organization that has been refused and is waiting, structured monitoring is more useful than occasional manual searches. The event that matters most is a change of holder. A TLD that moves to a different wallet may have a new owner with different intentions, and that is a sound reason to open a fresh inquiry.
For organizations concerned about broader exposure (the range of names that could affect a brand onchain, beyond a single TLD), the [Namespace Exposure Score](/namespace-exposure-score) is a free tool that scores how exposed a brand is and helps rank the gaps.
## Coming back with something different
A refusal on terms is an invitation, however unwelcome, to reconsider the terms. The most common mistake is returning with the same offer and expecting a different result. If price was the stated obstacle, consider whether the structure of the offer can move without the headline number being the only variable. Payment timing, certainty of funds, and the speed and simplicity of the transfer all have value to a holder, and any of them may matter more than a marginal increase in price.
If the refusal was "not to you," the economics are beside the point. The holder's concern is about who will control the namespace and what will be done with it. The honest response is to address that concern: explain the intended use, offer assurances the holder cares about, or let an intermediary carry the conversation so that it stays calm and confidential on both sides. An intermediary is a way to lower the temperature. It is not a way to get around a holder who has declined a particular buyer, and an approach designed to disguise that buyer would be exactly the conduct this article advises against.
Before re-approaching on any basis, the [rules of engagement](/rules-of-engagement) that govern a file are worth reviewing. A second approach that is too soon, too insistent, or poorly framed can harden a holder's position permanently. Spacing, tone, and the channel through which the note arrives all affect how it lands.
## Other names that would serve
A refusal on one TLD is not a refusal on every name that would serve the organization's purpose. This is easy to forget when a particular string feels essential, and it is worth examining whether it is.
The strategic value of a TLD usually comes from a combination of properties: recognizability, alignment with a brand or product name, utility for the names that would be issued under it, and the audience that would encounter those names. A TLD that scores well on all four may not be the only one that does.
Consider a fictional mid-sized manufacturer seeking a namespace for customer-facing payment names. Assume the TLD that most closely matches the brand is held and unavailable. The practical question is how much of the namespace's value comes from the exact string, and how much comes from having a clean, brand-aligned namespace at all. Where the use is a name such as `pay.yourbrand` that resolves to a payment address in a wallet, the answer depends on what the organization's customers will type or see. In some cases a closely adjacent string, or a sector word such as `.yoursector`, serves the function just as well.
For organizations with trademark rights in their name, the free [Trademark Name Check](/trademark-tlds#check) is a starting point for seeing how the mark sits onchain. It can bring up strings the organization had not considered but that would serve the purpose. A [buy-side acquisition](/buy-side-acquisition) mandate is better prepared when that mapping is done before any holder is approached, because a refusal on the primary name then does not leave the organization without a path.
It is also worth separating urgency from importance. Many organizations treat a TLD acquisition as urgent because they have only just noticed the question, not because the exposure itself is new or acute. An exposure score sometimes shows that a secondary string carries the real operational risk while the primary one is contested but not a live problem.
## The legal route and its realism
Legal remedies are real but narrow. They apply in specific circumstances, they carry costs and risks of their own, and they are frequently misunderstood as a general solution to a holder who will not sell at an acceptable price.
The UDRP (the Uniform Domain-Name Dispute Resolution Policy, an ICANN mechanism for resolving disputes over names registered under ICANN generic TLDs) does not apply to onchain TLDs. Onchain TLDs are not ICANN-governed: they exist on independent blockchain registries that operate outside the ICANN DNS. The policy binds through the contracts that registrars and registrants sign within that system, and the holder of an onchain TLD has signed none of them. A complaint on UDRP grounds therefore has nothing to attach to. Brand protection teams arriving from a DNS background sometimes miss this point.
What may exist, depending on the country, is a civil claim under trademark law. If the holder of an onchain TLD is using the name commercially in a way that creates a likelihood of confusion with a registered mark, a claim may be available. The details vary substantially by country, and the analysis depends on how the TLD is being used, whether names issued under it reach consumers, and whether confusion is plausible. Holding a TLD and declining to sell it is, on its own, a very different matter from using it against a mark. This is information, not advice: your own counsel decides whether a claim is available and worth pursuing.
Two practical limits apply regardless of jurisdiction. First, litigation over an onchain TLD is novel. There is little settled precedent on what it means to hold, use, or transfer an onchain TLD token, and the outcome of any proceeding is uncertain. Enforcement is a separate question: a judgment still has to reach a token held in a wallet that may be controlled from another country. Second, litigation is expensive, slow, and public. Even a meritorious claim takes time to resolve, and during that time the relationship with the holder, and with it the holder's willingness ever to transact, is usually lost. For most organizations, litigation is a last resort in cases of clear bad-faith use affecting real commercial interests, not a response to a negotiating impasse.
For most organizations whose aim is to hold the TLD that matches their name, the realistic route remains a negotiated purchase, which is what [brand namespace recovery](/brand-namespace-recovery) describes. The legal analysis informs that process. It does not replace it.
## What not to do after a refusal
Some responses to a refusal make the situation worse in ways that are difficult to undo. They are set out here because they can feel justified in the moment and are not.
**Pressure and implicit threats.** Telling a holder that your organization has trademark rights and will "take action" if they do not sell is a form of pressure that backfires in several ways. It puts you on record as having made demands. It may harden the holder's position instead of moving it. And it can complicate the legal position your counsel is trying to build. A holder who receives a threatening note is likely to consult a lawyer, at which point all further communication becomes formal and expensive. The rules of engagement exist partly to prevent this dynamic from starting.
**Publicity.** Writing publicly about the fact that you want a TLD and cannot obtain it, whether in a press release or a public post, signals the value you place on it to the holder and to every other party watching. It can convert a negotiating gap into a public contest. It rarely helps.
**Repeated contact.** Sending multiple notes after a clear refusal, or approaching through different channels in quick succession, is not persistence. It is pressure by volume. Beyond the damage to the relationship, some countries attach legal consequences to unwanted commercial contact after an expressed refusal. A single, clean follow-up after a reasonable interval, with a material change to offer, is appropriate. A pattern of contact is not.
**Tracing the person behind the wallet.** The registry record is public, and the wallet that holds a TLD can be checked on a block explorer. That information exists for transparency, not as an instrument of negotiation. Using wallet data to work out who an individual is, and then approaching that person through private channels, an employer or acquaintances, ends negotiations permanently and can expose the party doing it to legal proceedings.
**Over-disclosing your position.** Revealing how important a TLD is to a pending product launch, a rebranding, or an internal deadline gives the holder information that directly affects price. Say what is needed for the holder to take the approach seriously, and no more. Every exchange through the desk is covered by a mutual NDA, which protects what both sides do share.
## Practical next steps when the file is stalled
If an approach has been declined and the situation is stalled, the most productive use of the next period is internal: clarifying what the TLD is worth to the organization, what alternatives exist, and what would need to change for an acquisition to become possible or for the alternatives to become acceptable.
A structured [valuation](/valuation) of the specific TLD gives the organization a defensible basis for any future offer and a clear sense of how wide the gap is. It rests on the names that would be issued under the TLD, the royalty economics if those names carry registration fees, the alignment with the brand, and the exposure if the name were used by someone else.
[General counsel and brand protection teams](/brands-and-legal-teams) working through a stalled acquisition can also test whether the gap is one of method. A holder and a buyer who reason from the same valuation logic are sometimes closer than two anchored numbers suggest. That is not always the case, but it costs little to test before moving to more costly options.
If the situation calls for a fresh approach to the holder, with a different structure, a different channel, or a different framing, Hush Partners acts for organizations that mandate it to find and approach a holder. A file reopened after a refusal runs like any other at the desk: a standard mutual NDA covers every exchange, and one named partner follows it from first note to closing. For that work the desk charges a fixed amount and never a percentage, and it bills only the client who gives the mandate. A holder who answers a note pays no fee. The first step is a message through the contact form on the site, stating the TLD, what was said in the earlier exchange, and how the holder answered.
## Questions people ask
### If a holder accepts, how does the transfer actually happen?
Closing on an onchain TLD runs through onchain escrow on an aftermarket: Freename's by default, or another marketplace such as OpenSea if the client prefers. The token moves from the holder's wallet to the buyer's wallet against the payment, so neither side has to act first on trust. The [escrow and transfer](/escrow-and-transfer) page covers the process.
### Can a holder just ignore an approach and sell to someone else?
Yes. A holder has no obligation to respond to any approach or to prefer any particular buyer. An organization that has made an approach gains no priority over the TLD as a result. This is one reason monitoring matters: a change of holder is visible on the public record when it happens, and the new holder may answer differently.
### What happens to names already issued under a TLD if it is acquired?
Names that third parties registered under a TLD before its transfer remain theirs, held in their own wallets, and a change of holder at the top does not move them. Names the selling holder itself holds under the TLD are a different case: they can be transferred to the acquirer along with the TLD, if the two parties agree on it. What changes in either case is control over the issuance of future names and, where applicable, the royalty program. An organization acquiring a TLD with existing names under it should understand that namespace before closing, and confirm the details against the registry's current terms. Post-transfer activation is the stage at which the new holder takes operational control of a TLD that is already live.
### Is approaching a holder directly ever better than using an intermediary?
Sometimes. If the holder is a known party, the relationship already exists, and the approach is not commercially sensitive, a direct conversation is simpler. The case for an intermediary is strongest when the negotiation is likely to be long, when the buyer does not want its internal priorities exposed in the exchange, or when a previous direct approach has already been declined and a different voice may help.
### Does having a trademark in a name give an organization any priority claim on the onchain TLD?
Not automatically. A trademark protects a mark as used in commerce for certain goods and services; it is not a right in every string that resembles the mark in every context. Whether it supports any claim over an onchain TLD depends on the use the holder is making of the name, the country whose law applies, and the strength of the mark. The analysis belongs to your own counsel.