Step-by-step: file a UDRP complaint for a .cloud domain

A brand owner searches for its company name and finds a .cloud domain pointed at a competitor's ad network, a phishing page, or a parking lot demanding a five-figure ransom. The question arrives fast: is there a dispute route that actually works for .cloud, and what does it take to use it?

To file a UDRP complaint for a .cloud domain you must prove all three elements of Paragraph 4(a) of the UDRP: confusing similarity to your trademark, the registrant's absence of rights or legitimate interests, and registration and use in bad faith. The .cloud registry operates under ICANN's accreditation framework, meaning the UDRP applies in full. A standard case runs roughly two months from filing to decision, and the only remedies available are transfer or cancellation.

This guide takes each step in sequence, flags the practical trap inside it, and closes with what evidence actually decides these cases.

Does the UDRP apply to .cloud domains?

Yes – .cloud is a new generic top-level domain (new gTLD) whose registry has agreed to ICANN's standard accreditation terms, which incorporate the UDRP by reference. Every registrar accredited for .cloud must include the UDRP in its registration agreement. That means a brand owner can file a UDRP complaint for a .cloud domain at WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC without first proving eligibility or residency – the rules are the same ones that govern .com.

There is one important distinction from ccTLDs such as .uk or .eu. Because .cloud is a gTLD, there is no national nexus requirement and no parallel registry eligibility check. The three UDRP elements are the whole test. A .cloud registrant anywhere in the world can be named as a respondent, and the complainant can be a brand owner anywhere in the world.

Trap at this step: some brand owners assume that because .cloud is a newer extension, panels might treat it differently. They do not. Panels apply exactly the same UDRP doctrine to .cloud that they apply to .com. The zone itself – the generic string ".cloud" – is ordinarily set aside when assessing confusing similarity; only the second-level label matters for that element.

How do you choose a forum for a .cloud UDRP complaint?

Four ICANN-accredited providers handle UDRP complaints for gTLDs, including .cloud: WIPO, the Forum, the CAC, and the ADNDRC. Filing fees and caseloads differ. WIPO and the Forum together handle the substantial majority of all UDRP proceedings worldwide.

WIPO charges USD 1,500 for a single-member panel covering one to five domains. A three-member panel costs USD 4,000 for the same range. The Forum's entry point is approximately USD 1,300 for one to two domains on a single-member panel. The CAC offers the lowest entry point – approximately USD 500 to 800 – though it handles a smaller volume of cases. These are forum filing fees only; legal-fee estimates are separate.

In our practice, most .cloud UDRP complaints are filed at WIPO, where the procedural infrastructure is deepest and the panel pool is largest. For a single, straightforward .cloud dispute, WIPO's expedited option can deliver a decision in roughly one month for a single-member case covering up to five domains. That speed advantage matters when a phishing page is live and brand damage is accumulating.

Trap at this step: the complainant may request a single-member panel; if the respondent then requests a three-member panel, both parties share the higher fee. Budget for that possibility. Also confirm before filing that the .cloud registrar of record honors UDRP proceedings from your chosen provider – accreditation means they must, but verify the current registrar using RDDS (WHOIS) data before submission.

For an assessment of your domain dispute and forum selection advice, contact info@cognomenlaw.com.

What are the three UDRP elements you must prove for a .cloud complaint?

Paragraph 4(a) of the UDRP requires a complainant to establish three elements, and all three must be satisfied – a strong showing on two does not overcome failure on the third.

Element 1 – Confusing similarity. Your trademark (registered or, in some circumstances, unregistered) must be identical or confusingly similar to the disputed .cloud domain. Panels assess this element mechanically: strip the TLD (".cloud"), compare the remaining label to your mark, and ask whether an internet user could confuse the two. Typos, hyphens, and generic additions ("shop-", "-online", "-services") do not typically break confusing similarity. The trap here is complainants who rely on an unregistered mark – while panels have found common-law rights in some circumstances, the evidentiary burden is substantially higher. A registered trademark in any jurisdiction will ordinarily satisfy this element.

Element 2 – No rights or legitimate interests. You must show the registrant lacks a legitimate claim to the name. The Policy lists safe harbors in Paragraph 4(c): bona fide use before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use without intent to mislead. Because a complainant often cannot prove a negative, panels accept a prima facie case that shifts the burden to the respondent to come forward with evidence of legitimacy. Trap: if the registrant is a licensed distributor, a criticism-site operator, or a prior trademark owner, the safe harbor may apply. Investigate before filing.

Element 3 – Bad faith registration and use. This is the most litigated element. The conjunctive standard matters: bad faith at the moment of registration and bad faith in subsequent use. Paragraph 4(b) lists non-exhaustive indicators: registering primarily to sell back to the mark owner; registering to disrupt a competitor; using the domain to attract users by creating confusion with the complainant's mark; a pattern of abusive registrations. Panels also recognize passive holding – a domain that resolves to nothing – as capable of constituting bad faith where the registrant obviously knew the complainant's mark and has no plausible legitimate use.

Trap at this step: a brand owner who registered its trademark after the respondent registered the .cloud domain cannot satisfy the bad-faith element unless it can show the registrant anticipated and targeted the mark. Timing is everything. Check the domain creation date against your trademark's priority date before drafting a word of the complaint.

What evidence should you gather before you file?

Evidence is the complaint's backbone. A well-argued complaint with thin evidence loses; a moderately argued complaint with strong evidence often prevails. Gather the following before drafting.

Trademark proof. Certified copies or screenshots of your trademark registration certificate, including the registration number, goods and services, and priority date. If relying on an unregistered mark, compile sales figures, advertising spend, media coverage, and consumer recognition evidence – whatever establishes acquired distinctiveness in the relevant market.

Domain registration data. A dated RDDS (WHOIS/RDAP) record showing the registrant name, registrar, creation date, and expiry date. Archive this on the day of the search; RDDS data changes. The creation date is your key fact for the bad-faith timing analysis.

Use evidence. Screenshots of what the .cloud domain resolves to – parking pages, pay-per-click ads, redirect destinations, or content that mimics your brand. Use a web-archiving service to capture dated copies. If the domain resolves to nothing, document that too: passive holding evidence for the bad-faith argument.

Communications, if any. If the registrant has contacted you demanding payment, those communications are among the strongest bad-faith exhibits available. A demand to sell the domain to you for a sum "exceeding out-of-pocket costs" is a Paragraph 4(b) bad-faith indicator by name.

Prior dispute history. Run the registrant's name and email address through WIPO's case search. A pattern of prior abusive registrations across multiple domains is another Paragraph 4(b) factor. Even one prior UDRP loss against the same registrant can be powerful corroborating evidence.

Trap at this step: filing before evidence is complete. UDRP rules permit supplemental filings only in exceptional circumstances at panel discretion. There is no right to submit additional evidence after the complaint is filed. The record you build before filing is, in most cases, the record the panel decides on.

How do you draft and file the complaint?

Each provider publishes its own complaint form and procedural rules. The structure, however, is materially the same across forums. A UDRP complaint for a .cloud domain must include:

• Identification of the disputed domain name and the registry/registrar of record;
• Contact information for the complainant and its authorized representative;
• A statement of the three UDRP elements, argued in order with supporting evidence;
• The remedy sought (transfer or cancellation);
• A declaration that the information in the complaint is complete and accurate; and
• A mutual jurisdiction statement – that the complainant submits to the jurisdiction of the registrar's courts for any challenge to the panel's decision.

Annexes carry your evidence: trademark certificates, RDDS records, screenshots, correspondence, and any prior UDRP decisions you wish to cite as persuasive authority. Label annexes clearly and cross-reference them in the argument. Panels are not obligated to hunt through an appendix for evidence that is not cited in the text.

Filing is done electronically through the provider's online portal. WIPO's eCenter, for instance, allows electronic submission and automatically timestamps each document. Once the provider confirms the complaint is formally compliant, it notifies the registrar and commences the case. The registrar locks the domain from transfer immediately upon commencement – a critical protection that freezes the domain in place while the case proceeds.

In a recent matter – a .cloud domain mimicking a SaaS brand, spring 2025 – we identified at the drafting stage that the registrant had used a privacy service that masked RDDS data. We requested registrar-level disclosure as part of the filing process. The provider followed standard UDRP procedures, the registrant's identity was disclosed, and the complaint proceeded without delay. The lock also prevented a last-minute transfer that would have complicated enforcement.

Trap at this step: a complaint that fails the provider's formal compliance review wastes time and may forfeit part of the filing fee. Common deficiencies include missing annexes, an unsigned declaration, or a mutual jurisdiction statement that does not name the correct registrar courts. Review the provider's rules against a checklist before submitting.

What happens after you file – the 20-day response window and beyond?

After commencement the respondent has 20 days to file a response. That window is set by the UDRP Rules. A respondent who misses it defaults, and the panel decides on the complaint's record alone – though default does not mean automatic transfer. The panel still evaluates whether the three elements are established.

If a response is filed, the complainant typically has no automatic right to reply. Some providers allow a limited supplemental filing in rare circumstances, but this is at panel discretion. Plan the complaint as if it will be the final word.

Panel appointment follows the close of the response window. For a single-member panel, appointment and decision normally complete within the overall two-month window. A three-member panel takes modestly longer. Once a decision issues, the registrar implements it after a brief waiting period – ordinarily ten business days – to allow the losing party to seek a court injunction in the mutual-jurisdiction courts if it chooses. Court challenges to UDRP decisions are possible but comparatively rare.

Trap at this step: the complainant assumes filing is the end of its active role. It is not. Monitor the case docket. If the panel issues procedural orders – a request for clarification, a request to translate an exhibit, a question about the trademark's validity – missing the deadline to respond can prejudice the outcome.

To weigh UDRP against a court action for your .cloud dispute, or to review a complaint already in progress, email info@cognomenlaw.com.

What are the only remedies, and what happens if you lose?

The UDRP provides only two remedies: transfer of the domain to the complainant, or cancellation. No monetary damages, no costs award, and no injunction issue from a UDRP proceeding. If you want damages or injunctive relief covering activity beyond the domain itself, a court action is the appropriate route – handled in coordination with litigation counsel in the relevant jurisdiction.

If the complaint is denied, the domain stays with the registrant. Beyond reputational and cost consequences, a denied complaint can produce a Reverse Domain Name Hijacking (RDNH) finding if the panel concludes the complaint was filed in bad faith to deprive a legitimate registrant. RDNH findings carry no financial penalty, but they are published and searchable. We have advised complainants to withdraw a complaint rather than risk an RDNH finding where the evidence did not meet the standard on all three elements.

The right course where a complaint looks risky: seek a pre-filing assessment. Panels have consistently held that a complainant who files knowing its trademark post-dates the domain registration, without clear evidence the registrant anticipated the mark, fails the bad-faith element – and those cases are the principal source of RDNH findings.

In a recent matter – a .cloud domain dispute, autumn 2024 – we assessed a complaint where the complainant's registered mark was filed three months after the domain's creation date. Rather than file a likely-losing complaint, we pursued a confidential negotiated acquisition instead, securing the transfer within six weeks at a commercially reasonable sum and with no RDNH exposure. The right tool was not the UDRP.

Related at COGNOMEN

• UDRP domain recovery services – full details on filing, evidence, and forum selection
• How to recover a domain used in a phishing scheme – a step-by-step guide
• Trademark Clearinghouse claims notices – what they mean and what to do

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. Our practice covers the full spectrum of new gTLD disputes, including .cloud, as well as established gTLDs and ccTLDs worldwide. To discuss a domain, contact info@cognomenlaw.com.

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

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

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