# Running a market TLD for sport: who it serves and how
> For operators considering a TLD that names sport: who would hold a name under it, what they would use it for, and what running it involves.
Source: https://hush.partners/running-a-market-tld-for-sports-fans
Category: Acquiring
Published by Hush Partners.
---
A sector TLD built around sport sits in an unusual position. Unlike a brand TLD, which exists to serve one organization, a market TLD under a sport word exists to serve many: clubs, leagues, supporters' groups, volunteers, and the communities that form around them. That breadth is its opportunity and its complication. The operator does not use the namespace. The operator governs it, and what it returns depends almost entirely on whether others find it useful enough to register a name and keep using it.
This article is written for an operator, platform, or association in sport considering acquiring a TLD whose string is a generic sport word and issuing names to the constituency around it. It covers who would actually register a name, what they would use it for, how revenue models honestly in practice, and what running the TLD involves day to day. By the end you should be able to judge whether the demand is real enough to justify the investment, and what you would need to put in place before names go on sale.
The honest starting point is that demand under a generic sport word is real but uneven. Some groups have a clear reason to hold a name. Others would register once and then forget it. The sections that follow distinguish those groups carefully.
## Who would hold a name, and why
The practical population for a sport-word TLD breaks into three groups. Each has a different relationship to the namespace and a different reason to pay for a name.
| Holder type | Primary use | Likelihood of sustained use |
|---|---|---|
| Supporters' groups | Collective identity, group wallet, member contributions | High, where the group is active |
| Amateur clubs and leagues | Public presence, fee collection | Moderate, depends on digital confidence |
| Individual fans | Wallet alias, profile handle | Low to moderate |
**Supporters' groups** are the strongest group. An active supporters' group already has a name, a treasury, and a communications problem. Members scatter across chat apps and social platforms, money moves informally, and decisions require coordination among people who live in different places. A name under `.yoursector` gives the group a stable onchain address that does not belong to any single member, that can receive funds without anyone handing over a personal wallet address, and that persists when committee members change. That last point matters more than it sounds. When the person who set up the group's original accounts leaves, the accounts sometimes go with them. An onchain name held in a multisignature wallet (a wallet that requires agreement from more than one keyholder before anything moves) does not have that problem.
**Amateur clubs and leagues** are the second group. They are numerous and varied: junior football leagues, veterans' rugby sides, weekend cricket clubs, running groups that have grown into informal competitions. Their digital presence is often thin. Many rely on a free page on a social platform they do not control and a group chat for internal communication. A name under `.yoursector` is not going to replace either of those for most clubs, but it can serve as a payment address and a signal of intent. It says the club is organized enough to have its own onchain identity.
**Individual fans** are the weakest group. A fan who holds `theirname.yoursector` has something pleasing but not necessarily useful. Unless the name resolves in the tools they already use, the registration is mostly expressive. That is not worthless, because belonging has value, as the next section discusses. But you should not model individual fans as long-term active holders. Some will keep using the name. Most will let it go quiet unless it does something for them.
## Belonging as the primary reason for many registrations
The instinct when modelling a sport TLD is to focus on utility: what does the name do? For supporters' groups and clubs, utility is real and should lead any registration offer. But for a significant part of the market, especially individual fans and smaller groups, the reason to register is affiliation. The name says which corner of sport they are from.
This is not sentiment to be dismissed. Sport is one of the few sectors where people pay to display an allegiance that brings them no practical return: a scarf, a season card kept long after the season, a replica shirt from a year the team lost. An operator who frames a name under `.yoursector` as a lasting piece of onchain identity, something that ties a fan to the community, sits in their wallet, and points to the address they choose, is offering the same kind of object. The limit is that affiliation alone does not keep a name in use. The name needs to do something, even modestly, or the affiliation argument eventually wears thin.
Belonging in sport is also local and specific, and that shapes what a generic sport word can carry. A supporter does not belong to the sport in the abstract. They belong to a stand, a town, a travelling group, a five-a-side team that has played on the same evening for years. A name under `.yoursector` earns its place when it names that unit: the group, the team, the section of the ground. A name that only says "I like this sport" competes with every other way of saying so, most of them free.
The operator's job is to create enough utility that belonging and function reinforce each other. That means supporting wallet resolution, enabling payment links, and making it easy to build a lightweight public presence. The page on [what is live for onchain TLDs](/whats-live) lists what each of those capabilities actually does and where coverage is incomplete. Read it before you set expectations for your registrants.
## What a name concretely does for each group
### Supporters' groups
A supporters' group holding `groupname.yoursector` can do several practical things. It can publish a basic site to IPFS (the InterPlanetary File System, a distributed storage network where files are addressed by content instead of by server), reached through the name in browsers that support it. It can accept dues and donations through a payment link that pays out to the group's shared wallet instead of any individual's address. When a new treasurer takes over and the wallet changes, the name stays the same, so the forty places where the old details were written down do not need correcting. And a member who wants to confirm where contributions go can look the name up on a block explorer, a public tool that reads onchain records, without depending on a platform account that can be lost or suspended.
Onchain names sit outside the ICANN DNS root, which means an ordinary browser will not open one unless support has been added. Freename names [resolve in wallets](/onchain-tld-wallets), including Bitcoin.com Wallet and MetaMask through Freename's resolver, and desktop browsers reach them with the Freename Web3 extension. That coverage is partial and it changes, and you should say so clearly to registrants. A supporters' group whose members are not already using these tools will not benefit from resolution until they are. That is a real limitation.
### Amateur clubs and leagues
An amateur club's main practical use is payment. A club that runs a league needs to collect registration fees from teams, entry fees for tournaments, and contributions from members. Doing this in cash or through personal bank accounts creates friction and record-keeping problems. A name under `.yoursector` can point to a shared wallet, and a payment router such as [shaka](https://shaka.deal) lets a payment link pay out to that name in place of a raw address. Where the money is shared, for instance between the league and a venue, the parties agree the split and sign it onchain before any funds move. The router passes the funds on and does not hold them.
Consider a league of eight teams, each paying a registration fee every season. Its treasury problem is simple and persistent: who has paid, who holds the money, and what happens when the organizer steps down. A name does not remove the league's accounting or tax duties, which depend on the country and on the league's legal form. It does give the league one published address and a record that does not live in one person's banking app. That is specific to sport, because amateur sport has a chronic problem with informally managed money and the disputes that follow.
A league may also want a name for each of its member teams. Under the Freename registry only the holder of the TLD can issue names, so the league cannot do this alone. It asks you. Decide before names go on sale whether you will issue a batch of team names at a league's request, and under what conditions.
### Individual fans
For an individual fan, `theirname.yoursector` functions primarily as a wallet alias and a profile handle. It reduces the risk of mistyping a wallet address, a long string of characters where one wrong character can send funds to the wrong place for good. It works as a human-readable identity in the wallets and tools that support the TLD. Beyond that, its utility is bounded by resolution coverage.
An operator who is honest about this will frame individual fan names as identity and affiliation, not as full digital infrastructure. That framing is accurate, and it avoids the disappointment that follows an oversold product.
## Amateur clubs and their volunteers
Amateur sport runs on volunteers. The person who manages the club's finances is also the person who picks up the cones on Sunday morning. They do not have time to learn a new tool unless it solves a problem they already have.
This has a direct consequence for the operator. A name under `.yoursector` will not register itself. Unless registering is straightforward (a single page, a wallet, a payment, and done), volunteers will not complete the process. And unless the name does something visible within a few weeks of registration, it will be forgotten.
The operator's activation work is therefore not primarily technical. It is educational. A short guide that explains what the name does, how to set up a shared wallet, and how to publish a payment link takes ten minutes to read and saves an hour of confusion. Write it before the first name goes on sale, not after. The [Launch Roadmap](/activation-roadmap) tool on this site builds a launch roadmap for a newly acquired TLD, and this guide belongs early in it.
The positive version of this: volunteers talk to each other. If one club in a league finds that the name makes fee collection easier, others hear about it. Word of mouth in structured amateur sport moves through known networks (the association secretary, the regional committee meeting, the referees' group chat), and those networks are reachable by an operator who has relationships in the sector.
## Memberships, fees, and ticketing
Sport has structured money flows that few other sectors share: membership dues, match-day entry, tournament fees, travel levies, kit deposits. Most amateur sport handles these through a mix of bank transfers, cash, and informal agreements. Each one is a candidate for onchain payment, and a name under `.yoursector` is the address the payment goes to.
The clearest use is membership collection. A club that charges an annual membership fee can publish `clubname.yoursector` as the destination for that fee, with the amount and the split, if part of it goes to a governing body, settled in a payment router before the link is shared. Members pay to a name, not to a personal wallet. The treasurer can read on a block explorer which address paid and when. Matching an address to a member is still the treasurer's job, so the club needs a simple way to record which member uses which address.
Ticketing is harder. Onchain ticketing for amateur sport is a legitimate idea, but it requires every buyer to have a wallet and to know how to use it. For a match-day crowd made up of parents, neighbours and visiting supporters, that cannot be assumed, and a gate that turns people away is worse than a cash tin. An operator who positions the TLD as ticketing infrastructure for amateur clubs is ahead of where the tools are. The safer framing is that the name handles the treasury, and ticketing can follow if resolution and wallet use become broader.
The page on [payments to a name](/onchain-tld-payments) sets out what is supported, and it is the right reference to give a club treasurer who asks.
## The line between a generic sport word and a protected name
This is where legal counsel must be involved before any name goes on sale, and where an operator's rules need to be written precisely. What follows is information, not advice, and your own counsel decides.
A generic sport word, a string that describes a sport or a sporting activity, does not belong to any one organization. An operator who acquires `.yoursector` where the string is a common noun does not acquire rights over every club, league, or association active in that sport. The TLD is a namespace, not a certification mark.
The tension arises at the level of the name. Club names, crests, competition titles and the names of governing bodies are often registered trademarks, and even where they are not, they may be protected in other ways depending on the country. A name under `.yoursector` that is identical or confusingly similar to one of them may conflict with those rights. The UDRP (the Uniform Domain-Name Dispute-Resolution Policy, the dispute mechanism that binds registrants of names in ICANN-managed TLDs) does not apply to onchain names. That does not leave a rights holder without recourse. Trademark law still applies and can be invoked before national courts, with rules that vary by country, and the operator's own published process is the nearest and fastest route.
Sport makes this harder than most sectors for one reason: club names are built from generic parts. A town, a color, a word such as "united", "athletic" or "rovers". Many unrelated amateur clubs legitimately share those words with professional ones, and with each other. A rule that blocks every name resembling a professional club would block half your constituency. A rule that blocks none invites impersonation. The workable line is usually drawn around the full, distinctive name and around use: a village side registering the name it has played under for decades is in a different position from a stranger registering the exact name of a professional club and asking supporters for money.
The operator's rules must address this. At minimum, they should prohibit names that reproduce a club's word mark or a governing body's name without authorization, provide a clear challenge process for rights holders, and state what happens to a name found to breach the rules. Confirm with the registry what you can technically do to a name once it is issued, and write the rules to match. A remedy you promise and cannot apply is worse than none.
The same distinction decides which names you reserve before opening registration. Your own name and the names of the major rights holders in the sport should be reserved as a matter of course. Names that are common words in the sport (positions, actions, equipment terms) can generally be open to anyone. The exact trading names of professional clubs are the problem zone. Reserve them, or issue them only on evidence of authorization.
Supporters' groups sit in the middle of this line, and they deserve a rule of their own. A group's name very often contains the name of the club it follows. Some clubs welcome that, some tolerate it, and some object, particularly where money is collected under the name. You cannot settle that relationship for them. What you can do is ask a group, at registration, to state whether it is officially recognized by the club, and make clear in your rules that a name containing a club's name may be challenged by that club.
## The operator's role: rules, issuance, support, and disputes
Running a market TLD is not passive. Issuance is in your hands alone, and that control carries responsibility.
**Rules.** The operator publishes registration policies: who may register, what names are prohibited, what the challenge process is, and what happens when a registration is found to breach the rules. These are public documents, written before launch.
**Issuance.** A Freename TLD exists as a token recorded onchain, and whoever controls the wallet holding that token controls issuance. The operator decides whether to issue names to anyone, to restrict registration to verified members of a constituency such as affiliated leagues or recognized supporters' groups, or to require an application for names in sensitive categories. Each model carries a different administrative load. Open registration is the simplest to run. Restricted registration gives better control over what appears in the namespace but requires someone to process applications, and in sport that means someone who can tell a real club from a plausible invention.
**Support.** Registrants in amateur sport are not technical users. The support load will come from people who do not know what a wallet is, who registered a name and then lost access to the wallet that holds it, and who want to know why their name does not open in their browser. The operator needs written guidance for each of these, and a clear statement that wallet recovery is outside the operator's control: the registry record is public and can be checked, but a lost private key means a name nobody can manage.
**Disputes.** When a rights holder objects to a name, the operator needs a process. It should include a way to submit a complaint, a timeline for response, and criteria for the outcome. It does not need to replicate the UDRP in full, but it needs to exist and be published.
The wallet that holds the TLD deserves the same care you ask of clubs. If the token sits with one employee or one committee member, the whole namespace depends on that person. An association in particular should hold it in a multisignature wallet whose signers are officers by role, with a written procedure for replacing them. The page for [operators](/operators) describes the position of an organization that runs a market TLD as a namespace.
## Revenue from names, modelled honestly
Freename runs a royalty program for TLD holders. Each time a name is registered under the TLD, part of the registration fee goes to the holder. The share is advertised as reaching up to half, and both the registry's terms in force and its activation conditions apply. The TLD itself carries no annual renewal fee, but taking part in the royalty program has an annual cost set by the registry. Some TLDs were registered under earlier terms that cover the program for life, so confirm with the registry before closing whether those terms pass to a buyer.
The structure is therefore simple: revenue follows registrations. What the operator influences is demand, meaning how many clubs and groups register a name, and price: the holder of the TLD sets what a name costs and can charge a supporters' group, a club and an individual fan different amounts. The royalty share is governed by the registry's terms, so confirm it before you build any plan on it.
**Worked example.** Every figure here is an assumption made for illustration. A sport-word TLD launches with outreach to the amateur clubs of one regional association. The operator counts 400 clubs in that constituency. Assume that 60 of them register a name in the first year. Assume that each registration brings the TLD holder a royalty of USD 10. Royalties in year one are 60 times USD 10, which is USD 600. In year two, assume 30 further clubs register, a slower pace because the first outreach has already reached the most willing. Royalties in year two are 30 times USD 10, which is USD 300. Over two years, 90 of the 400 clubs hold a name and the operator has received USD 900. The example counts royalties on new registrations only and leaves out every operator cost, including the annual cost of the royalty program, which must be deducted.
| Period | Names registered | Royalty at USD 10 each |
|---|---|---|
| Year one | 60 | USD 600 |
| Year two | 30 | USD 300 |
| Two years | 90 | USD 900 |
These are not large numbers, and the example is not a forecast. Change the assumptions and the result changes in proportion, but the shape holds: amateur clubs are a finite list, each registers once, and the willing ones register first. A sport-word TLD run for royalty income alone is unlikely to justify the cost of acquisition and operation unless the constituency is very large and take-up is much higher than assumed here. Individual fans are the only group large enough to change the arithmetic, and they are the group with the weakest reason to register.
The honest model treats royalties as a secondary benefit and the TLD primarily as infrastructure for the operator's own purposes. It is a namespace that supports the operator's member clubs, gives those clubs a reason to engage with the operator's platform, and shows which clubs are active enough to hold and use a name. An association that already spends money on member services can judge the TLD against that budget, not against a revenue target.
To test your own assumptions before committing, the [Subname Revenue Calculator](/subname-revenue-calculator) estimates revenue from names issued under a TLD.
## What to check before acquiring the TLD
Acquiring a TLD is a single purchase, with no annual renewal of the TLD to budget for afterwards. Before committing, an operator should work through the following.
**Is the string genuinely generic?** A word that describes a sport or a sporting activity is one thing. A word that a governing body or a commercial entity has adopted as its trading name is another. Legal counsel should check the string against trademark registers in your key jurisdictions before any offer is made. A string that conflicts with a mark carries a risk that any [valuation of the TLD](/valuation) has to account for.
**Who holds the TLD?** The registry record is public, and anyone can check on a block explorer which wallet holds the token. The record shows a wallet, not a person. Finding and approaching the holder is a separate task, and it is what [buy-side acquisition](/buy-side-acquisition) covers: an organization mandates Hush Partners to find and approach a holder on its behalf.
**Have names already been issued?** Check whether names exist under the TLD, who they appear to serve, and whether any of them reproduce the name of a club or governing body. Names already sold to clubs, groups or fans stay with them when the TLD changes hands, and names the seller holds itself can come to you with the TLD if you both agree. Taking on a namespace with registrants means taking on their expectations.
**What does the transfer involve?** Closing takes place in onchain escrow on an aftermarket. Once the token is in your wallet, the public record shows it, and issuance is yours. Plan the wallet before closing, not after: which officers sign, and who replaces them. Putting the TLD to work from that point is the subject of [post-transfer activation](/post-transfer-activation).
**What are your obligations to the registry?** The registry's terms govern what a TLD holder can and cannot do. Read them. In particular, understand the activation conditions of the royalty program before you count on any royalty.
## A realistic first year
The first year of a sport-word TLD is mostly setup and outreach, with modest registrations even for an operator who is well connected in the sector.
First-year operating sequence for a sport-word TLD
Checks before acquisitionHave counsel clear the string against trademarks in the relevant jurisdictions. Check whether names have already been issued under the TLD. Confirm on a block explorer which wallet holds it.
Acquisition and transferAgree terms, close through onchain escrow, and confirm that the public record shows the TLD in your wallet. Verify before any public announcement.
Rules and governanceWrite the registration policy, the reserved and prohibited names, the challenge process and the support guides. Have counsel review them. Do not open registration until this is done.
Technical activationTest resolution in the wallets and browsers that support it, test a payment link to a name, and write down what does not work so that registrants are told.
Outreach before the seasonContact affiliated clubs and supporters' groups through existing channels, timed to the weeks when fees are collected. Lead with fee collection and a shared wallet, not with technology.
Open registration and monitoringOpen registration to the wider constituency. Watch the namespace for names that may conflict with a club's rights. Answer challenges within the timeline your rules state.
Review after a full seasonAsk registrants what they actually used the name for. Count the names that received a payment or point to a site. Decide from that evidence what to build next.
Timing matters more in sport than in most sectors. Clubs make their administrative decisions in a narrow window before the season starts, when fees are set and registrations with the league are due. An operator who opens registration mid-season asks treasurers to change a system that is already running, and most will decline until the following year. If the acquisition closes at the wrong point in the calendar, the sensible first year is preparation, with registration opening ahead of the next season.
A realistic expectation is close to the worked example above: a small share of the constituency, mostly clubs and supporters' groups already in your network. Individual fan registrations will be a minority. The measure of the year is not the count of names. It is how many of them did something visible for their holders, because those are the clubs that will bring the next ones.
## What you would do next
You are probably in one of two positions. Either the TLD exists and you are deciding whether to approach its holder, or you already hold it and are deciding whether to operate it actively.
In the first case, the practical step is to write down your constituency before you think about price: how many clubs and groups you can reach through channels you already have, what they pay each other during a season, and who on your side would answer their questions. If that list is short, the TLD will not lengthen it. If it holds up, a mandate to the desk is the way to have the holder found and approached. Every exchange with Hush Partners is covered by a standard mutual NDA, and one named partner follows the file from the first note to closing.
In the second case, the practical step is to choose one league or one federation of supporters' groups and run a single season with it. Write the rules, issue the names, publish the payment links, and count what was used at the end. A pilot of that size tells you more about demand in your corner of sport than any projection.
Either way, base the decision on a realistic read of your own constituency, not on general enthusiasm for the sector. The clubs and groups exist. Whether you can reach them, and whether what you build is useful enough to keep them, is the question to answer first.