# Your organization's name onchain: a guide for legal teams
> For general counsel and brand protection teams: what it means when your name exists as an onchain TLD, how to check, and what your options are.
Source: https://hush.partners/brand-name-onchain-legal-teams
Category: Brand protection
Published by Hush Partners.
---
Someone on your team has flagged that your organization's name exists as a top-level domain on a public blockchain registry, held by a wallet you don't recognize. The instinct is to escalate immediately, but the situation rewards a calm and methodical read before anyone does anything. This article gives you that read.
By the time you finish it, you will understand what an onchain TLD actually is, what its holder can and cannot do with it, how to verify what exists, and what your realistic options are. You will also have a clear picture of what to settle internally before any outward step is taken, and a concrete list of tasks to start this week.
The article is written for general counsel and brand protection teams. It does not assume prior familiarity with blockchain technology. It does assume that you are experienced in brand protection and capable of instructing counsel on what the situation requires.
## What an onchain TLD is, and why it differs from a conventional domain
A top-level domain (TLD) is the segment that follows the final dot in a name. In the conventional internet, TLDs are coordinated by ICANN, the Internet Corporation for Assigned Names and Numbers, which maintains the single list of TLDs that the Domain Name System (DNS) recognizes and sets the rules under which registries and registrars operate. No one can add a TLD to that list without going through ICANN's application process, which is long and expensive.
An onchain TLD sits in a different system entirely. What your team found on a registry such as Freename is a TLD recorded onchain as a token, and that token is held in a wallet. A token here is a unique digital record on a public blockchain, and a wallet is the software that holds the keys controlling it. ICANN is not involved, and no application to ICANN is needed to create one. Whoever controls the wallet controls the TLD. There is no annual renewal fee on a Freename TLD, so the record does not lapse because someone forgot to pay.
Because the TLD exists outside the list ICANN maintains, it also resolves outside the DNS that browsers use by default. A name like `pay.yourbrand` under a Freename TLD does not open in an ordinary browser without support. For a legal team sizing the audience, Freename names are supported in three places: Bitcoin.com Wallet, MetaMask through Freename's resolver, and desktop browsers through the Freename Web3 extension. Coverage is partial and it changes. That technical limitation matters when you are assessing how serious the situation is.
The key structural difference for legal teams concerns enforcement. The Uniform Domain-Name Dispute-Resolution Policy (UDRP), the standard route for disputes over conventional domain names, binds registrants because they accept it in the registration agreement for a domain in the ICANN system. A token on a blockchain registry is not registered under such an agreement, so the UDRP is not the route here. Your organization's existing brand protection playbook needs to be read against that constraint before any step is taken.
It also helps to be clear about what an onchain TLD is not. It is not a domain name that sits somewhere in the DNS waiting to be found by your customers, and it does not affect your existing domains, your email or your website in any way. It is a parallel naming system with its own users and its own software. For reach, universality and the maturity of its dispute procedures, the DNS is simply ahead. The onchain system matters to you only to the extent that your audience, or people who deal with your audience, use the applications in which these names resolve.
## What the holder can and cannot do with the name
Understanding the holder's actual capabilities is the foundation for any assessment. Start from what is technically possible.
The holder of an onchain TLD controls a namespace. Only the holder can issue names under that TLD. That means only the holder decides whether a name such as `pay.yourbrand` or `info.yourbrand` exists. The holder also has a commercial interest in issuing names: Freename runs a royalty program in which the holder of a TLD receives a share of each registration fee for names registered under it, advertised at up to half, subject to the registry's current terms and activation conditions. Names can be configured to point to wallet addresses, or to content hosted on IPFS, a peer-to-peer system for storing and retrieving files.
In practice, and within the limits of [what is live](/whats-live), names issued under a TLD can serve as readable labels for wallet addresses that receive payments, as identifiers in compatible applications, and as pointers to websites published on IPFS. A name like `pay.yourbrand` could, in a compatible wallet, resolve to a payment address. A name like `info.yourbrand` could point to a website. Neither use requires any action from your organization.
What the holder cannot do is force these names into the conventional internet. Without delegation by ICANN, `.yourbrand` does not open from a standard browser address bar. That is a genuine technical limit, and it matters for your harm assessment: the people who could realistically encounter names under this TLD are those using the wallets, extensions or applications that support the registry's resolver. That population is real, but it is not the general public.
The holder also acquires no trademark right in your name by holding the token, and holding it does not remove any right you have. Trademark law, and the law on unfair competition and passing off where it exists, applies to conduct whatever the technology involved; how far it reaches in this setting varies by country and is for your counsel to assess. What the holder does have is the string itself in that registry. That occupancy has commercial value and it lasts, because there is no renewal fee whose non-payment would end it.
One more limit is worth stating plainly. Holding the TLD gives the holder no access to your systems, your customers' data or your accounts. The exposure is one of association: a name that reads as yours, in an environment where your organization has no presence and no control. Whether that association matters depends on what is done with it, which is why the next step is to look.
## How to find out exactly what exists
Before any internal or external decision, establish the factual record. Three elements are worth checking.
**The TLD record itself.** The registry record is public and anyone can check it on a block explorer, a website that displays the records of a given blockchain. A block explorer shows when the token was created, which wallet holds it, and whether it has moved between wallets since. You do not need specialist tools to read a block explorer, though someone comfortable with blockchain records will read it faster. A wallet address is not a name: the record tells you which wallet holds the TLD, not who is behind it.
**Names issued under the TLD.** Names issued under a TLD are also recorded onchain. If the holder has issued names, you need to know what those names are and what, if anything, they resolve to. A name configured to point to a payment address or a website is materially different from a name that points nowhere.
**Your wider exposure.** The matching TLD is the obvious string, but your organization probably has more than one name worth checking: product brands, abbreviations, the names of subsidiaries. The free Trademark Name Check on the [trademark TLDs](/trademark-tlds) page is one starting point, and the [Namespace Exposure Score](/namespace-exposure-score) is a free tool that scores how exposed a brand is onchain. Use the result as one input to your internal assessment, alongside what you read on the block explorer yourself.
Record what you find with care. Save the address of the record, the wallet address that holds it, the date on which you looked, and screenshots of anything a name resolves to. Have one person do this, and keep the notes with the file. If the matter later goes to counsel, to a negotiation or to a board paper, a dated factual record made before anyone formed a view is worth more than a reconstruction.
If your organization has not already run a systematic check, do it before any other step. The results determine everything that follows.
## How to judge whether it matters for your organization
Not every instance of your name onchain represents the same level of risk. The judgment depends on a combination of factors that are specific to your organization.
**Current use and activation.** An onchain TLD that was created and left entirely dormant, with no names issued, no wallets configured and no content pointed anywhere, is a different situation from one under which many names have been issued and configured to receive payments. Activation is the key variable. Check what is actually live.
**Your sector and your audience.** If your organization operates in financial services, digital assets, technology, or any sector where onchain payments and wallets are already part of your audience's daily environment, the risk that a name like `pay.yourbrand` causes confusion is higher and more immediate than if your sector has no overlap with onchain activity. The legal assessment of likelihood of confusion, which your trademark counsel will conduct, should be informed by where your audience actually operates.
**The nature of the string.** A coined, distinctive name points to your organization and to little else. A name that is also a dictionary word, a surname or a place name may have been chosen for reasons that have nothing to do with you, and several organizations in different countries may have an equal claim to it. The more ordinary the word, the more care is needed before treating the TLD as a brand protection matter at all.
**Your trademark registrations.** Your trademark portfolio determines what legal options are actually available. The relevant questions: which jurisdictions cover the name, in which classes, and how broadly the registration is drawn. These are questions your IP counsel will already know the answers to, but they need to be applied to the onchain context, which may be less familiar to them. The page for [brands and legal teams](/brands-and-legal-teams) on this site is written for counsel who need that context.
**What the record suggests about the holder's plans.** A TLD left dormant is different from one under which names are actively being issued to third parties, or one whose names point to payment addresses presented as yours. The registry record and the names issued under the TLD are the evidence you have. Do not assume bad faith without looking at the evidence, and do not assume the absence of a plan because the TLD appears inactive. Many holders acquired strings as assets, with no particular organization in mind.
**The passage of time.** A TLD that has sat dormant for an extended period may be a less pressing matter than one that is being actively developed. However, because there is no renewal fee, time does not resolve the situation by itself. A dormant TLD can be activated or transferred at any point.
Taken together, these factors usually sort a file into one of three positions. Either there is live use that touches your audience, and the matter deserves a decision soon. Or there is no live use but the string is distinctive and your audience is close to onchain activity, and the matter deserves a deliberate choice between acquiring and watching. Or the string is ordinary, the audience is remote and nothing is live, and a documented decision to leave it is defensible. Writing down which position you are in, and why, is the most useful single page your team can produce in the first week.
## The options on the table
Four options are available to an organization that finds its name held by another party as an onchain TLD. Each has its own requirements and its own costs.
| Option | What it requires | When it fits |
|---|---|---|
| Acquire | A budget, an internal mandate, a negotiation and a closing | Control of the string matters to you |
| Watch | Monitoring, a named owner and review at set intervals | Exposure is low and nothing is live |
| Take legal advice on enforcement | A brief to IP counsel and a factual record | Live use that may infringe your rights |
| Leave it | A documented assessment and a review trigger | Exposure is genuinely immaterial |
**Acquire.** Acquisition means reaching the holder, agreeing a price, and transferring the TLD to your organization's control. Closing runs through onchain escrow on an aftermarket: the payment and the token are exchanged in one recorded transaction, so neither side has to perform first and trust the other to follow. Once you hold the TLD, you can issue names under it, configure them as you choose, or issue none at all. The [brand namespace recovery](/brand-namespace-recovery) service is built around this path.
The principal difficulty with acquisition is that you do not know, at the outset, whether the holder wants to sell, what they would accept, or whether the way you approach will itself raise the price. These are the reasons why the manner of the approach matters, and why some organizations prefer that an intermediary makes it.
**Watch.** If your assessment is that exposure is low (the TLD is dormant, your audience has limited overlap with onchain environments, and no names are configured), it may be appropriate to monitor without immediate action. [Namespace watch](/namespace-watch) is a service that monitors the names of a brand onchain. Watching is not a substitute for a decision. It is a structured way to know when the facts change, and it only works if someone is named to read the results and a review date is set.
**Take legal advice on enforcement.** Your IP counsel can advise on what causes of action may be available in the jurisdictions where your trademark is registered. The analysis is more complex than for a conventional domain dispute, because the UDRP is not the route and because there is no registrar in the ICANN sense to whom a decision can be addressed. A claim, where one exists, is generally directed at a person's conduct, which raises practical questions of identifying that person and of jurisdiction. This article does not go further into the legal analysis, which is work for your counsel, but it is sensible to enter that engagement with a realistic view of what remedies are and are not available, and of what they would cost relative to the other options.
**Leave it.** There are situations where the exposure is genuinely immaterial: the name is a coincidence of strings and not a use of your brand, the audience overlap is negligible, and no activation is in evidence. If your assessment leads there, document it and set a review trigger, such as a first name being issued under the TLD or your own entry into onchain payments. Doing nothing is a decision, and it should be made on the same factual basis as any other option.
The options are not exclusive, and they can follow one another. Watching while counsel forms a view is common sense. So is taking legal advice before deciding what an acquisition is worth to you. What does not combine well is an enforcement letter followed by an offer to buy, or the reverse, because each step colors how the other is read. That is the reason the order of moves deserves thought before the first one is made.
## Questions to settle internally before any contact
Before any outward step, whether a letter, an approach through a third party, or even an exploratory inquiry, your organization needs answers to the following questions.
**Who has authority to decide?** Acquiring a digital asset often touches the legal, brand and finance functions at once, and legal action may need approval at a higher level, depending on your governance. Know who is deciding before any approach is made.
**What is your budget for acquisition?** If acquisition is on the table, you need a realistic range before any approach is made. A holder who understands what the string means to a brand will price it with that in mind. Entering a negotiation without an approved range lengthens it, because every counter-proposal has to go back up the line.
**What is your preferred outcome?** Control can mean two different things. You may want the TLD so that you can issue names under it and build an onchain namespace of your own. Or you may simply want to hold it so that no one else issues names under it. The approach, the budget and the internal sponsor look different depending on which outcome you want.
**What is your legal position?** Before any contact, have a preliminary view from IP counsel, even an incomplete one, on what trademark rights you hold and what the realistic enforcement options are. This informs the negotiation. It also tells you whether legal action is a credible alternative to acquisition, which affects how much the string is worth to you.
**Who will hold the asset?** An onchain TLD is held in a wallet, and a wallet is controlled by keys. Decide which entity of the group would hold the TLD and how the keys would be governed. A multisignature wallet, which needs the approval of several keys before anything moves, is a common way to avoid dependence on one person. Your finance and security teams should be part of that conversation before closing, not after.
**Who will manage the process?** One named person should own the file and coordinate between legal, brand, and any external advisers. Sensitive negotiations go wrong more easily when several people believe they are in charge of them.
## Why discretion serves the organization
Discretion is not simply a preference. It is a practical asset in this kind of negotiation.
When your organization's name exists as an onchain TLD, the holder may not know that the brand owner is aware of it. If your first contact signals that a large organization with significant trademark rights has identified the TLD and is concerned about it, you have changed the holder's understanding of its value. A holder who might have accepted a modest sum in a quiet conversation may price the asset very differently once concern is on display.
The same principle applies to public statements. A press release, a social media post or a comment to trade press that acknowledges the TLD and calls it a problem will be read by the holder, and by people who hold similar strings. It may also create expectations among your own stakeholders that you are about to resolve the situation on a specific timeline.
Practical discretion means three things. Any approach is made once, by one person or one intermediary, with a prepared message. Commercial detail is exchanged only under a non-disclosure agreement. And the circle of people inside the organization who know about the file is kept to those who need to act on it. For exchanges with Hush Partners, the [standard mutual NDA](/nda) covers every exchange.
Discretion also protects the other side, which is easy to overlook. A holder who is treated as a counterparty in a private commercial conversation has every reason to answer plainly. A holder who learns of your interest through a public statement or a hostile first letter has reasons to become cautious. Brand protection matters tend to become more expensive when they become public.
## What happens if you receive a note about the name
Some organizations first encounter the situation not by finding the TLD themselves, but by receiving a note from someone who holds a TLD that matches their name, or who represents its holder.
The note might be framed as an offer to sell, as an introduction to a service, or simply as notification that the TLD exists. Whatever its framing, the response deserves the same internal groundwork described above. Do not respond on the strength of a first reaction.
A note is not an emergency. It is an opening communication, and the terms on which you respond will shape whatever follows. A first reply that signals distress, or that opens with a legal threat, tends to harden positions before you know what yours is.
Check the note against the record before anything else. Does the TLD it mentions exist on a block explorer? Does the sender explain in what capacity they write? Does the note ask for anything other than a conversation? A note that asks for payment outside a recognized escrow process, or that presses for an immediate answer, should be treated with the caution you would apply to any unsolicited commercial approach. Then route the note to the person who owns the file, so that the organization answers once and with one voice, or decides not to answer.
If the note comes from Hush Partners, a few fixed points apply. Every exchange is covered by a standard mutual NDA. The desk never names the seller of a given TLD. Its fee is a fixed amount, never a percentage, and it is charged only to the client who mandates the desk: a party that answers a note and goes on to buy pays the price of the TLD and no fee. The page for organizations that [received a note](/received-a-note) explains the rest. Read it before you reply.
## What to do this week
First-week checklist for legal teams
Verify the registry recordOpen the record on a block explorer to confirm that the TLD exists, when it was created and which wallet holds it. Note whether it has moved between wallets since it was created.
Check what names are issuedReview whether any names have been issued under the TLD, and whether any of them point to wallets, payment addresses or content. This activation check carries the most weight in your assessment.
Widen the checkRun your other brand names through the Trademark Name Check and the Namespace Exposure Score, both free tools on this site. Keep the dated results with your own notes as the baseline for the file.
Brief IP counselShare the record with your IP counsel and ask for a preliminary view on the trademark rights that apply and the legal options that exist. Make clear that the name sits outside the ICANN system and that the UDRP is not the route.
Settle your internal questionsConfirm who has decision authority, what budget is available if acquisition is pursued, which entity would hold the asset and what the preferred outcome is. Take no external step until these are settled.
Choose your immediate pathDecide whether to pursue acquisition, set up a watch, take further legal advice, or document the assessment and leave it. Write the decision down with its review date.
None of these steps commits you to anything, and none of them is visible to the holder. That is the point of doing them first: at the end of the week you hold a factual record, a legal first view and an internal position, and you have given nothing away.
If acquisition is the option you choose, the [buy-side acquisition](/buy-side-acquisition) service is the one in which an organization mandates Hush Partners to find and approach a holder. Your legal team then deals with one named partner, who follows the file from first note to closing, and that closing runs through onchain escrow on an aftermarket.
If you would prefer to understand the wider picture before deciding, including which capabilities are live and how a TLD that matches a trademark differs from one that is a sector word such as `.yoursector`, the pages named above are the place to start. To reach the desk, the contact form on the site is the only channel.
## Questions people ask
### Does holding a trademark give my organization any automatic rights over the matching onchain TLD?
Not automatically, and not through the mechanisms that apply in the conventional domain system. A trademark registration is the foundation for any enforcement claim, but the UDRP does not govern onchain TLDs, and there is no equivalent administrative procedure to which a complaint can be addressed. What rights are available, and through what mechanisms, depends on the jurisdictions where your trademark is registered and on the specific conduct of the holder. That analysis belongs to your IP counsel, not to this article.
### Can the holder of `.yourbrand` issue names to third parties without any restriction?
Technically, yes. Only the TLD holder can issue names, but the holder can issue them to anyone and they can be configured for any use the registry supports: wallet addresses, payments, websites. Nothing in the system obliges the holder to run the namespace in a particular way or to apply a brand protection mechanism of the kind found in the ICANN system. The limits come from the law that applies to the holder's conduct and from the registry's own terms.
### If I acquire the TLD, what can I actually do with it?
Once you hold the TLD, you control the entire namespace under it. You can issue names for your own operations, for example a readable payment name for your treasury, names for wallets your teams use, or a website for particular content, always within the partial coverage described earlier. You can also issue no names at all and simply hold the string. Both are legitimate outcomes, and the choice can be made after closing. What cannot wait until after closing is the question of custody: who holds the keys.
### Is this likely to be confined to one registry?
Not necessarily. Freename is the registry discussed in this article, but other blockchain naming systems exist, each with its own records and its own rules. If your brand is prominent, it is reasonable to ask whether the same string exists elsewhere and in what state. Treat each registry as a separate factual question: what a holder can do, what it costs to hold and where names resolve all differ from one system to the next.
### What if the holder cannot be found or refuses to engage?
An onchain TLD is held in a wallet, and the wallet address is public. Whether the person behind that wallet can be reached, and whether they are willing to talk, varies. A holder who is unreachable or who declines limits the acquisition path but does not close the legal analysis: your counsel can advise on whether identifying the person behind a wallet is possible through lawful means and whether that changes the enforcement options. In the meantime, a watch is the proportionate response.