How to recover a .cloud domain held passively in bad faith

How to recover a .cloud domain held passively in bad faith. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your case.

A registrant sits on a .cloud domain that mirrors your brand. No active website. No evident business use. Just a parked page or a blank DNS record – and a name that your customers might try to reach. Passive holding is not a safe harbor under the UDRP. Panels have consistently treated inactivity as a species of bad faith, particularly when the domain is confusingly similar to a well-known mark and the registrant offers no credible explanation for the registration.

To recover a .cloud domain held passively in bad faith, you must satisfy all three elements of Paragraph 4(a) of the UDRP: confusing similarity to a mark you hold, no legitimate interest on the registrant's side, and registration and use in bad faith. Passive holding – doing nothing with a domain while it disrupts a mark owner – counts as "use" in bad faith under settled panel consensus. A standard WIPO case for a .cloud domain takes about two months from filing to decision, and the only remedies available are transfer or cancellation.

This page sets out the procedure, the evidence that decides passive-holding cases, the cost structure, and when a court route should supplement or replace the UDRP for .cloud.

Why .cloud sits squarely within the UDRP

The .cloud new gTLD operates under standard ICANN accreditation, which means every registrar offering .cloud registrations must incorporate the UDRP into its registration agreement. WIPO is the natural forum of first choice. A complainant files, WIPO verifies compliance, and the respondent receives 20 days to answer. There is no separate .cloud dispute procedure and no national eligibility filter – anyone, anywhere, may hold a .cloud domain, and anyone with qualifying trademark rights may challenge an abusive one.

That uniform applicability matters practically. A brand owner with a US, EU, or UK trademark registration can file a WIPO complaint against a .cloud registrant located in any jurisdiction. The case proceeds in writing, entirely online. The panel applies a single consistent standard regardless of where either party sits. We regularly advise clients for whom .cloud domains have appeared as part of a broader registration pattern, and the procedural route is consistently the same: UDRP at WIPO, single-member panel for a straightforward passive-holding complaint.

For an assessment of whether your .cloud complaint meets the three UDRP elements, contact info@cognomenlaw.com.

What are the three UDRP elements for a passive-holding complaint?

Passive holding does not change the three elements; it changes how the third is analyzed. Each element carries its own burden and its own evidentiary requirements.

Element one – confusing similarity. The panel compares the domain name to the trademark in isolation, stripping the TLD. For .cloud domains that string is typically the second level – the part before ".cloud." Exact matches or near-exact matches are straightforward. Typosquats and phonetic equivalents are evaluated against how closely a user scanning a URL would associate the string with the mark. Trademark registration is the strongest evidence, but unregistered marks with demonstrable secondary meaning also qualify if the complainant documents them. The .cloud suffix itself is treated as non-distinctive – it neither adds to nor subtracts from the similarity analysis in the way a descriptive word might.

Element two – no legitimate interest. The complainant makes an initial prima facie case; the burden then shifts to the respondent to demonstrate one of the three safe harbors in Paragraph 4(c): a bona fide offering of goods or services before any notice of the dispute; being commonly known by the domain name; or a legitimate noncommercial or fair use. Where a domain sits passively unused, the respondent finds this element hardest to answer. A silent registrant – one who defaults and files nothing – cannot avail itself of any safe harbor.

Element three – bad faith, registered and used. The cumulative standard – both registered and used in bad faith – might seem to favor a passive holder who appears to "do nothing." The consensus view under the UDRP is that this appearance is wrong. Panels evaluate the totality of circumstances. Factors that routinely tip a passive-holding case toward bad faith include: the mark's fame or distinctiveness at the time of registration; the absence of any plausible legitimate use; the registrant's failure to respond; a concealed or privacy-shielded WHOIS record; and prior correspondence showing a sale demand or refusal to transfer. A well-constructed complaint documents each circumstance separately.

What evidence decides a passive-holding .cloud case?

Evidence of passive holding falls into two categories: evidence showing what the registrant has not done, and evidence showing what the registrant clearly knew at registration. Both matter.

On the "not done" side: screenshots of the DNS record or parking page taken on multiple dates over a reasonable period; RDDS/WHOIS data showing the registration predates any conceivable new-gTLD-related business by the registrant; absence of a live website, active email, or brand presence associated with the domain string. Panels have refused to equate a single screenshot with a sustained pattern; take timestamped captures at intervals.

On the "knew at registration" side: evidence of the mark's fame, advertising spend, press coverage, or commercial volume at the date the .cloud domain was registered. Where the mark predates the .cloud TLD's general availability, this comparison is relatively straightforward. Where the domain was registered close in time to the mark's creation, documentary evidence of actual knowledge – a demand letter, a social-media mention, a reverse WHOIS showing the registrant holds other mark-similar domains – carries disproportionate weight.

In our practice we have found that panels respond most forcefully to a complaint that pairs a clear timeline (mark established, new gTLD launches, domain registered within weeks) with a pattern of inactivity spanning a meaningful period. The inference of opportunistic registration becomes hard to rebut without any counter-evidence at all.

In a recent matter (a .cloud passive-holding complaint, spring 2025), we assembled a timeline showing the complainant's mark predated the registrant's acquisition of the domain by more than five years, combined with approximately eight months of documented inactivity and a privacy-shielded WHOIS record. The panel transferred the domain within the standard case window, with no extension requested by either side.

How should you choose between WIPO, the Forum, and a court action for .cloud?

The choice of forum and route is a practical decision, not only a legal one. Three routes are realistically available for a .cloud dispute.

WIPO – the standard choice. The WIPO filing fee for a single-panel complaint covering one to five domains is USD 1,500. For a three-member panel the fee rises to USD 4,000. WIPO administers the largest share of UDRP filings and its decisions form the deepest jurisprudential pool on passive holding. The consensus passive-holding doctrine is most fully developed in WIPO decisions. Legal fees for a straightforward single-domain complaint typically fall in the USD 3,000 – 7,000 range, separate from the forum fee.

The Forum – a workable alternative. The Forum handles a meaningful share of UDRP filings. Its filing fees begin around USD 1,300 for one to two domains, single-member panel. Substantively, the Forum applies the same UDRP standard. For passive-holding cases specifically, where the doctrine is stable and well-understood, the choice between WIPO and the Forum turns mainly on fee preference, panel familiarity, and any preference the complainant's representative has developed from prior proceedings.

Court action – when UDRP is not enough. The UDRP transfers or cancels a domain. It awards no damages, no legal costs, and no injunction reaching outside the DNS. Where the passive holding has caused calculable commercial harm – customer diversion, fraudulent invoices issued under the domain, a data-security incident – US anticybersquatting litigation or the equivalent in another jurisdiction may be the right supplementary step. Court action is substantially more expensive and slower than UDRP, but it is the only route that reaches money. We coordinate that work with local litigation counsel in the relevant jurisdiction. For a .cloud domain the UDRP is almost always the first move; court comes into play when you have already won the transfer but need to address downstream harm.

What if the registrant holds both a .cloud and a .com on the same string? A single UDRP complaint can cover multiple domains only if the registrant is the same holder. Where the holder differs, separate complaints are required. Where both sit with the same entity, a single filing is more cost-efficient and gives the panel a clearer view of any pattern.

To weigh UDRP against a court action for your .cloud case, email info@cognomenlaw.com.

What does the UDRP process look like end to end for .cloud?

A .cloud UDRP complaint moves through five stages, and the pace is set by the Rules themselves rather than by court scheduling.

Stage one – complaint preparation and filing. The complaint is a written submission documenting all three elements, supported by annexes: trademark certificates, RDDS/WHOIS records, domain screenshots, prior correspondence, and any evidence of the registrant's actual knowledge. Quality here determines the outcome. WIPO reviews the complaint for formal compliance before serving it.

Stage two – service and response window. Once the case commences, the respondent has 20 days to file a response. A passive holder who registered the domain speculatively and has no legitimate story to tell will often default – filing nothing. Default does not mean automatic transfer; the panel still reviews the complaint on its merits, but the evidentiary balance shifts sharply toward the complainant when no counter-narrative is offered.

Stage three – panel appointment. For a single-member complaint WIPO appoints a panelist from its roster. Either party may request a three-member panel; where only one party requests it, that party pays the cost difference. A three-member panel is rarely necessary in a passive-holding case where the doctrine is settled, but a respondent may request one if it believes the facts favor a fight.

Stage four – decision. The panel issues its decision in writing. For a standard single-domain passive-holding case the combined process normally runs within about two months of filing. WIPO's expedited option can deliver a decision within roughly one month for eligible single-panel cases of up to five domains.

Stage five – registrar implementation. The registrar implementing the transfer typically waits ten business days to allow for any court challenge by the losing respondent. Absent a challenge, the domain transfers to the complainant's designated registrar account.

In a second recent matter (a .cloud domain registered shortly after a technology brand's product launch, autumn 2024), we filed a complaint documenting both the mark's priority and a pattern of passive holding across approximately four related new-gTLD registrations by the same entity. The panel found bad faith established on the passive-holding doctrine and ordered transfer. The registrant did not seek a three-member panel or file a response.

What myths stop complainants from filing – and what the evidence actually shows

One common hesitation runs like this: "The domain isn't pointing at anything harmful, so how can it be bad faith?" The answer is settled. Panels have held consistently that the absence of an active harmful use does not immunize a registration that was clearly opportunistic at the outset. The passive-holding doctrine emerged precisely because a registrant who simply parks a domain – or leaves it dark – can disrupt a mark owner as effectively as one who puts up a counterfeit site. The disruption is different but real: it prevents the legitimate brand owner from using its own name in the zone, and it leaves consumers who type the address with nothing or with confusion.

A second hesitation: "My trademark isn't registered in the country where the registrant is located." Jurisdiction of the mark is not a UDRP requirement. The policy asks whether you hold trademark rights, not where they were issued. A US federal registration, an EU trademark, or a UK mark each independently supports a UDRP complaint regardless of the registrant's location. The complainant does not need a local mark to access UDRP for a .cloud domain.

A third hesitation: "The domain has been sitting there for years – it's too late." There is no UDRP statute of limitations. Delay in filing is not a bar. It can, however, affect the weight a panel gives to the complainant's claimed urgency, and in rare cases a long-standing passive holder can argue acquiescence if the complainant's own conduct suggests acceptance of the registration. Panels rarely find acquiescence conclusive, but filing promptly once the issue is identified is a cleaner position.

How do costs and outcomes compare in passive-holding .cloud complaints?

The cost structure for a .cloud UDRP complaint has two entirely separate components: the forum filing fee and the legal fee for preparing and arguing the case.

The forum filing fee at WIPO for a single domain, single-member panel is USD 1,500. If the case settles or is withdrawn before panel appointment, WIPO typically refunds approximately USD 1,000 of that fee. For a three-member panel the forum fee rises to USD 4,000. Those are fixed published rates; they do not vary by the strength of the case or the jurisdiction of either party.

Legal fees in a straightforward passive-holding .cloud complaint are typically in the USD 3,000 – 7,000 range, depending on complexity, the number of annexes, and whether a response is filed that requires a reply. That range is a market figure, not a COGNOMEN-specific quote; it reflects what a specialist practitioner charges for a single-domain, well-documented matter. A default case is faster to resolve than a contested one; a multi-domain complaint is priced differently because the evidentiary work scales.

What is the realistic outcome? The only remedies under the UDRP are transfer or cancellation. There are no damages, no costs awards against the respondent, and no injunction. If the priority issue is recovering the domain and stopping the passive disruption, UDRP reaches that outcome faster and at lower cost than any court route. If damages are also needed, court remains an option after or alongside the UDRP – that decision depends on the quantum of harm and the respondent's assets in a reachable jurisdiction.

Related at COGNOMEN

• UDRP domain recovery services – all gTLD and ccTLD zones
• Recovering a .tv domain from a serial cybersquatter – strategy and process
• How to enforce a UDRP transfer decision in the UK