What USD 227,000 buys in an ICANN application
What the expected ICANN evaluation fee covers, which costs sit outside it, and how the cost structure of an onchain TLD differs. For CFOs and counsel.
A single number travels well. When ICANN opened its 2026 application round for generic top-level domains, the first in more than a decade, the figure that reached finance teams was the expected evaluation fee: USD 227,000 per application. It appears in board papers and budget requests as if it were the price of a top-level domain.
It is not a price. It is the charge for having one application examined, and ICANN’s new gTLD program pages present it that way: an evaluation fee, before advisers and before the cost of running a registry. A CFO who approves that number has approved the entry ticket and nothing that follows it. Counsel who signs the application has committed the organization to obligations whose cost appears on other lines, in other years, and sometimes in other departments.
This article reads the number the way a finance lead would read any headline cost: what is inside it, what is outside it, which of the outside lines are fixed, which are open-ended, and which never end. It then sets the same questions against an onchain TLD, where the cost structure is built differently. No amount appears here other than the fee itself, because the other lines depend on your own choices and on quotes only your suppliers can give.
Fee from ICANN's new gTLD program pages; application count as reported by trade press; renewal rule from the Freename registry.
What the evaluation fee pays for, in outline
The fee funds a review. ICANN, with the outside panels it appoints, examines each application against the criteria of the program, and the fee is how the program recovers the cost of doing that. Three questions run through the review, whatever the detailed rules of a given round say.
The first is about the string, meaning the word applied for. Reviewers consider whether it could be confused with an existing top-level domain or with another applied-for string, whether it could cause technical trouble in the DNS, and whether it falls into a reserved or restricted category.
The second is about the applicant. The organization and the people behind it are screened, and the applicant has to show it has the financial standing to keep a registry running. A top-level domain is infrastructure that others will depend on, so the program wants evidence that the operator will still be there in several years.
The third is about the operation. The applicant describes how the registry will be run technically, which registry services it will offer and who will provide them. Where a specialist provider runs the technical side, part of that examination concerns the provider and not the applicant.
That is the perimeter of the fee. It buys a process with an outcome that is not guaranteed: an application can pass, can be sent back with questions, or can fail. Passing the evaluation does not hand the applicant a working top-level domain either. It makes the applicant eligible for the stages that follow, and those stages carry their own costs.
One point matters for a finance reader. The fee is charged per application, and an application is for one string. An organization that wants its group name and a product name files two applications and pays twice. The headline number is a unit price, and the first budgeting question is how many units.
The cost lines that sit outside the fee
Everything else is outside. The table below sets out the categories a full budget needs. It carries no amounts except the one that is public, because the others are quotes, negotiations or outcomes that differ for every applicant.
| Cost line | In the fee? | Nature | Set by |
|---|---|---|---|
| Evaluation of one application | Yes: USD 227,000 expected | One-off, per string | ICANN |
| Advisers: legal, policy, technical writing | No | One-off, front-loaded | Your suppliers |
| Additional reviews and dispute procedures | No | Conditional | ICANN and providers |
| Contention with another applicant | No | Conditional, open-ended | Outcome of the process |
| Registry back end and compliance | No | Recurring | Your provider |
| Ongoing registry fees to ICANN | No | Recurring | The registry agreement |
| Internal staff time | No | Recurring | You |
Read the third column before the first. Two lines are one-off, two are conditional, three recur. The headline number is the largest visible figure on the day of filing, yet it belongs to the group that is paid once and never returns.
The recurring lines are the ones a CFO should weigh most carefully, because they turn a project into a standing commitment. The conditional lines are the ones counsel should weigh most carefully, because they are triggered by other parties and cannot be capped by a decision taken inside your organization.
Advisers: the line a CFO controls least well
Few organizations write an application alone. The documents are long, the vocabulary is specific to ICANN, and a mistake in the description of the registry or of the applicant can cost months. So the fee is almost always accompanied by a second one-off cost: the people who prepare the file.
That cost usually has three parts. Legal advisers handle the applicant’s undertakings, the corporate documents and, for a brand, the trademark basis of the application. Policy consultants who know the program handle the answers to the application questions and follow the file through evaluation. Technical writers, often supplied by the back-end provider, write the sections on registry operations.
Finance teams tend to underestimate this line for a simple reason. It does not stop at filing. Evaluators ask clarifying questions, the program publishes updates, other applicants or third parties may comment or object, and each event produces billable work. An adviser engaged on a fixed fee for “the application” may reasonably treat everything after submission as a separate scope.
Three questions bring the line under control. Which stages does the engagement cover: filing only, filing through evaluation, or through to the signing of the registry agreement? Which events are excluded, and at what rate are they billed? Who inside your organization answers the advisers, and how many hours a month will that person lose to the file? The last is a real cost even though no invoice carries it.
Fees that follow evaluation and fees that depend on events
The evaluation fee is not the only money that goes to ICANN or to the bodies working with it. In general terms, further charges fall into two families. The amounts and conditions are in the program documents and the registry agreement, and they are the authority, not a summary such as this one.
Charges triggered by an event
An application that does not pass on first reading can sometimes go through a further, deeper review, and that additional review may carry its own charge. An application that claims a special status, for instance as the voice of a defined community, may be examined on that claim by a dedicated panel, again with a separate cost.
Disputes are a second source. Third parties can object to an application on grounds the program defines, such as an existing legal right in the string. Objections are heard by independent dispute resolution providers, and filing and panel costs fall under the provider’s rules, which also say who bears them in the end. An applicant cannot know at filing whether anyone will object. It can only judge how exposed its string is.
Charges that begin once the registry exists
A successful applicant signs a registry agreement with ICANN, and that contract carries ongoing fees. In broad terms they combine a fixed periodic component with a component tied to the volume of domain registrations. A brand that issues few names under its own top-level domain will mostly feel the fixed part. An open registry selling names to the public will feel both.
The agreement also brings obligations that cost money without being called fees: depositing registry data with an escrow agent, publishing registration data in the required way, meeting service levels, reporting, and keeping arrangements in place so that the registry could continue if the operator failed. Each has a supplier or a staff cost behind it.
Registry operations: the cost that never ends
A top-level domain in the DNS is a service that must answer every query, every second, for anyone on the internet. Somebody has to run the name servers, the registration system, the data publication service and the security around them. This is the registry back end, and most applicants buy it from a specialist provider instead of building it.
The commercial shape of that contract varies. Some providers charge a fixed periodic fee, some charge per name registered, many combine the two, and set-up and testing may be invoiced separately. For a brand’s own top-level domain, where the number of names stays small, the fixed part dominates, so the cost per name actually in use can be high.
Around the back end sit the tasks that stay with the applicant whatever is outsourced:
- deciding who may have a name and recording those decisions;
- handling reports of abuse concerning names in the registry;
- answering ICANN’s compliance inquiries and audits;
- managing the provider, its renewals and, one day, a change of provider;
- keeping the people who understand all of this employed and replaceable.
None of these appears in the headline number. Together they decide whether a top-level domain costs your organization a contract and a part-time owner or a small team. A fair internal estimate assigns named people and hours to each task, then asks the uncomfortable question: if the sponsor of the project leaves, who inherits this list?
Contention: the line with no ceiling
Contention is what happens when two or more applicants want the same string, or strings similar enough that they cannot coexist. Only one can be delegated. The program provides ways to settle the matter, and the applicants concerned form what is called a contention set until it is settled.
For a budget, the important feature is that this cost is not a fee at all. It is the outcome of a contest. Where applicants cannot resolve the matter between themselves and no rule gives one of them priority, the last resort in past practice has been an auction among them, and an auction price is set by what the other party is prepared to pay. No tariff caps it.
That makes contention the only line in the table that your organization cannot bound by its own decisions. You can choose your advisers, negotiate your back end and count your staff. You cannot choose whether another applicant filed for the same word, and you learn who else applied only when ICANN publishes the list of applied-for strings, on the day the program calls Reveal Day.
Exposure differs sharply by type of string. A distinctive coined brand name backed by trademark registrations is unlikely to attract a rival applicant, though an unrelated company with the same name in another country or industry is always possible. A dictionary word, a sector term or a short string is far more exposed, because many parties can have a legitimate interest in it. With 1,616 applications going forward in the round, according to trade press reporting, overlaps on attractive generic words are a normal feature of the process and not an anomaly.
The sensible treatment is a decision taken in advance, not a provision. Ideally before filing, agree internally what your organization would do if it found itself in a contention set: withdraw, negotiate, or compete up to a stated internal limit approved by the people entitled to approve it. A limit agreed calmly beforehand is worth more than one improvised during a contest.
How an onchain TLD is costed instead
An onchain TLD is a top-level name recorded on a blockchain instead of in the DNS root. On the Freename registry it exists as a token held in a wallet, and whoever holds that token is the only party able to issue names under it, for example pay.yourbrand under .yourbrand. It is a different instrument from an ICANN top-level domain, with a different reach, so the comparison below is about cost structure only. The side-by-side comparison of a dotBrand and an onchain TLD covers the other dimensions.
| Cost question | ICANN gTLD | Onchain TLD on Freename |
|---|---|---|
| Entry cost | Published fee per application | Price agreed privately |
| Outcome of paying | An evaluation, result uncertain | Transfer of an existing token |
| Annual fee to keep it | Ongoing registry fees | No renewal fee |
| Infrastructure to run | Registry back end, compliance | A wallet, safely held |
The first row is the one a CFO notices. The ICANN fee is public and identical for every applicant. An onchain TLD that is already held by someone has no tariff: its price is whatever the holder and the buyer agree, and that price is not published. Whether a string nobody holds can be registered, and on what terms, is a question for the registry. Transparency is on the ICANN side here, and that deserves saying plainly. A public fee can be put in a budget on day one. A negotiated price needs a valuation built on stated reasoning and a negotiation before the figure is known.
The second row runs the other way. The ICANN fee buys a review that may or may not end in a delegation, after a process measured in long stretches of time. A purchase of an existing onchain TLD buys the thing itself, and the transfer is complete when the token reaches the buyer’s wallet, through onchain escrow at closing. The uncertainty is in the negotiation, not after payment.
The third row is the structural difference. A Freename TLD carries no annual renewal fee, so there is no recurring charge merely for continuing to hold it. That does not make holding free of all cost. A holder who wants a share of the registration fees for names registered under the TLD takes part in the registry’s royalty program, which carries an annual cost set by the registry unless the TLD was registered under earlier terms that include the program. Safe custody of the wallet, and the people responsible for it, are a real internal cost as well.
The fourth row explains why the recurring lines are so different. The record of an onchain TLD lives on a blockchain and the registry’s contracts, so the holder does not contract for name servers or deposit data with an escrow agent. The holder’s operational duty is narrower and less forgiving: keep control of the wallet.
Where the cheaper structure stops being the better one
A lighter cost structure is not an argument on its own, and a cost comparison that stopped at the table would mislead. What the two instruments deliver is not the same.
A top-level domain in the DNS root works everywhere the internet works. Every browser opens it, every mail system can route to it, and no user needs to install anything. That universality is what the evaluation fee, the back end and the ongoing fees pay for in the end, and for an organization that needs public websites and email on its own top-level domain there is no onchain substitute.
An onchain name has no entry in the DNS root, which is why a browser cannot open it unless support has been added. For Freename names that support exists in Bitcoin.com Wallet, in MetaMask via the resolver Freename provides, and on desktop for browsers that carry the Freename Web3 extension. That coverage is partial and it changes over time, so any plan that relies on it should be checked against what works in practice, with sources, and not against a general impression.
There is also a difference in what stands behind the asset. An ICANN top-level domain rests on a contract with a body whose processes are public, deliberate and well documented. An onchain TLD rests on a registry and on the software that chooses to support it. Both are forms of dependence, and they are not the same form. A finance lead comparing the two should record this as a risk line next to the cost lines, not inside them.
If your purpose requires universal resolution, the ICANN route is the instrument and the headline fee is the smaller part of its true cost. If your purpose is a name used in wallets, payments or identities for software, the onchain route has a simpler cost profile and a narrower reach.
Turning the headline number into a full budget
The fastest way to stop a headline figure from standing in for a budget is to rebuild the budget in front of the people who approve it. The sequence below works for an application already filed as well as for one under consideration in a later window, and its last step applies the same discipline to an onchain TLD.
- Count the stringsWrite down every string concerned. The evaluation fee applies to each application, so the unit count comes before any other figure.
- Scope the advisersFor each adviser, record which stages are covered, which events are excluded and how excluded work is billed. Add the internal hours of the person who manages them.
- Price the standing commitmentObtain the back-end quote, read the ongoing fees in the registry agreement, and estimate staff time for policy, abuse handling and compliance. Express the total per year, for as many years as you plan to hold the top-level domain.
- Mark the conditional linesNote additional reviews, objections and contention as items with a trigger and no fixed amount. For contention, record the decision taken in advance and who approved it.
- Record what is recoverableThe program terms say whether part of the fee is returned on withdrawal and at which stage. Note those stages and review the project at each one. How any of this spend is recorded is for your accountants, under the rules of your country.
- Cost the alternative on the same gridIf an onchain TLD is under consideration, fill the same lines for it: entry price, recurring charges, custody, internal time and the limits of where the name resolves.
A budget built this way usually changes the conversation. The question stops being whether the organization can afford the fee and becomes whether it wants the commitment, which is the question the board should have been asked first.
What a CFO or counsel can do with the number next
Start with the document that already exists. Take the budget request or board paper in which the USD 227,000 appears and check which of the seven lines in the first table it mentions. If it carries the fee and one adviser estimate, it describes the filing and not the project. Ask its author for the missing lines in the order of the steps above, and ask counsel to confirm in writing what the organization has decided about contention.
Then ask the comparison question honestly. Write one sentence stating what the top-level domain is for. If the sentence contains websites and email for the public, the ICANN lines are the ones to refine. If it contains names in wallets, payment destinations or identifiers for automated systems, it is reasonable to fill the same grid for an onchain TLD and see what the cost profile looks like. The page for general counsel and brand protection teams sets out the questions legal teams usually raise at that point.
The entry price is the one line of the onchain grid that cannot be read from a public source. This is where Hush Partners works: an organization can mandate the desk to find and approach the holder of a TLD on its behalf, with a standard mutual NDA over every exchange. The desk’s fee is a fixed amount, charged only to the client who gives the mandate. If you want to discuss a specific string, the contact form is the only way in.
Questions people ask
Is the evaluation fee the same for a brand as for an open registry?
The expected fee is stated per application, and the headline figure is quoted without distinction between a brand’s own string and a generic word. The program documents describe any conditions that alter what a particular applicant pays, such as support for applicants who meet defined criteria. Check those documents for your own case instead of assuming a reduction.
Can an organization share one application across several brands?
An application concerns one string and one applicant. A group can decide which of its entities files and can let its affiliates use names under the resulting top-level domain within the rules of the registry agreement, but each additional string needs its own application and its own fee.
Does paying the fee protect the string against other parties?
No. The fee starts an evaluation. It gives no right in the word itself, and it does not prevent another applicant from filing for the same string in the same window. Rights in a word come from trademark law, which is territorial and varies by country, and your own counsel can say what your registrations cover.
Does an onchain TLD need a new budget every year?
Not for holding it: a Freename TLD has no annual renewal fee. A recurring budget is still sensible for the things that do recur, namely the safe custody of the wallet, the time of the people responsible, and the annual cost of the royalty program if the holder chooses to take part.
