Hush Partners · Quiet by designSome names change hands without a sound.
Hush Partners is a private onchain TLD broker. We sell for holders and acquire for organizations, with no listing, no announcement and no names.
Brands just queued for their .brand. Yours already exists onchain.
More than sixteen hundred applications, a USD 227,000 fee each, years of evaluation. Meanwhile the onchain TLD matching your name exists, works in wallets, payments and agents, and sits in someone's wallet. One side holds it, the other needs it. We make that deal quietly.
Your trademark may already be an onchain TLD.
Many onchain TLDs that match well-known organizations were registered early, and most of them sit with a handful of large holders. Many of them can be acquired through Hush Partners. For a legal team, one conversation can cover the group name, the brands and the products.
Type your brand. See what we would look for.
We do not run lookups in public. That is the point. A partner checks these privately and answers within days.
Get the private answerWhat anyone can do with your name, today.
A website, payments, wallets that resolve it, AI agents that act under it. None of this is a roadmap. Whoever holds the TLD can do it now, which is why the question of who holds yours matters now.
Freename AI drafts a site from a brief and publishes it to IPFS, where it opens on an onchain name. Minutes of work, not a project.
How it worksBitcoin.com Wallet users can send to a Freename name instead of a long string of characters.
How it worksA Freename resolver brings onchain names into the most widely used Ethereum wallet.
How it worksThe Freename extension opens sites published on onchain names in desktop browsers.
How it worksshaka.deal payment links route invoices and payouts to a name, with splits signed onchain before money moves.
How it worksERC-8004 defines identity, reputation and validation registries for agents. A name under a TLD makes each agent readable.
How it worksManage a TLD and the names under it by asking an AI assistant.
How it worksOne desk. Two quiet sides of the same deal.
Most of what we do happens on one side of a transaction or the other. The rule is the same on both: nobody hears about it unless you decide they should.
Sell a TLD without ever listing it.
You hold a TLD that belongs with someone. We value it, map the few buyers who matter, make the approach and run the negotiation. Your name never appears, before or after.
- Private valuation before anything moves
- Holder identity kept from every counterparty
- Settled in escrow, never on trust
Acquire a name without showing your hand.
Your name, or the one you need, sits in someone else's wallet. We approach the holder on your behalf, without revealing who is asking, and bring it home clean.
- Your identity withheld until you choose
- Clean title checked before you commit
- Nothing issued under the TLD on the way
How a quiet file runs.
Four stages, one named partner, and a private room that only your counterparty can open.
Mandate
Ownership verified onchain. Valuation and buyer map agreed in private.
Approach
One short note to the right person, with a reference and an unlisted private room.
Terms
A single counterpart on each side. Terms carry a real validity date.
Transfer
Escrow, transfer confirmed onchain, silence on both sides.
Typical timeline. Every file moves at the pace of the counterparty.
Eight services. All of them quiet.
Onchain top-level domains are the core of the desk. Any other digital asset that needs a discreet negotiation can go through the same process.
Sell-side mandates
Sell a TLD without ever listing it.
Read moreBuy-side acquisition
Acquire a name without showing your hand.
Read moreBrand namespace recovery
Bring your organization's name home, quietly.
Read moreTLD valuation
What a TLD is worth, to whom, and why.
Read moreEscrow & transfer
Onchain escrow, on the venue you choose.
Read morePost-transfer activation
Subnames, verified wallets, payments, agents.
Read moreNamespace watch
Your names, monitored across registries.
Read moreOther digital assets
Premium domains and other quiet negotiations.
Read moreNo listings. No logos. No leaks.
Our rules of engagement are the product. They protect the holder, the buyer and the price.
- We never publish a TLD, a client or a counterparty. Not before, not after.
- No invented urgency. Deadlines and shortlists are stated only when they are real.
- Nothing is issued under a TLD while it is under discussion.
- A clear no ends the approach. We do not chase.
- Referral partners are paid through an onchain split at closing.
- Every file has one named partner, from first note to closing.
Received a note from us?
It was meant for you. The note carries a reference and a link to a private room with the onchain record of the asset, what you would hold and how a transfer would close.
Check everything yourself.
Ownership, subnames issued and transfer history are public records. Your room links to each of them. Verify first, then talk.
From the Journal

Onchain TLDs and retailers: what to check
What is specific to retail when the organization's name exists as an onchain TLD, and what to check first.

Succession planning for holders of onchain TLDs
The asset has no registrar to call and no account to recover. Planning is the only route.

Who gets a name under your TLD: writing an issuance policy
A namespace without rules fills up with names nobody remembers approving. The policy fits on two pages.

Onchain TLDs and airlines: what to check
What is specific to airlines when the organization's name exists as an onchain TLD, and what to check first.

One name, several blockchains: how a name maps to addresses
The same name can lead to different places depending on the network. Useful, and a source of costly confusion.

Onchain TLDs and car makers: what to check
What is specific to automotive when the organization's name exists as an onchain TLD, and what to check first.

Onchain TLDs and crypto exchanges: what to check
What is specific to crypto when the organization's name exists as an onchain TLD, and what to check first.

Terms of use for names issued under your TLD
The document a registrant accepts is the only place where your rules for a name become a commitment. Here is what belongs in it, clause by clause, and what to leave out.

What an onchain name proves, next to a certificate
A name proves who controls a namespace. It does not prove who that is. The difference matters.

What a resolver is, and why it decides where a name works
A name works exactly where a resolver answers for it. Understanding that one component explains most of the limits.

How to acquire an onchain TLD, from first check to transfer
Six stages, the decisions in each, and who inside your organization should be in the room.

What a seller still owes after closing
The token moves in one transaction. The seller's obligations do not end with it. A plain account of what you still owe the buyer once the sale has closed, and where those duties stop.

When a lookalike name reaches your customers
Customers report an onchain name that imitates yours. Here is the order of work for the first day, the first week and the review that follows.

Who actually buys an onchain TLD
A buyer is not a company. It is a person with a reason, a budget line and someone to convince.

When leaving an onchain TLD alone is the right decision
Inaction is a decision like any other, provided someone made it and wrote down why.

The regulatory questions around onchain names
There is no dedicated regime. That does not mean no rules apply.

Naming AI agents under your own TLD
An agent that negotiates, orders or pays on your behalf needs an identity others can check. Where naming fits.

How to audit your brand's onchain namespace
A namespace audit fits in a few working sessions. The method, step by step, with the document you should end up holding.

Approached about your name onchain: an internal procedure
The first hour decides whether the note reaches the right desk or dies in a spam folder. A procedure for the recipient.

IPFS and content addressing, explained without the mythology
Permanent, uncensorable, free: three things people say about IPFS that need qualifying.

Verifying a counterparty by its onchain name
A name narrows the question from which address to whose name. The second question still needs an answer.

You applied for a dotBrand: deciding on the onchain twin
The application covers the DNS. The same string onchain is a separate asset with a separate holder. A way to decide what to do about it.

Your organization's name onchain: a guide for legal teams
Registries, TLDs, subnames, and the options on the table when your organization's name shows up onchain.

How a corporate treasury pays for an onchain TLD
Your company has agreed to buy a TLD and the price must be paid onchain. Here is how a treasury team that has never done it gets from budget to escrow under its normal controls.

Staged payments and earn-outs in a TLD sale
A TLD changes hands in a single transfer, and it does not come back. Here is how to stage a price or tie part of it to registrations without leaving one side exposed.

Approaching the holder of a TLD without showing your hand
A holder who sees a large organization behind an enquiry prices the organization. How to be heard without being read.

Paying advisers and referrers at closing
A sale rarely has only two people to pay. Here is how to settle everyone from one payment, in the open, with nobody left chasing an invoice.

How a brand gets impersonated onchain: five vectors
A TLD matching your brand is a namespace. Whoever holds it decides which names exist beneath it. Five uses a brand team should recognise.

How to write your onchain name in brand guidelines
Brand guidelines govern the logo to the millimeter and say nothing about the name a customer types into a wallet. Here is the chapter that fills the gap.

What trademark law reaches onchain, and what it does not
The right exists. The difficulty is the defendant, the forum and the remedy. A plain account for brand owners.

Running a market TLD for places: who it serves and how
A sector word as a namespace: who needs a name in places, what it does for them, and what the operator takes on.

Acquiring several onchain TLDs in one conversation
One file for several names is quieter and usually simpler. It also raises questions a single acquisition does not.

Geographic names: what the DNS learned, and onchain
A place name has many claimants and no owner. The DNS built rules for that. Onchain has none.

Onchain TLDs and luxury houses: what to check
What is specific to luxury when the organization's name exists as an onchain TLD, and what to check first.

Lookalike characters in onchain names: the homoglyph problem
A name can look exactly like yours on a screen and be a different string. An old problem in a new setting.

An investment thesis for onchain TLDs
Written the way an analyst would write it for an investment committee: the case, the case against, and the conditions under which the position should be closed.

Founder and executive names onchain
A founder's name is not a trademark, and it does not belong to the company by default. A working method for deciding who holds it and what happens when the person leaves.

Onchain TLDs and publishers: what to check
What is specific to media when the organization's name exists as an onchain TLD, and what to check first.

Seven pricing mistakes onchain TLD holders make
Most pricing errors are made before the first conversation. Seven of them, and what to do instead.

Registry, wallet and marketplace policies a brand can invoke
Every platform between a name and a customer has terms. Knowing which one to address, and what to ask, is most of the work.

Tax and accounting questions to settle before you sell a TLD
Nobody can answer these for you in an article. What an article can do is make sure you ask them in time.

Onchain names in a corporate domain portfolio
Your register was built for domains that expire and sit in a registrar account. An onchain name has neither, so the entry needs different columns.

What the domain aftermarket learned in thirty years
The resale of names is not new. Most of what goes wrong today went wrong before.

Running a market TLD for online communities
A sector word as a namespace: who needs a name in online communities, what it does for them, and what the operator takes on.

The Freename name collision patent, in plain language
A patent on how colliding names are resolved was granted before the application window opened. What it says, without the claims language.

Email and onchain names: what does not work yet
Internet mail looks for its destination in the DNS, and an onchain name is not there. A plain account of the limit, and of the division of work that holds up.

What the applied-for strings list tells a TLD holder
A match raises interest in your TLD. It does not entitle you to pressure anyone.

Tokens, wallets and keys: what a lawyer needs to know
Who owns it, who controls it and who can prove it are three different questions. The vocabulary that separates them.

The Trademark Clearinghouse and sunrise, absent onchain
Sunrise gave trademark owners first refusal on their own names. Onchain, whoever came first simply registered.

Royalty program terms when a TLD changes hands
Two TLDs that look identical on the public record can carry different royalty terms. Here is how to find out which ones apply before closing, and who should ask.

The holder says no: the options that remain
No often means not now, or not on those terms. Reading a refusal, and choosing what follows.

The board memo on your brand's onchain TLD
Directors do not need a course on blockchains. They need the issue, the options and what you recommend.

Preparing an onchain TLD for sale
Buyers pay for a clean string, a clean history and a clean handover. Most of that is in the holder's hands.

Privacy on a public record: what others see about your TLD
Nothing on the record says who you are. A good deal can still be learned from what you do.

Lookalike onchain TLDs: which variants of your name matter
You cannot hold every variant of your name, and you do not need to. A way to rank them.

Browser extensions that resolve onchain names: what to ask
The bridge between an onchain name and a browser is usually an extension. A plain look at what that means.

Running a market TLD for events: who it serves and how
A sector word as a namespace: who needs a name in events, what it does for them, and what the operator takes on.

Forget Jerseys: Claim Your Esports Name for Digital Identity and Brand Power
In esports the name is the asset: the tag on the scoreboard, the handle on the stream. A name under .esports puts that asset in your own wallet.

Who holds the keys: custody of an onchain TLD
The most valuable decision after an acquisition is made before it: where the TLD will live and who can move it.

What the list of applied-for strings tells a brand owner
The list answers one question publicly: who applied for which string. What a brand team should do with it.

What running a TLD in the DNS involves, year after year
Applicants plan for the application. The obligations begin the day it succeeds.

Measuring the use of a TLD from its public record
A count of names issued says little by itself. Here is how to measure issuance, spread across wallets and records set, and where the record stops.

Contention sets: when several applicants want the same TLD
The DNS resolves competing claims through a process. Onchain, the first registration simply stands. Two models of priority.

Writing a teaser for a TLD without naming it
The first document a possible buyer reads describes the TLD and leaves out its name. Here is how to write that page so it is useful and still gives nothing away.

Selling a finance word TLD: who buys it and how it runs
What is particular about selling a TLD that names a financial activity or product, from the first list of buyers to the terms.

How to read the public record of an onchain TLD
The record does not lie, but it does not explain itself either. A guide to what you are looking at.

Getting a TLD acquisition through procurement
The business case is agreed, then the purchasing system asks the seller for a supplier number. A file-by-file route through the four functions that must sign.

Running a market TLD for the legal profession
A sector word as a namespace: who needs a name in the legal profession, what it does for them, and what the operator takes on.

Onchain TLDs and payment companies: what to check
What is specific to fintech when the organization's name exists as an onchain TLD, and what to check first.

Writing an internal policy for onchain names
Most organizations meet onchain names through an employee who registered one on a personal wallet. Here is the internal rule that prevents that, clause by clause.

Testing an onchain name before you publish it
A name that fails in the one wallet your largest customer uses is worse than no name. Test first.

Selling a TLD held by several people
A buyer wants one counterpart who can commit. Getting there is work to do before the first approach.

Running a market TLD for health professions
A sector word as a namespace: who needs a name in health professions, what it does for them, and what the operator takes on.

Interoperability between naming systems: why it is hard
Nobody designed these systems to agree. Interoperability is negotiated one piece of software at a time.

What no renewal fee changes for a TLD holder
The renewal date was a cost, a risk and a reminder at once. Take it away and a holder has to decide what replaces each of the three.

What a dotBrand is, and what it obliges its owner to do
A dotBrand is not a domain you buy. It is a registry you run. What that difference involves.

Selling a TLD that already has names issued under it
An occupied namespace is not unsellable. It is a different asset and should be presented as one.

Acquiring a TLD ahead of a product launch
A launch date is fixed and a holder's calendar is not. Here is how to plan an acquisition backward from the day the name has to work.

Registry risk: what a TLD holder depends on
Holding the token is certain. What it does for you depends on others. A holder should know on whom.

Onchain TLDs and banks: what a general counsel should check
A bank's name next to a payment instruction carries weight. That is the reason this sector should look first.

Does the UDRP apply to onchain TLDs?
The UDRP binds registrars under contract with ICANN. An onchain registry is outside that contract. Here is what remains.

The records an onchain name can carry
A name does nothing until records are set. The kinds of record, and the discipline they need.

The accounting questions an acquired onchain TLD raises
Auditors will want to know what it is, who controls it and how you know. Prepare the answers before they ask.

Running a market TLD for independent work
A sector word as a namespace: who needs a name in independent work, what it does for them, and what the operator takes on.

Selling a community TLD: who buys it and how the sale runs
What is particular about selling a TLD that names an interest, a culture or a community, from the first list of buyers to the terms.

Two interested buyers: running a fair process
Two parties want the same TLD and only one can have it. How a holder treats both the same way, chooses once, and leaves the other with nothing to resent.

Running a market TLD for gaming communities
A sector word as a namespace: who needs a name in gaming communities, what it does for them, and what the operator takes on.

Losing access to a TLD: prevention and real recovery
Most losses are organisational before they are technical: a departure, a device, a note nobody kept.

Announcing your onchain TLD, or not
Some holders launch quietly and let the names speak. Others announce. What each choice commits you to.

Group name, brands, products: which onchain names matter
The famous name is rarely the legal entity's name. Start from what the customer says, not from the organisation chart.

Objections and rights protection in an ICANN round
The DNS gives third parties a moment to object. Onchain, that moment does not exist.

The case against onchain TLDs, taken seriously
A desk that sells these assets should be able to state the case against them. Here it is, without softening.

Selling a short or acronym TLD: who buys it and how it runs
What is particular about selling a very short TLD or an acronym, from the first list of buyers to the terms.

Managing a TLD from an AI assistant: what to delegate
Convenience is not the question. The question is which actions on your namespace should ever happen without a second pair of eyes.

Selling a profession TLD: who buys it and how the sale runs
What is particular about selling a TLD that names a profession or a trade, from the first list of buyers to the terms.

Negotiating with a legal department as a TLD holder
A legal department does not negotiate like a trader. Knowing how it works shortens the road.

How prices form in a market without comparables
Art, private companies, spectrum: many assets are priced without a ticker. The same reasoning applies.

Building the evidence file when your name appears onchain
The record is public, but screens change and memories fade. A disciplined file costs an hour and saves weeks.

What is a TLD worth? Valuing onchain TLDs
Comparables are thin. Here is what actually drives the value of a TLD, and how a private valuation works.

Onchain TLDs and pharmaceutical companies: what to check
What is specific to pharma when the organization's name exists as an onchain TLD, and what to check first.

Onchain names on a phone: what resolves
Most of your customers will meet your onchain name on a phone. Here is what that screen can do with it, what it cannot, and how to check before you print the name anywhere.

Pricing the names under your TLD
A price list decides who registers under your TLD long before it decides what you earn. Here is how to build one you can explain to any registrant.

Who governs onchain names
No one is in charge of everything, which is not the same as no rules. Where the rules actually sit.

What an earlier creation date is worth
An early creation date is a fact about your TLD, not a title to the string. Here is how to give it the weight it deserves in a valuation, and no more.

When not to sell a TLD
A desk that sells TLDs should say when not to. Here are the cases.

An offer arrives for your TLD: what to do before you answer
The first offer is rarely the best one and rarely the last. What it tells you, and how to reply.

ICANN's new gTLD round, explained for brand owners
Sixteen hundred applications and a six-figure fee each. What the round is, and the namespace it leaves untouched.

Names for staff and teams under your own TLD
A name that says who someone is in the organization is useful only if it can be withdrawn the day they leave.

Running a market TLD for wine and spirits
A sector word as a namespace: who needs a name in wine and spirits, what it does for them, and what the operator takes on.

What makes a naming system last
Durability is not a promise a system makes. It is a set of conditions you can examine.

Onchain TLDs and consumer goods brands: what to check
What is specific to consumer goods when the organization's name exists as an onchain TLD, and what to check first.

What happens to the names under a TLD when it changes hands
A buyer of a TLD inherits whatever was issued under it. Why that matters to all three parties.

Warranties a buyer should ask a TLD seller for
A public record shows which wallet holds a TLD. It does not show what the seller promised to someone else. That gap is where warranties do their work.

Onchain TLDs and sports clubs: what to check
What is specific to sport when the organization's name exists as an onchain TLD, and what to check first.

How wallets and browsers decide which names to support
No rule obliges a wallet to understand a name. Support is a product decision, made for product reasons.

Escrow for digital assets: how a clean transfer works
How escrow protects both sides, and how to check a transfer yourself.

Due diligence before you acquire an onchain TLD
The record is public, which makes diligence easier than for most assets. What to read, and what the record cannot tell you.

Running a market TLD for real estate: who it serves and how
A sector word as a namespace: who needs a name in real estate, what it does for them, and what the operator takes on.

A website on an onchain TLD: how publishing to IPFS works
A site on an onchain name is not a replacement for your main website. It is a different kind of presence, with different strengths.

The reserved list: names to hold back before launch
Four families of names should not be available on opening day. Here is how to find them, who approves the list, and the routes by which a name leaves it.

From application to delegation: the path of a gTLD
Passing evaluation does not put a string on the internet. Here is the road that follows, stage by stage, and what an onchain TLD of the same string is doing meanwhile.

Staying anonymous as a holder, from first contact to closing
A buyer who knows who you are negotiates with you, not with the asset. Where identity leaks, and how it is kept in.

Licensing a TLD instead of selling it
A holder who will not sell can still let someone else build on a TLD. The license is a contract, the token stays put, and every name is issued by the holder on instruction.

ERC-8004 explained: the draft standard for trustless agents
Three registries, one question: can you trust an agent you have never met. A plain reading of the draft.

The terms of a TLD sale, explained line by line
Most failed sales fail on a term nobody discussed. The lines to look at before the number.

Planning the exit of an onchain TLD portfolio
The order of sales changes the outcome. A plan for holders who registered early and at scale.

A shared suffix or a TLD of your own: two naming models
Under a shared suffix you are a tenant of the namespace. With your own TLD you write the rules.

Where the value sits: the TLD and the names beneath it
Holding the TLD means holding every name that could ever exist under it. That changes where the value is.

Paying to a name instead of an address
A forty-character address invites mistakes. A name removes one class of error and introduces a question: who controls the name.

Name collisions: when a DNS TLD meets an onchain TLD
Two systems, one string, no shared authority. What happens at the point where they meet.

Choosing an intermediary to sell a TLD: the questions to ask
You are hiring a voice and a judgment. Ask how both will be used before you sign.

Onchain TLD and DNS domain: twelve practical differences
They look alike on a screen and behave differently in almost every respect that matters to an owner.

Trademark TLDs onchain: what they are and why they exist
Onchain TLDs matching well-known names exist. How that came about, and what it means for the organizations they match.

Onchain TLDs and telecom operators: what to check
What is specific to telecom when the organization's name exists as an onchain TLD, and what to check first.

Selling a trademark TLD vs a market TLD: different jobs
One has a single logical buyer and a legal department. The other has a shortlist and a business case. The method follows.

Running a market TLD for music: who it serves and how
A sector word as a namespace: who needs a name in music, what it does for them, and what the operator takes on.

Onchain TLDs and game publishers: what to check
What is specific to gaming when the organization's name exists as an onchain TLD, and what to check first.

AI agents that pay and get paid under a name
An agent with a budget is a new kind of counterparty. Identity and payment have to be thought about together.

What USD 227,000 buys in an ICANN application
The headline fee pays for one thing: having an application evaluated. Here is the rest of the budget, line by line, and how an onchain TLD is costed instead.

Buying a TLD without revealing the buyer
A buyer can stay unnamed through a negotiation. The public record is another matter, and it is decided by the wallet you choose before the first note goes out.

Running a market TLD for the art market
A sector word as a namespace: who needs a name in the art market, what it does for them, and what the operator takes on.

Where onchain names fit in a brand protection budget
No renewal fees change the arithmetic of a defensive portfolio. What that means for the budget holder.

A short history of namespaces outside the DNS
People have been building names outside the DNS for decades. The pattern of those attempts explains what is different now.

Selling a geographic TLD: who buys it and how the sale runs
What is particular about selling a TLD that names a city, a region or a country, from the first list of buyers to the terms.

Running a market TLD for sport: who it serves and how
A sector word as a namespace: who needs a name in sport, what it does for them, and what the operator takes on.

Onchain names in a company acquisition: the IP checklist
A target can hold an onchain name that no trademark schedule or registrar report shows. Here is what to ask, what to verify yourself and what to write into the deal papers.

Onchain TLDs and hotel groups: what to check
What is specific to hospitality when the organization's name exists as an onchain TLD, and what to check first.

How much do names under a TLD add to its value
Revenue from names is real arithmetic on uncertain inputs. A worked example, and the discount a buyer applies.

Onchain TLDs and delivery companies: what to check
What is specific to logistics when the organization's name exists as an onchain TLD, and what to check first.

Onchain TLDs and insurers: what to check
What is specific to insurance when the organization's name exists as an onchain TLD, and what to check first.

What a sell-side mandate contains, clause by clause
A mandate is short. Each clause answers a question that would otherwise come up at the worst moment.

The first ninety days after acquiring an onchain TLD
An acquired TLD that sits unused protects the name and nothing else. A plan for the first quarter.

Onchain TLDs and universities: what to check
What is specific to universities when the organization's name exists as an onchain TLD, and what to check first.

Selling a non-English TLD: who buys it and how the sale runs
What is particular about selling a TLD in a language other than English, or in a non-Latin script, from the first list of buyers to the terms.

How a new gTLD application is evaluated, in outline
Evaluation asks whether the applicant can run a registry and whether the string raises problems. An outline for non-specialists.

Abuse handling in the DNS and onchain: who can stop a name
Suspension is the DNS reflex. Onchain, the question is which piece of software will stop answering.

Licensees, franchisees and names under your TLD
A name under your TLD tells the public that a third party belongs to your network. Decide who gets one, on what terms, and how it ends before you issue the first.

Onchain top-level domains: the complete guide
What a TLD is, who holds it, what it is for, where its limits are, and how it changes hands.

What a buyer map is, and how one is built
A list of companies is not a buyer map. A map says who, why, through whom, and in what order.

Setting a ceiling for the acquisition of an onchain TLD
A ceiling is built from what the name is worth to you, not from what is asked. A method that finance will accept.

Running a market TLD for travel: who it serves and how
A sector word as a namespace: who needs a name in travel, what it does for them, and what the operator takes on.

Running a market TLD for education: who it serves and how
A sector word as a namespace: who needs a name in education, what it does for them, and what the operator takes on.

Onchain TLDs and healthcare providers: what to check
What is specific to healthcare when the organization's name exists as an onchain TLD, and what to check first.

Onchain TLDs and energy companies: what to check
What is specific to energy when the organization's name exists as an onchain TLD, and what to check first.

How an onchain name resolves, and where it does not
Resolution is the difference between a name that exists and a name that works. Where things stand, without overstatement.
Asked quietly.
What does Hush Partners actually do?
We run discreet negotiations for onchain top-level domains, on the sell side for holders and on the buy side for organizations. Valuation, approach, negotiation, escrow on the marketplace both sides choose, and activation after transfer.
Why is nothing listed on this site?
A listed TLD loses value and draws noise, and a name that matches an organization is a statement about that organization. We discuss assets with the parties concerned, privately, and nowhere else.
How much does it cost?
There is no price list. A fixed fee, quoted privately, paid by whoever mandates us to find a buyer or a holder. If you buy a TLD we offer, you pay its price and nothing on top.
Will the other side know who I am?
No. Holders stay anonymous to buyers and buyers stay anonymous to holders until the client decides otherwise. The contract is with Hush Partners LLC.
How is payment secured?
In escrow, on the venue you prefer. The asset and the payment move in one operation.