Step-by-step: request a three-member panel to defend a .cloud domain

Step-by-step: request a three-member panel to defend a .cloud domain. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your c…

A UDRP complaint lands in your inbox naming a .cloud domain you registered legitimately. The complainant has legal counsel, a trademark registration, and what reads like a confident filing. Your first instinct may be to respond quickly and hope a single panelist sees the merits. That instinct can cost you the domain.

When you receive a UDRP complaint targeting a .cloud domain, you have the right to request a three-member panel in place of the single panelist the complainant chose. That right is established in the UDRP Rules: if the complainant selected a one-member panel, the respondent may elect a three-member panel by paying the cost difference. At WIPO, a three-member panel costs USD 4,000 for one to five domains, compared with USD 1,500 for a single-member proceeding – and the parties typically split that higher fee. The request must be made within the response window: 20 days from the date the case commences.

This guide walks each step of that process for a .cloud respondent, flags the trap hidden in each one, and explains how to build the legitimate-interest record that the three panelists will evaluate.

Why .cloud domains are subject to the UDRP – and what that means for respondents

.cloud is a new generic top-level domain operated under ICANN's delegated-registry program, and like all ICANN-accredited gTLD registries it is bound by the UDRP. That means any brand owner with a trademark can file a complaint against a .cloud registrant before WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC.

The governing test is the same three-element structure that applies across every accredited gTLD. The complainant must prove: (1) the domain is identical or confusingly similar to a mark it holds; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. All three elements must be satisfied. If the complainant cannot carry element two or element three, the complaint fails – and if it was filed opportunistically against a registrant with a clear legitimate interest, a panel may go further and make a finding of Reverse Domain Name Hijacking (RDNH).

In our practice we regularly advise registrants who hold .cloud names for genuine business purposes – a cloud-services company, a software developer, a niche community operator – and who face a complaint from a brand owner whose mark postdates the registration or covers a different field. The .cloud extension itself is descriptive, and that descriptiveness matters when a panel weighs whether confusion is likely and whether the registrant had a legitimate purpose in choosing it.

One further point before the steps: the only remedies available under the UDRP are transfer or cancellation of the domain. A panel cannot award damages or costs. That means the dispute is binary – you keep the domain or you lose it – and the quality of your response, and the composition of the panel deciding it, are the main variables within your control.

Step 1: Confirm the filing deadline and read every line of the complaint

The moment you receive formal notice of commencement from the chosen provider – WIPO in the majority of cases – your 20-day response window begins. That window is fixed by the Rules. Missing it means defaulting, and a default almost always results in transfer.

Read the complaint in full before doing anything else. Note: which trademark(s) the complainant relies on and their registration dates; which forum was chosen; whether the complainant explicitly asked for a single-member panel; and the specific bad-faith allegations made. The complainant's choice of single-member panel is the trigger for your election decision. If the complaint is silent on panel size, the default under the Rules is a single panelist.

The trap in this step is assuming the complaint is weak and that any panel will see it. A poorly reasoned complaint can still succeed before a single panelist who applies the threshold test mechanically. Three panelists deliberate. Minority views surface. Nuanced fact patterns get fuller analysis. That is why the election matters most precisely when the facts are genuinely on your side but require explanation.

Check the commencement date carefully. Providers calculate it from the date formal notice is sent, not the date you open the email. If you are uncertain, contact the provider's case administrator immediately to confirm the exact deadline – this is a straightforward administrative inquiry and providers are accustomed to it.

Step 2: Decide whether to request a three-member panel – and why the answer is often yes

The decision to elect a three-member panel is a tactical judgment, not a formality. It adds cost. It may add a week or so to the timeline. But for a respondent with a legitimate defense, the case for electing is usually stronger than the case against.

When does a three-member panel improve the outcome? Consider these situations. First, the complainant's mark is weak, descriptive, or covers a field clearly distinct from the registrant's use. Three panelists applying the confusing-similarity test to a descriptive term in a specialized zone like .cloud are more likely to weigh the zone-level context. Second, the registration predates the complainant's trademark rights. Bad faith cannot exist at the time of registration if the mark did not yet exist – but establishing that timeline benefit from deliberation. Third, an RDNH finding is realistic. A finding of Reverse Domain Name Hijacking requires a panel to conclude affirmatively that the complaint was filed in bad faith. Single panelists are statistically more reluctant to make that finding. Three panelists, deliberating together, are more likely to name it when the evidence supports it.

Conversely, if the complaint is plainly meritorious – the domain is identical to a famous mark, the registrant has no discernible legitimate interest, and the registration was contemporaneous with a public brand launch – the three-member panel will reach the same result as a single panelist, only more slowly and at greater cost to the respondent. Honest assessment of the merits comes first.

For an assessment of your domain dispute – including whether a three-member panel election is the right strategy for your .cloud defense – contact info@cognomenlaw.com.

Step 3: Submit the election within the response window – the procedural mechanics

The election of a three-member panel is not a separate filing. It is a mandatory field within the response itself. At WIPO, the response form includes a section on panel composition; the respondent checks the three-member box and pays the cost difference at the time of filing.

Here is what the mechanics look like at WIPO, which handles the substantial majority of UDRP cases filed against new gTLD domains including .cloud:

1. Log in or register on the WIPO eADR portal and locate the case reference number from your notice of commencement.
2. Open the online response form and complete all required fields: contact information, the domain in dispute, and the respondent's substantive arguments (see Step 4).
3. In the panel-composition section, elect a three-member panel.
4. If you wish to nominate a panelist from WIPO's published list, do so in the same section. You are not required to nominate; if you do not, WIPO appoints one panelist from its list, the complainant nominates one, and WIPO appoints the presiding panelist.
5. Pay the respondent's share of the three-member fee. At WIPO for one to five domains this is approximately USD 1,250 – half the difference between the USD 1,500 single-member fee already paid by the complainant and the USD 4,000 three-member fee total. Verify the exact amount on the WIPO invoice; the arithmetic can vary if the complainant already paid a partial three-member supplement.
6. Submit before the deadline. WIPO's system timestamps submission; file with at least several hours to spare, not at midnight on day 20.

The trap in this step is the panelist-nomination decision. Many respondents skip it, which is defensible. But if you know the subject matter is technical – cloud computing, software architecture, domain industry practice – nominating a panelist with documented experience in that area can shape the deliberation. Review WIPO's panelist list and pick deliberately if you choose to nominate.

How do the Paragraph 4(c) safe harbors apply to a .cloud defense?

Paragraph 4(c) of the UDRP lists three circumstances that, if the respondent can demonstrate them, establish rights or legitimate interests in the domain. These are the safe harbors, and they are the core of any respondent's case.

The first safe harbor is a bona fide offering of goods or services under the domain name before any notice of the dispute. For a .cloud registrant operating a cloud-services business, a software-as-a-service platform, or a technology community, this is often the strongest ground. Evidence: screenshots of the live site predating the complaint, invoices to customers, server logs, business registration records, and any correspondence showing the domain was in active operational use – not parked or redirected.

The second safe harbor is that the respondent has been commonly known by the domain name. A company called "Cloudstream" that registered cloudstream.cloud and traded under that name for three years does not become a cybersquatter because a trademark owner later files a complaint. Evidence: corporate registration documents, marketing materials, press coverage, email headers from a time predating the complaint.

The third safe harbor is legitimate noncommercial or fair use of the domain, without intent for commercial gain misleadingly to divert consumers. Commentary sites, fan projects, and parody domains sometimes fall here – though panels apply this narrowly when the site is monetized.

For .cloud specifically, the generic character of the extension is a double-edged fact. A complainant will argue that adding ".cloud" to a mark creates confusing similarity. A respondent can counter that ".cloud" is a descriptive descriptor for an entire industry category, and that registration of a generic or descriptive term in a descriptive zone signals legitimate intent rather than an attempt to exploit a specific brand. Panels have accepted that argument where the term itself is dictionary-based and the use is genuine.

We have advised registrants who held .cloud names for technology ventures and faced complaints from companies with marks in unrelated sectors. Building the 4(c) record – the documentary history of legitimate use – is the work that decides the case, and it begins before the response is due, not the night before filing.

What evidence decides the outcome before a three-member panel?

Three panelists weigh evidence more deliberately than one. That makes the quality of the evidentiary record the primary variable the respondent controls.

For element two (legitimate interest), the key exhibits are: the registration agreement and its date; website screenshots archived before and after notice of the dispute; business formation documents; revenue records or invoices showing the domain in commercial use; and any third-party references to the registrant using the name. Contemporaneity is everything – a screenshot taken after the complaint arrives carries far less weight than one captured by a web archive service before any dispute arose.

For element three (bad faith), the respondent must undercut the complainant's theory. The most common bad-faith allegation for .cloud names is an intent to attract users for commercial gain by confusion. The rebuttal is documentary: show that your business predates the mark, operates in a distinct field, and selected the domain for reasons unrelated to the complainant's brand. If the complainant's mark was filed or first used after your registration date, say so clearly and provide the evidence. Panels apply bad faith as a cumulative requirement – registered and used in bad faith. Negating either limb ends the inquiry on that element.

For an RDNH argument, look for: a complainant who knew of the registration history before filing; a mark that is generic or narrowly registered; allegations that rely on inference rather than fact; or a demand for three-member costs that the complainant then dropped. Panels have consistently held that an RDNH finding requires affirmative bad faith on the complainant's part – filing to harass or to obtain a domain to which the complainant has no colorable right. The finding is reputational in effect, not monetary, but it matters to a brand owner who files future complaints.

In a recent matter (a .cloud technology domain, summer 2025), we assembled a legitimate-interest record for a registrant whose SaaS platform had operated under that name for approximately four years. The complainant's trademark postdated the registration by two years. The three-member panel denied the complaint and made an RDNH finding, citing the complainant's failure to account for the registration chronology before filing.

Step 4: Draft the response – structure, length, and what to avoid

A UDRP response is not a brief. It is a structured document that addresses each of the three elements in turn, marshals the evidence under each, and states the conclusion the panel should reach. Three-member panels appreciate economy; a response that buries its strongest points in 80 pages of exhibits loses the argument even if the facts are favorable.

Structure the response in this order. Open with a one-paragraph summary of the registrant's position: who you are, when and why you registered the domain, and what you use it for. Then address the three elements of Paragraph 4(a) in sequence. For each element, state whether you dispute the complainant's position and why, then cite your evidence by exhibit number. Close with a request for an RDNH finding if the facts support it – but only if they genuinely do. Overreaching on RDNH when the complaint has colorable merit damages credibility on the legitimate-interest arguments.

Avoid these traps. Do not respond emotionally. Do not accuse the complainant of lying without documentary support. Do not attach hundreds of irrelevant exhibits. Do not make arguments that require the panel to accept factual claims you cannot prove. And do not ignore bad facts – if your site was briefly redirected to a competitor's page or hosted pay-per-click links, address it directly and explain the context, because the complainant certainly will.

If a prior filing or response produced a bad outcome, a focused review can find the element that was missed. Contact info@cognomenlaw.com to discuss your position.

Step 5: After submission – what happens next and what to monitor

Once the response is filed and the three-member panel elected, the provider appoints the panel. WIPO notifies both parties of the panelist names, giving each side a brief window to raise any conflict objection. Review the appointed panelists' published decisions. If a conflict exists – a panelist who has previously written opinions that are directly adverse on the precise legal question in your case, or a business connection to the complainant – object promptly and in writing to the provider, with specifics. Objections based on outcome preference alone are not accepted.

From panel appointment to decision, a standard UDRP proceeding typically runs within the overall two-month window from commencement. Three-member panels may take slightly longer than single panelists; that is normal. Neither party may submit additional materials after the response deadline without the panel's permission. If new evidence arises – for example, a screenshot of the complainant's public statements that postdates your response – contact the provider immediately and request leave to file a supplemental submission. Panels grant such leave sparingly.

When the decision issues, the registrar implements it within a short mandatory period unless you seek a stay through a court of competent jurisdiction. A stay requires filing an action in the appropriate court – for .cloud, this typically means the court with jurisdiction over the registrant or registrar, depending on the registration agreement's dispute-resolution clause. If you believe the panel got it wrong and you have grounds for a court challenge, the window is narrow. That is a decision for counsel to evaluate immediately on receipt of the decision.

In another matter we handled (a .cloud brand dispute, autumn 2025), a respondent received an adverse single-panelist decision after responding without legal counsel. We reviewed the decision, identified a clear error in the bad-faith analysis, and advised on the court-challenge option under the applicable national procedure. The window was tight. Acting within days made the difference.

Comparing routes: UDRP three-member panel versus alternative paths for .cloud

The UDRP three-member panel is not the only path open to a .cloud respondent. The right route depends on the facts and the goal.

If the complaint is already filed and the respondent's aim is to keep the domain, the UDRP response with a three-member election is the correct and only forum-level route. There is no appeal within the UDRP system; a court challenge after a decision is the only post-decision remedy, and it is expensive and uncertain.

If no complaint has been filed yet but a cease-and-desist letter has arrived, the respondent has more options. In some cases, negotiating a coexistence agreement or a sale at a fair price is the better outcome than litigating a defense through the UDRP. In others, the letter is a prelude to an abusive complaint, and building the evidentiary record now – before any notice of dispute is formally issued – is the highest-value step. We regularly advise registrants at this pre-dispute stage, and the documentation assembled then directly feeds the 4(c) safe-harbor record if a complaint eventually arrives.

If the dispute involves not only .cloud but also a parallel .com or a ccTLD registration, the registrant may face multiple proceedings simultaneously. UDRP complaints can be consolidated only when the same registrant holds all the domains; otherwise each proceeding is separate. A .de domain in the same dispute does not go to UDRP at all – it goes to the German courts, with the DENIC DISPUTE entry available to block transfer while litigation proceeds. A .uk domain goes to the Nominet DRS, which uses an "abusive registration" test and requires the complainant to prove "registered or used" abusively – a structurally different element from the UDRP's cumulative "registered and used." Managing multi-zone exposure requires a coordinated strategy, not parallel isolated filings.

The URS (Uniform Rapid Suspension) also applies to new gTLDs including .cloud, but it is a complainant-side remedy only. A respondent cannot initiate a URS. If a URS is filed against your .cloud domain, the respondent may file a response – but the remedy on success for the complainant is suspension, not transfer. A URS defense is a separate and shorter proceeding; the substantive analysis overlaps with UDRP but the standard is "clear and convincing evidence," which is a higher bar for the complainant.

Related at COGNOMEN

• Respondent defense and RDNH services – how COGNOMEN builds the legitimate-interest record and pursues RDNH findings
• How to prove legitimate interest in a .co domain – doctrine and evidence patterns that apply across new gTLDs
• URS vs. UDRP for .dev domains – procedural differences, cost, and when each applies