# Group name, brands, products: which onchain names matter
> A group has a holding name, operating brands and hundreds of products. A way to decide which onchain TLDs matter, and in what order.
Source: https://hush.partners/group-names-brands-and-product-names-onchain
Category: Brand protection
Published by Hush Partners.
---
Most IP teams have already settled whether the group's names deserve attention onchain. The harder question is which names, in what order, and who inside the group owns the decision for each one. A trademark portfolio that runs to hundreds of registrations across many jurisdictions cannot be transposed directly into an onchain TLD strategy. The two regimes differ in structure, in cost logic and in the nature of the risk.
What this article gives you is a working method. By the end you will be able to take any multi-brand group, sort its names into three layers, apply a short set of criteria to each layer, and come out with a ranked list of onchain TLDs worth securing. You will also have a clear view of who inside the group should be in the room when each decision is made.
The method starts from customers and money flows, not from the corporate register. That distinction matters more than it sounds.
## The three layers every group contains
Every multi-brand group, whatever its sector, contains the same three layers of name.
The first is the **group name**: the name under which the holding structure is known to investors, regulators and the financial press. It may appear in an annual report heading, in stock exchange filings or in a group-wide sustainability statement. Customers of the operating businesses may never see it. In a house-of-brands structure, where each business trades under its own name, that invisibility is deliberate.
The second layer is the **operating brand names**: the names under which the group's businesses actually trade. A customer walks into a shop, downloads an app or signs a service contract under one of these names. These names carry accumulated goodwill, appear in trademark portfolios in multiple classes and jurisdictions, and anchor the group's commercial identity in a way the holding name never does.
The third layer is the **product names**: the names given to individual products, product lines, formulations, model ranges or service tiers. Some product names are trademarked. Many are not. A few become more famous than the brand that sells them, but most cycle in and out of a catalog without accumulating the kind of independent goodwill that makes an onchain TLD worth holding.
Understanding which layer a name belongs to is the first act of prioritization. Conflating them produces a list that is too long to act on. That happens when the group name and the operating brand are treated as equally important, or when every well-known product name is assumed to need its own TLD.
## Which layer customers actually use
The answer is almost always the second layer, and occasionally the third.
A customer buying a product does not think about the holding company. They think about the brand that made it and, sometimes, the product name within that brand. The group name is an organizational fact, not a customer-facing identity. That does not make it irrelevant to onchain strategy, but it does place it lower in the priority order.
Operating brands are where customer trust accumulates. They are the names a person types into a search engine, says aloud to a voice assistant, or sends to a friend as a payment reference. A name that resolves in a wallet under `.yourbrand` will be used by a customer precisely because they already trust the mark it matches. For the same reason, a third party looking for a name to imitate would choose the operating brand before any other name in the group.
Product names occupy a narrower band. Where a product name has become independent, meaning the customer no longer needs the brand to recognize it, it may warrant its own TLD. Where the product name only works next to the brand, as a model line or a tier that follows the brand name, it does not. The test is simple: would a customer use this name alone, without the brand name, to identify the source of what they are buying?
There is a practical way to run that test without commissioning research. Look at how customers write to you. Support requests, search queries on your own sites and the wording of reviews show which name people reach for when nobody prompts them. If the product name appears alone in that material, it passes. If it always travels with the brand, it belongs under the brand's TLD as a name such as `product.yourbrand`, not at the top level.
## Which layer receives payments
The payment test is distinct from the customer-recognition test, and it often sharpens the priority order.
An onchain name can stand in for a wallet address: `pay.yourbrand` can receive a payment in the way an email address receives a message. This works in the wallets that support the registry's names, and coverage is partial and changes, so check [how payments to a name work](/onchain-tld-payments) before you build on it. The question of which name a payer would use to send funds is therefore operational. If the answer is the operating brand name, that name is a Tier 1 priority. If the answer is a product name, because the product is sold independently and buyers transact under that product's identity, that product name moves up in the order.
The group name rarely receives payments from external counterparties. Intercompany transactions inside the group use accounting references, not public-facing brand names. For onchain TLD purposes, the group name's payment relevance is low.
Where a brand runs a marketplace, a subscription service or a direct payment flow to end customers, the payment test is unambiguous. That brand's name is the one a payer would expect to see on a payment name, and so the one where a look-alike would do the most harm. Only the holder of a TLD can issue names under it, which is why holding the TLD is a control on that risk and holding a single name under someone else's TLD is not.
### The three layers side by side: who uses each name and who decides
The table below maps each layer to its primary users, its payment relevance and the party inside the group who typically owns the onchain decision. The last column is the one most teams neglect when building the priority list.
| Layer | Primary user | Payment relevance | Typical decision owner |
|---|---|---|---|
| Group name | Investors, regulators, press | Low | Group GC or CFO |
| Operating brand | Customers, partners, distributors | High | Brand IP lead or brand counsel |
| Product name | Customers (direct purchase) | Medium to high if sold independently | Brand marketing and IP jointly |
The decision owner matters because an onchain TLD does not behave like a domain registration that lapses if nobody renews it. On Freename, a TLD is recorded onchain as a token held in a wallet, and there is no annual renewal fee. Nothing forces a yearly review, and nothing tidies up a decision taken by the wrong team. That makes the decision closer to a trademark filing than to a domain renewal. It should be owned by whoever is accountable for the trademark portfolio, not delegated to a web team.
## Subsidiaries and local names
A group that operates across multiple countries will often have subsidiary names and local-market names that do not appear prominently at the group or brand level. These names deserve their own assessment, not a blanket assumption.
The relevant question for each subsidiary or local name is whether a customer in that market would use it as a payment or contact identifier independently of the main brand. A subsidiary that operates under its own name because the main brand is not licensed in that market, or because local regulation requires a separate entity, may have onchain exposure that the group name and the main brand do not. A holding subsidiary that exists only for tax or structural reasons does not.
### Local trading names
The legal name of a subsidiary and the name on its storefront are often different. The register of companies shows the first. Customers know the second. For this exercise only the second counts. A local entity whose legal name is the brand followed by a country and a corporate suffix adds nothing to the list: its customers say the brand. A local business that kept the name it had before it joined the group is a different case, and it is assessed exactly as an operating brand would be, in its own market.
### Translated and transliterated names
Names that have been adapted phonetically, or written in a non-Latin script, are a separate consideration. An onchain TLD is a string recorded with a token, and the characters a registry accepts depend on that registry. Where a local-script name is the customer-facing identity, and where transactions flow under that name, it belongs in the priority assessment regardless of its relationship to the parent brand. Where the local form is only used in advertising and customers pay under the Latin-script brand, it goes on the watch list.
The free [Namespace Exposure Score](/namespace-exposure-score) gives a structured first reading of how exposed a brand is onchain. It is a reasonable way to compare a local name with the main brand before committing time to either.
## Acquired brands and legacy names
Acquisitions produce the most complicated part of any group's name portfolio, and the part most likely to be underweighted in an onchain review.
When a group acquires a business, it acquires the brand equity that came with it. That equity includes the trust customers place in the acquired name. The trust does not move to the acquiring group's name, so any imitation would use the acquired name, not the acquirer's. The acquired brand may continue to operate independently under a transitional or permanent arrangement. It may be wound down gradually while its customers migrate. Either way, for as long as customers use and trust that name, it has onchain exposure.
Legacy names, the brands the group has discontinued but that remain in public memory, are a harder call. The test is whether a customer would still transact under that name. If the answer is yes, even at low volume, the name has residual onchain exposure. If the answer is no, the effort of securing a TLD for a name no one uses is not justified, and the name goes on the watch list.
Responsibility for an acquired brand's names is often unsettled when the deal closes. The acquiring group's IP team may not look at the acquired brand's onchain namespace until the integration review reaches it. Setting up a [namespace watch](/namespace-watch) on the acquired brand when the deal closes, instead of waiting for that review, closes the gap.
## Building the ordered list
With the three layers mapped and the customer and payment tests defined, the priority list is built by working through a fixed sequence. The steps below produce a ranked order for a group of any size.
Building the onchain TLD priority list
List all names the group carriesInclude the group name, every operating brand, every actively sold product name with independent customer recognition, every subsidiary trading name, and every acquired brand still in active use. Leave out internal project names, holding entities and discontinued brands with no remaining customer base.
Apply the customer testFor each name, ask: would a customer use this name alone to identify the source of a product or service? Names that pass move to the next step. Names that fail are removed from the priority list and kept on a watch list.
Apply the payment testFor each remaining name, ask: is this a name under which a customer would send or receive a payment? Names that pass are Tier 1. Names that pass the customer test but not the payment test are Tier 2.
Assess current onchain statusFor each Tier 1 and Tier 2 name, check whether a matching TLD already exists. No special access is needed for this step, since the registry record is public and can be checked by anyone on a block explorer. A name that is not yet registered can be registered by the group. A name that is already registered calls for a different path: acquisition or monitoring.
Assign a decision ownerMap each name to the last column of the three-layer table. Confirm that the person accountable for that trademark is the one who approves the onchain decision. A web or IT team does not acquire a TLD without IP sign-off.
Sequence by risk, not by brand sizeA smaller brand that receives direct customer payments may rank above a larger brand that does not. Order the list by the combination of customer recognition and payment flow, not by revenue or trademark filing count.
Set a review trigger for the watch listNames removed from the priority list are not forgotten. A change in how customers pay, a product launch under a watch-listed name, or the acquisition of a business that uses one of those names is a trigger to run the assessment again for that name.
### The method applied to an invented group
Consider a fictional consumer goods group. Its holding name is known to investors only. It has four operating brands, one of which sells by subscription directly to consumers while the other three sell through retailers. One of the retail brands has a product whose name customers use alone. The group also owns a local business that kept its original name, and a discontinued brand that older customers still remember.
The subscription brand passes both tests and is Tier 1: customers say its name and pay under it. The three retail brands pass the customer test only, because the retailer takes the payment, and are Tier 2. The independent product name passes the customer test and joins them. The local business is assessed in its own market: it takes payments from its customers directly, so it is Tier 1 there. The discontinued brand fails both tests and goes on the watch list, with the holding name beside it.
The result is two Tier 1 names, four Tier 2 names and two watch-listed names. The holding name, which heads the organization chart, sits at the bottom. That is the usual outcome, and it is the one a list built from the corporate register would never produce.
## One conversation for several names
A group with five operating brands and three major acquired brands does not need eight separate conversations about onchain TLDs. It needs one structured conversation that covers the full portfolio and produces a single ranked output.
The value of that single conversation is that it surfaces conflicts a name-by-name approach misses. Two brands in the same group may share a word. A legacy name may sound like an active product name. The group name may be contained in one of the operating brands. These overlaps matter onchain in a way they may not in a conventional trademark portfolio, because an onchain TLD is held as a single token. There is no filing in several classes and no division by territory. Whoever holds `.yourbrand` holds it for every use and every market at once, so two business units that could each have had their own registration in the trademark system have to share one TLD, or agree which of them issues names under it.
One conversation also sets the order of work. The Tier 1 names that are not yet registered are dealt with first, because registering them is the simplest step. Where a Tier 1 name is already registered by someone else, the choice is between [acquiring the TLD that matches the brand](/brand-namespace-recovery) and monitoring it, and that choice is easier to make when the whole list is on the table. A group that negotiates for one name while ignoring three others of equal rank has not reduced its exposure by much. Where an approach to a holder is decided, [a buy-side mandate](/buy-side-acquisition) lets the organization have the holder found and approached on its behalf.
The general counsel is usually the right convener of this conversation, because it requires both the IP knowledge that lives with the trademark team and the business authority to make decisions that will stand. Brand marketing can supply the evidence of what customers say. Finance can confirm which names sit in active payment flows. The IP lead executes.
## Who inside the group decides for each layer
The question of who decides is the one most often left to the end and the one that most often delays action. Clarifying it before the priority list is final saves time.
For the **group name**, the decision owner is at group level: the general counsel or the chief financial officer, depending on how the group has organized IP ownership. In many groups, a dedicated entity owns the intellectual property, brand names included, while the operating entities use those assets under license. Where that structure exists, the IP holding entity is the natural acquirer of an onchain TLD matching the group name. The operating companies are not.
For **operating brands**, the decision owner is the IP lead for that brand. That person knows the filing history, the enforcement posture and the commercial importance of the name. They are also the person who will fold an onchain TLD into the existing brand protection program. Which entity holds the TLD has to be settled at the same moment, because a TLD is held in a wallet and the wallet must be under the control of an identified legal entity. A multisignature wallet, which needs several approvals before anything moves, is the usual way to avoid one employee controlling a group asset alone.
For **product names**, the decision is shared. The IP lead can assess the trademark status. The commercial question, whether this product name will remain active and customer-facing for long enough to justify holding a TLD, is a marketing and business decision. Both parties need to be in the conversation.
Where a group separates corporate IP from brand IP, the authority to take onchain decisions should be written into the IP governance policy. Leaving it implicit produces gaps: a brand team that acts without IP authority, or an IP team that cannot act without a brand's agreement it cannot obtain. The page for [general counsel and brand protection teams](/brands-and-legal-teams) sets out how these questions usually reach a legal department.
## What goes wrong when the order follows the organization chart
Ranking the group name above the operating brands because it sits at the top of the organization chart is the most common error in a multi-brand onchain review. It is the old mistake of protecting what the register shows instead of what the customer knows.
A TLD that matches an operating brand and is held outside the group is a risk to manage. A name under it could be presented to customers as a payment name or as a point of contact. Acquiring the TLD is possible, but it takes a negotiation, a price and time, and none of the three can be planned for a name that was never on the list.
The group name is rarely the first name anyone would imitate, because it lacks the customer-facing trust that gives an imitation its effect. There are exceptions. A group whose holding name is also its main consumer brand has one name in two layers, and that name takes the higher rank. A group that raises money from the public under its holding name has a payment flow at group level, and the payment test applies to it like any other.
The opposite error exists too. A team that discovers onchain names can end up wanting a TLD for every product in the catalog. The customer test is what prevents that. Most product names fail it, and a name under the brand's TLD serves them well.
### Limits to keep in view
An onchain TLD does not replace anything in the DNS. Onchain names resolve outside the ICANN DNS root, so an ordinary browser does not open them without support, and wallet coverage is partial and changes. Your domain names, your trademark registrations and the dispute procedures attached to them stay the foundation of the brand's protection. The ordered list in this article sits beside that foundation.
The dispute procedures themselves do not carry over. The UDRP binds the registrants of domain names in the ICANN system through their registration agreements. It does not reach a token recorded on a blockchain. Trademark law still applies to how a name is used, with rules that vary by country, and your own counsel decides what that means for a given name. This is one more reason to rank names by actual exposure: the tools available afterward are fewer than in the DNS.
## Turning the list into a first step
Take the trademark schedule you already maintain and add three columns: layer, customer test, payment test. Fill them for the group name, every operating brand and the product names your customers know best. Most teams can do this in one working session with a colleague from marketing and one from finance, and the Tier 1 names are usually visible before the session ends.
Then check the status of the Tier 1 names. The free [Trademark Name Check](/trademark-tlds) is a simple way to start with a single name. For names that turn out to be registered by someone else, the decision between monitoring and an approach belongs to the decision owner named in your table.
Hush Partners is a private desk for onchain TLDs. An organization can mandate the desk to find and approach a holder, every exchange is covered by a standard mutual NDA, and the desk is reached through the contact form on the site.
## Questions people ask
### Does the legal entity that owns the trademark have to be the same entity that holds the onchain TLD?
Not necessarily, but there should be a clear and documented relationship between the two. Where an IP holding entity owns the trademarks and licenses them to operating companies, the same logic can apply to an onchain TLD: the token is held by the IP holding entity and used operationally by the brand. The holding structure should be deliberate, documented and consistent with the group's IP ownership policy. Your own counsel should confirm the appropriate entity for each acquisition.
### What happens to a product name TLD if the product is discontinued?
The TLD does not lapse. On Freename, a TLD is a token held in a wallet with no annual renewal fee, so it stays where it is until the holder transfers it. If a product is discontinued, the IP team decides whether to keep the TLD defensively, reuse it within the group, or sell it. Keeping it costs little. Letting it go without a plan means someone else may later hold a name that customers still associate with you.
### How does an onchain TLD differ from a conventional domain registration for the same brand name?
A conventional domain name is registered through a registrar for a period, must be renewed, and falls under ICANN's dispute resolution procedures, including the UDRP. An onchain TLD is a token held in a wallet, with no annual renewal fee on Freename and no ICANN oversight. It is also a whole TLD, not a name under one. The [comparison of an ICANN dotBrand and an onchain TLD](/dotbrand-vs-onchain-tld) covers the structural differences in detail.
### How often should the ordered list be reviewed?
Tie the review to events, not to the calendar. An acquisition, a disposal, a rebrand, the launch of a direct-to-customer payment flow or the retirement of a brand each changes the result of the customer test or the payment test for at least one name. A list reviewed at those moments stays accurate with very little effort.
### Is separating the TLD from the operating company a protection in itself?
Groups often hold intellectual property in a separate entity to centralize control and simplify licensing, and some also see it as a way to keep assets apart from operating liabilities. Whether that separation has any effect in an insolvency or a dispute depends on the country and on how the structure was set up. Treat it as a question for your own counsel, and do not assume that holding a token in a different entity changes the answer.