How to choose between WIPO and the Forum for a .cloud dispute

How to choose between WIPO and the Forum for a .cloud dispute. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your case.

A brand owner discovers that a .cloud domain mirroring their trademark is already registered – pointed at a pay-per-click parking page, a competing storefront, or simply held dormant while someone waits for an offer. The domain sits in the gTLD space, so the UDRP applies. The question now is not whether to file a complaint. It is where.

To recover or defend a .cloud domain through the UDRP, a complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark the complainant holds, no legitimate interest on the registrant's side, and registration and use in bad faith. The forum choice – WIPO or the Forum (formerly the National Arbitration Forum) – does not change the legal test, but it affects filing cost, procedural pace, panel culture, and the strategic weight the decision carries. WIPO's single-panel filing fee is USD 1,500; the Forum's entry point is around USD 1,300. The difference is real but secondary to the factors covered below.

This page examines the governing rules for .cloud, the head-to-head comparison between WIPO and the Forum, the evidence that decides outcomes, and the concrete steps a complainant or respondent should take before choosing a provider.

Why the .cloud zone falls squarely under the UDRP

.cloud is an ICANN-accredited new gTLD, and every registrar authorized to sell .cloud domains is bound by the Uniform Dispute Resolution Policy as a condition of accreditation. That means the same three-element test, the same 20-day response window, and the same binary remedies – transfer or cancellation, nothing more – that govern .com apply equally here. No monetary damages are available. No injunction issues.

Some brand owners assume new gTLDs carry a different or relaxed procedure. They do not. The UDRP attaches to the registration contract the moment a .cloud domain is purchased from any accredited registrar. If anything, panels have shown particular willingness to infer bad faith in new gTLDs registered shortly after a trademark owner's mark became publicly known – because the registrant's awareness of the mark at the time of registration is harder to deny when the domain exactly replicates a recognizable brand in a sector-specific zone like .cloud.

The URS (Uniform Rapid Suspension) also applies to .cloud as a new gTLD. However, URS only suspends a domain for the remainder of its registration term – it does not transfer ownership. For brand owners who want the domain, not merely its deactivation, the UDRP is the operative route.

What does the three-element UDRP test require for a .cloud complaint?

A .cloud complainant must establish each of Paragraph 4(a)'s three cumulative elements; failure on any one defeats the complaint entirely. Element one – confusing similarity – is the easiest hurdle. Where the domain incorporates the complainant's registered mark in full, panels routinely find the element met regardless of any descriptive suffix or TLD appended. The .cloud suffix itself is generally disregarded in the comparison, as panels strip the TLD before assessing similarity.

Element two requires showing the registrant lacks rights or legitimate interests. The complainant need only make a prima facie case; the burden then shifts to the registrant to produce evidence of one of the Paragraph 4(c) safe harbors – a bona fide offering of goods or services under the name before the dispute arose, being commonly known by the name, or legitimate noncommercial or fair use. In our practice, we see element-two defenses most frequently attempted on the "bona fide offering" and "fair use" grounds, and both require the registrant to produce contemporaneous evidence, not post-hoc assertions.

Element three – bad faith in both registration and use – is where most contested cases are decided. Paragraph 4(b) lists non-exhaustive indicators: registration primarily to sell to the mark owner at a profit, a pattern of abusive registrations, disrupting a competitor's business, or intentionally attracting users by trading on the mark's goodwill for commercial gain. Passive holding – simply sitting on a domain without active use – can itself constitute bad faith use where the registrant could have had no plausible legitimate reason for the registration.

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

How does WIPO compare to the Forum for a .cloud filing?

WIPO and the Forum together account for roughly 97% of all UDRP proceedings globally, and for .cloud disputes either is an eligible provider. The choice between them is a strategic one. Neither is uniformly "better"; each carries attributes that favor specific situations.

Filing fees. WIPO charges USD 1,500 for a single-member panel covering one to five domains. The Forum's entry point is approximately USD 1,300 for one or two domains on a single-member panel. The gap narrows at higher domain counts, and both providers charge more for a three-member panel. If the complainant opts for a single-member panel but the respondent requests a three-member panel, the parties generally split the higher three-member fee – a cost variable worth budgeting for.

Procedural pace. A standard UDRP case at either provider typically concludes within about two months of filing. WIPO also offers an expedited option – roughly one month for single-panel cases of up to five domains – useful where a .cloud domain is actively diverting traffic or causing immediate commercial harm. The Forum does not publish a comparable formal expedited track, though processing times in uncomplicated cases can be similarly quick.

Panel selection and culture. Both providers draw from pools of experienced panelists with UDRP expertise. WIPO's international character means its panel pool is particularly diverse across jurisdictions, which can matter where the complainant's trademark rights arise under non-US law – including EU, UK, or Asia-Pacific registrations – and the registrant is domiciled outside the United States. The Forum's panel pool is deep and well-established, with particular strength for US-domiciled parties and US trademark holders. Neither is a formal rule; it is a practical observation from our experience handling disputes at both providers.

Decision visibility. WIPO publishes its decisions in a fully searchable database and issues its Jurisprudential Overview, which distills the consensus positions on recurring issues. That transparency is useful for predicting how a panel may approach a novel fact pattern in a .cloud matter – for instance, where the complainant holds trademark rights that postdate the domain registration. The Forum publishes decisions as well, though the WIPO database is more consistently cited in subsequent proceedings.

Language of the proceeding. The UDRP requires that the language of the administrative proceeding follow the language of the registration agreement unless the parties agree otherwise or a panel orders differently. If the registrant's agreement is in a language other than English, WIPO's multilingual infrastructure handles that more fluently. The Forum operates predominantly in English.

In our practice, the default for .cloud complaints where the complainant holds international trademark rights and the dispute involves a non-US registrant is WIPO. Where the complainant is US-based, the mark is US-registered, and the registrant appears US-domiciled, either provider is suitable and cost-efficiency at the Forum becomes a reasonable consideration.

What evidence actually decides a .cloud UDRP outcome?

Forum or WIPO, the decision turns on evidence – not on which provider received the filing. Panels decide on the written record. There is no oral hearing. What you submit at the outset is, with rare exceptions for supplemental filings, what the panel sees.

For the complainant, the core evidentiary package for a .cloud dispute should include: certified trademark registrations (or evidence of common-law rights where registration is absent), WHOIS or RDDS records showing the registrant's identity and registration date relative to the mark's priority date, screenshots of the domain's current and historical use (the Wayback Machine is a standard source), any communications from the registrant offering to sell the domain, and evidence placing the registrant on constructive or actual notice of the mark. Where the domain was registered shortly after a press announcement or product launch bearing the mark, that timing is itself significant evidence.

For the respondent, evidence must be contemporaneous. Panels are skeptical of after-the-fact narratives. If the registrant registered the domain because they were known by that name or operating a bona fide business under it, the registration-era documents – business records, contemporaneous website captures, commercial contracts – are essential. Generic dictionary word claims in .cloud are harder to sustain than in early-internet-era .com cases, because the specific gTLD signals a technological or cloud-computing association that narrows the plausible universe of legitimate registrants.

In a recent matter – a .cloud typosquat, spring 2025 – we assembled a showing of bad faith from WHOIS history, a pattern of approximately eight similar registrations by the same registrant across related gTLDs, and a documented pay-per-click monetization scheme. The panel ordered transfer within the standard two-month window, with no extension needed.

To assess the three UDRP elements and determine whether your evidence supports a complaint or a defense, email info@cognomenlaw.com.

Should a .cloud respondent choose the same forum as the complainant filed in?

A respondent does not choose the forum – the complainant selects the provider, and the respondent receives the complaint from that provider. The respondent's choices are narrower: file a response within 20 days of commencement, request a three-member panel (splitting the higher cost with the complainant), submit evidence of legitimate interest, and where the complaint is abusive on its face, seek a finding of Reverse Domain Name Hijacking (RDNH).

RDNH is available at both WIPO and the Forum. It is a panel finding that the complaint was brought in bad faith to deprive a legitimate registrant of a domain – essentially the cybersquatting concept inverted. An RDNH finding carries no monetary penalty but creates a reputational record. Panels at both providers have granted RDNH findings where the complainant filed with full knowledge that the respondent had prior rights, a long registration history, or a legitimate business use that the complaint ignored.

In a recent defense matter (a .cloud domain, autumn 2024), a registrant approached us after receiving a WIPO complaint from a complainant who had registered its trademark years after our client had registered and genuinely used the domain for cloud-services marketing. We built the legitimate-interest record from contemporaneous business filings and a documented web presence predating the complainant's mark. The panel denied transfer and issued an RDNH finding. The complainant had filed without adequate due diligence – a pattern we see more frequently as brand owners conflate UDRP with a standard trademark enforcement letter.

Does every respondent with a plausible story prevail? No. Default rates – cases where the registrant files no response at all – are high, and panels generally grant transfer in uncontested cases where the complainant has submitted a facially complete record. A respondent with legitimate interests who does not respond forfeits those interests by silence.

How does the UDRP route for .cloud compare to other dispute paths?

The routing decision is simpler for .cloud than for many other zones because the ccTLD alternatives are not available. .cloud is a gTLD. It is not a country-code zone, so Nominet DRS, EURid ADR, DENIC dispute entry, and similar national procedures simply do not apply. The operative dispute paths are the UDRP (at WIPO or the Forum), the URS, or – where the complainant is willing to invest substantially more time and cost – court action.

Consider the routes in sequence. If the goal is transfer and the complainant can meet the three UDRP elements, WIPO or the Forum is the standard path: filing fee of USD 1,300–1,500 for a single-member panel, a two-month timeline, a binary transfer-or-cancellation outcome. If the goal is rapid suspension and full transfer is not essential – perhaps the domain is actively diverting traffic right now – URS offers a faster suspension at lower cost, though the domain will eventually re-enter registration on expiry rather than landing in the complainant's account. If the complainant also wants monetary damages, neither the UDRP nor the URS reaches money. That requires US anticybersquatting litigation handled with local litigation counsel, substantially higher in cost and duration, but the only path that combines a transfer remedy with a damages award.

Where the registrant is unknown or has concealed identity behind privacy protection, the UDRP still allows filing against the privacy registrant as disclosed in the RDDS record. Registrar unmasking through the complaint process is standard procedure; WIPO's and the Forum's provider rules address it directly.

And what if the same brand is infringed across both a .cloud domain and a .com? A single UDRP complaint can cover multiple domains only where the domains are registered to the same registrant. Where the .com and .cloud registrants differ, two separate complaints are required. Filing both at WIPO allows portfolio coordination and consistent panel assignment if sought; filing one at WIPO and one at the Forum risks divergent decisions on similar facts.

What is the realistic cost structure for a .cloud UDRP dispute?

Total cost has two independent components: the forum filing fee and legal fees. They are always separate and should be budgeted separately.

The forum filing fee for a .cloud single-domain complaint is USD 1,500 at WIPO (single-member panel) or approximately USD 1,300 at the Forum. If the respondent requests a three-member panel, both parties share the higher three-member fee – USD 4,000 at WIPO. WIPO offers a partial refund of approximately USD 1,000 of the USD 1,500 single-panel fee if the case is withdrawn or settled before a panel is appointed, which is a meaningful consideration where settlement is possible.

Legal fees for a straightforward single-domain UDRP complaint – assembly of the complaint, evidence package, and filing – commonly fall in the USD 3,000–7,000 range in the market, separate from the forum filing fee. Respondent defense work, particularly where an RDNH argument is viable, runs in a comparable range. Contested three-member panel matters, where additional rounds of briefing may occur, carry higher totals. These are market ranges, not COGNOMEN quotes; the right measure is always the complexity of the specific record.

For a brand owner choosing between WIPO and the Forum primarily on cost: the fee differential alone – roughly USD 200 on a single-panel single-domain filing – rarely justifies overriding a strategic preference for panel culture, expedited track availability, or multilingual capacity. The legal fee is typically the dominant cost variable regardless of provider.

What is the step-by-step path from decision to filed complaint?

Step one is the pre-filing assessment: do the three UDRP elements appear met on the available evidence? This is a legal question, not a checklist. A complainant who files without clearing element two – registrant's lack of legitimate interest – or without genuine bad-faith evidence for element three risks a panel finding for the respondent and, in an egregious case, an RDNH finding in response.

Step two is forum selection, applying the factors set out above: the complainant's trademark jurisdiction, the registrant's apparent location, whether an expedited track is needed, the domain count, and budget.

Step three is the complaint draft. A UDRP complaint is a structured legal document covering the three elements in order, attaching exhibits in a format both providers specify in their Supplemental Rules. Errors in format or missing exhibits can cause a complaint to be found formally deficient, requiring cure and resubmission – adding time.

Step four is filing and commencement. After the provider verifies formal compliance, it serves the complaint on the registrant and the registrar. The 20-day response window opens at that point.

Step five is monitoring and, if a response is filed, possible supplemental filings (subject to provider and panel discretion). Most cases do not reach supplemental rounds, but where a response raises a new factual claim, a reply can be critical.

Step six is the panel decision and registrar implementation. If the panel orders transfer, the registrar implements it after a short waiting period, during which the respondent may seek a court stay. That court route is rarely pursued but remains available.

Does the process feel linear? It is, mostly – but each step hides a decision point that can make or break the outcome. The evidence assembled at step one determines the quality of the complaint at step three. The forum chosen at step two affects the panel pool available at step five. And a missed deadline at any stage forfeits the right to be heard at that step.

Related at COGNOMEN

• UDRP domain recovery – full service across gTLD and new-gTLD zones
• Recovering a .org domain registered in passive holding – the bad-faith analysis
• Respondent defense and RDNH – protecting a domain registered in good faith