Step-by-step: defend a generic-word .global domain

Step-by-step: defend a generic-word .global domain. UDRP and ccTLD domain recovery and defense across .global. Email the firm to assess your case.

A brand owner files a UDRP complaint against your .global domain. The name is a common dictionary word — "summit," "market," "connect," "origin" — and you registered it years ago for a project that had nothing to do with that complainant. Now you have 20 days to respond before a default transfer order moves the name out of your account. The generic character of the word is your strongest asset. Used correctly, it can also produce a finding of Reverse Domain Name Hijacking against the complainant.

To defend a generic-word .global domain under the UDRP, a registrant must demonstrate at least one safe harbor under Paragraph 4(c) of the Policy — most commonly a bona fide use or a legitimate noncommercial purpose — while dismantling the complainant's bad-faith case. The .global registry operates under the UDRP, so the same three-element test that governs .com applies here. The filing fee for a WIPO single-member panel starts at USD 1,500, paid by the complainant; your defense costs are separate.

This guide walks each step in sequence, flags the trap hidden in it, and explains what evidence actually decides the outcome.

Step 1: Understand What the .global Zone Means for Your Defense

The .global registry applies the UDRP in full — the same Policy, the same Rules, and the same WIPO procedural timetable that govern .com disputes. There is no special ccTLD procedure and no Nominet-style mediation stage before the panel appointment. That means the full adversarial UDRP process begins the moment WIPO formally commences the case.

Why does the zone matter? A complainant targeting a .global domain will often argue that the TLD itself signals an intent to attract global audiences under a brand name. Panels have generally treated the TLD as non-distinguishing for the confusing-similarity analysis — they typically ignore the string ".global" when comparing the second-level label to a trademark. So the label "summit" in summit.global is compared to a mark reading "SUMMIT," and any registered trademark containing that word will satisfy Element One for the complainant with minimal effort.

The trap at Step 1: registrants sometimes believe that because .global is a new gTLD with a small user base, the complainant's case is weak on confusion alone. That is incorrect. Panels routinely find confusing similarity on dictionary-word domains when the second-level label matches the trademark exactly, regardless of zone. Your real defense lives in Elements Two and Three, not in the TLD string.

For a read on whether the three UDRP elements are met in your specific .global dispute, reach us at info@cognomenlaw.com.

Step 2: Read the Complaint in Full Before Anything Else

Before drafting a single word of the response, read the complaint twice. The first pass identifies the trademark registration the complainant relies on: its filing date, its class of goods or services, and its jurisdiction. The second pass maps the complainant's factual theory of bad faith — what conduct it alleges and what evidence it attaches.

Generic-word complaints follow predictable patterns. The complainant will typically argue one of three bad-faith grounds under Paragraph 4(b): that you registered the domain to sell it at a profit to the mark owner; that you are a competitor attempting to disrupt its business; or that you are using the name to attract users by creating confusion with its brand. Each theory requires specific evidence to sustain it. Your response must address each theory directly, not generically.

The trap at Step 2: registrants who skim the complaint miss the specific exhibit — a WHOIS record, a screenshot of the website, a prior correspondence — that the complainant has placed in the record. Panels decide on the record actually filed. If the complainant has attached an email in which you offered to sell the domain, that single document can override an otherwise strong legitimate-interest argument. Know what is in front of the panel before you write your defense.

Check the complaint for procedural defects as well. Does it name the correct registrant of record? Does it name the correct registrar? Are all domains listed in one complaint registered to the same holder? Defects of that kind can be fatal to the complainant's case or at minimum delay it.

Step 3: Lock Down Your Legitimate-Interest Evidence Under Paragraph 4(c)

Paragraph 4(c) of the UDRP sets out three safe harbors, any one of which is sufficient to defeat the complaint. For a generic-word .global domain, the two most commonly available are: (i) demonstrable preparations for a bona fide commercial offering made before notice of the dispute; and (ii) legitimate noncommercial or fair use without intent to mislead or tarnish.

The word "demonstrable" does the work. Panels will not accept an assertion. They require contemporaneous documentation: business plans dated before the complaint was filed, wireframes, development invoices, incorporation documents naming the project, emails discussing the launch, or any record showing the domain was part of a genuine business activity. The generic character of the word strengthens this case considerably. A panel faced with "summit.global" registered by a company that operates event-management software has obvious reason to credit a legitimate interest in the word on its ordinary meaning, wholly apart from any complainant's trademark.

The trap at Step 3: the safe harbor applies to preparations made "before any notice" of the dispute — not before the complaint was filed, but before any notice, including any cease-and-desist letter or even a documented approach by the complainant. If the complainant sent a demand letter six months ago and you only began building a website after that, your preparation evidence post-dates notice. Panels treat that as suspect. Pull together all evidence and check its dates against every communication you have received from the complainant or its agents.

In our practice, the registrants who fare best are those who can produce a folder of dated project materials, not a retrospective narrative. If the folder does not exist — because the domain was purchased speculatively or parked — the analysis shifts. A legitimately held generic dictionary word, parked with no content, is still defensible, but the argument changes: panels applying the consensus view have recognized that generic-word domain holdings can themselves constitute a legitimate interest where the registrant had no knowledge of the complainant's trademark and the word has obvious value as a descriptor. That argument requires a careful factual showing that you were unaware of the mark and that the word's descriptive value explains the registration.

Is an RDNH Finding Realistic for a Generic-Word .global Domain?

Reverse Domain Name Hijacking — a panel finding that the complainant brought the complaint in bad faith to deprive a legitimate registrant — is available in any UDRP proceeding and is realistically available in a generic-word .global dispute where the complainant had clear notice of the word's descriptive meaning before filing. RDNH carries no monetary penalty, but it is a published reputational finding that brands pay attention to.

Panels have found RDNH where: the complainant's trademark was registered after the domain; the complainant knew or should have known the word was generic and the registrant had no knowledge of the mark; or the complainant mounted a reverse-burden argument — essentially daring the registrant to prove legitimacy with no affirmative bad-faith showing of its own. An RDNH finding in a generic-word case is most likely when (a) the registration predates the trademark application by a meaningful period, (b) the word is in common descriptive use in the industry, and (c) the complainant's evidence of bad faith is thin or conclusory.

The trap at Step 4: seeking RDNH is a litigation choice, not a free move. Raising it changes the tone of the response and may provoke supplemental filings. More importantly, a panel will rarely find RDNH unless the respondent has made a clear and affirmative showing of legitimacy first. Do not lead with RDNH. Build the legitimate-interest case and let the RDNH argument follow from the obvious inadequacy of the complainant's case.

We regularly advise respondents to include a measured RDNH request — one that specifically identifies the fact pattern (e.g., trademark postdating the domain registration, generic word with descriptive value, no evidence of targeting) — rather than a boilerplate sentence at the end of the response. The specificity is what earns panel attention.

If you are weighing whether to seek an RDNH finding in your .global response, email info@cognomenlaw.com for an assessment before the deadline.

Step 4: Draft the Response — Structure, Tone, and What Panels Read Carefully

A UDRP response is a pleading. It should read like one: precise, element-by-element, and free of emotional appeals. Panels are experienced adjudicators. They respond to factual precision and relevant citation of the consensus view; they do not respond to arguments about the complainant's market power or general unfairness.

Structure the response as follows. Open with a brief summary of why the complaint fails — ideally one paragraph that a panel could lift verbatim into its decision. Then address Element Two (legitimate interest) first, because it is where the generic-word argument is strongest and where you control the most evidence. Then address Element Three (bad faith), pointing to each Paragraph 4(b) theory and explaining why the facts do not support it. Close with the RDNH request if appropriate.

On tone: the response should be confident without being combative. Panels notice when a respondent is dismissive of the complainant's trademark rights entirely — that can read as evasion. Acknowledge that the complainant holds the trademark. Then explain precisely why that trademark does not reach your registration of a generic or descriptive term.

The trap at Step 4: annexes. Many respondents attach voluminous exhibits with no annotation. The panel will read what you direct it to read. Each exhibit should be numbered, referenced in the body of the response, and summarized in a one-sentence description of what it shows. A panel facing a two-page response and forty unnumbered exhibits will not excavate them. An annotated record does the work the panel would otherwise skip.

Sentence-length note on the deadline: the response must be filed within 20 days of formal commencement. That window runs from the date WIPO sends the commencement notification — not from the date you received the complaint, not from the date it was filed. Check the commencement email for the exact deadline date. Missing it by even one day typically results in a default, with the panel deciding on the complaint alone.

Step 5: Address the Cross-Zone Dimension — What If There Is Also a .com or a ccTLD?

A single UDRP complaint may cover multiple domains, but only if all domains are registered by the same registrant of record. If the complainant has also filed — or is threatening to file — against a .com or a country-code domain you hold, each proceeding is governed by its own rules.

The decision about how to structure a defense across zones matters. A .com dispute at WIPO runs under the same Policy as your .global case. A parallel defense on both domains in a single consolidated complaint is possible if you are the common registrant. If the complainant has filed separately — a .global complaint at WIPO and, say, a .uk complaint under the Nominet DRS — those are two distinct proceedings with different tests. The Nominet DRS uses an "abusive registration" standard, not the UDRP three-element test, and includes a mandatory mediation stage before a panel decision. The .uk defense strategy and the .global strategy, while related on the facts, must be tailored to each forum's rules.

Consider also the URS. For new gTLDs — and .global is a new gTLD — a complainant may alternatively file a URS complaint rather than a UDRP complaint. The URS applies a higher "clear and convincing" standard and its remedy is suspension, not transfer. A URS proceeding is faster and cheaper for the complainant but harder to win. If the complainant chose the UDRP over the URS for your .global domain, that choice itself is relevant: it signals the complainant believes the transfer remedy (rather than mere suspension) is the goal. That framing is worth noting in your response, because it reinforces the inference that this is a domain-acquisition effort dressed as a dispute.

In a recent matter involving a new gTLD and a descriptive single-word domain (spring 2025), we successfully defended a registrant who held both a .global and a .com version of the same generic term. The complainant filed against the .global only. We secured a denial of the complaint on legitimate-interest grounds, preserving both registrations — the .com was never endangered because the complainant knew the UDRP evidence for the .com would be even thinner than for .global.

Step 6: Understand What the Decision Looks Like — and What Happens After

A standard UDRP case at WIPO is normally completed within about two months of filing. The panel issues a written decision that is published on the WIPO website. If the panel denies the complaint, the domain remains with you and no further action is required at the registrar level — the registration simply continues. If the panel finds for the complainant, WIPO notifies the registrar and there is a brief implementation period before transfer, during which you may seek a court stay in the competent jurisdiction if you believe the decision is incorrect.

A finding of RDNH is noted in the published decision and in WIPO's public record. It does not carry a fine or a cost award — the UDRP does not permit monetary awards of any kind. Its value is reputational and strategic: it is on the public record and is regularly cited in subsequent UDRP proceedings involving the same complainant.

The trap at Step 6: many registrants believe a denial ends the dispute. It does not always do so. A complainant denied at the UDRP retains the right to pursue the matter in a competent court. Courts in many jurisdictions will independently evaluate the domain dispute. If the complainant holds a registered trademark and has genuine commercial grievance, a court action — particularly in the United States under anticybersquatting legislation — remains available. A robust denial decision that includes specific findings about the registrant's legitimate interest is useful evidence in any subsequent court proceeding, but it is not binding.

We have advised registrants who, after prevailing in a UDRP defense, later faced a court filing in the complainant's home jurisdiction. In those matters, the UDRP record — particularly the factual findings in the panel's decision — became central to the litigation defense. Building the record carefully in the UDRP response, even if you are confident of winning, serves the registrant's interests in any downstream dispute as well.

Related at COGNOMEN

• UDRP respondent defense and RDNH — full service overview for domain registrants facing a complaint
• How to file a UDRP response within the deadline — answers to the most common procedural questions
• URS vs. UDRP for new gTLDs — key differences and which procedure a complainant is likely to choose