What is Legal Rights Objection (LRO)? Definition and meaning

A Legal Rights Objection (LRO) is a formal challenge filed with WIPO during ICANN's new generic top-level domain application process, allowing a trademark holder to argue that delegation of a proposed new gTLD string would infringe its established rights.

An LRO is not a UDRP complaint and not a URS filing. It targets the string itself – the proposed new zone, such as .brand or .term – before any domain registrations inside that zone can occur. The objector must show that the applied-for gTLD string takes unfair advantage of, or is detrimental to, its distinctive mark. WIPO administers LRO proceedings as the designated dispute-resolution provider for this objection type under ICANN's rules.

This page defines the LRO precisely, distinguishes it from the procedures it resembles, traces its rules, and shows the patterns where it matters most.

What an LRO is – and what it is not

An LRO is a rights-based objection to a top-level domain string in ICANN's application process. It does not target a registration inside an existing zone. It does not transfer or suspend a domain. Its sole function is to prevent ICANN from delegating a new gTLD that would harm a trademark holder with established rights.

The term readers most often confuse with LRO is UDRP complaint. A UDRP complaint challenges a second-level domain – for example, yourbrand.com – after that domain has already been registered. An LRO operates one level higher and one stage earlier: it challenges the zone name itself, before any delegations occur and before anyone can register anything inside it. The test is different, the forum is different, and the timing window is strictly bounded by ICANN's published schedule.

A second source of confusion is the Trademark Post-Delegation Dispute Resolution Procedure, which applies after a new gTLD is already operating. The LRO is a pre-delegation tool. Once the string has been delegated, LRO is no longer available; the objector's remaining routes are UDRP, URS, or court action against registrations inside the live zone.

Where the LRO comes from in the rules

ICANN's Applicant Guidebook for new gTLDs establishes four categories of objection: string confusion, legal rights, limited public interest, and community. The Legal Rights Objection is specifically designed for trademark holders. WIPO is the designated provider for LRO proceedings. The objection must be filed within a defined window that runs from String Confirmation Day – the point in ICANN's process at which applied-for strings are publicly confirmed.

As of August 2026, ICANN's application window for the next new-gTLD round closed on 12 August 2026. ICANN announced it had received more than 1,600 primary applications. String Confirmation Day and the LRO filing window follow later in the evaluation schedule; ICANN sets those dates, and any brand owner monitoring the round should confirm the current schedule with counsel.

The LRO standard itself draws on trademark law. An objector shows (1) that it has rights in a name that is identical or confusingly similar to the applied-for string, and (2) that delegation of that string would take unfair advantage of, or be unjustifiably detrimental to, those rights. This is a higher threshold than similarity alone. Panel examiners at WIPO weigh the fame of the mark, the intent evident from the application, and the likely public perception of confusion.

How the LRO works in practice

Three patterns recur in LRO practice, and each carries a different strategic calculus.

Pattern 1: a third party applies for a string that is identical to a well-known brand. A global consumer goods company holds a mark in continuous use for decades. An unrelated applicant applies for .itsbrand. The company files an LRO at WIPO within the objection window. WIPO appoints an expert panel. The panel reviews the mark's distinctiveness, the applicant's stated purpose, and the likelihood that internet users would associate the zone with the mark holder. Where the mark is famous and the applicant has no plausible independent basis for the string, this pattern produces the strongest objection.

Pattern 2: a brand owner applies for its own .brand gTLD, and a competitor or squatter files a defensive LRO. This inverts the more common scenario. The objector's case is weaker – a brand owner applying for its own name has an obvious legitimate basis – but the objection forces costs and delay on the applicant. Applicants in this position need a clear record of prior rights and a response that demonstrates the applied-for string is their own mark, not a generic term.

Pattern 3: a descriptive or generic string overlaps with a registered mark. An applicant seeks .cloud, .green, or another term that multiple parties have registered as trademarks in different classes and territories. LRO proceedings in this scenario are contested, because no single party can show exclusive rights to a string with broad independent meaning. Panels are unlikely to sustain an LRO against a string that is primarily descriptive, even if the objector holds a registration for it. A brand owner should assess the distinctive character of its mark honestly before investing in this type of objection.

Why the LRO matters to a brand owner now

With the 2026 round now past its application window, brand owners face a closing countdown to the objection stage. Miss the LRO window and the string will proceed through evaluation without a trademark challenge on the record. The post-delegation remedies – UDRP, URS suspension – operate at the registration level inside the zone, not at the zone level itself. They are useful but they arrive later and they address individual domain names, not the delegated string.

A new zone carrying your brand name creates structural problems beyond any single registration. Phishing, invoice fraud, and customer confusion can operate through the zone name itself even before a malicious operator registers a single domain. This is the scenario AUDIENCE_PAIN describes: a zone launches, a third party holds it, and your brand is embedded in the zone string before you have any domain-level rights to challenge.

Brand owners holding marks that could be targeted in the current round should map their portfolio against the confirmed application strings as they emerge on String Confirmation Day. The LRO window is short and the preparation – gathering evidence of rights, assessing distinctiveness, and drafting the objection – cannot be left to the last days of the period.

LRO versus URS and UDRP: a brief comparison

These three instruments address different moments and different levels of the DNS hierarchy. Placing them side by side clarifies when each applies.

The LRO operates before delegation. It challenges the zone string. The only outcome is rejection or approval of the application – there is no transfer or suspension of a domain name. WIPO decides. The window runs from String Confirmation Day.

The UDRP operates after a domain is registered inside an existing zone. It challenges a second-level registration, such as yourbrand.newzone. The remedies are transfer or cancellation. WIPO, the Forum, CAC, and ADNDRC are all providers. The respondent has 20 days to file a response. The UDRP's three-element test – similarity, no legitimate interest, bad faith registration and use – governs the case.

The URS is available for new-gTLD domains specifically. Its remedy is suspension, not transfer – a point widely misunderstood. It operates under a clear-and-convincing evidentiary standard, which is higher than the UDRP's preponderance standard. It is faster and cheaper than a UDRP, but it does not put the domain in the complainant's hands. For an LRO-level question about the zone string itself, neither the UDRP nor the URS applies.

For a closer look at the distinction between the two post-delegation tools, see urs vs udrp ai, which works through the decision factors for new-gTLD registrations in detail.

Related concepts: rights or legitimate interests

An LRO objector must demonstrate positive rights – an established trademark, held before the application was filed. The question of whether the other party has rights or legitimate interests of its own is a separate inquiry, one more familiar from UDRP practice. In the LRO context, the applicant for the gTLD string may assert a community, geographic, or descriptive interest that displaces the objector's claim. Understanding the boundary between these concepts matters when assessing whether an objection is worth filing. For a closer examination of how rights and legitimate interests are analyzed in domain disputes generally, see What is Rights or legitimate interests? Definition and meaning.

About COGNOMEN

COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants – including respondent-side defense and reverse domain name hijacking. In our practice, we advise brand owners at every stage of the new-gTLD cycle, from monitoring the application round through filing LRO objections and managing post-delegation disputes under the UDRP and URS. To discuss a Legal Rights Objection or a new-gTLD dispute, contact info@cognomenlaw.com.

Related at COGNOMEN

• urs newgtld – full-service handling for new-gTLD disputes and URS filings
• What is Rights or legitimate interests? Definition and meaning – how the legitimate-interests test applies across UDRP and new-gTLD zones
• urs vs udrp ai – decision guide for choosing between URS suspension and UDRP transfer

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.