# Onchain TLDs and luxury houses: what to check
> A sector guide for luxury houses: why a TLD matching the name matters here, where the exposure sits, and a short list of checks.
Source: https://hush.partners/onchain-tlds-and-luxury-houses
Category: Brand protection
Published by Hush Partners.
---
A luxury house's name is not a label. It is the primary asset: the thing that attaches provenance to an object, price to a material, and trust to a transaction. When that name exists as an onchain TLD, meaning a top-level domain recorded as a token on a public blockchain, the exposure is structural, not incidental. Whoever holds the token decides what is issued under that name, in a layer that operates outside the ICANN domain name system and outside the remedies that system provides.
This guide is for the IP director and the general counsel of a luxury group. It maps the exposure that is specific to the sector, identifies where the positive uses of the TLD sit, and gives a checklist that can be delegated the same day. It does not cover the brand protection principles that apply equally to any large organization; those are assumed. The focus throughout is what is different here.
After reading, you will have a picture of where the exposure sits by function, a basis for instructing internal teams and outside counsel, and enough context to weigh the options open to the house.
## Why onchain TLDs work differently from conventional domains
An onchain TLD is a string, `.yourbrand` for instance, whose ownership is recorded on a blockchain as a token held in a wallet. The holder is the only party who can issue names under it, such as `receipts.yourbrand` or `pay.yourbrand`. On the Freename registry, a TLD carries no annual renewal fee, so nothing lapses for want of a payment: whoever controls the wallet controls the TLD.
Resolution is partial. Without added support, the ordinary browser a client uses does not open an onchain name. Where Freename names do work is in Bitcoin.com Wallet, in MetaMask with the help of Freename's resolver, and in desktop browsers to which the Freename Web3 extension has been added. That coverage is incomplete and it changes. The limit matters for your assessment: what a TLD outside the house's hands can affect is concentrated in specific uses (payments, wallet identity, digital certificates) and not in open-web traffic.
Because these registries sit outside the ICANN root, the UDRP, the standard procedure for contesting a domain registered in bad faith in the conventional DNS, does not reach them. The remedies an IP team uses against a `.com` or country-code registration are not available. The page on [what a trademark TLD is](/trademark-tlds) sets out the basics, and the free [Namespace Exposure Score](/namespace-exposure-score) scores how exposed a brand is onchain.
## Why luxury is a different category of exposure
Most brand protection analysis treats a name as a reputational asset. In luxury, the name is also a transactional instrument. A customer paying for an order, receiving a certificate of authenticity, verifying a resale, or dealing with a concierge expects that the name they see is the house. The consequence of a false name is not merely confusion. It is a completed transaction: a payment sent to the wrong wallet, a certificate issued by a party with no authority, an object accompanied by a provenance document that looks authoritative.
The house's name carries weight because the house has spent decades, sometimes centuries, making it mean something. That accumulated signaling power is exactly what gives a matching TLD its interest for someone else. Where a technology brand can dismiss a lookalike name as unrelated, a luxury house often cannot: the name *is* the guarantee.
The secondary market compounds this. The market in pre-owned luxury goods is large and distributed, and much of it happens at a distance. Buyers cannot examine the object before purchase with the same ease as in a boutique. They rely on signals: the name attached to a certificate, the address a transfer comes from, the name on a payment link. A TLD that matches the house's name, in hands other than the house's, can carry signals the house never sent.
Heritage positioning adds a further dimension. A house that presents itself as the custodian of a tradition cannot easily argue that an onchain presence under its name is separate from that tradition. In the conventional DNS, the house holds its `.com` and the country-code registrations that matter. Clients will reasonably expect the same coherence wherever the name appears.
Price per object is the last difference. A mass-market brand faces many small incidents. A house faces few, each of which can concern a single piece of high value, bought by a client the house knows by name. One misdirected payment or one false certificate lands on a relationship, not on a statistic. That is why the review belongs with the people who protect the name, and not only with those who run the websites.
## Authenticity and provenance: the positive case for the house holding its TLD
Most IP review of onchain TLDs starts and ends with defense. That is necessary, but it leaves the positive case unexplored. A house that holds its own TLD controls a namespace from which it alone can issue names, and in this sector a name that a client can check has concrete value.
Consider what `certificate.yourbrand` or `archive.yourbrand` would mean if issued by the house itself. A name issued under a TLD the house holds is a statement: the TLD is the house's, the name is the house's, and the registry record is public, so anyone can check it on a block explorer. The owner of a piece can present the name at resale, and any party in the chain can check where it comes from without contacting the house's client service.
None of this waits on a future technology. The list of [capabilities that work today](/whats-live) includes names that resolve in supported wallets, payments to a name, and websites published under a TLD. A house that holds `.yourbrand` can issue `receipt.yourbrand` to a buyer, take a payment at `payments.yourbrand` through a payment router such as [shaka](https://shaka.deal), and publish a verification page at `verify.yourbrand` for browsers that support it. The honest limit is reach: a client with an ordinary browser and no supporting wallet sees none of it, so these names complement the house's website and boutiques and do not replace them.
The provenance use is particularly strong for watchmaking and jewelry, where resale markets are deep, objects are small, and paper certificates can be lost or falsified. A name attached to an object at the point of sale, issued under a TLD the house holds, gives the piece a reference that follows it from owner to owner and does not depend on a document staying in a drawer. A buyer does not have to trust the seller's paperwork; the buyer checks who issued the name.
The same logic applies to limited editions and archive pieces. A name such as `edition.yourbrand`, tied by the house to a specific series, creates a reference that resale platforms, auction houses and specialist dealers can check independently. The house does not need to run a new service desk for this. It needs to hold the TLD and to issue names from it under proper internal controls.
For a house that wants to accept onchain payments, the page on [payments to a name](/onchain-tld-payments) explains how a name under a TLD stands in for a raw wallet address, which is the part a client can read and recognize.
## Resale and certificates: the question of who may speak in the name of the house
The resale market involves many actors who are not the house: authorized resellers, auction houses, secondary platforms, private dealers, and the clients themselves. Each of them may, at some point, make claims about an object that invoke the house's authority. In the physical world, the house controls what it issues: a certificate, a service record, a letter of authenticity.
Onchain, the position depends entirely on who holds the TLD. If it is not the house, names under `.yourbrand` are issued by someone else, and a name that reads like a certificate or a payment address tells the reader nothing about the house's involvement. Your teams should know this well enough to recognize such a name when a client or a dealer forwards one.
A house that holds its own TLD is the only party who can issue names under it. That exclusivity is the key control. An authorized secondary partner can be given one name, `resale.yourbrand` for instance, and cannot create further names under the TLD without the house acting. The architecture enforces what contractual terms in the physical world only approximate, and a buyer can read the authorization in the registry instead of taking a letterhead on trust.
This matters for the gray market as much as for outright fraud. A dealer outside the authorized network who shows a name under `.yourbrand` next to a genuine object is implying that the house endorses the sale. When the house holds the TLD, the answer is simple and public: every name under `.yourbrand` was issued by the house, and a party the house has not named has none to show.
The resale question also reaches internal operations. Someone inside the group must be authorized to issue a name under the TLD, and someone else must be able to withdraw a partner's name when a contract ends. That is a governance decision at the meeting point of IT, brand and legal. It is easier to take before the TLD is in the house's hands than after, but it has to be taken in either case.
## Many maisons, one group: the multi-brand complexity
A luxury group typically holds several houses, each with its own heritage name, its own clientele, and often its own IP portfolio managed at the maison level. The onchain TLD question is therefore not one question for the group. It is one question per maison.
The exposure varies by maison, and you can reason about it before any search. A name that is also a common word or a family name in some language can be registered by a party with no thought of the house at all, which changes both the conversation and the legal analysis. A coined name with no other meaning leaves less room for coincidence. A maison that has already sold digital collectibles or accepted onchain payments has clients who look for it there; a maison that has done neither may still find its name registered. None of these is a prediction. They are reasons to check every maison instead of assuming the flagship is the only one concerned.
The group's IP team usually holds or coordinates the trademark registrations across all maisons. The onchain position is rarely as tidy: some names may be in outside hands, some unregistered, and some held by a team inside the group with no documented policy. Mapping the portfolio across all maisons is the first step, and it calls for a systematic check, not a case-by-case inquiry.
[Namespace Watch](/namespace-watch) is the service that monitors a brand's names onchain. For a group, the list of strings to watch is longer than for a single-brand organization: the exact trade name of each maison, its common variants and transliterations, archive names, the founder's name where the house trades on it, and product lines that have a recognition of their own.
Governance inside the group is the related issue. If a TLD sits at maison level, the wallet may be controlled by the maison's IT team, by a group digital function, or by a provider acting for the group. A multisignature wallet, one that requires more than one approved key to sign a transaction, is a standard precaution for an asset of this kind. Set the policy at group level and apply it to every maison, so that the smallest house is not the weakest point of the largest name.
## Discretion as a brand value: why a public dispute is costly
Some IP disputes are best resolved quietly. In luxury, almost all of them are. The name of the house is the product. A public dispute about who controls that name, in any forum, sends a signal the house would prefer not to send: that the name is contested, that part of its digital presence is not under its control, and that the house arrived second in a space it now claims.
In the conventional DNS, the house can turn to the UDRP or to the courts, and decisions under both are generally published. Onchain, there is no equivalent of the UDRP. A house that wants the TLD matching its name must either negotiate privately or go to a court with jurisdiction over the holder, if the holder can be identified at all. Blockchain records are public, but a wallet address does not, on its own, name the person behind it. Which courts would hear such a claim, and on what basis, varies by country and is for your own counsel to assess.
Private negotiation is usually the quieter route, and it keeps the matter out of any published decision. It also suits a house's habits: discretion is how it already handles client disputes, supplier matters and succession. At Hush Partners, a standard mutual NDA covers every exchange, so a conversation about a TLD starts under confidentiality and not after it.
Discretion also governs how the review is run inside the house. A luxury house in this position has one question a technology company might not weigh as heavily: what has been done under the name in the meantime. Even a single name issued under `.yourbrand` by someone else, whether or not it was used for anything harmful, speaks in a voice the house did not authorize. Establish that calmly, from the public record, before anyone drafts a letter.
## Exposure by function inside the organization
The question touches several functions, each with a different stake and a different first action. The table is a starting point for the briefing each of them receives. One event often lands on two rows at once: a payment link under a name such as `pay.yourbrand` that the house did not issue concerns finance and client relations together.
| Function | Exposure | First action |
| --- | --- | --- |
| IP and brand protection | Name used without authority; UDRP not available | Map every maison; decide on monitoring |
| General counsel | Issuance authority; liability questions if a client suffers a loss | Own the file; set internal policy |
| Digital and e-commerce | Payment and site names shown to clients | Audit names used in client communications |
| Communications | A public dispute becomes the story | No statement; hold a prepared line |
| IT and security | Wallet custody; lookalike names in phishing | Multisignature policy; alerting |
| Client relations | Clients forward certificates or payment requests they doubt | Brief advisers on what the house issues |
| After-sales and heritage | Service records and archive attributions cited at resale | List what the house certifies and how |
| Finance | Payments sent to addresses the house does not control | Review every onchain payment flow |
The audience page for [general counsel and brand protection teams](/brands-and-legal-teams) covers the same ground from the legal side.
## Checklist: eight checks and who owns each
Each check below can be handed to its owner with no more context than this article. The first five establish facts from public records. The last three are decisions.
Onchain TLD review for a luxury group: eight checks
Search for exact matchesRun the trade name of every maison in the group through the Freename registry and any other onchain registry your advisers cover. Record what you find and where. Owner: IP team, with outside counsel.
Search for variants and heritage namesInclude transliterations, founder names, archive names and product lines with a recognition of their own. Owner: IP team.
Score the exposureUse the free Namespace Exposure Score on the site to get a structured view of how exposed each name is onchain, and use it to order the work. Owner: brand protection manager.
Check which names exist under each TLDWhere a matching TLD is in outside hands, check whether names have been issued under it. A block explorer shows the registry record, which is public, to whoever carries out this check. Owner: IT security, briefed by IP.
Check what clients could actually meetEstablish whether any of those names resolve in a supported wallet, receive payments or carry a published site. This separates a dormant name from one a client could encounter. Owner: digital and IT teams.
Inventory what the group already holdsList any onchain TLD or name held by a maison, a subsidiary or an agency on its behalf. Confirm who controls each wallet and whether custody is documented. Owner: IT and finance, reporting to the general counsel.
Decide the route for each nameFor each string, choose between monitoring, registration where the name is free, and a private approach under NDA. Record the reason for each choice. Owner: general counsel, with the IP director.
Draft the issuance policyDefine who may issue a name under a TLD the house holds, by what process, and who may withdraw one. Cover certificates, payment names and partner names. Owner: general counsel, with digital, after-sales and finance.
## What holding the TLD lets the house do, beyond defense
Securing the TLD is the starting point. What the house can do once it holds `.yourbrand` deserves a separate answer, because that answer is not the same for a luxury house as for most organizations.
**A payment name clients can read.** A name issued under the TLD resolves, in supported wallets, to the address the house sets. A client or a partner can pay `payments.yourbrand` instead of copying a long hexadecimal address. For a private client settling a significant purchase at a distance, a name they recognize is a real safeguard against a mistyped or substituted address.
**Names for the places and services of the house.** A house is a set of addresses a client trusts: the flagship, the atelier, the after-sales workshop, the private salon. Names such as `atelier.yourbrand` or `service.yourbrand` extend that map. A service record or a restoration note published under a name of this kind carries the house's authority in the same way the stamp in a service booklet does, and can be checked by the next owner.
**One namespace across the client journey.** Purchase, certificate, service and authorized resale can each carry a name under the same TLD. The earlier sections describe these uses one by one. Their value together is coherence: a client learns once that anything ending in `.yourbrand` comes from the house, which is the lesson a house already teaches about its hallmarks and its packaging.
**Revenue from the namespace, if the house opens it.** Freename runs a royalty program that pays the holder of a TLD a share of the registration fee on names registered under it. The registry advertises that share at up to half, and its current terms and activation conditions apply. The program is not free to join: the TLD has no renewal fee, yet the registry sets an annual cost for taking part, and where a TLD was registered under earlier terms that include the program for life, the house should confirm with the registry before closing whether those terms pass to a buyer. Most houses will keep the namespace closed and issue names only internally, so this is a secondary point. It becomes relevant if the house offers names to members of a client circle or to partners in a controlled way.
**Identities for AI agents.** ERC-8004, "Trustless Agents", is a draft Ethereum standard in which each agent is an ERC-721 token pointing to its agent card. It is a draft and may change, and how naming registries connect to it is still evolving. A house that deploys an AI concierge will at some point have to answer how a client knows the agent speaks for the house. A name such as `concierge.yourbrand`, under a TLD only the house can issue from, is one coherent answer to keep in view.
**A planned first set of names.** The first question after a transfer is what to issue and in what order. The page on [post-transfer activation](/post-transfer-activation) describes putting a TLD to work once it is in the organization's wallet. For a house, restraint is part of the plan: a few names, each with a clear owner and a clear meaning to clients, serve the name better than a long list.
## Owning the file: options and the right structure
### The options, name by name
For each string the review turns up, the house has four routes, and they can differ from one maison to the next.
The first is to monitor and do nothing else. This fits a name that is dormant, or a string so generic that the house has no particular claim to it. It costs little, and its weakness is that it changes nothing about who can issue names.
The second applies where the string is free: the house registers it with the registry. The negotiation falls away, and what remains is custody and the issuance policy.
The third is a private approach to the holder with a view to acquiring the TLD. This is the route that matches the sector's preference for discretion, and it is the work described on the [brand namespace recovery](/brand-namespace-recovery) page: an organization mandates the desk to find and approach the holder, and closing runs through onchain escrow on an aftermarket.
The fourth is a legal route. It stays available in principle, depends on identifying the holder and on a forum with jurisdiction, and produces a public record. Your outside counsel decides whether it has a place. In practice it is weighed against the third route with the value of discretion on the scale.
### Who holds the file
The review spans IP, legal, digital, IT, after-sales and client operations. It needs one owner who can convene those functions without creating a visible project. In a group, that owner sits at group level, because a maison acting alone can reveal the interest of the whole group and because the custody policy must be the same everywhere.
One workable structure is a small circle: the IP director or the general counsel as the single internal owner, outside counsel for the legal analysis, and a specialist desk where a holder has to be approached. Each maison names one correspondent. Internal teams are briefed only on what they need in order to act on their own check.
### The next step
Hand out the eight checks with a return date, and ask for facts only: what exists, who inside the group holds what, which names a client could meet. With that in hand, the choice of route for each name is a short meeting. If a holder needs to be approached, Hush Partners takes the request through the contact form on the site, and one named partner follows the file from the first note to closing. The fee is a fixed amount, never a percentage, and it is charged only to the client who gives the mandate.
## Questions people ask
### Does the house need to act if the TLD is not being used for anything harmful?
Not necessarily at once, but the position does not resolve by itself. A Freename TLD carries no annual renewal fee, so there is no yearly deadline at which a holder must decide whether to keep it. A dormant TLD is a reason to monitor and to decide deliberately between waiting and approaching. It is not a reason for alarm, and it is not a closed question either.
### Can the house simply register its own name as a TLD if it is free?
Yes. If the string is not registered on the registry concerned, the house can register it there. The decisions on custody, issuance and activation still have to be taken, and each registry is a separate namespace, so a registration on one says nothing about another.
### How does the onchain TLD relate to the house's existing domain registrations?
They are separate namespaces. The house's `.com` and country-code names sit in the ICANN DNS and open in any browser, which is where the DNS is simply better for reaching the public. An onchain TLD resolves only where there is support, and it is not coordinated with ICANN. Holding one does not protect the other. The [comparison of an ICANN dotBrand and an onchain TLD](/dotbrand-vs-onchain-tld) sets the two side by side.
### Should each maison hold its own TLD, or the group?
There is no single answer. Holding at group level gives one custody policy and one team that knows the keys. Holding at maison level matches how the trademarks and the client relationship are often organized, and it simplifies matters if a maison is ever sold. Many groups will choose a group policy with the maison as the named beneficiary. Tax and corporate consequences vary by country, and your own counsel decides.