How to choose between URS and UDRP for a .cloud domain

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

A brand owner discovers that a .cloud domain matching its registered mark has been registered by a stranger and is pointing at pay-per-click advertising. Two dispute procedures are available: the Uniform Rapid Suspension System (URS) and the Uniform Domain Name Dispute Resolution Policy (UDRP). Both apply to .cloud as a new generic top-level domain. The choice between them is not cosmetic – it determines the remedy you receive, the evidentiary standard you must meet, and the timeline to resolution.

To choose between URS and UDRP for a .cloud domain, the decisive question is whether you need the domain suspended quickly or transferred to you permanently. The URS provides suspension for the remainder of the registration term at a lower cost but requires a clear and convincing evidentiary standard and delivers no transfer. The UDRP, filed at WIPO with a filing fee starting at USD 1,500 for a single-member panel, takes roughly two months but transfers ownership and applies the standard three-element test under Paragraph 4(a) of the Policy.

This page sets out the legal test for each procedure, maps the fact patterns that favor one route over the other, and explains the evidence and process your case will need – so you can act, not just analyze.

What rules apply to .cloud disputes, and why does that matter?

.cloud is a new gTLD launched in the expansion of the domain name space by ICANN, and like all new gTLDs it is bound by the UDRP and the URS as mandatory dispute-resolution policies in the registry agreement. Both procedures are therefore available for every .cloud domain registered through an ICANN-accredited registrar. There is no separate national or sectoral rule specific to .cloud: the global UDRP text and the URS rules apply in full.

That availability is the starting point, not the finish line. A complainant who goes to the wrong procedure wastes the filing fee and the time. A complainant who files URS when the evidence falls short of the heightened standard walks away with nothing and has alerted the registrant. In our practice, every .cloud matter we assess begins with the same threshold question: what remedy does the client actually need, and what can the evidence support right now?

One further point is worth noting for registrants. If you hold a .cloud domain in good faith and receive a URS or UDRP complaint, the procedural route chosen by the complainant directly affects your exposure, your response deadline, and your defense options. A URS suspension is faster and harder to reverse once entered than a UDRP transfer order during the appeal window.

How does the URS work for a .cloud domain, and when should you choose it?

The URS is a suspension-only remedy: if the complaint succeeds, the domain is locked and pointed at an informational page for the remainder of the current registration term. Ownership does not transfer. The registrant can renew the domain when the term expires, but during the suspension period the brand owner has effective control of the name's resolution. The URS was designed for cases of clear-cut, egregious abuse – a domain that is obviously confusingly similar to a well-known mark, with no plausible defense.

The URS applies a clear and convincing evidentiary standard rather than the UDRP's preponderance standard. That distinction is material. Clear and convincing evidence means the panel must be highly confident in each element; a close case will fail. The three elements are substantively the same as the UDRP elements – confusing similarity, no legitimate interest, bad faith – but the bar for satisfaction is set higher.

Choose the URS for a .cloud domain when three conditions align: the mark is registered and well-known, the infringement is naked (no colorable defense visible from the WHOIS or the website), and your primary goal is rapid neutralization rather than permanent acquisition. The URS filing fee is lower than the UDRP, and a successful URS case can be decided faster. If you need the domain back in your hands with full registrant rights, the URS is the wrong tool.

In a recent matter – a .cloud typosquat of a well-known software brand, spring 2025 – we advised the brand owner to pursue the UDRP rather than the URS, because the registrant was actively redirecting traffic to a competing product. The goal was transfer and permanent control. The domain was transferred approximately seven weeks after the complaint was filed.

How does the UDRP work for a .cloud domain, and when is it the better route?

The UDRP is the full-form dispute procedure that has governed domain-name recovery since ICANN adopted it in 1999. A successful complaint results in transfer or cancellation of the domain – permanent, not time-limited. Under Paragraph 4(a) of the Policy, the complainant must prove all three elements: the domain is identical or confusingly similar to a trademark in which the complainant has rights; the registrant has no rights or legitimate interests; and the domain was registered and is being used in bad faith.

That last element is cumulative: registered AND used in bad faith. A panel will not transfer a .cloud domain merely because the registration looks opportunistic if current use looks passive and the surrounding facts are ambiguous. The UDRP's preponderance standard does not make the cumulative bad-faith element disappear. Complainants who misread the passive-holding doctrine – which panels apply carefully and narrowly – sometimes lose cases they expected to win.

Choose the UDRP for a .cloud domain when any of these conditions are present: you want permanent transfer rather than suspension; the evidence of bad faith, while clear, is not so overwhelming as to satisfy the URS clear-and-convincing standard with certainty; the registrant has constructed a defense (a "use" of the name, a business argument, a prior registration date that requires scrutiny); or you want the option of a three-member panel for a precedent-quality decision. WIPO and the Forum are both available for .cloud UDRP complaints; WIPO handles the large majority of new-gTLD cases in practice.

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

What evidence decides the outcome, and what does "bad faith" require in practice?

Evidence decides .cloud disputes at both procedural levels, but the type and weight of evidence that satisfies the URS clear-and-convincing standard is a narrower category than what the UDRP accepts. Both procedures rely entirely on written submissions – there is no oral hearing. What you put into the record is what the panel decides on.

For confusing similarity, the analysis is straightforward in most .cloud cases. The domain name is compared to the trademark, disregarding the TLD extension. A domain that reproduces a registered mark in full, or adds a generic suffix such as "cloud" or "services," is almost always held confusingly similar. This element is rarely the deciding factor.

For legitimate interest, the complainant must set out a prima facie case; the burden then shifts to the registrant to rebut. The safe harbors under Paragraph 4(c) of the Policy – a bona fide offering of goods or services before notice of the dispute; being commonly known by the name; legitimate noncommercial or fair use – are the main lines of respondent defense. A bare parking page or a redirecting domain provides the registrant almost nothing to work with.

Bad faith is where most .cloud disputes are actually decided. The non-exhaustive list in Paragraph 4(b) covers registration for sale to the mark owner; registration to disrupt a competitor; and registration to attract users for commercial gain by creating confusion with the mark. Pay-per-click parking, redirect to a competing site, and a demand for a sum exceeding out-of-pocket costs are each strong bad-faith indicators. Passive holding – the domain resolves to nothing, or to a blank page – can still constitute bad faith when the mark is distinctive and the registrant provides no explanation for the registration.

For a URS complaint the same categories apply, but the evidence must be unambiguous on its face. A case that requires the panel to weigh competing inferences is not a URS case. It is a UDRP case.

What is the realistic process, timeline, and cost for each route?

Filing the right procedure early matters because there is no deadline for a brand owner to bring a UDRP or URS complaint under the Policy – but every day the infringing .cloud domain operates, it erodes your goodwill and potentially confuses customers.

For the UDRP: the complaint is filed with the chosen provider (WIPO or the Forum). The respondent has 20 days to file a response once the case commences. A single-member WIPO panel deciding a one-domain matter will typically deliver its decision within about two months of filing. The WIPO filing fee for one to five .cloud domains before a single-member panel is USD 1,500; a three-member panel costs USD 4,000. Legal fees are separate and depend on the complexity of the matter; market rates for a straightforward single-domain complaint typically fall in the USD 3,000–7,000 range, paid in addition to the forum fee.

For the URS: the filing fee is lower than the UDRP. The process is faster, and a successful determination suspends the domain promptly. However, because the remedy is suspension rather than transfer, a brand owner who later wants full ownership must file a separate UDRP complaint – at additional cost and time. If the evidence is strong enough to justify the URS, it is almost certainly strong enough to win a UDRP outright. The incremental cost of going directly to UDRP is often justified.

The decision matrix for .cloud domains runs as follows. If the mark is registered, well-known, and the infringement is naked – route to URS for speed, accepting the non-transfer remedy. If the mark is registered but the registrant has any arguable position – route to UDRP. If you need permanent ownership – UDRP only. If the registrant is running a pattern of registrations across multiple domains with the same holder – UDRP, because a single complaint can cover multiple .cloud domains under one registrant. If you also want damages – neither URS nor UDRP reaches monetary relief; US anticybersquatting litigation is the only path that does, handled with local litigation counsel in the relevant jurisdiction.

How do respondent rights differ between URS and UDRP in a .cloud dispute?

The procedural protections available to a .cloud domain registrant differ materially between the two routes. Understanding these differences matters whether you are a brand owner deciding which procedure to bring or a registrant assessing your exposure.

Under the UDRP, the respondent has 20 days to file a full written response. A three-member panel is available on request by either party. The decision is published. An RDNH (Reverse Domain Name Hijacking) finding is available if the complainant brought the proceeding in bad faith to deprive a legitimate registrant – a finding that carries significant reputational weight even though it carries no monetary penalty.

Under the URS, the response window is shorter and the respondent's materials are limited. The evidentiary standard cuts both ways: the complainant bears a higher burden, but a respondent who fails to file a response faces a default determination with minimal process. An appeal mechanism exists after a URS determination, but the window is tight and new evidence is generally not admitted on appeal.

In our practice we have defended registrants against both URS and UDRP complaints for .cloud and other new-gTLD domains. The most common respondent error in a URS proceeding is assuming that the higher evidentiary standard means the complainant cannot satisfy it, and therefore filing no response. That assumption is dangerous. A clear-cut case of confusing similarity with a parking page will satisfy the URS standard even without a response.

In a recent respondent matter – a .cloud domain held for over three years by a legitimate reseller, summer 2024 – we filed a timely UDRP response documenting prior use, the registrant's business purpose, and the absence of bad faith. The complaint was denied. The complainant's failure to distinguish generic use of the term from trademark use was a central weakness we identified early and pressed through the written record.

To assess whether a URS or UDRP complaint against your .cloud domain can be defeated, email info@cognomenlaw.com.

What cross-zone considerations apply if the dispute spans .cloud and other TLDs?

A brand owner frequently discovers that the same bad actor has registered the infringing name across multiple zones: the .com, the .cloud, a .net, and perhaps a ccTLD. Each zone and each remedy must be assessed separately, but a single UDRP complaint can cover multiple domains – across different TLDs – if the registrant is the same holder. That consolidation option is one reason UDRP often becomes the preferred route in multi-zone situations: one filing fee, one record, one decision, one timeline.

The URS does not offer the same consolidation efficiency in practice, and its suspension-only remedy means a brand owner who resolves the .cloud domain via URS still faces a separate UDRP or court action for other zones. Running parallel procedures is expensive and creates inconsistent records.

For .de domains in the same portfolio, there is no URS or UDRP: disputes proceed through the German courts, with a DENIC DISPUTE entry available to block transfer while the case is litigated. For .uk domains, the Nominet DRS applies its own "abusive registration" test, which reads "registered or used" abusively – a lower bar than the UDRP's cumulative "registered and used" standard. For .eu domains, the EURid ADR.eu procedure applies, with EU eligibility requirements for transfer. Any cross-zone strategy for a brand spanning .cloud, .com, and one or more ccTLDs needs to map each forum's rules before filing anything.

For further background on how TMCH claims notices interact with new-gTLD registrations – a related issue for brand owners monitoring the space – see our analysis of TMCH claims notice mechanics. For context on URS and new-gTLD procedures more broadly, visit our URS and new-gTLD disputes service page.

What common errors cause .cloud URS and UDRP complaints to fail?

Most failed .cloud complaints share one of four structural defects. First, the complainant relies on unregistered mark rights without building the secondary-meaning record that panels require – a single brand-use declaration is rarely sufficient. Second, the complainant conflates the URS and UDRP standards and files URS in a case with any arguable defense, only to receive a denial and alert the registrant. Third, the bad-faith evidence is thin: a parking page alone, absent other indicia such as a sale demand or a prior abusive-registration pattern, may not cross the threshold. Fourth, the complaint covers multiple domains registered to different holders on a theory of common ownership that the evidence does not support.

On the respondent side, the mirror errors are equally costly. Filing no response because the case "looks weak" hands the complainant an uncontested record. Submitting a response that addresses only one element – usually legitimate interest – while ignoring bad faith leaves the panel to fill in the gap against you. And asserting RDNH without documenting the complainant's knowledge of your rights at the time of filing is an assertion that panels decline to credit.

These patterns are correctable. They are also largely avoidable with a proper pre-filing or pre-response assessment – the work that determines which procedure to use, what evidence to assemble, and how to frame the argument before a single filing fee is paid.

For additional context on how domain assignment and title issues can affect a dispute record, see our alert on domain assignment agreements.

Related at COGNOMEN

• URS and new-gTLD disputes: suspension, UDRP, and new-zone recovery options
• TMCH claims notices: how they interact with new-gTLD registrations and brand strategy
• Domain assignment agreements: what the title record means for a dispute filing