Objections and rights protection in an ICANN round
A new TLD can be challenged before it exists. The kinds of objection in outline, who can raise them, and the contrast with onchain.
A TLD in the Domain Name System does not appear overnight. It is applied for, evaluated and only then delegated, and between the application and the delegation ICANN gives third parties a structured way to challenge it. For brand owners and their counsel, that challenge process is both a shield and a calendar: it protects only those who use it within the period the round allows.
This article maps the objection mechanisms of a new gTLD round in outline, the separate layer of rights protection that applies after delegation, and the contrast with onchain TLDs, where none of these mechanisms exist. By the end, a trademark lawyer advising a brand owner should be able to describe each ground of objection in general terms, say which kind of client can raise which one, and explain what takes the place of these mechanisms in an onchain context.
The round these mechanisms now serve is the new application round for generic top-level domains that ICANN opened in 2026, the first in more than a decade. The application window closed on August 12, 2026, and 1,616 applications are going forward. The rights protection machinery described below runs alongside the evaluation of those applications, once the applied-for strings are public.
Application count as reported by the trade press; evaluation fee from ICANN's new gTLD program pages.
Why a round includes a moment to object
A new gTLD is not simply registered. It is delegated by ICANN into the DNS root after an evaluation in several stages, and each stage asks whether the applicant is able to run a registry and whether the string itself creates a problem. That evaluation cannot capture every conflict. ICANN therefore gives parties with standing, meaning a recognized interest that entitles them to be heard, a period in which to raise objections that the review is not designed to catch.
The rationale is structural. ICANN is not a trademark office, and its evaluators do not decide whether an applied-for string infringes a mark in one country or another. Without a formal objection mechanism, a trademark owner who found its brand reproduced in an applied-for string would have no route inside the program to halt the application before delegation. The objection process fills that gap. It gives businesses, individuals, public bodies and communities an opportunity to argue that a particular string should not enter the DNS, or should not enter it in the hands of that applicant.
There is a second reason, which is about cost. A delegated TLD is expensive to undo. Names are registered under it, contracts are signed, users come to rely on it. A dispute settled on paper before delegation is far less disruptive than one fought after a registry is live. The design therefore puts the dispute first and the delegation second.
That order matters for the brand owner. The objection process belongs to the period before delegation. A brand owner who waits for delegation before acting can no longer stop the TLD from existing. Remedies remain after delegation, but they operate at the second level, against names registered under the TLD, and not against the TLD itself.
The grounds of objection in outline
The program’s design provides for objections on several distinct grounds. Each has its own standing rule and its own test, and choosing the wrong one is the most common way to lose an argument that could have been won. The names below are those ICANN’s program has used. The exact criteria belong to the rules of the round and should be read there.
String confusion
A string confusion objection targets an applied-for string that so nearly resembles an existing TLD, or another applied-for string, that users would probably be confused if both were delegated. The test is not mere resemblance. Confusion has to be probable in the mind of an average, reasonable internet user, not just conceivable. Similarity can be argued on how the strings look, how they sound or what they mean.
Standing is narrow. This ground is designed for parties that have a TLD of their own at stake: the operator of an existing TLD, or another applicant in the same round. A trademark owner who is neither has, as a rule, no standing here, even if the applied-for string is identical to its registered mark. That owner must look to the next ground.
Existing legal rights
The legal rights objection is the mechanism most relevant to brand protection teams. It targets an applied-for string that is said to infringe the existing legal rights of the objector, and the objector must be the holder of those rights. In practice the right relied on is almost always a trademark, registered or otherwise recognized under the law of a country.
The decision maker does not ask only whether the string and the mark look alike. It weighs how the string would be used by this applicant: whether it takes unfair advantage of the mark’s distinctive character or reputation, whether it impairs them, and whether it creates a likelihood of confusion that the law would not accept. A dictionary word that happens to be a mark in one class of goods is a much harder objection than an invented word that means nothing other than the brand. The applicant’s own rights in the same word, its intended use and its good faith all carry weight.
This is the point where trademark law’s territorial nature meets a global namespace. A mark protected in a handful of countries is set against a string that will resolve everywhere. How much weight that carries depends on the facts and on the criteria of the round, which is one more reason the assessment belongs to counsel.
Limited public interest
A limited public interest objection argues that the applied-for string is contrary to generally accepted legal norms of morality and public order that are recognized under principles of international law. Standing is the widest of all the grounds, and the procedure includes a filter for objections that are frivolous or abusive.
For most brand owners this ground is peripheral. It is useful where a string would be objectionable under widely shared legal standards, not where it merely conflicts with a particular trademark.
Community
A community objection argues that there is substantial opposition to the string from a significant portion of the community that the string explicitly or implicitly targets. The objector is expected to be an established institution with an ongoing relationship to a clearly defined community.
Opposition alone is not enough. If there is no strong association between the community and the string, the objection fails, and the objector is generally expected to show a likelihood of material detriment to the rights or legitimate interests of that community. This ground is the one a professional body or an established association might consider against a sector-word TLD.
Other inputs that are not formal objections
Beyond the formal grounds, a round includes other channels that can affect an application without being an objection.
Governments take part in ICANN through its Governmental Advisory Committee. In the program’s design, that committee can signal concern about a particular application at an early stage, and it can give formal advice to the ICANN Board. The early signal is a notice: it tells an applicant that a government sees a problem, and it leaves the applicant free to respond, adjust or withdraw. Formal advice adopted by the committee as a whole is harder to overcome, because the Board is expected to take it seriously and explain itself if it does not follow it.
The program’s design also provides for an independent objector function: a person or small group that acts for no particular party and may file objections on public interest or community grounds, in the interest of internet users at large. It is a backstop for cases that no private party has the standing or the means to raise.
Finally, there is public comment. Any member of the public can put a concern about an application on the record. A comment has no binding procedural effect in the way an objection does, but evaluators can take it into account, and it costs little. For a brand owner whose concern is real but does not reach the level of an objection, it is the proportionate tool.
Who decides
ICANN does not decide objections itself. Each ground is assigned to an independent dispute resolution provider appointed for the round, and the provider appoints a panel of one or more experts to each case. The proceeding is mainly written. The objector files its case, the applicant has an opportunity to respond, and the panel issues a reasoned determination.
An applicant faced with an objection can answer it, settle with the objector or withdraw the application. An applicant that does not respond generally loses by default. Settlement is more common than outsiders expect: an applicant may agree to restrictions on how the TLD will be used, and those commitments can end the dispute.
The effect of a determination differs by ground. Where an objection based on legal rights, public interest or community succeeds, the application as a rule does not proceed. A successful string confusion objection brought by another applicant has a different effect: the two strings are treated as being in direct contention with each other, and only one of them can be delegated.
Two points about finality deserve attention. First, whether and how a determination can be reviewed inside the program is a matter for the rules of the round, and it should be checked there, not assumed from experience of other procedures. Second, an objection is not a court case and does not replace one. A rights holder who files an objection is not generally understood to give up the ability to enforce its rights before the courts of a competent country. How the two routes interact is a question for the rights holder’s own counsel.
What a brand owner should watch during a round
The key moment for a brand owner is Reveal Day, the day ICANN publishes the list of applied-for strings. Until that list is published, the strings are not public. Once it is, the list shows both the strings applied for and the cases where several applicants want the same or a similar string.
In practice, watching a round means the following.
- Preparing before the list. A brand owner who has audited its trademark portfolio, and knows which words, abbreviations and transliterations matter, can read the list in an afternoon. One who has not will spend the objection period finding out what it owns.
- Reading the list against the portfolio. Identical strings are easy to spot. The harder cases are strings that contain the mark, evoke it, or translate it.
- Assessing each conflicting string promptly. The period for filing an objection is fixed by the rules of the round and is not extended because a rights holder noticed late. The filing period should be read in ICANN’s program documents as soon as the list is out.
- Choosing the ground. A string that reproduces a mark points to the legal rights ground. A string that resembles a TLD the brand owner has itself applied for may also support a string confusion objection. The choice affects both standing and the test the panel applies.
- Considering the lighter channels. A public comment, or contact with the relevant government’s representative to ICANN where a public interest is at stake, can complement an objection or stand in for one that would not succeed.
- Checking the record of the marks. The Trademark Clearinghouse, the central record of verified trademark data that ICANN’s program uses, feeds the protections that apply after delegation. A mark that is not recorded there cannot benefit from them.
Scripts add a further difficulty. A round accepts internationalized strings, meaning TLDs written in scripts other than Latin. A rights holder may therefore face an application that reproduces or evokes its mark in a language or script it has never monitored, and a trademark watch built around Latin characters may not catch it.
There is also a question of proportion. Not every string that touches a mark deserves an objection. An objection costs money and management time, and it puts the brand owner’s position on the record. Where the applicant has a credible right of its own in the word, a negotiated commitment about use may protect the brand better than a contested proceeding with an uncertain result.
A round is also a natural occasion to look at the same words outside the DNS. The page on trademark TLDs explains what it means to hold a TLD that matches a brand and carries a free Trademark Name Check. Brand and legal teams who assess DNS and onchain exposure together avoid running the same review twice.
After delegation: protection at the second level
If no objection is filed, or an objection fails, and the TLD is delegated, rights protection moves from the TLD to the second level, that is, to the names registered under the TLD.
The Trademark Clearinghouse and sunrise. Before a new gTLD opens to the general public, its registry operator runs a sunrise period. During it, a trademark owner whose mark is recorded in the Trademark Clearinghouse can register the names that match its mark before anyone else can. Sunrise is a priority, not a grant: the trademark owner pays for the registration like any other registrant.
Trademark claims. For a period after general registration opens, the registry uses the Clearinghouse to warn a person who tries to register a name matching a recorded mark, and to notify the trademark owner if the registration goes ahead. The claims service does not block a registration. It informs both sides and removes any later argument that the registrant did not know.
The UDRP and rapid suspension. The Uniform Domain-Name Dispute-Resolution Policy, the administrative procedure through which a trademark owner can obtain the transfer or cancellation of a domain name registered and used in bad faith, applies to names registered under new gTLDs as it does to older ones. ICANN’s program also introduced a faster and lighter procedure for clear-cut cases, whose remedy is the suspension of the name and not its transfer.
Conduct of the registry itself. A further procedure lets a trademark owner complain about the conduct of a registry operator, where the operator itself is said to be acting in bad faith toward marks. This is a different concern from the conduct of an individual registrant, and it is seldom needed.
None of this layer works on its own. It requires the brand owner to have recorded its marks and to follow the launch of each relevant TLD. The table places the mechanisms by stage.
| Mechanism | Stage | What it does | Who starts it |
|---|---|---|---|
| Legal rights objection | Before delegation | Challenges a conflicting string | Rights holder |
| String confusion objection | Before delegation | Challenges a confusingly similar string | TLD operator or applicant |
| Community objection | Before delegation | Challenges a string aimed at a community | Established institution |
| Government input | Before delegation | Signals or advises on a concern | A government, through ICANN |
| Sunrise | Before general launch | Priority registration of matching names | Owner of a recorded mark |
| Trademark claims | Early launch | Notice to registrant and mark owner | Automatic |
| Rapid suspension | After launch | Suspends a clearly abusive name | Rights holder |
| UDRP | After launch | Transfers or cancels an abusive name | Rights holder |
Onchain: no objection window, no panel
None of the mechanisms described above applies to a TLD recorded on a blockchain. An onchain TLD is a token held in a wallet, and on a registry such as Freename only the holder of that token can issue names under it. It comes into existence through a transaction with the registry. There is no application round, no published list of pending strings, no body to receive an objection and no panel to hear one.
This is not an oversight. Onchain TLDs live in a different namespace and are not delegated into the DNS root. They do not need ICANN’s approval, so ICANN’s objection process has nothing to attach to. The consequences for a brand owner are nonetheless concrete:
- A string that reproduces a registered mark can be registered as an onchain TLD without any review of prior rights.
- There is no sunrise period, no Clearinghouse check and no claims notice for the names issued under it.
- Once registered, the TLD is controlled by whoever holds the token. On Freename there is no annual renewal fee, so the TLD does not lapse for non-payment in the way a domain name can.
- The UDRP and the rapid suspension procedure do not apply. They are contractual: they bind registrars accredited by ICANN and the registrants who accept their terms. An onchain registry stands outside that chain of contracts.
Two limits keep this in proportion. First, an onchain name resolves outside the DNS root, so an ordinary browser does not open it without support, and its reach is narrower than that of a delegated gTLD. Second, the absence of an ICANN procedure is not the absence of law. Trademark law, unfair competition law and the courts apply to conduct onchain as they do elsewhere, with the usual differences from country to country. What is missing is the administrative shortcut: a neutral panel, a known test and a remedy carried out by the registry.
Visibility is the other half of the picture. A brand owner, like anyone else, can open a block explorer and check the registry record, which is public. That tells a brand owner that a TLD exists and which wallet holds it. It does not provide a procedure.
The contrast with the DNS is therefore one of structure. The DNS gives a brand owner a defined moment, the objection period, in which to act before the TLD exists. Onchain, that moment does not exist: the TLD is there from the first transaction. The page comparing an ICANN dotBrand and an onchain TLD sets the two models side by side, and the glossary defines the terms that differ between them.
What takes their place in practice
Because nothing can be challenged before issuance, the practical substitutes are awareness and negotiation.
Monitoring instead of a published list
In a round, the list of applied-for strings is published once, and the brand owner reads it. Onchain there is no list and no round. TLDs can be registered at any time, on more than one registry. The equivalent of a Reveal Day review is therefore a standing watch on the strings that match the brand. The desk runs that watch as Namespace Watch, its service for monitoring a brand’s names onchain. A brand owner who wants a first view before commissioning anything can use the Namespace Exposure Score, a free tool that scores how exposed a brand is onchain.
Acquisition instead of an objection
Where an onchain TLD that matches the mark already exists and the brand owner wants to hold it, the usual route is a negotiated transfer. An objection asks a panel to stop something. An acquisition asks a holder to agree a price. The two call for different skills, and the second depends on reaching the holder, who may have no idea that the brand owner is interested. Brand namespace recovery is the service for acquiring the onchain TLD that matches a brand. More generally, an organization can give the desk a buy-side mandate to find and approach a holder.
The courts, where the facts call for it
Where a TLD or a name under it is used in a way that infringes a mark or deceives the public, the ordinary legal routes remain. Which court, which law and which remedy are questions that vary by country and by the facts, and they are for the brand owner’s own counsel. An honest assessment includes the practical difficulty: a judgment has to be carried out against a person, and a token in a wallet does not move because a registry was asked to move it.
The table sets the two environments against each other.
| Question | In an ICANN round | Onchain |
|---|---|---|
| Notice of new strings | Published list of applications | None; the public record must be watched |
| Challenge before the TLD exists | Formal objection | None |
| Who decides | Independent panel | No panel; negotiation or the courts |
| Priority for mark owners | Sunrise for recorded marks | None; the holder decides who gets a name |
| Abusive names under the TLD | UDRP and rapid suspension | Not available |
| Obtaining the TLD itself | Apply in a round | Negotiated transfer |
The two environments are best watched together. A brand owner who watches only the applications in a round will miss what is registered onchain. One who looks only onchain will miss the objection period in the DNS. The work overlaps, because the list of words that matter is the same in both.
Next step for legal teams advising on a round
If you advise a brand owner during a round, the work comes down to four tasks. Read the published list of applied-for strings against the client’s marks. Confirm that the relevant marks are recorded with the Trademark Clearinghouse. Decide, string by string, whether an objection, a public comment or no action is proportionate, and on which ground. Then run the same list of words against onchain namespaces, so that the client has one picture, not two.
For the onchain part, the Namespace Exposure Score gives a first reading at no cost. Where a TLD of concern exists and its holder needs to be approached, Hush Partners can be reached through the contact form. Every exchange is covered by a standard mutual NDA, and one named partner follows a file from first note to closing.
Questions people ask
Does a successful legal rights objection give the brand owner the TLD?
No. A successful objection stops the conflicting application. The objector does not receive the string as a result. To hold the TLD in the DNS, the brand owner would need to apply for it itself in a round, under ICANN’s eligibility and process requirements.
Can a brand owner object to a dotBrand application filed by a competitor?
Only if the brand owner’s own rights are affected. If the competitor’s string reproduces the brand owner’s mark, the legal rights ground may be open. If the string is simply the competitor’s own brand, the brand owner generally has nothing to object to, however unwelcome the application. The facts govern, and the question is one for counsel with experience of ICANN proceedings.
What happens if two applicants apply for the same string and nobody objects?
Their applications are placed in contention, because only one of them can be delegated. In the program’s design, contention ends when applications are withdrawn, when the applicants reach an agreement, when one application is given priority as a community application, or, as a last resort, by auction. The rules of the round set out which of these apply and how.
Does the UDRP cover names issued under an onchain TLD?
No. The UDRP is a contractual mechanism that binds registrars accredited by ICANN and the registrants who accept their registration terms. Onchain registries operate outside that contractual chain. A brand owner with rights in a name issued under an onchain TLD has to rely on other remedies, which vary by country and by the facts.
Is monitoring a round the same as monitoring onchain namespaces?
No. Monitoring a round means reading a defined list of applied-for strings once it is published, and then following the launch of each newly delegated TLD. Onchain monitoring has no list and no calendar: a TLD can be registered at any time, so the watch has to be continuous and has to cover more than one registry.
