Onchain TLDs and pharmaceutical companies: what to check

Pharmaceutical brand protection teams already run monitoring programs for conventional domain names, social media impersonation and gray-market sales sites. Onchain top-level domains (TLDs recorded as tokens on a public blockchain, outside the ICANN DNS root) are often missing from that standard sweep. They sit in a different part of the namespace, they resolve differently, and the enforcement paths that work in the ICANN system do not map cleanly onto them. That gap is the subject of this guide.

The mechanics are short. On a registry such as Freename, the TLD itself (the string after the dot) is a token that sits in a wallet, and nobody but the holder of that token can issue names under it, for example verify.yourbrand or order.yourbrand. Because these names resolve outside the ICANN DNS root, an ordinary browser does not open them without a supporting wallet or extension, and that support is partial and changes over time. A brand protection analyst can check the registry record for any such TLD on a block explorer, since that record is public.

The reason this matters more in pharma than in most sectors comes down to one word: harm. A name that misleads a patient is a patient-safety problem before it is a brand problem, and its consequences reach well beyond the trademark counsel’s desk. After reading this guide, you will be able to map the exposure across your portfolio, assign the checks to the right internal functions, and make a decision about ownership that you can explain to your board.

Why pharma is not a generic brand-protection problem

Most brand-protection work starts from the same concern: someone holds a name that looks like ours, and we want it taken down or acquired. In pharma, three structural features make that framing insufficient.

The first is the depth of the product portfolio. A consumer goods company might protect one master brand. A pharmaceutical organization protects a corporate name, a long list of product brands, combination product names, device brands and the names of digital health platforms. Each one is a string that could exist as an onchain TLD in someone else’s wallet.

The second is the severity of the downstream harm. When a name in an ordinary consumer sector is misused, the damage is reputational and financial. When a name in pharma is used to direct a patient to a falsified or diverted product, the damage can be physical. The credibility that a brand name lends to a counterfeit is exactly what makes the counterfeit dangerous.

The third is the density of the trust chain. A patient rarely deals with the manufacturer. They deal with a prescriber, a pharmacist, a distributor or an online channel. Each of those intermediaries makes trust judgments, often quickly, and a credible-looking name at any point in that chain can distort the judgment. An onchain name that accepts payment for product described as official is the kind of artifact that sits just outside the reach of conventional monitoring.

Taken together, these features make the exposure wider than in most sectors, the cost of a gap higher, and the coordination needed to close it broader than trademark alone. To see how the exposure scores for your own names, the Namespace Exposure Score is a reasonable place to start.

The portfolio problem: every product name is a candidate

Trademark teams in pharma are used to long watch lists: filings across many countries, sound-alike watches, look-alike domain registrations. Onchain TLDs add a dimension that does not follow the logic of the second-level domain disputes those teams know.

In the DNS, the familiar pattern is a third party registering yourbrand under an existing extension. In the onchain namespace, a third party can hold .yourbrand itself, the whole extension. Whoever holds it can issue authentic.yourbrand, refills.yourbrand or verify.yourbrand, and decides what each of those names points to. That is a different order of control from one second-level domain.

So the check does not stop at the corporate name. It covers:

• Flagship product brands. These are the names patients and prescribers ask for. They carry the most trust and therefore the most exposure.
• Brands close to a generic name. A product whose brand name resembles the non-proprietary name of its active substance carries added confusion risk, because patients and pharmacists already hear both.
• Digital health and companion app brands. If the organization runs a patient-support app under its own name, that name is in scope.
• Legacy brands. A product that has lost exclusivity and left active promotion still carries equity and trust. It may be more exposed, not less, because monitoring tends to drop off when commercial priority shifts.
• Pipeline names. A name that has appeared in public communications before launch can be taken up by a third party before the brand is established. The check extends to every name the organization has publicly tied to a development program.

One medicine, several names

Pharma has a complication that few other sectors share: the same medicine is often sold under different brand names in different countries, and a name cleared for one market may have been rejected in another. The list to check is therefore the list of names per market, not the list of products. Regulatory affairs usually holds that list in its most complete form, which is one reason the function belongs in this review from the start.

Drug naming also has its own culture of similarity. Product names are screened before approval so that they are not confused with one another in speech or handwriting. The onchain namespace applies no such screen. A string one letter away from a product name can exist as a TLD beside the exact match, so the watch list should hold the close variants your team already tracks for prescribing-error reasons, not only the registered spelling.

Each of these names can be submitted through the free Trademark Name Check. For names that need watching over time, Namespace Watch is the service that monitors a brand’s names onchain.

A credible name is a patient-safety matter

Counterfeit and diverted pharmaceutical products depend on one thing above all: the appearance of legitimacy. Packaging, labeling and channel positioning all contribute to it. So does the name that a transaction or a website shows to a patient or a pharmacist.

An onchain name can stand in for a wallet address. With an onchain payment router such as shaka, a payment link can pay out to a name where it would otherwise show a raw address. A payment request that reads pay.yourbrand looks very different from one that shows a long string of characters. That difference in presentation is where the exposure lies.

Consider a fictional scenario. A third party holds .yourbrand, and a name under it leads to a page that resembles a product verification page. A patient who reaches that page sees the product name in the address and a confirmation on the screen. Nothing in what they see tells them that the manufacturer has no part in it.

The pattern behind the scenario is old. A credible identifier has always been what lends legitimacy to a falsified product. Onchain names carry that pattern into a part of the namespace that many pharmaceutical monitoring programs do not cover.

Keeping the risk in proportion

The limits belong in the same picture. A patient using an ordinary browser does not reach an onchain name at all. Freename names open in Bitcoin.com Wallet, in MetaMask by way of Freename’s resolver, and on desktop through the Freename Web3 extension, and that coverage is partial and changes. The audience that can reach a name under .yourbrand is therefore much narrower than the audience of a conventional website, and for reaching the general public the DNS is simply better.

That narrows the exposure without removing it. Payment requests travel by message and by link, outside any browser address bar, and trade counterparties who already settle onchain are exactly the people for whom a name is readable. The reasonable conclusion is to size the review to the channels where a name can actually be seen, and not to treat every finding as an emergency.

Why the stakes differ from a domain dispute

The distinction between brand harm and patient harm is not semantic. Brand harm shows up in lost sales, legal costs and reputation. Patient harm shows up as adverse events, and those bring safety-reporting duties, possible liability and the attention of health authorities, all of which vary by country. The function that owns onchain monitoring should understand that the stakes are of that order, and not those of a domain-name dispute.

Patients, pharmacists and distributors as three distinct audiences

The exposure is not uniform across the people who deal with a pharmaceutical brand. Three audiences see different things and are misled in different ways.

Patients are the most vulnerable. They are the least likely to know the difference between a conventional website and one reached through a wallet or an extension. They often act under pressure of their own: managing a chronic condition, seeking a refill, looking for a lower price. A name that matches the product they have been prescribed is authority enough for many. They are also the least likely to report a suspicious interaction: they may not know a reporting channel exists, or they may fear that admitting a purchase outside normal channels will affect their care.

Pharmacists and dispensing professionals make rapid trust judgments at the point of dispensing. An ordering portal or a secondary wholesaler that presents product under a name matching the manufacturer’s brand earns a different kind of trust than an anonymous source. Pharmacists can also be unwitting intermediaries: a diverted or falsified product that enters the supply chain under a credible identity may never raise a flag at the counter.

Distributors and secondary wholesalers work in a segment of the supply chain where price differences are the main commercial signal. A seller who presents a name-matched onchain identity, a payment name such as trade.yourbrand and documents that appear to come from the manufacturer has several of the outward signs of an authorized source. This is the audience where organized diversion is most likely, as opposed to a passive holder who has never used the name.

Knowing which audience a given name addresses sets its priority and the team that responds. A name built to face patients is a drug-safety and security matter first. A name built to face the trade is a supply chain integrity and legal matter first.

Coordination between trademark, regulatory affairs and security teams

In most pharmaceutical organizations, three teams hold part of this problem, and none has a natural mandate to own it from end to end.

Trademark and IP counsel know what the organization owns, what it has filed and what remedies exist in the ICANN system. They are less likely to look at the onchain namespace as a matter of routine. The tools they rely on do not carry over: the UDRP binds registrants through the agreements of ICANN-accredited registrars, and an onchain TLD sits outside those agreements. Where a third party holds the TLD, the practical route is acquisition, which puts the file closer to negotiation than to dispute resolution. Trademark law itself still applies, in ways that differ by country, and your own counsel decides what it offers.

Regulatory affairs knows the product names, the approved labeling, the authorized channels and the product lifecycle. It can say which names carry the highest patient-safety risk and which authorized channels an impersonation would most plausibly imitate. It is rarely included in domain-name monitoring.

Security and anti-counterfeiting teams run the existing online monitoring, handle takedown requests for fake sites and manage intelligence on counterfeit networks. They are the natural owners of the intelligence side of onchain monitoring. They may not have block explorers, the public tools for reading a blockchain’s records, among their usual instruments, and telling an onchain TLD from a conventional domain is a new distinction for many of them.

The practical recommendation is a named coordinator, usually in IP or brand protection, with a standing relationship to all three functions. That person receives the monitoring findings, sends those that touch patient safety to regulatory affairs and security, and sends acquisition questions to legal. Without that role, findings tend to stall at the boundary between functions.

Exposure by function inside the organization

The table maps the exposure to the functions most likely to meet it. It is not exhaustive: in a large organization, investor relations or digital marketing may face a variant of one of these rows.

Ten checks, each with the function that owns it

The ten checks run in order, and each names an owner so that the list can be handed out as it stands.

1. Check the corporate nameLook for the organization's legal name and its trading names as onchain TLDs, and note what the public registry record shows for each. Owner: trademark and IP, supported by brand protection.
2. Check every active product brand, market by marketRun the same check across every product brand that is promoted or dispensed, using the per-market list of names. Start with flagship products and those with the highest patient-safety profile. Owner: trademark and IP, with regulatory affairs setting the order.
3. Check legacy, pipeline and near-variant namesExtend the sweep to brands no longer promoted, to names that have appeared in public communications about pipeline products, and to the close variants already tracked for confusion risk. Owner: trademark and IP, with medical affairs for pipeline names.
4. Look for names already issued under a matching TLDWhere a TLD matching a brand exists, check whether names have been issued under it. Names such as verify.yourbrand, order.yourbrand or pay.yourbrand point to active use, not passive holding. Owner: brand protection and security.
5. Assess the patient-facing risk of each findingFor each finding, decide whether a realistic way of misleading patients exists. A name that could imitate a verification or refill channel ranks above one that could only confuse experienced intermediaries. Owner: regulatory affairs and anti-counterfeiting.
6. Assess the trade-channel riskReview whether a finding could be used to imitate an authorized trade identity toward distributors and wholesalers. Owner: supply chain integrity, with general counsel.
7. Decide a posture for each findingAgree on one of three responses per TLD: acquire, monitor, or document and defer. Record the decision and set a date to review it. Owner: general counsel, with trademark and brand protection.
8. Set up continuous monitoringOne check gives one picture. New onchain TLDs and new names under them keep appearing, so the watch list needs a standing review. Owner: brand protection for operations, general counsel for the mandate.
9. Put a mutual NDA in place before sharing anythingAny outside adviser or provider involved in the review signs a mutual non-disclosure agreement before seeing its scope or its findings. Owner: general counsel.
10. Document the review for the board or audit committeeA written review with findings and responses gives the board a record of a risk it may never have seen described, and supports the case for a continuing budget. Owner: general counsel and the head of brand protection.

The options and who should own the file

Once the first sweep is done, the decisions look more like acquisitions than like domain-name disputes.

Acquisition is the main path for a TLD that a third party holds and that matches a brand name. There is no central body to petition. The holder of the token controls the TLD, and a transfer needs the holder’s agreement, so the process is a quiet negotiation, not a formal dispute. How the approach is made matters. A clumsy first contact can reveal how much the name is worth to you and shape the price, or bring the matter into public view at a moment you did not choose.

Two services of the desk correspond to this path. Brand namespace recovery covers acquiring the onchain TLD that matches a brand. Where the holder is not known, buy-side acquisition is the mandate under which the desk finds and approaches that holder for your organization.

Monitoring is the right posture for a TLD that exists but shows no sign of active use. A monitoring mandate should state the watch list, who receives a finding and how it escalates.

Deferral is seldom right for a high-priority brand, though it can suit a legacy name with low patient-safety risk. A deferral is written down with a review date.

Ranking findings when there are many

A long portfolio can produce more findings than any budget will acquire. Rank them on two questions that are specific to pharma. First, could the name plausibly face patients, given how the product is prescribed, dispensed and paid for? A medicine that patients buy directly, or seek out online for reasons of price or discretion, ranks above a product administered only in a hospital. Second, how much does the product’s supply rely on intermediaries who trade on documents and price? The more hands a product passes through, the more a trade-facing name matters. Findings that score high on either question move to acquisition or close monitoring. The rest can be deferred with a clear conscience and a review date.

Who owns it

The file belongs with general counsel or the head of brand protection, with one named person who can act when a finding calls for a response. The choice of path for each TLD is legal and strategic in equal measure. The page for brands and legal teams sets out the subject for general counsel and brand protection teams, and can help when you brief colleagues who are new to it.

What a pharmaceutical company could do as the TLD holder

Acquiring the TLD that matches a brand removes the exposure. It also opens uses that go beyond defense, and knowing them helps you build a case that reaches past the risk register.

Payment names the organization controls. Under a TLD it holds, the organization can issue names that receive payments, for example trade.yourbrand for settlements with authorized distributors or returns.yourbrand for a product return scheme. A name is easier to read and to audit in a transaction record than a raw address. The page on payments to a name shows what that looks like in practice.

Verification pages under the organization’s own name. The organization controls what every name it issues points to. A verify.yourbrand name leading to its own verification system is a direct answer to the imitation page in the earlier scenario. Patients and pharmacists who use a supporting wallet or extension reach the real page, and no third party can issue a competing name under that TLD.

A namespace for internal functions. A held TLD can supply names for wallets, payment routing and software agents without depending on anyone else’s naming decisions. On agents, ERC-8004 (“Trustless Agents”) is a draft Ethereum standard that includes an identity registry for agents. It is a draft and may change, and the way naming registries connect to it is still evolving, so treat this as a direction to watch, not a plan to budget.

Names for authorized partners. A manufacturer that works with licensed distributors or pharmacy partners could issue each of them a name under its TLD, so that a counterparty can see at a glance which identities the manufacturer has issued. Freename also runs a royalty program that pays the TLD holder part of each registration fee for names registered under the TLD, advertised at up to half and subject to the registry’s current terms and activation conditions. For a pharmaceutical company, the trust function is the point. Any royalty is secondary.

Capabilities that already work, with their limits. Wallet resolution, payments to a name and websites published on an onchain TLD are set out, with sources, on the what’s live page. Read it with the limits in mind: resolution is partial, and nothing published under an onchain TLD replaces the organization’s website in the DNS.

Holding is also inexpensive to maintain. A Freename TLD carries no annual renewal fee, so a name acquired for defense can sit unused while the organization decides what, if anything, to build on it. When it does decide, post-transfer activation is the service that covers putting a TLD to work after the transfer.

A first week that can be delegated

The review does not need a project. It needs a list, an owner and a first meeting.

Ask regulatory affairs for the per-market list of product names, and ask trademark for the close variants it already watches. Give the combined list to one coordinator in brand protection, who runs the first three checks and brings the findings to a single meeting with regulatory affairs, security and legal. In that meeting, rank the findings on the two questions above and record a posture for each.

If a finding calls for an approach to a holder, that is the point at which Hush Partners can be of use. It is a private desk for onchain TLDs, and an organization can mandate it to find and approach a holder. Exchanges with the desk are covered by a standard mutual NDA, the same named partner stays with the file from the first note through closing, and closing runs through onchain escrow on an aftermarket. The desk is reached through the contact form on its site.

Questions people ask

Can a pharmaceutical company use the UDRP to recover an onchain TLD?

The UDRP is a contractual procedure. It applies to domain names registered through ICANN-accredited registrars, because registrants accept it when they register. An onchain TLD is outside that system, so the procedure does not reach it. The practical route is acquisition by negotiation. Whether trademark law offers other claims depends on the country, and your own counsel decides.

Is the holder of an onchain TLD publicly visible?

The record is, in the sense that the registry keeps it public and a block explorer lets anyone check it. What it shows is a wallet address, not a name. An organization should not assume that it can learn who is behind a TLD from the record alone.

What if a TLD exists for a product name that is not yet launched?

Pipeline names are a particular exposure because public communications can make a name known before the brand is established. Treat such a finding as a priority and bring it to regulatory affairs early. In some cases the pending choice of brand name is still open, and that is itself an option worth discussing with your counsel.

Does holding the TLD mean the organization has to run a namespace?

No. An organization that acquires the TLD matching its corporate or product name can hold it and issue no names at all. Issuing names is a choice it can make later, for one function at a time, starting with whichever of the uses above answers a real need.