How to recover a typosquatted .cloud domain

How to recover a typosquatted .cloud domain. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your case. Transparent fees, re…

A registrant mirrors your brand name with a single transposed letter – your trademark becomes "yourbrand" with a swap, a dropped vowel, or an extra character – and parks the .cloud domain on a pay-per-click page. Traffic meant for you earns revenue for them. The question your legal team is already asking: can we get that domain back, and how fast?

To recover a typosquatted .cloud domain you file a UDRP complaint, because .cloud is a new generic TLD whose registry has adopted the UDRP as the mandatory dispute-resolution procedure. You must prove all three elements of Paragraph 4(a): confusing similarity to a mark you hold, no legitimate interest in the registrant, and registration and use in bad faith. A standard case runs about two months, the WIPO single-panel filing fee is USD 1,500, and the only remedies are transfer or cancellation – no damages, no costs award.

This page covers the legal test, the evidence that decides .cloud typosquat cases, the timeline from filing to transfer, forum choice, and the realistic next step for a brand owner ready to act.

Why the UDRP governs .cloud – and what that means for you

The .cloud registry adopted the UDRP as its mandatory dispute procedure when the zone launched as part of the ICANN new-gTLD program. That means the same three-element test that applies to .com applies here. No national court action is required as a first step. No separate national-law eligibility test stands in the way.

That uniformity is a genuine advantage. A brand owner who already holds a registered trademark can file directly at WIPO, the Forum, the Czech Arbitration Court (CAC), or the Asian Domain Name Dispute Resolution Centre (ADNDRC) without establishing a local presence or satisfying a country-connection requirement. For .cloud specifically, WIPO and the Forum handle the overwhelming majority of UDRP proceedings.

There is one practical nuance worth noting. Because .cloud is a new gTLD rather than a legacy zone, panels have examined it under the same typosquat doctrine used for .com, .net, and .org – a body of well-settled consensus decisions. The TLD string itself is disregarded in the confusing-similarity analysis. A domain like "cognomn.cloud" is assessed against the mark COGNOMEN as if the .cloud extension were invisible. The misspelling is what matters.

We regularly advise brand owners whose marks appear in .cloud typosquats. The single most important first step is verifying that the trademark right relied on is currently registered and that the registration predates – or, in certain circumstances, is otherwise consistent with – the disputed domain's registration date. That predicate question shapes everything downstream.

The three UDRP elements: what you must prove to recover a typosquatted .cloud domain

A successful complaint must satisfy all three elements of Paragraph 4(a) cumulatively. Fail one and the panel denies the complaint – regardless of how clear the bad faith appears on the other two.

Element 1: confusing similarity

For a typosquat, this element is almost invariably met. The test is whether the domain, ignoring the TLD, is identical or confusingly similar to the complainant's mark. Panels treat letter transpositions, vowel deletions, doubled consonants, and phonetic equivalents as classically confusingly similar. A domain like "acmecorp.cloud" versus the mark ACMECORP leaves no room for debate. The real work is in elements two and three.

Element 2: no rights or legitimate interests

The consensus approach shifts the burden once the complainant makes a prima facie showing. If the registrant cannot demonstrate that it was commonly known by the domain name before the dispute, was making a bona fide offering under Paragraph 4(c), or had a legitimate noncommercial fair use, the second element falls in the complainant's favor. For a pure pay-per-click typosquat, that showing is rarely made. What does appear: a thin response claiming "descriptive use" or "intended development" that panels have consistently found insufficient absent corroborating evidence of actual use before notice of the dispute.

Element 3: registration and use in bad faith

This element is cumulative – both prongs must be satisfied. Paragraph 4(b) provides non-exhaustive bad-faith factors. The two most relevant for a .cloud typosquat are: registration primarily to sell to the trademark owner at an above-cost price, and registration to attract users for commercial gain by creating a likelihood of confusion with the mark. A pay-per-click parking page displaying advertisements related to the complainant's industry is a recurring fact pattern that panels treat as strong bad-faith evidence. Passive holding of a typosquat domain – no active use, but no plausible good-faith use either – can also satisfy this element under the doctrine panels apply to clearly abusive registrations.

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

What evidence decides a .cloud typosquat complaint?

The strength of a UDRP complaint is almost entirely evidence-driven. Filing early with thin documentary support is one of the most common ways a recoverable case is lost. Here is what panels actually rely on.

Trademark registration certificates

Current, clean trademark certificates – with the registration number, the owner of record, and the relevant goods or services – are the foundation. If ownership has changed through a corporate restructuring, the chain of title must be documented. A provisional application with no registration date close to the domain's registration is a vulnerability a respondent's counsel will probe.

The WHOIS / RDDS record and registration date

The domain's registration date in WHOIS (or the Registrar Data Directory Service under ICANN's current terminology) anchors the bad-faith timeline. If the registrant registered the domain after your mark was established in the marketplace – even before formal registration, in common-law trademark jurisdictions – that temporal sequence supports bad faith. The older and the more widely recognized the mark, the stronger the inference.

Evidence of bad-faith use

Screenshot captures of the disputed domain's resolved content are critical. A parking page monetizing traffic, a page impersonating the brand owner, or a page linking to competitors all supply the "use" half of the bad-faith element. Screenshots must be timestamped and sourced from a reliable archiving mechanism. Panels also accept Wayback Machine captures where contemporaneous screenshots were not taken.

Prior correspondence or a buy-back demand

If the registrant has already contacted you with an unsolicited offer to sell – at a price clearly above registration cost – that correspondence is direct evidence of Paragraph 4(b)(i) bad faith. Preserve every message, every voicemail description, every broker communication. In our practice, a documented buy-back demand in the five-figure range has been one of the most persuasive single pieces of evidence in panels' written decisions.

Pattern evidence

Where the registrant holds multiple typosquats of different marks, that pattern supports a finding under Paragraph 4(b)(ii). Identifying the registrant's broader portfolio – through WHOIS history, reverse-WHOIS lookups, and related domain profiles – and appending that evidence to the complaint strengthens the case substantially.

In a recent matter (a .cloud typosquat, spring 2025), we assembled a complaint that combined a pay-per-click screenshot, a Wayback Machine capture, and three related domains held by the same registrant. The panel found bad faith on registration and use, and a transfer order issued roughly eight weeks after filing.

If you have already gathered some of this evidence and want to know whether it is enough to file, email info@cognomenlaw.com for an assessment.

Timeline and process: from complaint to transfer

A standard UDRP complaint for a .cloud typosquat follows five stages, typically completed in about two months absent procedural delays.

1. Filing and formal compliance review. The complaint is submitted to the chosen forum (WIPO, the Forum, CAC, or ADNDRC). The provider checks the complaint for formal compliance – correct fee, correct identification of parties, correct registrar. If deficiencies exist, an amended complaint is required before the clock starts.
2. Commencement and the 20-day response window. Once the provider formally commences the case, the registrant has 20 days to file a response. Default – no response – is common in typosquat cases. Default does not automatically mean the complainant wins; the panel still applies the three-element test. But default deprives the registrant of the chance to present legitimate-interest evidence.
3. Panel appointment. After the response period closes (with or without a response), the provider appoints a panelist. The parties may each request a three-member panel; if so, the higher fee applies and the parties generally split it.
4. Decision. The panel issues its decision in writing. The reasoning is publicly published by the forum. The decision either orders transfer, orders cancellation, or denies the complaint. No monetary awards are available under the UDRP.
5. Registrar implementation. Following a ten-business-day implementation window – during which the losing respondent may seek court relief to stay the transfer – the registrar implements the panel's order. The domain is transferred to the complainant's designated registrar account.

WIPO also offers an expedited procedure delivering a decision in approximately one month, available for single-panel cases covering up to five domains. For a brand owner who needs the domain stopped quickly – because the typosquat is actively diverting customer inquiries, for example – the expedited route is worth the shorter timeline it provides.

Choosing the right forum: WIPO, the Forum, or CAC?

For a .cloud typosquat, three forums are realistically in play: WIPO, the Forum, and CAC. The choice affects cost, timeline, and – at the margin – procedural culture.

WIPO is the default choice for most brand owners. The USD 1,500 single-panel filing fee covers one to five domains, and WIPO's case administration is widely regarded as consistent and predictable. Its published jurisprudential overview is the closest thing the UDRP has to a precedent guide, which means parties and panels share a common reference. WIPO and the Forum together handle roughly 97% of all UDRP proceedings.

The Forum's filing fee begins around USD 1,300 for one to two domains under a single-member panel – a modest difference. The Forum has a strong track record in US-brand-owner cases and is well-suited to disputes where the evidentiary record is straightforward.

CAC offers the lowest entry-point fee, beginning around USD 500–800. For a single, clear-cut typosquat with unambiguous evidence and a defaulting respondent, cost efficiency is a legitimate consideration. CAC is less frequently used, however, and brand owners with complex evidentiary records often prefer WIPO's institutional depth.

What if the same registrant holds both the .cloud typosquat and a .com typosquat of your mark? A single UDRP complaint can cover multiple domains provided the registrant is the same holder. Filing a consolidated complaint at WIPO or the Forum eliminates the duplication of forum fees, reduces elapsed time, and places the full picture of the registrant's conduct before a single panel.

And what if the .cloud domain is accompanied by a lookalike on a country-code TLD – say, a .de or a .uk? Those require separate, zone-specific procedures. A .de dispute runs through the German courts with a DENIC DISPUTE entry to block transfer during litigation; a .uk dispute proceeds through the Nominet DRS. Neither is part of the UDRP, and neither can be consolidated with it. We handle each route separately, identifying the governing national procedure, checking eligibility, and preparing the filing for that registry.

In a second recent matter (a combined .cloud and .com typosquat complaint, autumn 2024), we consolidated both domains into a single WIPO filing where the registrant's WHOIS record confirmed common ownership. A transfer order covering both domains issued within the standard two-month window, at the same USD 1,500 filing fee applicable to multi-domain complaints under a single registrant.

What can go wrong – and what the RDNH risk means for complainants

Most typosquat complaints are well-founded. But panels also have the authority to find Reverse Domain Name Hijacking (RDNH) – a finding that the complaint was brought in bad faith to strip a legitimate registrant of a domain it had a genuine right to hold. That finding is reputational, not monetary, but it is publicly published and follows the complainant's name in the decision record.

RDNH findings are more common than many complainants expect. The most frequent triggers: filing against a registrant that demonstrably registered the domain before the trademark was in use; filing a complaint that relies on a mark registered after the domain; and filing where the complainant knew or should have known that the registrant had a plausible legitimate interest.

A second common failure mode is filing with incomplete evidence on the bad-faith element. A bare assertion that "the registrant must have known of our mark" – without corroborating WHOIS timing, use evidence, or pattern data – is regularly rejected. Panels have consistently held that constructive knowledge of a mark is insufficient; targeted awareness, evidenced by the circumstances, is the standard.

A third risk: the complainant's trademark registration predates the domain but the mark was not in use in the relevant territory at registration time. Some panels require at least constructive awareness by the registrant; if the mark was unknown in the registrant's country, the bad-faith finding may not be sustained.

The myth worth addressing directly: that a typosquat case is automatically won because the similarity is obvious. Confusing similarity is typically the easy element. Bad faith – specifically, proof that this registrant registered this domain with awareness of your mark and with an abusive purpose – is where complaints succeed or fail on their merits.

Related at COGNOMEN

• UDRP domain recovery – full service overview across gTLDs and ccTLDs
• WIPO vs. the Forum for tech-sector domain disputes – a direct comparison
• Case study: recovering a lapsed .uk domain – strategy and outcome