Step-by-step: protect a brand in a new .org gTLD launch

Step-by-step: protect a brand in a new .org gTLD launch. UDRP and ccTLD domain recovery and defense across .org. Email the firm to assess your case.

A new .org registry opens registrations. Within hours, a third party has secured the domain that matches your brand. The registrant has no connection to your business. The landing page is blank — for now. You want to protect a brand in a new .org gTLD launch before that page becomes a fraud site, a competitor redirect, or a ransom demand.

Protecting a brand during a new .org gTLD launch means working through a layered set of tools in sequence: the Trademark Clearinghouse (TMCH) for pre-launch notice and blocking, the Uniform Rapid Suspension (URS) for fast suspension of clear-cut cybersquats, and the UDRP for transfer where URS cannot reach. The decisive facts are trademark registration status and the timing of your action relative to the launch phases. Acting before the domain is registered is always better than acting after it.

This guide follows that sequence step by step, flags the trap hidden in each, and explains which tool fits which situation in the .org zone.

Why does .org have its own protection rules — and what governs them?

.org is a legacy gTLD administered by the Public Interest Registry (PIR) and operates under ICANN's standard contractual framework, meaning the UDRP and the URS both apply. For new .org launches — meaning a new registry operating under the .org string or a variant rollout by PIR with new registration phases — ICANN's requirements for pre-launch rights protection mechanisms (RPMs) impose specific obligations on the registry. Those RPMs include mandatory Sunrise periods for trademark holders, TMCH integration for claims notices, and post-launch access to both URS and UDRP.

The practical consequence: a brand owner who has not entered its mark in the TMCH before the Sunrise period opens has effectively skipped the first line of defense. That is the first trap. Registration in the TMCH is not automatic; it requires an active application, verification of the underlying trademark, and renewal. Missing the Sunrise window means competing with general-availability registrations from day one.

In our practice, we regularly advise brand owners who discover that a new .org launch was announced months before they were aware of it. By the time they call, the Sunrise period is closed. The guide below works backward from that reality — what you can still do, and how quickly each tool can act.

Step 1: Register your mark in the Trademark Clearinghouse before the launch phases open

TMCH registration is the foundational step for protecting a brand in any new gTLD launch, including .org variants. The TMCH is a centralized database maintained under ICANN authority; it records verified trademark rights and feeds that data to participating registries during Sunrise and claims-notice periods.

A verified mark in the TMCH gives you two rights. First, during the Sunrise period, you may register the domain matching your mark before general availability opens — at a registry-set premium, but with priority. Second, during the claims period (typically lasting 90 days after Sunrise, though the exact window varies by registry), any third party attempting to register a domain matching your mark receives a real-time notice that a mark is on file. If they proceed anyway, that notice becomes important evidence in any subsequent URS or UDRP proceeding.

The trap in Step 1: the TMCH records only registered trademarks in qualifying jurisdictions, not common-law marks or unregistered rights. If your brand rests on use-based rights rather than a registration, TMCH entry is unavailable. You then have no Sunrise access and no claims-notice trigger. That pushes your entire brand-protection strategy into post-registration enforcement — the harder path.

For marks that do qualify, TMCH registration should be completed well ahead of any known launch announcement. ICANN requires registries to allow at least 30 days of Sunrise, but the timeline between announcement and launch can be short. We have seen brand owners miss Sunrise by days simply because TMCH verification queues ran longer than expected.

If a launch phase has already opened or you are unsure whether your mark qualifies for TMCH entry, contact info@cognomenlaw.com for an assessment before the window closes.

Step 2: Monitor the Sunrise and claims periods actively — and respond to any conflicting application fast

TMCH entry alone does not prevent conflicting registrations. Sunrise periods in new gTLD launches operate on a first-come, first-served or auction basis depending on registry design; multiple parties with legitimate-looking trademark claims can apply for the same domain. Sunrise disputes — challenges to another party's Sunrise application — are time-sensitive and procedurally specific, governed by the Sunrise Dispute Resolution Policy (SDRP) that ICANN mandates registries to implement.

The claims period that follows Sunrise is your monitoring window. During claims, any party that registers a domain matching your TMCH-recorded mark receives a notice. They may still complete the registration. Your obligation at this stage is to watch for registrations that slide through and to flag them immediately for URS or UDRP assessment.

The trap in Step 2: many brand owners treat claims-notice monitoring as passive. It is not. A registrant who received a claims notice and registered anyway has arguably done so with constructive knowledge of your mark. That fact, documented, strengthens a subsequent bad-faith argument significantly. But documenting it requires a screenshot of the notice, a record of the date, and evidence that the registrant proceeded with knowledge. Those records must be gathered in real time; reconstructing them later is difficult.

Automated monitoring services can flag new registrations matching your TMCH records across participating registries. We recommend that brand owners operating in multiple zones maintain active monitoring rather than relying on inbound alerts from the registry alone.

Step 3: Choose between URS and UDRP — the choice that most brand owners get wrong

A bad-faith .org registration exists. You now face the central decision: file a URS or a UDRP complaint? The answer depends on what you need and how strong your evidence is.

The URS (Uniform Rapid Suspension) is designed for speed. It applies to new gTLDs, including .org variants launched under new registry agreements, and it offers a faster decision than the UDRP — typically within weeks rather than the UDRP's roughly two months. But the URS remedy is suspension, not transfer. The domain is taken offline for the registration term; it does not come to you. And the evidentiary standard is deliberately higher: the complainant must establish its case by clear and convincing evidence, a more demanding threshold than the UDRP's balance-of-probabilities standard. The URS is best suited to the clearest cases — an exact match of your registered mark, a live abuse (phishing, fraud, competitor confusion), and documentary evidence that is unambiguous.

The UDRP is the tool if you want the domain transferred. It applies to .org under the standard ICANN framework. It requires proof of all three elements under Paragraph 4(a): confusing similarity to a mark, no legitimate interest in the registrant, and bad faith in registration and use. A standard WIPO proceeding costs USD 1,500 in filing fees for a single-member panel on one to five domains. The timeline is roughly two months. The UDRP can handle more complex fact patterns — typosquats, phonetic variants, and cases where the registrant has a facially plausible but ultimately hollow defense.

The decision matrix in practice: if the domain is an exact match of your registered mark, is being used abusively right now, and you primarily need it offline quickly, URS is the faster tool. If you need the domain transferred to you, the fact pattern is contested, or the registrant is likely to raise a legitimate-interest defense, UDRP is the right route. In a recent matter (a .org cybersquat, spring 2025), we filed a UDRP rather than a URS after assessing that the registrant appeared to have constructed a thin fair-use argument — the UDRP's broader briefing scope let us address that argument directly, and the panel ordered a transfer.

There is also a hybrid scenario worth noting. Where you file URS and succeed, the domain is suspended. If the registrant seeks a de novo challenge (available under URS rules), or if you want the domain transferred after the URS suspension expires, you may need to follow up with a UDRP filing. We plan both proceedings together in situations where the abuse is clear-cut but transfer is also the eventual goal.

To weigh URS against UDRP for your specific .org registration, email info@cognomenlaw.com — we can assess the three UDRP elements and the URS clear-and-convincing standard against your evidence in one call.

Step 4: Assemble the evidence package — and understand what actually decides the outcome

Whether you file URS or UDRP, the evidence package is the spine of the proceeding. Panels decide on the written record; there is no hearing, no live cross-examination. The documents you submit are the case.

For Element 1 (confusing similarity) under the UDRP, the trademark certificate is typically sufficient. A registered mark in any qualifying jurisdiction establishes rights. The comparison between the mark and the domain string is largely mechanical. Typosquats — minor character substitutions, added words like "official," "inc," or the zone itself — are regularly found confusingly similar by panels. This element is rarely the battleground.

For Element 2 (no legitimate interest), the complainant bears an initial burden of making a prima facie case, which then shifts to the registrant to produce evidence of a right or legitimate interest under the safe harbors of Paragraph 4(c): a bona fide offering before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use. In new gTLD launch contexts, a registrant who received a TMCH claims notice before registering cannot easily claim ignorance of the mark. That notice record is valuable here.

For Element 3 (bad faith in registration and use) — the UDRP's cumulative requirement — you must show both. Panels have consistently recognized that a registrant who registered a domain identical to a well-known mark with no plausible legitimate use satisfies the bad-faith test. Passive holding — doing nothing with the domain — can itself satisfy the use limb in appropriate circumstances, particularly where the mark is well-known and the registrant offers no innocent explanation. The claims-notice record, registration timing relative to the launch, WHOIS/RDDS data, and the content (or absence of content) on the domain all feed this element.

The trap in Step 4: brand owners routinely underinvest in the evidence for Elements 2 and 3 because Element 1 seems easy. A thin complaint that proves similarity but offers bare assertions on bad faith gives the registrant room to survive on default. A defaulting registrant — one who files no response — still requires the panel to be satisfied on all three elements. Submit the evidence as if the registrant will contest.

Step 5: File the complaint — and choose the right forum for .org

For a .org domain under the UDRP, WIPO and the Forum are the two primary providers, together accounting for approximately 97% of all UDRP proceedings. WIPO is the natural starting point for most brand owners: it is the most widely recognized forum, its panel pool is deep, and its published decisions provide the most extensive body of precedent. The filing fee is USD 1,500 for a single-member panel on one to five domains. The Forum's entry-level fees begin around USD 1,300.

The choice between WIPO and the Forum is tactical. WIPO's panelists tend to write longer, more thoroughly reasoned decisions. For a fact pattern involving a nuanced bad-faith argument — passive holding, a claimed fair-use defense, or a pattern-of-conduct allegation — WIPO's deliberative process is generally preferable. The Forum may be faster in scheduling on straightforward cases. For new gTLD launch disputes that involve a clear abusive registration, either forum will suffice, and we select based on the specific fact pattern and any existing precedent that favors one forum's interpretive approach.

Once filed, the respondent has 20 days to respond after the case commences. A standard case resolves in roughly two months absent procedural complications. WIPO also offers an expedited option delivering a decision in about one month, available for single-panel cases covering up to five domains — a useful tool when active abuse is ongoing and speed matters.

After the panel decision, the registrar implements the outcome. For a transfer order, the registrar places the domain in a temporary lock and, if no court action is filed by the registrant within 10 days, effects the transfer to the complainant. That 10-day window is the last point at which a determined registrant can delay execution by filing suit in a competent court.

Step 6: What if the registrant fights back — or you discover you are the target of an abusive complaint?

Not every .org domain dispute runs in one direction. Registrants who hold a domain in genuine good faith sometimes receive UDRP complaints from brand owners who overreach — filing against a domain that the registrant legitimately registered, perhaps because it matches a descriptive term or the registrant's own name, and using the UDRP as a mechanism to take a domain they want rather than a domain they are entitled to recover.

Panels may make a finding of Reverse Domain Name Hijacking (RDNH) — a determination that the complaint was brought in bad faith to deprive a legitimate registrant of a domain. RDNH carries no monetary penalty, but the finding is public and reputational. We regularly defend registrants facing overreaching UDRP complaints, including in .org and other gTLD zones, and we pursue RDNH findings where the record supports them.

For a registrant who receives a UDRP complaint in a new .org launch context, the 20-day response window is firm. Missing it results in a default, and panels routinely transfer on default where the complainant's evidence satisfies the three elements — even without a counter-submission. The most common mistake a registrant makes is waiting to see what happens. Nothing good happens by waiting.

A registrant's strongest defenses under Paragraph 4(c) are: evidence of a bona fide offering of goods or services at the domain before the dispute arose, evidence that the registrant is commonly known by the name corresponding to the domain, or evidence of legitimate noncommercial or fair use without intent to mislead. In new gTLD launch contexts, a registrant who can show that it registered during a Sunrise period on the basis of its own trademark rights has a strong record for rebuttal.

In a recent matter (a contested .org registration, autumn 2024), we acted for a respondent who had held a matching domain for years as part of a genuine fan-site project. The complainant — a corporate brand owner — filed for transfer relying on a newly obtained trademark registration that post-dated the domain's registration. The panel found for the respondent on bad faith and issued an RDNH finding, noting that a trademark acquired after the domain's registration cannot retroactively make the registration bad faith.

Related at COGNOMEN

• URS and new gTLD dispute services — full overview of suspension and transfer options across new gTLDs
• TMCH claims notice — how to respond when a claims notice is issued for your mark
• Proving legitimate interest in .org — respondent defense and RDNH findings