# Onchain TLDs and sports clubs: what to check
> A sector guide for sports clubs: 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-sports-clubs
Category: Brand protection
Published by Hush Partners.
---
A professional sports club carries something most commercial brands do not: a name that supporters feel they own. The badge, the abbreviation, the stadium nickname and the chant are all in daily use by people who never asked the club for permission and never will. When names can be created onchain from those same words, some of those people will want one. What matters for the club is who controls the TLD under which those names are issued.
This guide is for the commercial or legal director of a club or league who needs to understand where the exposure sits and what to do about it. Nearly all of it deals with what is particular to sport: the supporters, the match-day payments, the split of rights between club, league and player, and the partners who carry the club's name for a few seasons.
It ends with a checklist of eight checks, each with the function that owns it, which you can hand out the same day.
## Why sport is structurally different from a generic brand
Most consumer brands have one name, one legal entity and one brand protection team that owns the file. A professional sports organization rarely has any of the three cleanly.
The club's name belongs, in trademark terms, to the legal entity that registered it. That entity may be a holding company, a stadium company or an operating company, and those are often three separate things. The league owns rights in the competition name and sometimes in the event name. A player's name carries image rights that sit with the player and are often managed by a separate agency. Sponsors and licensees are permitted by contract to use the club's name in defined ways. None of these parties coordinates on onchain names by default, and the exposure collects in the gaps between them.
The name itself is also weaker, as a legal matter, than the passion around it suggests. Many clubs are named after a town, a district or a region, with a short descriptive word attached. A trademark protects a sign for given goods and services, and how far that protection reaches over a place name varies by country. The abbreviation on the scoreboard may be shared with a club in another sport or another country. A consumer brand with an invented name does not face this. A club often does, and it changes how confident the legal team can be about any claim over a string of letters.
Then there is the supporter dimension. A supporter's relationship with a club name is emotional before it is commercial. Supporters have always produced fanzines, forums and unofficial scarves that use the name. The same impulse produces onchain names and wallet identifiers. Most of that is harmless and some of it is not, and the club has no say over any of it unless it holds the TLD, because issuing names under a TLD is reserved to its holder.
Finally, a fixture concentrates a very large number of small payments into a few hours: tickets, food, merchandise, digital collectibles. Each one is a moment where a supporter trusts a name on a screen. An address that resembles the club's, shown at that moment, can be mistaken for an official channel, and news of a bad experience travels through a supporter base faster than through an ordinary customer base.
### What an onchain TLD is, in brief
An onchain TLD is a top-level name, such as `.yourbrand`, recorded on a blockchain instead of in the DNS root that ICANN coordinates. On the Freename registry, the TLD exists as a token sitting in a wallet, and the wallet that holds it is the only one able to create names such as `pay.yourbrand` beneath it. A Freename TLD carries no yearly renewal charge.
The limits matter as much. An ordinary browser does not open an onchain name without added support. For a supporter, the places where a Freename name does open are Bitcoin.com Wallet, MetaMask routed through Freename's resolver, and a desktop browser fitted with the Freename Web3 extension. That coverage is partial and it changes. For the club's public website, its email and its ticketing platform, the DNS is simply the better tool and will remain so. An onchain TLD matters where wallets and onchain payments are involved, and that is exactly where supporter products built on tokens operate. The [Namespace Exposure Score](/namespace-exposure-score) is a free tool that scores how exposed a brand is onchain, and it is a reasonable first measurement.
## The fan community as a namespace with real positive uses
Before the risks, the positive case deserves a fair hearing, because in sport it is stronger than in most sectors. A consumer rarely wants an address that ends in the name of a detergent. A supporter may well want one that ends in the name of the club.
Consider a fictional mid-sized professional club with a strong supporter culture, and assume it holds the TLD that matches its name, written here as `.yourbrand`. It could use `membership.yourbrand` as the wallet-facing address of its membership program. It could give recognised supporter groups a name each, such as `northstand.yourbrand` or `awaydays.yourbrand`. Licensed fan media could be told apart from unofficial channels by whether their address ends in `.yourbrand`. The academy could operate under `academy.yourbrand`. A supporter who receives a name under the club's TLD holds something with meaning: a link to the club that the club itself issued.
Three features of supporter culture make this more than a gimmick.
- **Belonging is already expressed through names.** Supporters identify by stand, by branch, by away-travel group and by the year they first held a season ticket. A namespace gives each of those a form the club has approved.
- **Supporter groups are organized.** Many have committees, membership rolls and their own merchandise. They are natural recipients of a name and natural partners in deciding who else gets one.
- **Authenticity is a constant question.** Supporters already ask whether an account, a ticket seller or a collectible is official. An ending that only the club can issue answers that question in one glance, wherever the name can be read.
The same enthusiasm has a second edge. A name that supporters would value is a name that a party unconnected to the club may also find worth holding. That is not a reason for alarm. It is the reason the club should know the status of the TLD before it designs any supporter product that touches a wallet.
For a sober view of which functions actually work, the page on [what is live on onchain TLDs](/whats-live) sets out each capability with its sources. Read it before promising supporters anything.
## Tickets, merchandise and memberships as payment moments
A club sells the same few things again and again to the same people: admission, membership, shirts and, increasingly, digital items. Each has its own way of going wrong when a name is involved.
### Tickets
A supporter who pays an unofficial seller through an address that looks like the club's will not blame the seller for long. The complaint arrives at the club's ticket office, and it arrives on a match day. The club may also owe exclusivity to an official ticketing partner, which turns a supporter problem into a contract problem.
An onchain payment can be directed to a name instead of a raw wallet address, so the name is what the supporter sees when paying. That helps when the club controls the name and hurts when it does not. `tickets.yourbrand` is unambiguous if the club holds `.yourbrand`. If another party holds the TLD, an address that reads the same way pays out to a wallet the club cannot see into, and an onchain transfer is generally not reversible once confirmed.
### Memberships
Membership renewal has three features that deserve attention together: a high level of trust, a regular payment rhythm and a reminder message that arrives every season in a familiar format. A supporter told to renew at `renew.yourbrand` will assume the instruction is official. The longer a supporter has been a member, the less likely they are to question a renewal notice. Loyalty lowers scrutiny, which is the reverse of how most consumer relationships work.
### Merchandise and digital items
Physical merchandise is already policed through licensing and anti-counterfeiting work, and none of that changes. Digital merchandise is different. Items sold as tokens involve a wallet address at every step: the first sale, the resale and any share of a resale that returns to the club or to a licensed creator. If one of those addresses is a name under a TLD the club does not hold, the club's licensing team has no contractual lever over it.
The page on [payments to a name](/onchain-tld-payments) explains the mechanics. One example of the tooling is [shaka](https://shaka.deal), an onchain payment router with which a payment link pays out to a name in place of a raw address. The parties agree the split and sign it onchain before any money moves, and the router passes funds through without holding them. For a club that shares revenue with a league, a creator or a charity partner, a split fixed in advance is the relevant feature.
## Club, league, competition and player names: who owns which
This is where the internal complexity of sport becomes a practical problem. Four kinds of name surround a club, and each has a different owner.
The club name is typically owned by the main trading entity or by a holding company above it. The league name is owned by the league. The name of a cup or tournament may belong to a governing body or to a commercial rights holder. A player's name belongs to the player, and image rights agreements usually give the club limited use of it for defined commercial purposes and a defined period.
Each of those names can exist as a TLD independently of the others. The club's legal team has no authority to act on the league's name, and the league may hold collective rights that restrict what a club can do commercially with its own. A player's representatives may reasonably wish to secure the player's name. So may someone with no connection to either.
A club's review therefore cannot be built around the club name alone. It needs to cover:
- The club's full legal name, its common short name and its abbreviation
- The nickname supporters use, where it is distinctive
- The stadium name, if it carries the club's name or a distinctive element of it
- Competition names the club uses under license, noted as belonging to someone else
- Brand extensions the club controls, such as an academy, a women's team or an esports team
Two points are specific to sport and easy to miss. The first is the league. Where the league sells rights collectively, it may regard anything that looks like a new category of digital rights as its own business, or at least as something to be coordinated. A club that acquires a TLD and launches a supporter namespace without checking the league's rules may find that the commercial program needs approval. The second is ownership change. Clubs are sold, merged into multi-club groups and restructured more often than their names change. The wallet that holds the TLD should belong to the entity that owns the trademarks, under controls that survive a change of directors. A multisignature wallet, which needs several approvals before anything moves, is the usual way to avoid dependence on one person.
Player names sit outside the club's authority unless the image rights agreement says otherwise, and a clause drafted with broadcast and print in mind is unlikely to mention onchain naming. Advisers who negotiate image rights can add the question to their standard review. Players also move between clubs, which is a strong argument for leaving a player's name with the player.
## Sponsors and licensees who use the club's name
A shirt sponsor has permission to associate its own brand with the club's name for a defined period. A kit manufacturer has a license to use the badge. A hospitality operator may have a license to use the stadium name. A stadium naming-rights partner has, for a time, put its own name on the building. Few of these agreements were drafted with onchain names in view.
This creates two distinct exposures. First, a partner may create names that combine its brand with the club's, in good faith, as part of an activation campaign, without anyone asking whether the license covers it. The contract is silent because nobody anticipated the question. Second, partnerships end. A sponsor changes, a kit deal moves to another manufacturer, the stadium takes a new name. An onchain name created during the partnership does not lapse because the contract did. Whether it can be withdrawn at all depends on the terms of the registry it was created on, and not on the sponsorship agreement.
Sport makes this sharper than it is elsewhere because partner turnover is built into the model. A club may carry a different shirt sponsor every few seasons and a long tail of regional partners that changes every year. Each cycle can leave names behind.
A clause in future agreements is necessary and is not sufficient, because it does nothing about names that already exist. The club also needs a view of what is in circulation. [Namespace Watch](/namespace-watch) is the desk's service for monitoring a brand's names onchain. For a club with many partner relationships, a standing watch is a more realistic control than asking each partner what it has created.
## Exposure by function inside the organization
Different parts of the club meet the question in different forms, and the right response differs with them. The table maps each function to its main exposure and to the kind of action that follows.
| Function | Primary exposure | Action type |
| --- | --- | --- |
| Legal and IP | Matching TLD held outside the club | Acquisition or monitoring |
| Commercial and sponsorship | Partner creates names outside its license | Contract clause; audit of agreements |
| Ticketing and retail | Payment names that resemble official ones | TLD control; rules for issued names |
| Digital and technology | Supporter apps display unofficial names | Architecture review; official names |
| Communications | Unofficial content attributed to the club | Monitoring; clear public statement |
| Player services | Player names outside the club's rights | Image rights clause review |
| Supporter liaison | Groups adopt names under another TLD | Dialogue; official names for groups |
The supporter liaison row has no equivalent in most sectors. The people most likely to adopt an unofficial name are the club's most committed supporters, acting out of loyalty. They should hear about the question from the club, in a conversation, before they hear about it from the legal department.
## A checklist of eight checks, with the function that owns each
The checks are ordered so that each one feeds the next. The first six gather facts and can run in parallel across functions. The last two are decisions and belong to whoever owns the file.
Onchain TLD checks for a sports organization
Write down every name the club has rights inRecord the legal name, short name, abbreviation, nickname, stadium name and the names of the academy, women's team and esports team. Mark competition names as held under license. Owner: legal.
Establish which of those names exist as onchain TLDsA registry record is public and anyone can check it on a block explorer. Record only whether each name exists as a TLD. Owner: legal, with digital.
Read partner agreements for silenceReview every active sponsorship and license for any wording on digital naming, onchain addresses or tokens. Flag those that say nothing, and note each expiry date. Owner: commercial, with legal sign-off.
Read image rights agreementsCheck whether any agreement gives the club rights in a player's name as a digital identifier. Flag the gap for the next renewal. Owner: player services, with legal.
Map the payment momentsGo through tickets, memberships, merchandise and digital items, and note where a supporter sees a name or an address when paying. Owner: ticketing, retail and technology.
Ask the leagueFind out whether the league's rules or collective agreements cover digital naming, and whether the league has reviewed its own names. Owner: commercial director or general counsel.
Decide, name by name, between acquiring and watchingWeigh how strongly supporters identify with the name and whether it appears at a payment moment. Owner: the holder of the file, on legal advice.
Write a one-page naming policyState which names the club will hold, who may receive a name under them, who approves each issue and what partner agreements must say from now on. Owner: legal drafts; commercial, digital and supporter liaison adopt.
Two practical notes. The second check asks only whether a TLD exists, and it should stop there: the record shows a wallet, and guessing at who stands behind a wallet is neither reliable nor useful. And the sixth check is the one most often skipped, because it means raising with the league a subject on which the club has no settled position. Raise it anyway. The league's answer changes what the seventh check can decide.
## The options and who should own the file
Once the seventh check produces a decision for each name, there are three paths.
**Hold the TLD from the outset.** If the TLD that matches the club's name does not yet exist, the club can obtain it from the registry. This gives the club the sole ability to issue names under it and the base for an official supporter namespace. It is the simplest position, and it is the only one that opens the positive uses described above. The absence of a renewal fee on a Freename TLD suits an organization that thinks in generations and whose name will outlast every current contract. The page on [trademark TLDs](/trademark-tlds) explains what a TLD matching a mark is, and holds the free Trademark Name Check form.
**Acquire the TLD from its holder.** If the TLD exists and is held elsewhere, the realistic route is a negotiated purchase. The UDRP, the dispute policy that registrants of ICANN domain names accept through their registration agreement, does not reach names recorded outside that system. What a trademark claim can achieve against the holder of an onchain TLD depends on the country and the facts, and that judgment belongs to your own counsel. A purchase, where the price is acceptable, is usually quicker and more certain. For a club on this path, the service that covers acquiring the onchain TLD matching a brand is [brand namespace recovery](/brand-namespace-recovery).
**Watch and review.** For names where acquisition is not proportionate, such as a competition name used only under license or the name of a newly signed player, monitoring is the appropriate position. It keeps the facts up to date so that the decision can be revisited when a contract renews or the squad changes.
### Who owns the file
Onchain naming sits where four functions meet: legal for trademarks and contracts, commercial for sponsorship and licensing, digital for wallets and payment flows, and communications or supporter liaison for the rules of a fan namespace. In most clubs none of them has a mandate for the whole.
The practical answer is one named owner with a small group to draw on. Where the main question is whether to acquire and under what contract terms, the owner is general counsel. Where the club already holds the TLD and the question is what to build, the owner is the commercial director, with legal approving the naming policy. In both cases the board should know that the file exists, because a TLD is an asset that will sit in a wallet and someone must be accountable for the keys.
A league has a slightly different file. Its own name and its competition names are its direct concern, and it is also the natural place for a common position that spares each member club from negotiating the same clauses separately. A league that settles its view early gives its clubs a clear answer to the sixth check.
## What a club can build once it holds its TLD
The defensive reasoning is sound, and it is half of the picture. A club that holds its TLD has something to build with, within the limits of where onchain names resolve.
**An official supporter layer.** Names under the club's TLD can go to members, season-ticket holders, recognised supporter groups and licensed media. The holder of `northstand.yourbrand` is inside the club's namespace because the club put them there, which is different from claiming allegiance in a display name. The club sets the criteria for issue. It should also read the registry's terms on whether an issued name can later be withdrawn before it promises anything about names tied to a membership that can lapse.
**Payment names for digital products.** In place of raw wallet addresses for digital merchandise, collectible releases or charity collections, the club can publish names such as `shop.yourbrand` or `foundation.yourbrand`. Supporters see an ending they recognise, and the club decides which wallet stands behind it.
**A place for partners inside the club's rules.** Instead of managing partner naming through contract clauses alone, the club can issue a name such as `partner.yourbrand` to a sponsor as part of the package, under the club's naming policy. That gives the commercial team something new to sell and gives the legal team a single set of rules. The sponsorship agreement should say what happens to the name when the term ends.
**A share of registration fees.** Freename operates a royalty program under which the holder of a TLD is paid part of every registration fee for names registered beneath it. The registry advertises that part as reaching up to half, and the registry's terms and activation conditions in force at the time govern it. For a club this is best read as a way to cover the cost of running a supporter namespace, and the program has a cost of its own: there is no annual renewal fee on the TLD, but taking part in the royalty program carries an annual cost set by the registry. Some TLDs were registered under earlier terms that include the program for life, and whether those terms pass to a club that buys such a TLD should be confirmed with the registry before closing. It is no substitute for a revenue forecast, and no figure should enter a budget before the terms have been read.
**Identities for automated services.** Clubs already run ticketing assistants and supporter chat services. ERC-8004, known as "Trustless Agents", is a draft Ethereum standard that sets out three registries for AI agents: an identity registry in which every agent is an ERC-721 token that points to its agent card, a reputation registry for feedback from parties that dealt with the agent, and a validation registry for independent checks of what it did. The text is still a draft and can change, and the way naming registries connect to it is not settled. It is a development to follow. A project should not be built on it yet.
What to do in which order after an acquisition is the subject of [post-transfer activation](/post-transfer-activation). The sequencing matters in sport: a supporter namespace launched in the close season, with supporter groups consulted first, lands very differently from one announced in the week of a derby.
## Start with the list of names and one accountable owner
The first step costs nothing and needs no outside help. Appoint the owner of the file, have legal produce the list of names from the first check, and establish which of them exist as onchain TLDs. A week of internal work gives the commercial and legal directors enough to decide whether the subject deserves a place on the board's agenda.
If the review shows that a TLD matching the club's name is held outside the club, and the club decides to explore a purchase, the approach is better made by an intermediary than by the club in its own name. This is the work Hush Partners does: a private desk for onchain TLDs that organizations mandate to find and approach a holder. A standard mutual NDA covers every exchange. A single named partner stays with the file from the first note through to closing, and closing takes place through onchain escrow on an aftermarket. The fee is a fixed amount, not a percentage, and only the client that gives the mandate is charged.
The page for [brands and legal teams](/brands-and-legal-teams) is written for general counsel and brand protection teams. The desk is reached through the [contact form](/contact).
## Questions people ask
### Does the club need to do anything if the matching TLD is not visibly in use?
A TLD that is not in visible use is still held, and its holder alone can issue names under it. Whether that calls for action depends on the checks above, mainly on whether the name appears at a payment moment. Watching is the proportionate minimum. Acquisition is a commercial decision, taken without haste.
### Does an earlier trademark give the club priority over the TLD?
Not by itself. A trademark registration is not recognised by an onchain registry as a prior claim, and no administrative procedure comparable to the UDRP covers onchain TLDs. Whether a court would act on a trademark claim depends on the jurisdiction, the goods and services covered and how the TLD is used. This is information and not advice: your own counsel decides the legal strategy.
### What happens to names already issued under a TLD when the club acquires it?
A transfer moves the TLD. Names that the seller itself holds under it can be transferred to the club at the same time, if the two sides agree, while names sold to third parties remain theirs. So establish what exists under the TLD, and who holds each name, before closing.
### Should a player's name be handled by the club or by the player's representatives?
By whoever holds the relevant rights, which in most cases is the player. Unless the image rights agreement clearly gives the club rights that extend to onchain naming, the player's representatives are the right party to act. The club's interest is narrower: that any use of the player's name inside the club's own commercial program stays within the agreed license.