Running a market TLD for health professions

A namespace built around a health profession sits where three things meet that rarely align cleanly: public trust, professional regulation, and real utility for the people it names. Those three forces shape every decision an operator makes, from the policy that governs who gets a name to the revenue model that pays for the checks.

This article is written for an operator, platform, or professional association considering the acquisition of a sector TLD for health professions and the issuance of names under it. It covers who would actually register a name and why, what makes this sector different from, say, finance or architecture, and what the operator takes on. By the end you should be able to judge whether the namespace has real users in health professions, what it would take to serve them well, and where the risks concentrate.

Health professions are not a single audience. They span independent practitioners, group practices, licensing bodies, and specialist colleges. Each has a different reason to hold a name and a different relationship with verification, privacy, and promotion. An operator who treats them as one audience will build the wrong product.

Who would hold a name under .yoursector

Three broad registrant types exist, and their needs diverge enough that you need to decide, before launch, whether the TLD serves all three or just one.

Individual practitioners (physicians, nurses, physiotherapists, pharmacists, midwives, and others licensed by a national or regional authority) form the potential base. They do not need a name to practice, so registration is a choice, not a requirement. That matters for demand modeling: discretionary registrations accumulate much more slowly than mandated ones, unless the namespace carries a signal that matters professionally. Be honest with yourself here. A practitioner with a full appointment book has little reason to register anything, and most will wait until a body they respect tells them the name means something.

Group practices and clinics are fewer but have a clearer practical motive. A clinic wants a stable, recognizable name for payments and for its dealings with other practices. If the TLD is regarded within the profession as credible, a clinic name under it carries some of that credibility.

Professional orders, the regulatory or representative bodies that license and discipline practitioners, are the smallest group by count and the most important to get right. An order that takes part as an attesting authority and holds its own name gives the TLD a legitimacy it cannot obtain any other way. An order that opposes the TLD, or is indifferent to it, removes that signal entirely. Engage them early and honestly.

What a name under .yoursector actually does

The utility is concrete, and it varies by registrant type.

For an individual practitioner, a name such as familyname.yoursector can do two things. First, when an onchain name resolves in a wallet, it stands in for a raw hexadecimal address: a peer sending funds to familyname.yoursector does not need to copy and compare a long string of characters. Second, the name can be tied to an attestation, a structured statement that a licensing body, or the operator after a check, has confirmed the holder is registered to practice. How that statement is published depends on what the registry supports and on what you build: it may sit in a record attached to the name, or in a public register you keep and that anyone can consult by name. Either way, a person who looks up the name can see the attestation without writing to the licensing body.

For a clinic, the main use is receiving and splitting payments. A group practice settles money in several directions: associates who share the cost of premises and staff, visiting practitioners who work sessions there, suppliers, and patients where the clinic accepts onchain payment at all. Payments to a name give the clinic a readable destination in place of a raw address, which reduces copying errors. One caution is specific to this sector. Many health professions restrict or forbid sharing fees with whoever refers a patient, so a tool that makes splits easy does not make every split permissible. The rules of the profession decide what may be split, and the clinic’s own counsel confirms it.

For a professional order, the TLD is an administrative tool. The order can hold a name such as register.yoursector and use it to publish attestations, point to its member directory, or receive administrative payments. The more the order builds the TLD into its own work, the more the names issued under it mean.

What a name does not do is replace the underlying license. The name is not a credential; it points to one. An operator who confuses the two, or who lets registrants present the name as proof of licensure, creates a risk for the public and a problem for itself.

Verification: where it matters to the public and who attests

The professions where being verified matters

In health, the gap between appearing qualified and being qualified is not only a matter of reputation; it is a matter of patient safety. In professions such as medicine, nursing, pharmacy, and physiotherapy, practitioners are licensed by authorities set up by law, and practicing without a valid license is unlawful in many countries, with rules that vary by jurisdiction. The public has a direct interest in knowing whether the person treating them holds a license that is in force and not suspended.

This is where a health-sector TLD differs most from a generic namespace. A name under .yoursector tied to an attestation from the relevant licensing body is more useful than an unverified name anywhere else, because the check has been made once, by the body entitled to make it, and can be read by anyone. The operator does not make that attestation; the licensing body does. The operator provides the frame in which it is published.

The professions where this matters most to the public are those where an error costs most: physicians and surgeons, nurses and pharmacists with prescribing rights, and any practitioner who provides mental health treatment. In those professions, a prospective patient who can look up a name and read an attestation that is in force gains something a website or a business card does not give.

At the other end sit health coaches, wellness practitioners, and nutritional advisers, who are unlicensed in many places or licensed only in some. Attestation is possible for them, but the attesting authority is less obvious, and you must think carefully about who is qualified to attest and what the attestation actually claims. Demand for a verified name is also weaker there, because the public does not expect a license in the first place.

Three models of attestation

Who attests is the hardest operational question you face, and the answer must be settled before the TLD launches. There are three realistic models.

The first is attestation by the licensing body itself. You agree a procedure under which a recognized authority (a medical council, a nursing board, a pharmacy authority) confirms, when a name is issued and at intervals afterward, that the holder has a valid license. This model has the highest public value and the highest setup cost: licensing bodies move slowly, are cautious about liability, and are understandably protective of their endorsement.

The second is attestation checked by the operator. You compare the license number and the holder’s name with the public register of the licensing body, issue the attestation yourself, and commit to withdrawing it if the registration lapses or is suspended. You carry the risk of error and the cost of monitoring. This model is faster to launch but places you in a role close to a regulator’s, one you may not be equipped for.

The third is self-declaration. The holder declares a license number, the name is issued, and no attestation is made. You are then issuing names, not verifying anyone. The TLD offers little more than a sector-branded name, which may be enough for some uses but does not produce the signal that sets a health namespace apart.

Most operators in health professions will need to decide which professions they can verify rigorously and limit the verified tier to those. Two tiers, verified names that show an attestation and unverified names that show none, are honest and defensible. It is better to be transparent about what the namespace checks than to imply a standard of verification that the process does not meet.

One point of sequence deserves attention. A license is not a permanent fact. It is renewed, restricted, suspended, or withdrawn by the body that granted it, and none of those events reaches you unless you have arranged to hear of them. An attestation that is checked once and never again decays quietly. Decide at the outset how often each attestation is rechecked and who does it, because that recurring check, not the first one, is where most of the cost of this namespace sits.

Privacy and the limits on what a name should reveal

Health professions carry a particular privacy tension. A practitioner who registers a name wants to be findable and trusted. That does not mean the practitioner wants the name to expose information he or she has not chosen to share.

Be precise about what the name reveals. A name points to a wallet address and, where you provide for it, to an attestation. That alone has a consequence many practitioners will not have considered: a wallet’s transactions are visible on a public ledger, so a name that is publicly tied to a practitioner makes the payments to that wallet readable by anyone. A practitioner who uses the same wallet for professional and personal purposes exposes both. Your guidance to holders should say so plainly and suggest a wallet kept for professional use only.

The name does not need to reveal the holder’s home address, date of birth, or area of practice unless the holder has chosen to publish it. The line between public-facing data and private data should be clear in the registration terms and respected in the way you store what you collect.

There is also a legal dimension. In many countries, health data and patient data fall under strict data protection and health privacy law. A name under .yoursector is not patient data. But the information you collect to verify a holder (a license number, an employer, a disciplinary status) is personal data about the practitioner, and it falls under whichever framework applies where you and the holder are. How that data is collected, stored, and processed is a question for your own counsel.

One practical rule helps: whatever is published onchain is hard or impossible to erase, so publish only what the holder has agreed to and what must be public for the attestation to work. The fact that a license was confirmed, the body that confirmed it, and the wallet address are legitimate contents. Anything about patients is not. A payment reference that names a patient or a treatment is patient information written to a public ledger, and the registry policy should forbid it in terms a busy clinic administrator will understand.

Why promotion rules constrain the operator’s choices

Most licensed health professions work under advertising codes that restrict what practitioners may claim in public. The restrictions vary by country and profession, but common prohibitions include patient testimonials, before-and-after comparisons, claims to be the best or most qualified in a field, and guarantees of outcomes.

These rules apply to the practitioner’s own communications, not directly to the operator of a namespace. But your choices about what information a name can carry, what directory features the TLD supports, and how you market the TLD itself all create a surface on which those rules become relevant.

Suppose you publish a directory that ranks practitioners by patient rating, even one fed by holders who volunteer the ratings. In a country with a strict advertising code, that directory may well be treated as advertising of regulated health services. You become the publisher of a promotional statement on the practitioner’s behalf, and the practitioner may face discipline for an entry he or she did not ask for.

The same caution applies to the names themselves. A name built on a superlative or a promise of results, issued to a practitioner whose code forbids that claim in any other medium, puts the holder in breach by the mere fact of using it. A reserved list that excludes such words, and words that suggest a specialty the holder does not have, protects holders from their own enthusiasm.

The safe course is to design the namespace so that the name is neutral: it identifies, it points to a confirmation of licensure, and it receives payments. It does not rank, recommend, or review. Any directory or discovery feature built on top should be designed with legal advice specific to the countries you intend to serve. That is not a reason to avoid those features. It is a reason to build them carefully and apart from the core function of issuing names.

The operator’s role: rules, issuance, support, and disputes

Running a health-sector TLD is more demanding than running a generic namespace, and the reasons are structural.

Operators who run a market TLD as a namespace are responsible for the rules under which names are issued, for what happens when a holder stops qualifying, and for the support given to holders. In health those responsibilities weigh more than in most sectors, because the names carry a signal of public trust.

Rules and issuance

The core document is the registration policy: who is eligible, what they must provide, and what happens when a license lapses. On Freename, only the holder of a TLD can issue names under it, so the gate is yours to keep. Issuance should not be open to anonymous registrants, nor first come, first served without a check.

Think through the ordinary events of a career. A practitioner retires, moves to another country, changes specialty, or has a license suspended. A name that still shows an attestation after the license has gone is worse than a name with no attestation at all. Your policy should say what happens in each case, and your process should be able to act on it within days of learning of the change.

Disputes

In the DNS, the UDRP (Uniform Domain-Name Dispute-Resolution Policy) handles certain trademark disputes over domain names. Onchain TLDs sit outside the ICANN DNS root, and that procedure does not extend to them, so you write your own. It should address at least three situations: a complaint that an attestation is false, a complaint that a name poses as another practitioner or clinic, and a request from a licensing body concerning a practitioner removed from its register.

The procedure does not need to be elaborate, but it must be written, published, and followed the same way every time. In a sector where trust is the entire product, an operator who decides disputes inconsistently loses the confidence of the bodies whose attestation gives the names their meaning.

Support

Support in a health-sector namespace is not purely technical. Holders will ask what the attestation means, how to update it, what to tell a patient who cannot open the name in a browser, and what to do with a name registered under one specialty after a change of discipline. Many holders will never have used a wallet. Plan for a person who can answer those questions, not only a page of standard answers.

Revenue from names, modeled honestly

Revenue from a namespace comes mainly from the fees paid when names are registered. On Freename, the holder of a TLD can take part in a royalty program in which part of each registration fee for a name under the TLD goes to that holder. The registry advertises the share at up to half, and it depends on the registry’s current terms and on activation conditions.

A worked example shows the scale. Every figure below is an assumption chosen for illustration, not a forecast and not a price quoted by any registry:

• Registration fee per name: USD 50
• Share of each fee received by the operator: half, the advertised ceiling, so the results are an upper bound
• Names registered in year one: 200 (one profession, one country)
• Names registered in year two: 500 (after a professional order agrees to attest)
• Names registered in year three: 1,000 (a second and third profession added)

The royalty column is the ceiling: it counts registrations only, at the highest advertised share, and the share actually paid depends on the registry’s terms. Operator costs (verification, rechecks, support, legal advice, dispute handling) are not deducted. Neither is the annual cost of taking part in the royalty program, which the registry sets and which comes off the royalty column, although the TLD itself carries no annual renewal fee. Where a TLD was registered under earlier terms that include the program for life, confirm with the registry before closing whether those terms pass to a buyer.

These figures are modest, and that is the point of showing them. A health namespace where verification is real grows more slowly than a generic one, because every registration requires a check and every check takes a person’s time. Set the USD 5,000 of year one against the cost of a lawyer with health-regulatory experience, a verification process, and a support contact, and the royalty does not cover the work. The subname revenue calculator lets you run other scenarios once you have firmer assumptions about fees and pace.

The honest reading of this model is that royalty alone is unlikely to justify the operator’s costs in the first two years, and may never do so in a small profession. The TLD is easier to defend when the operator has another reason to run it: a professional association, for instance, that values the namespace as a service to members and treats the royalty as a contribution to running costs, not as the return.

What to check before acquiring the TLD

Before committing to a TLD that names a health profession, work through a short list.

First, does the word have trademark exposure? A sector word, the name of a profession, is less likely to be a registered trademark than a brand name, but check. The Trademark Name Check is a reasonable starting point, and your own counsel confirms.

Second, is the word a protected title? In many countries the names of health professions are reserved by law to people who hold the license, and using the title without it is an offense in its own right. A namespace built on a protected title raises a question a namespace built on a general word does not: whether issuing a name under that word to an unlicensed person helps that person misuse the title. This is the strongest argument for gated issuance, and it is a question to put to counsel before the acquisition, not after.

Third, can you run a credible verification process for at least one profession in at least one country at launch? A TLD that opens without one is a generic namespace with a health word on it. The word delivers nothing unless the verification works.

Fourth, is the word specific enough to anchor identity? A broad word that covers dozens of professions is harder to make credible than a word tied to one profession or a small group of related ones. Practitioners identify strongly with their own discipline, and a physiotherapist is unlikely to feel named by a word that also covers every other carer.

Fifth, what can you actually do to a name once it is issued? Read the registry’s terms to learn whether a name under your TLD can be withdrawn, suspended, or only stripped of its verified status in your own register. Your policy on suspended and removed practitioners can promise no more than the registry lets you carry out.

Sixth, what is your plan if a licensing body objects to the use of the word? Bodies that license practitioners are protective of the vocabulary of their profession, and some will regard a namespace using it without their consent as confusing to the public. Have a response ready, ideally one that invites the body into the namespace as attesting authority.

Each of these factors bears on what the TLD is worth to you. The page on how a TLD valuation is built sets out the elements a valuation weighs, and it is worth reading before you agree a price.

A realistic first year

The first year of a health-sector TLD is almost entirely groundwork. Names will be issued in small numbers. The work that matters is the work that makes the second and third years possible.

1. Acquire the TLD and confirm itComplete the acquisition through onchain escrow. Check the public registry record on a block explorer, then test how names resolve in the wallets and browsers that support them.
2. Write and publish the registration policyDefine eligibility, the verification process, how often a license is rechecked, and what happens when it lapses. Work with a lawyer who has health-regulatory experience in your first country.
3. Approach one licensing bodyChoose a single profession in a single country. Present the namespace as a service to members and to the public, and offer the body the attesting role before you ask it to endorse anything.
4. Issue names to a pilot cohortRegister a small group by hand, checking each holder against the license register. Document every step before you automate any of it.
5. Test resolution and paymentsConfirm that pilot names resolve in at least one supported wallet and that a payment to a name arrives. Note where resolution fails and tell holders.
6. Rehearse a disputeSimulate a complaint of false attestation from start to finish. Check that the outcome is clear and prompt and that verified status can in fact be withdrawn.
7. Open registration to the professionOnce the process is documented and tested, open it more widely, at a pace the people doing the checks can sustain without error.
8. Review at mid-yearCompare what happened with what you planned: checks completed, time per check, complaints, and how many holders use their names.

Under the worked example above, the royalty of the first year is small against the cost of this groundwork. Plan for that explicitly, and define success at the end of year one in terms other than revenue: a verification process that works, a professional body that takes part, and a cohort of holders who use their names for payments or identity instead of merely holding them.

Next step for an operator considering this path

If you are assessing whether a particular word is worth acquiring for a health-profession namespace, start with three things: a trademark and protected-title check with your counsel, a first view of what the TLD is worth to you, and a conversation with at least one professional body before you commit.

Hush Partners is a private desk for onchain TLDs. An organization that wants a specific TLD can mandate the desk to find and approach a holder, and the buy-side acquisition page describes that service. For what follows the transfer, see post-transfer activation and the activation roadmap tool, which builds a launch roadmap for a newly acquired TLD. An association or operator in the health professions reaches the desk through the contact form on the site.

Questions people ask

Can a professional order operate the TLD itself?

Yes. A licensing body or professional association can acquire the TLD and act as both operator and attesting authority. This folds two relationships into one and gives the body control of the namespace. The trade-off is that the body takes on issuance, dispute handling, and holder support, which do not always suit an organization whose core function is regulatory.

What happens to a name when a practitioner retires or is removed from the register?

That is a policy question to answer before launch. A sensible approach is that a retired practitioner’s name loses its verified status and is not issued again to someone else, at least for a long period, so that no one inherits a known practitioner’s name. For a practitioner who is suspended or removed, verified status is withdrawn promptly on confirmed notice from the licensing body. Whether the name itself can be withdrawn depends on the registry’s terms, and the registration terms should state both outcomes.

Is the DNS simply better for this use?

For patient-facing websites and email, yes. The DNS works in every browser and every mail system, and a patient needs no extra tool. An onchain name is an addition for specific functions, such as payments to a name and a verified professional identity. An operator who presents the health-sector TLD as a way to host a clinic’s website will not convince anyone, and should not try.

How does paying a clinic by name work in practice?

A clinic that holds clinicname.yoursector can use an onchain payment router such as shaka, where a payment link can pay out to a name instead of a raw address. Where a payment is divided, for example between a clinic and a visiting practitioner who works sessions there, the split is agreed and signed onchain before funds move. The router routes the funds and does not hold them.

What if the profession has no licensing body?

Health coaching, wellness therapy, and parts of nutrition and complementary medicine are licensed in some countries and unregulated in others. Where no body licenses the profession, no attestation of licensure is available. You can still issue names, but say clearly that the name is then a sector-branded identity and not a verified credential. That is a narrower offer, and the fee and the wording around it should reflect that.