How to recover a .cloud domain confusingly similar to your trademark

How to recover a .cloud domain confusingly similar to your trademark. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your c…

Someone has registered a .cloud domain that mirrors your brand. It may be redirecting your customers, sitting parked behind a pay-per-click page, or simply being held back until you offer a price. Whatever the registrant's play, the question is the same: how do you get the name transferred to you as efficiently as possible?

To recover a .cloud domain confusingly similar to your trademark, the standard route is a UDRP complaint filed before WIPO. You must satisfy all three elements of Paragraph 4(a) of the Policy: the domain is identical or confusingly similar to a mark you hold; the registrant has no rights or legitimate interests; and the domain was registered and is being used in bad faith. A WIPO case for a single domain runs approximately two months, and the filing fee starts at USD 1,500 for a single-member panel. The only remedies a panel can order are transfer or cancellation – no damages, no costs.

This page covers the legal test, what evidence a panel weighs, how the procedure runs from filing to transfer, what it costs, and where a .cloud dispute fits against other available routes.

Why .cloud falls under the UDRP

.cloud is a new generic top-level domain (new gTLD) delegated by ICANN, and every accredited registrar that sells .cloud registrations is bound by the UDRP as a condition of accreditation. That means the UDRP governs .cloud disputes exactly as it governs disputes over .com, .net, or any other ICANN-accredited gTLD. There is no separate national procedure to learn, no eligibility requirement to satisfy as a complainant, and no residency condition. If you hold a registered or unregistered trademark with a reputation sufficient to support a UDRP filing, the .cloud zone is fully in scope.

Complainants may file before WIPO, the Forum, the Czech Arbitration Court (CAC), or ADNDRC. In practice, WIPO and the Forum together handle roughly 97% of all UDRP proceedings. Most brand owners with an international portfolio select WIPO for its reputation, its searchable precedent database, and its expedited option for straightforward single-domain cases. We regularly advise clients on that forum choice, and the analysis below tracks WIPO procedure.

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

A panel deciding a .cloud UDRP complaint must find that all three elements of Paragraph 4(a) of the Policy are established. Miss any single one, and the complaint fails regardless of how strong the other two appear.

Element 1 – Confusing similarity. The domain must be identical or confusingly similar to a mark in which the complainant has rights. Panels assess this by comparing the textual string of the domain (disregarding the TLD suffix, which is typically treated as non-distinctive) with the trademark. Adding a generic term, a geographic word, or a hyphen to a well-known mark rarely escapes a finding of confusing similarity. What matters is whether the dominant, distinctive element of the mark is recognizable in the domain. A .cloud suffix is itself treated as generic for this purpose, so yourbrand.cloud is assessed against "yourbrand" alone.

Element 2 – No rights or legitimate interests. The complainant does not have to prove a negative absolutely. Under the consensus approach, the complainant makes a prima facie showing – typically by establishing that the registrant is not a licensee, is not commonly known by the name, and has no authorized connection to the brand – and the burden shifts to the registrant to produce credible evidence of a legitimate interest. Panels look for a bona fide offering of goods or services before notice of the dispute, a personal name or business identity that genuinely corresponds to the domain, or legitimate noncommercial or fair use. Absent any of those, the element is met.

Element 3 – Registration and use in bad faith. This is cumulative: the domain must have been registered and it must be used in bad faith. Paragraph 4(b) of the Policy lists illustrative bad-faith circumstances: offering the domain for sale to the mark owner at a price exceeding out-of-pocket costs; attracting users for commercial gain by creating a likelihood of confusion with the complainant's mark; registering to disrupt a competitor; or registering in a pattern of abusive registrations. Passive holding – registering a domain without making active use of it – can also constitute bad faith where the circumstances are so compelling that no plausible good-faith use exists.

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

How does the UDRP process work for a .cloud complaint – step by step?

The UDRP procedure follows five stages from the moment you file to the moment the registrar implements the panel's order. Understanding each stage helps you anticipate where time is spent and where things can go wrong.

1. Draft and file the complaint. The complaint identifies the mark, the domain, the registrant, and your factual case under each of the three elements. WIPO's online filing system accepts the submission and triggers an administrative compliance review.
2. Formal commencement. Once the complaint clears the compliance check, WIPO formally commences the case and notifies the registrant. The 20-day response window opens at this point.
3. Response (or default). The registrant has 20 days to file a response. Failure to respond does not automatically result in a transfer – a panel still reviews the complaint on the merits – but defaults are common in clear-cut cybersquatting cases and often produce faster decisions.
4. Panel appointment. WIPO appoints a single panelist, or a three-member panel if either party requested one. The panel reviews the record and may request further statements in limited circumstances.
5. Decision and registrar implementation. A standard case produces a decision within about two months of filing. If a transfer is ordered, there is a brief implementation period during which the respondent can seek a stay through a court of competent jurisdiction; absent a stay, the registrar carries out the transfer.

WIPO also offers an expedited option for single-panel cases covering up to five domains, delivering a decision in approximately one month. In our practice, that option is worth considering where the bad-faith evidence is documentary and unambiguous – a parking page with pay-per-click links to competitors being a straightforward example.

What evidence does a UDRP panel weigh for a confusingly similar .cloud domain?

Evidence decides .cloud cases far more than legal argument alone. A panel reads the written record – there is no oral hearing – so every fact that matters must be in the submission. The complainant should document the trademark registration (certificates, priority dates, territorial scope), the domain's registration date relative to the mark's priority, and the current and historical use of the domain.

Screenshots of the resolving page are critical. A pay-per-click page with links to competitors, a page soliciting a sale of the domain, or a redirect to an unrelated commercial site all speak directly to bad faith under Paragraph 4(b). WIPO accepts archived webpage captures from services such as the Wayback Machine where the current content has changed.

Registrant conduct also matters. A demand letter sent by the registrant seeking a purchase price well above the registration fee, communication that expressly references the trademark, or a WHOIS/RDDS history showing the registrant's name changing after the dispute arose – all of these strengthen the third element. We have defended brand owners in cases where a registrant's own email correspondence established bad faith without any additional inference required.

What weakens a complaint? Evidence that the mark is highly descriptive, weak, or confined to a narrow geographic market can undermine Element 1. Evidence that the registrant genuinely used the domain in a descriptive sense before the dispute began can carry Element 2. And a registration date that clearly pre-dates the complainant's trademark rights is often dispositive on Element 3. Panels require that the registrant could have known of the mark at the time of registration; a mark that did not exist when the domain was registered generally defeats a UDRP complaint, irrespective of how the domain is used today.

In a recent matter – a .cloud typosquat, spring 2025 – we assembled a brand owner's evidence file in two weeks and filed at WIPO. The registrant had pointed the domain at a phishing page using the brand's visual identity. The panel transferred the domain in less than eight weeks from commencement, with the registrant defaulting.

If you have already attempted outreach to the registrant and received a demand for a significant sum, that correspondence is itself evidence. To assess how to use it, email info@cognomenlaw.com.

What does it cost to recover a .cloud domain through UDRP?

There are two separate cost lines: the forum filing fee and legal fees. They are always quoted separately at COGNOMEN, because conflating them is one of the most common sources of surprise in this market.

WIPO filing fees. For a single-member panel and one to five domains, the WIPO filing fee is USD 1,500. A three-member panel for the same range costs USD 4,000. If a complainant selects a single panelist and the respondent requests a three-member panel, the parties generally split the higher fee. WIPO offers a partial refund – commonly around USD 1,000 of the USD 1,500 fee – if the case is withdrawn or terminated before panel appointment.

Legal fees. Market rates for a straightforward UDRP complaint on a single domain typically run in the USD 3,000–7,000 range, separate from the filing fee. The position of the domain on that range depends on the complexity of the trademark record, the strength of the bad-faith evidence, the number of domains covered, and whether the registrant files a substantive response that requires a reply. We publish ranges, not quotes on request, because transparency in fee structure is part of how we operate.

For a .cloud domain sitting behind a parking page with links to a competitor, total outlay for a standard single-panel WIPO case is in the range of USD 4,500–8,500. Against that, weigh the cost of the brand damage while the domain is live, the ongoing customer confusion, and the alternative of purchasing the domain at whatever the registrant is asking – often a five-figure or six-figure sum in active cybersquatting cases.

How does a .cloud dispute compare to other zones and other routes?

The right forum and the right procedure depend on where the abuse is occurring, what remedy you need, and whether the .cloud domain is the only problem or one in a larger pattern.

If the registrant holds the infringing name across multiple gTLD zones – say, yourbrand.cloud and yourbrand.com simultaneously – a single UDRP complaint can cover both, provided the registrant of record is the same entity. One filing fee covers the entire set. That economy matters when you are dealing with a systematic squatter rather than a one-off opportunist.

If the abuse extends to a ccTLD – yourbrand.uk or yourbrand.eu alongside the .cloud – a separate procedure applies to each national zone. The Nominet DRS governs .uk and operates differently from the UDRP: it has a mandatory free mediation stage, and its legal test is "abusive registration" (registered or used abusively, a lower bar than the UDRP's cumulative "registered and used in bad faith"). The .eu ADR procedure is administered through the Czech Arbitration Court's ADR.eu platform and allows a wider set of rights as the basis for a complaint. Coordinating a UDRP filing over the .cloud with a parallel ccTLD proceeding – where the facts and evidence overlap – is a practical approach to resolving the abuse across zones in a single campaign.

If the registrant's conduct is egregious and you also want monetary compensation, the UDRP cannot help: it transfers or cancels, nothing more. US anticybersquatting litigation is the only route that reaches damages. That path involves court proceedings, substantially higher cost, and a longer timeline, but it is sometimes the appropriate response where the registrant's operation has caused quantifiable commercial harm.

Finally, if the domain was registered on a new gTLD and you need it suspended rather than transferred, and the case is clear-cut, the Uniform Rapid Suspension (URS) procedure is available at lower cost than the UDRP. URS applies a higher evidentiary standard – clear and convincing evidence – but the timeline is faster. The URS remedy is suspension for the remainder of the registration term, not a permanent transfer, so it is better suited to situations where you need the harm stopped immediately and a full UDRP complaint will follow.

In another recent matter – a new-gTLD cluster including a .cloud domain, autumn 2024 – we combined a UDRP complaint at WIPO covering three domains with a coordinated ccTLD filing in the relevant national zone, resolving the full naming abuse in one coordinated campaign. Each filing was separate; the evidence record was built once and adapted for each forum's requirements.

What happens if the registrant files a response – or turns the tables on you?

A substantive response changes the character of the proceeding. The panel must weigh both sides, and the complainant's initial file must be strong enough to carry the day without the opportunity to supplement it freely. Where WIPO does permit supplemental filings, the bar is high – new evidence not reasonably available at the time of the complaint, or a direct rebuttal of a point raised for the first time in the response.

The more serious risk for a complainant with a weak case is a finding of Reverse Domain Name Hijacking (RDNH). RDNH is a panel finding that the complaint was brought in bad faith – typically to harass a legitimate registrant or strip a name the complainant simply covets but has no legal right to. An RDNH finding carries no monetary penalty under the UDRP, but it is published in the public record and is damaging to a brand owner's reputation in subsequent disputes. Panels have found RDNH where a complainant with a weak or geographically limited trademark targeted a domain registered years before the mark existed, or where the complainant's counsel was demonstrated to know the case was baseless.

For complainants, the practical lesson is straightforward: assess the three elements honestly before filing. A domain registered before your mark, by a registrant with a genuine business reason for the name, is not recoverable through UDRP – and the attempt can produce a worse outcome than no filing at all. We provide that assessment as a first step, and we decline matters where the elements are not supportable. That discipline protects our clients and the integrity of the process.

For registrants receiving a UDRP complaint over a .cloud domain they hold legitimately, the 20-day response window is the critical deadline. Defaulting does not concede the case, but it eliminates the ability to present a legitimate-interest defense. We build respondent defense files and, where the complaint is abusive, pursue RDNH findings.

Related at COGNOMEN

• UDRP domain recovery – the full service overview across gTLD zones
• Case study: recovering a typosquat domain in a new AI-adjacent zone
• UDRP versus national procedure – comparing routes across zones