Step-by-step: protect a brand in a new .cloud gTLD launch

Step-by-step: protect a brand in a new .cloud gTLD launch. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your case.

A new generic top-level domain opens for general registration. Within days, your brand name – or a close variant – appears as a .cloud registration held by a stranger. The registrant parks it, points it at a competing service, or simply waits. You need to act, and the clock is already running.

To protect a brand in a new .cloud gTLD launch, brand owners have two principal tools: the Trademark Clearinghouse sunrise registration to claim the name before general availability, and – once abuse occurs – either a Uniform Rapid Suspension (URS) proceeding or a full UDRP complaint before WIPO. URS suspends a domain for the registration term under a clear-and-convincing standard and does not transfer ownership; UDRP can transfer the domain but takes roughly two months and a higher evidentiary investment. The right path depends on the conduct of the registrant and the relief you actually need.

This guide walks each step from pre-launch preparation through post-registration enforcement, flagging the trap that each step conceals.

Step 1: What governs disputes in .cloud – and why that matters before you file anything

The .cloud registry has adopted the UDRP and the URS, meaning WIPO and the other accredited UDRP providers have jurisdiction over abusive .cloud registrations, exactly as they do over .com. That is the right starting point – but it conceals a trap.

The trap is forum choice. Both UDRP and URS are available, and a brand owner who files the wrong one loses time and filing fees without obtaining the remedy that actually solves the problem. URS yields only suspension; UDRP yields transfer or cancellation. If you want the domain in your own portfolio, URS will not get you there. If you only need the infringing registration taken offline quickly, URS is cheaper and faster.

The governing texts are the ICANN UDRP Policy (adopted 1999, mandatory for all accredited registrars in .cloud), the URS Procedure administered by WIPO for new gTLDs, and the Trademark Clearinghouse (TMCH) framework that feeds into sunrise and claims periods. Knowing which document controls your situation on day one prevents wasted motion later.

We regularly advise brand owners entering new gTLD launch cycles who treat .cloud as if it were a ccTLD with a separate national procedure. It is not. The full UDRP machinery applies, including all three elements of Paragraph 4(a) – similarity to a mark you hold, absence of the registrant's legitimate interest, and registration and use in bad faith.

For an early assessment of whether your .cloud situation meets the UDRP or URS threshold, contact info@cognomenlaw.com.

Step 2: How does the Trademark Clearinghouse sunrise period work – and what is the trap in relying on it?

The TMCH sunrise period is the pre-emptive layer: a trademark owner who has recorded a qualifying mark with the TMCH may register the corresponding domain in .cloud before general availability opens. This is the cleanest protection because it avoids a dispute entirely.

The trap is the scope of what sunrise covers. Sunrise registration is limited to an exact match of the mark as recorded. It does not block phonetic variants, abbreviations, or descriptive combinations that a cybersquatter might register the moment the general availability phase opens. A brand named APEX registers apex.cloud in sunrise. Nothing stops a bad actor from registering apex-cloud.cloud, apexservices.cloud, or getapex.cloud on the first day of general availability.

A second trap lies in timing. Sunrise windows are short – typically two to four weeks – and they require an active TMCH recording. If your trademark was not recorded in the TMCH before the launch was announced, you may arrive too late for sunrise. The claims period that follows sunrise provides notice to both parties, but it does not prevent the registration; it only alerts the would-be registrant that a TMCH-recorded mark exists.

For brand owners who missed sunrise or who face variants the sunrise could never have covered, the enforcement tools in Steps 3 through 5 are the only path.

Step 3: When should you use URS rather than UDRP to protect a brand in a new .cloud gTLD launch?

URS is the right tool when you need a domain taken offline quickly and do not need to own it. The proceeding is designed for clear-cut cases – a registrant using a domain that is obviously identical to a registered mark, with no plausible legitimate use.

The evidentiary standard is higher than the UDRP's preponderance standard. URS requires clear and convincing evidence that all three elements are met: the domain is identical or confusingly similar to a mark 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 higher standard is the trap most brand owners miss. A UDRP complaint with the same evidence might succeed; a URS filing with ambiguous or borderline evidence will not. Filing URS on a close-but-arguable case and losing wastes time and puts a denial on the record before any UDRP proceeding.

Use URS when the registration is an obvious lift of your mark – identical string, no added words or numbers, pointed at pay-per-click parking or a directly competing service. The remedy, suspension for the registration term, is blunt but fast. The domain stops resolving. The registrant retains technical ownership but cannot use it.

Use UDRP when you want the domain transferred to your portfolio, when the case involves a combination or variant where legitimate interest arguments are possible, or when a prior URS denial has left the record in a state requiring a fuller proceeding. The USD 1,500 WIPO single-member filing fee and roughly two-month timeline are the price of that broader remedy.

We have advised registrants in .cloud enforcement cycles who received a URS suspension notice and faced a decision within days. The analysis – whether the case is genuinely clear-and-convincing or merely probable – is where the strategy turns.

What evidence decides whether a .cloud dispute succeeds or fails?

Evidence is the axis on which UDRP and URS cases turn, and assembling it before filing is more effective than searching for it under time pressure once a response is due.

For the similarity element, the foundation is proof of trademark rights: a registration certificate, the filing date, and the classes of goods or services covered. A registered mark is the strongest starting point. Common-law rights can satisfy the element, but the evidentiary burden is meaningfully higher because the complainant must demonstrate that the mark acquired distinctiveness through use before the domain was registered.

For the legitimate interest element, the absence of a right is proved by negatives: the registrant is not known by the domain name, has no apparent authorization from the mark owner, and made no bona fide offering of goods or services before receiving notice of the dispute. Panels look at the content of the resolving website, the registration date relative to the mark's priority date, and whether there is any plausible non-infringing use for the string.

For bad faith, the most probative evidence in .cloud cases includes pay-per-click landing pages displaying the complainant's competitors, direct offers to sell the domain at a price well above registration costs, a pattern of registering brand names in new gTLD launches, and passive holding combined with a mark that is so well known that no innocent use is conceivable. The trap here is relying on bad faith that is implied but not documented. Panels do not infer bad faith from inconvenience; they require evidence of it.

Practical steps before filing: screenshot the resolving website with a date-stamped URL, run a WHOIS/RDDS lookup and preserve the registrant record, check for prior UDRP decisions involving the same registrant across any zone, and pull the complainant's trademark registration certificate from the official register. These four steps, done before the complaint is drafted, address three of the most common reasons complaints fail on evidentiary grounds.

Step 4: How do you choose between WIPO and the other UDRP providers for a .cloud complaint?

WIPO and the Forum together account for roughly 97% of all UDRP proceedings, and either can accept a .cloud complaint. The Czech Arbitration Court (CAC) is a lower-cost option. The ADNDRC is available for certain Asia-Pacific matters. The choice is not arbitrary.

WIPO offers the largest panel pool, the most developed jurisprudential body, and an expedited option for single-panel cases covering up to five domains, delivering a decision in approximately one month. If your .cloud problem involves multiple domains registered by the same holder, WIPO's experience with multi-domain complaints is a practical advantage, since a single complaint may cover all registrations held by the same registrant.

The Forum's filing fees begin around USD 1,300 for a single-member panel covering one to two domains. CAC begins lower still, roughly USD 500–800. Neither option sacrifices the binding nature of the remedy; all three accredited providers apply the same UDRP Policy and Rules. The cost difference matters more in a portfolio enforcement scenario where multiple filings are anticipated.

The trap in provider selection is inconsistency. Experienced practitioners know that panel composition varies across providers and that certain factual issues – passive holding, descriptive terms, good-faith investment – are decided with slightly different emphasis by different panels. Choosing a provider without considering the nature of the legal question in your case is a missed optimization.

For most standard .cloud cybersquatting cases, WIPO is the appropriate first choice. Where cost is a primary constraint and the case is straightforward, CAC or the Forum may serve equally well.

Step 5: What happens after a transfer or suspension – and how do you hold the position?

A UDRP transfer order from WIPO directs the registrar to transfer the .cloud domain to the complainant. There is a ten-business-day waiting period before the registrar implements the order, during which the registrant may file a court action in the registrar's jurisdiction to stay the transfer. In practice this rarely happens, but brand owners should be aware that the UDRP decision is not self-executing at the moment it is published.

After a URS suspension, the domain resolves to an informational page indicating it is suspended. The registrant retains ownership until the registration expires. A successful complainant does not receive the domain in its portfolio; it simply becomes unavailable for the suspended term. Brand owners who secured a URS suspension and then watched the registrant re-register the same string in a different new gTLD at expiry will recognize why a UDRP complaint, resulting in transfer, is often the better long-term answer for a well-known mark.

Post-transfer portfolio hygiene matters. Renew the domain, configure its DNS to prevent parking by default, and monitor for new variant registrations in .cloud and across any other new gTLDs where the string is available. The completion of one proceeding is not the end of the exposure; it is the end of that particular registration.

In a recent matter (a .cloud cybersquatting complaint, spring 2025), we secured a UDRP transfer order for a technology brand whose mark was registered in .cloud within forty-eight hours of general availability opening. The registrant had pointed the domain at a pay-per-click page displaying competitor links. The complaint turned on a strong similarity showing and documented bad-faith use – the kind of clean record that a well-prepared evidence set produces.

If a .cloud filing has already been made or you have received a complaint, email info@cognomenlaw.com to assess what the record shows.

How does cross-zone strategy change when a dispute spans .cloud and a legacy gTLD?

Brand owners protecting well-known marks frequently encounter a cybersquatter who registers both the .com and the .cloud variant simultaneously. The strategic question is whether to file a single UDRP complaint covering both registrations – permissible where the registrant is the same holder – or to file separately.

A single multi-domain complaint at WIPO is almost always more efficient when the registrant is confirmed to be the same across both registrations. The USD 1,500 single-member WIPO fee covers up to five domains, so the marginal cost of adding the .cloud registration to a .com complaint is zero. A panel that finds bad faith on the .com evidence is highly likely to make the same finding on an identical .cloud registration, since the analysis of the registrant's intent is the same.

The trap arises when the .com and .cloud registrations are held by different apparent registrants – possibly the same bad actor using different contact details in WHOIS/RDDS. Filing a single complaint against the wrong named registrant produces a procedural objection that can derail the whole proceeding. Confirm registrant identity carefully before filing a combined complaint.

Where the dispute involves a ccTLD alongside .cloud – for example, a .de registration as well as .cloud – the strategic picture changes entirely. .de has no UDRP procedure. A dispute over .de belongs in the German courts, and DENIC offers a DISPUTE entry to block transfer while litigation proceeds. UDRP secures the .cloud transfer; local litigation counsel in the relevant jurisdiction handles the .de matter in parallel. The two proceedings run independently, on different timelines and under different evidentiary rules.

In a separate matter (a multi-zone enforcement campaign, autumn 2025), we coordinated a WIPO UDRP complaint covering .com and .cloud registrations for a software brand, while coordinating with local litigation counsel to file the corresponding national court action for the .de variant. Transfer of the gTLD registrations was implemented within weeks; the national court matter followed its own, longer course.

What are the respondent-side risks – and when does a .cloud registrant have a genuine defense?

Not every .cloud UDRP or URS filing is legitimate. A brand owner with a weak mark, a narrow registration, or a filing timed to capture a generic or descriptive domain from a legitimate registrant may be engaging in reverse domain name hijacking (RDNH) – defined under the Policy as a complaint brought in bad faith to deprive a registrant of a legitimately held domain. Panels may make an RDNH finding against a complainant. The finding carries no financial penalty but is published and damages the complainant's credibility in future proceedings.

A .cloud registrant with a genuine defense should act immediately on receiving a URS notice or UDRP complaint. The respondent has 20 days to file a response once the case commences under UDRP. Defaulting – simply not responding – is the single most common error among registrants who had a viable defense. Panels do not award transfers automatically on default, but the absence of a response removes the evidentiary contest, and panels routinely find for the complainant where the complaint is facially adequate.

The Paragraph 4(c) safe harbors are the respondent's primary tools: demonstrating a bona fide offering of goods or services under the domain before any notice of the dispute; showing that the registrant is commonly known by the domain name; or establishing a legitimate noncommercial or fair use without intent to mislead. Each safe harbor requires documentation – screenshots, business records, correspondence – assembled and filed within the response window.

We handle respondent defense in .cloud and across all gTLDs. Where a complaint is abusive, we pursue the RDNH finding as part of the defense strategy, not as an afterthought.

Related at COGNOMEN

• URS and new gTLD dispute services – suspension and defense across new gTLDs
• TMCH claims notice in .cloud – what to do when the notice arrives
• Recovering a passively held .com domain through UDRP