Onchain TLDs and publishers: what to check

A publication’s name is the product. The masthead, the program title and the byline each carry a trust that readers have built up over years. That trust is paid in attention and, more and more often, in money. When the name of a publication also exists as an onchain top-level domain (TLD), meaning a string recorded on a public blockchain, held as a token and able to carry names beneath it, the publisher faces a pattern of exposure that differs in kind from the one facing a manufacturer or a bank.

This guide is written for the general counsel of a publisher or broadcaster. It explains what is specific to the sector, maps the exposure by function inside the organization, and ends with a checklist that can be delegated the same day. A single short section is all this guide spends on how onchain TLDs work in general. The rest is about what those mechanics mean for a newsroom, a subscriptions desk and a group of titles.

After reading, you will know where the pressure points are, which teams own which part of the response, and what your options look like, including what holding the TLD would let you do beyond defense.

What an onchain TLD is, and why DNS tools do not reach it

Onchain TLDs sit outside the ICANN DNS root. On a registry such as Freename, the TLD exists as a token recorded on a blockchain and kept in a wallet, so the record lives on the chain and not in a registrar’s account. Whoever holds that token is the only party able to issue names beneath the TLD, for example subscribe.yourbrand or news.yourbrand. A Freename TLD carries no yearly renewal charge, so there is no expiry date to wait for.

Because these names resolve outside the DNS, an ordinary browser does not open them unaided. A reader can open a Freename name today in Bitcoin.com Wallet, in MetaMask when it goes through Freename’s resolver, or in a desktop browser once the Freename Web3 extension has been added. That coverage is partial and it changes. Your website, your apps and your email stay on the DNS, and for reaching a mass audience the DNS is simply better. The exposure described here sits elsewhere: in payments sent to a name, in identities given to AI agents, and in what a wallet displays.

The tools your brand protection team uses for conventional domains, such as the UDRP and registrar takedown procedures, were built for the DNS and do not extend to this layer. The registry record is public and anyone can check it on a block explorer, but there is no equivalent procedure to file. The Namespace Exposure Score, a free tool on the Hush Partners site, scores how exposed a brand is onchain and gives a first read.

Why publishers are different from other brand owners

Most brand owners worry that someone might confuse a third party’s product with their own. Publishers have that concern and three others that few sectors share in the same form.

The name signals authenticity, not only origin. When a reader pays for a subscription, the publication’s name is the main guarantee that the journalism behind the paywall is genuine. A manufacturer’s brand guarantees a physical product, and the buyer can inspect the product. A publication’s brand guarantees that the content was produced under editorial standards the reader cannot verify in advance. The name has to do more work.

The byline carries trust alongside the masthead. A publication’s value sits in its title, and also in the names of the people who write and present under it. A TLD matching the publication could carry names such as editorial.yourbrand or newsdesk.yourbrand, and a reader, a source or a counterparty who meets such a name will tend to read it as an institutional address. Reporters and freelancers are not the security team. An individual contributor is unlikely to know what an onchain name is, let alone to spot one that borrows the title.

Subscriptions are a frequent payment moment. A publication that runs a paywall or a membership model collects a large number of small payments under its name. Each one is a moment at which a reader confirms who is being paid. A payment made to an onchain name is generally final once confirmed, and a name that reads correctly is harder for a reader to question than a misspelled web address.

The output is quoted, summarized and passed on by others. A manufacturer’s product reaches the customer in a box. A publisher’s product reaches most people second hand, through aggregators, quotations, clips and, more and more, software that summarizes it. Each relay drops context and keeps the name. The further the content travels from your own site, the more the name alone has to carry.

Few sectors combine all four: a high volume of small payments tied to a name, an identity layer made of individual bylines, a product that travels mostly through third parties, and a brand whose whole value is that readers believe what appears under it.

Mastheads and program titles as trusted names

A masthead is more than a trademark in the usual sense. It is a promise about what the reader will find on the other side of the link. That promise is what a reader pays for, what an advertiser buys against, and what an editor defends. For broadcasters, the program title plays the same role: viewers and listeners tie a title to a set of editorial judgments about what is included and how it is presented.

Both are valuable because the value is intangible and granted in advance. A counterfeit physical product fails on inspection. A counterfeit editorial identity may never be inspected at all, because the reader trusts the name enough not to look further.

On the onchain layer, the masthead works as the anchor of a namespace. If the TLD that matches the title were held outside the organization, the holder, and nobody else, would decide which names exist beneath it. Those names could appear in wallets, in payment flows and in records that describe AI agents. The publication would have no say in any of it.

Program titles deserve the same attention, in particular where a title is tied to one presenter. A name such as presenter.yourbrand follows the pattern a broadcaster already uses when it presents its talent, which is why an audience would find it plausible.

Groups with many titles

A media group rarely has one name to check. It has a parent brand that readers may never see, a set of mastheads that readers know well, regional editions, newsletters, podcast series, events and studio imprints. The trust sits with the titles, not with the holding company, so the review starts from the titles.

Three situations are particular to groups. Acquired titles often keep their own trademarks, registered by a former owner and assigned at some later point, and the chain of title should be confirmed before anyone relies on it. Closed or merged titles keep their reputation long after the last edition, and an archive under a retired masthead still attracts trust. Licensed formats and joint ventures raise a question of standing: if a program runs under a format licensed from another owner, the license decides who may act on the name, and it may not be you.

Have the IP team list every name that an audience trusts, with its trademark status and its owner inside the group, and run each through the Trademark Name Check. Do this before assuming the question is limited to the main mark.

Authenticity of content and of the journalists behind it

Editorial trust rests on two claims that a reader takes on faith: that the content was produced under the standards of a named publication, and that the journalist credited with it is who the byline says. Both claims can be echoed on the onchain layer by a name.

Consider a name that pairs a reporter’s surname with the title, such as surname.yourbrand. Where it appears, in a wallet, in the description of an AI agent or in a payment link, it implies that the institution stands behind it. The journalist whose name is used would not be told. Nor would the publication. This is a scenario, described so that it can be recognized, and nothing here suggests it has occurred for any particular title.

Provenance and archives

Content provenance, meaning technical methods that attach a verifiable statement of origin to an article, an image or a clip, is an area in which publishers have an obvious interest. Where a publisher plans to tie provenance statements to onchain identifiers, the namespace those identifiers sit in should be one the publisher controls. A statement of origin that points to a name controlled by someone else proves less than it appears to.

The same reasoning applies to archives. An archive is the part of a publication most often cited by others, and the part where a small alteration matters most. If archive records are ever referenced through onchain names, those names should sit under a TLD the publication holds, so that nobody else can issue a name beside them that looks like part of the archive.

Channels that sources and readers rely on

Newsrooms publish named channels for tips, corrections and complaints. People use them at moments when they are trusting the title with something that matters to them. A name such as tips.yourbrand would look like one of those channels to someone who has never heard of onchain names. The practical answer is editorial, not technical: state in one fixed, well-known place which channels are official, and keep that statement current.

Monitoring helps as well. The Namespace Watch service monitors the names of a brand onchain. Monitoring does not change who holds a TLD, but it replaces assumption with observation.

Subscriptions and paywalls as payment moments

A reader at a paywall has already decided that the name in front of them deserves payment. For a publisher, that is the most valuable moment in the commercial relationship, and it is repeated at every renewal, gift subscription and one-off purchase.

Onchain payments add a new form of that moment. A payment can be addressed to a name in place of a long wallet address. If subscribe.yourbrand existed under a TLD held outside the organization, a payment sent to it would go wherever its holder had pointed it. The reader would see a confirmation. Nothing on the screen would say that the payee was not the publication, because the name would read correctly.

The page on payments to a name explains how this kind of routing works. The point for a legal team is that the name is the control, not the address behind it. A reader who is used to paying a name does not compare the underlying address each time, in the same way that nobody reads the account number on a recurring card payment.

Two features of media make this sharper than in other sectors. The first is that payment models are varied and often informal: tips to a presenter, a contribution to fund an investigation, a donation to a non-profit newsroom, a ticket to a live recording. Each is presented under a different name, and readers do not expect them to look identical. The second is that media groups commonly rely on outside platforms to collect money, so the reader is already used to paying the publication through something that is not the publication’s own site.

This matters only to the extent that your audience pays, or will pay, from a wallet. For many titles that share is small. The audit in the checklist below establishes the facts for your own titles before any conclusion is drawn.

AI agents that summarize or speak in a publication’s name

Software agents now summarize, curate and redistribute published work. Some are run by publishers. Others are run by third parties that aggregate or comment on what publishers produce. Both raise a naming question: when an agent says where its words come from, what does it point to?

One attempt to give agents a verifiable identity is ERC-8004, known as “Trustless Agents”. It is a draft Ethereum standard, and a draft may change. Its design rests on three registries. The identity registry represents each agent as an ERC-721 token that points to the agent’s card, a file describing the agent. The reputation registry collects feedback from those the agent has worked with. Independent checks of what an agent has produced are recorded in the validation registry, the last of the three. The way naming registries connect to this design is still evolving, so nothing here should be read as settled practice.

The direction is what matters to a publisher. If agents come to be identified by names, an agent presented as summary.yourbrand under a TLD held outside the organization would look like the publication’s own. A reader, an advertiser or another agent would have little means of telling the difference.

The editorial exposure is distinct from the payment exposure. A summary is an editorial act. It selects, compresses and sometimes gets things wrong. When a summary circulates under the title’s name, its errors are attributed to the newsroom, and so are its omissions and its tone. For a manufacturer, an unauthorized agent is a customer service problem. For a publisher, it touches the standards the title is known for, and the correction process has no way to reach text the newsroom never wrote.

There is a second, quieter issue. Publishers license content to others, and those agreements usually say how the title must be credited. An agent that speaks under a name resembling the title blurs the line between licensed use, fair quotation and something else. Legal teams that are drafting or renewing licensing terms can address how licensees may name agents that draw on the content.

Publications that plan to run their own agents, for reader questions, content delivery or subscription support, have a design decision to make early: under which namespace will those agents be named, and does the organization hold it?

Exposure by function inside the organization

The exposure is not spread evenly. Each function sees a different part of it, and each has a first question it can answer without outside help.

No single function owns the whole question. Legal frames the trademark position and the options. Editorial has to understand what a name beneath the title means for bylines and corrections. Commerce audits payment flows. Technology checks whether its own plans rest on a namespace the group does not hold. Communications needs one agreed line for readers, because a reader’s question will reach the audience desk long before it reaches the legal department.

One point is particular to media: the separation between the editorial and commercial sides. In many organizations the newsroom does not take instructions from the business, and the business does not speak for the newsroom. A file that touches bylines, tip lines and subscriptions crosses that line. Decide at the start who may ask the newsroom for information, and through whom, so that the review does not stall on a question of internal protocol.

Ten checks to run, with the owner of each

Each check below can be handed to its owner as written. None requires contact with anyone outside the organization.

1. Check the mastheadEstablish whether the masthead, and each common variant of it, exists as an onchain TLD. The free Trademark Name Check on the Hush Partners site is one place to start. Owner: IP and brand protection.
2. Extend the check to program titles and secondary brandsCover active program titles, newsletters, podcast series, imprints and retired mastheads that still carry an archive. Owner: IP and brand protection, with input from editorial.
3. Confirm who owns each name inside the groupFor acquired titles, licensed formats and joint ventures, confirm which entity holds the trademark and who has standing to act on it. Owner: legal.
4. Audit wallet-based payment flowsList every flow, including tips, donations and events, in which a reader can pay from a wallet. Note which name is shown to the reader at the payment moment. Owner: subscriptions and finance, with technology.
5. Map planned AI agentsList every agent the group runs or plans to run under a title, and the name each is expected to carry. Owner: product and technology, with legal sign-off.
6. Review provenance and archive plansWhere content provenance or archive records are to be tied to onchain identifiers, record which namespace those identifiers use and who controls it. Owner: technology, with editorial review.
7. Review bylines and official channelsConfirm that the list of official tip, correction and contact channels is published in one place. Check what contributor contracts say about the use of a contributor's name. Owner: editorial, with legal.
8. Score the exposureRun the Namespace Exposure Score for each main title and file the result with the review. Owner: legal and IP.
9. Set a monitoring baselineFor any title that exists as a TLD outside the group, record what can be observed in the public registry record and decide how often it is reviewed. Owner: brand protection.
10. Decide the path and record itChoose between monitoring, a mandated approach and activation, and record the reasoning. Owner: general counsel.

The first three checks are desk work for one person. Checks four to seven depend on other departments and take longer, mostly because the answers sit in project plans and supplier contracts that the legal team does not see every day.

The options and who should own the file

Once the checks are complete, the organization has three broad options. They are not mutually exclusive, and the choice depends on what the checks found.

Monitor. Where a title exists as a TLD outside the group and the checks show no wallet payments, no agent plans and no provenance work, monitoring is a defensible position. It needs a named owner and a review cadence. Monitoring without an owner is only an assumption that nothing will change.

Acquire. Where the checks show real exposure, or where the group has plans that depend on the namespace, the usual next step is a quiet approach to whoever holds the TLD. The UDRP does not apply, so the route is a negotiation. Brand namespace recovery is the service that covers acquiring the onchain TLD matching a brand. An organization can mandate Hush Partners to find and approach the holder, and every exchange is covered by a standard mutual NDA.

Activate. Where the group holds the TLD, or acquires it, the question moves from defense to use. The next section covers that.

The file should sit with the general counsel. The decisions that follow, whether to approach a holder, how to structure an acquisition and what to do with the TLD afterward, all have trademark and contract dimensions. In a group, there is also a question of level: a file opened by one title’s legal team may cut across a sister title with a similar name. Opening it at group level avoids two parts of the same organization working on the same name without knowing it.

There is a media-specific reason for discretion as well. A publisher’s interest in a name is itself a story, and newsrooms, including your own, are good at finding stories. Keep the circle small.

What holding the TLD lets a publisher do

Defense is a sufficient reason to hold a TLD. For a publisher there are also uses, and it helps to set them out plainly, with their limits.

Payment names that carry the masthead. A name such as subscribe.yourbrand that pays out to the publication’s own wallet shows the reader the title at the payment moment, in place of a string of characters. Where revenue is shared, for example between a title and a freelance contributor or a co-producer, a payment router such as shaka lets a payment link pay out to a name, with the split between the parties agreed and signed onchain before any funds move. It routes the funds without holding them.

Names for journalists and contributors. Under its own TLD, a publication can issue one name per journalist, in the form surname.yourbrand. Since issuing names is reserved to the TLD’s holder, a name of that form can only have come from the publication. This is the mirror image of the exposure described earlier. It also raises questions that only a publisher has: what happens to the name when a journalist leaves, whether freelancers receive one, and whether the name implies employment. Settle these in contributor terms before the first name is issued.

Agents named under the title. A publication that runs its own agents can name them under its own TLD, so that an agent’s stated affiliation and the namespace it sits in match. Agent identity standards are still in draft, so treat this as a design choice and not as a finished feature. The page on what is live lists every capability of onchain TLDs that works, with sources, and is the reference to check before any plan is approved.

Provenance and archive identifiers. Identifiers issued under a TLD the publication holds do not depend on the continued cooperation of anyone else. For an archive meant to last decades, that independence is the point.

A share of registration fees. Freename runs a royalty program. Under it, when someone registers a name beneath a TLD, part of the registration fee goes to that TLD’s holder. Freename advertises that part as reaching up to half of the fee, and what a masthead’s holder actually receives turns on the registry’s terms in force and on its activation conditions. Taking part is not free of cost either: the TLD itself has no annual renewal fee, but 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 publisher that buys the TLD is a point to confirm with the registry before closing. For a publisher this is a side effect, not a business case. Whether to open registration to readers or members at all is an editorial question first, since every name issued under the masthead borrows its standing.

The limits are the same as for any onchain name. Resolution is partial, most readers will never type one of these names, and none of this replaces the website. The uses above matter for the share of the audience and the counterparties that work from wallets and agents.

Post-transfer activation is the service that covers putting a TLD to work after a transfer, and the free Launch Roadmap tool builds a launch plan for a newly acquired TLD.

For a concrete next step, send checks one to three to your IP lead and ask for the list of titles, their trademark owners and the result of each name check. That list decides whether the remaining checks are needed and for which titles. If you want a general view of how files of this kind run for legal teams, the page for brands and legal teams is the place to read first.

Questions people ask

Does a trademark give automatic rights over the matching onchain TLD?

No. An onchain TLD is governed by the terms of its registry, and the UDRP does not apply to it. A registered trademark supports your position in a negotiation and may support other remedies depending on the country and the facts, but it does not by itself entitle you to the TLD. Your own counsel decides which remedies are available to you.

Can a competitor register names under a TLD that matches our masthead?

Not on its own. Issuing names beneath a TLD is reserved to its holder. A rival title cannot add names to a TLD it does not hold. The question that matters is therefore who holds the TLD, not who might try to register beneath it.

Does our website have to move if we hold the TLD?

No. The website, the apps and email stay on the DNS, which every browser resolves. An onchain TLD is used alongside the DNS for the purposes where it works, such as wallet payments and names for agents. It is an addition to the masthead’s presence, not a replacement for any part of it.

What about names already issued under the TLD?

The public registry record shows what exists beneath a TLD. Names that the seller itself holds beneath the TLD can be transferred along with it if the two sides agree, while names already sold to third parties remain with those third parties, so establish which is which before a negotiation starts and not after. Ask whoever handles the acquisition to confirm it in writing as part of the file.

Should each title in a group hold its own TLD?

It depends on where the trust sits. If readers know the titles and not the parent, the titles are the names to consider, one by one, in the order the checklist produces. If the group trades under one name across all its output, that name comes first. Either way, hold what is acquired in a group entity, so that the sale of a single title does not carry off a name the others depend on.