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

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

A UDRP complaint lands against your .io domain. The complainant has selected a single panelist. You have 20 days to respond — and inside that window sits a decision most registrants miss: whether to request a three-member panel instead. That choice reshapes the case before a single word of substantive argument reaches anyone.

To request a three-member panel when defending a .io domain under the UDRP, a respondent must include the request in the response filing and accept responsibility for half the additional panel fee — bringing the three-member cost from USD 1,500 to USD 4,000 at WIPO, with the complainant covering the other half. The .io zone operates under UDRP rules administered through WIPO, which means the same procedural machinery that governs .com disputes applies here. The request is strategic, not automatic; it makes sense in specific fact patterns, and this guide walks each step.

This page covers the procedural mechanics, the evidence you need to build before filing the request, the fee-split trap, when an RDNH finding becomes a realistic objective, and the questions to ask at each stage.

Does the UDRP actually apply to .io domains?

Yes — and that answer matters before anything else. The .io ccTLD is administered by the Internet Computer Bureau on behalf of the British Indian Ocean Territory, and the registry has adopted the UDRP as its governing dispute-resolution policy. In practice, .io disputes are filed with WIPO and proceed under the same three-element test and procedural rules that govern .com, .net, and the other accredited gTLDs. The same Paragraph 4(a) requirements apply: confusing similarity, no rights or legitimate interests, registration and use in bad faith — all three, cumulatively.

One practical consequence: the full suite of WIPO procedural options is available. That includes the right to request a three-member panel, supplemental filings under exceptional circumstances, and the RDNH mechanism. Registrants who assume .io sits outside the UDRP system sometimes skip a response altogether. That is a costly mistake — default hands the panel only the complainant's version of events.

In our practice, we have seen .io disputes filed by brand owners who view the ccTLD as an easy target precisely because some registrants do not realize the procedure is identical to .com. The zone does not change the substantive test. It does not shorten the response window. And it does not reduce the weight of the three-member panel option.

What is a three-member panel and when should you request one?

Under the UDRP, a single panelist is the default unless the complainant specifically chooses three or the respondent exercises the right to escalate. A three-member panel means three independent arbitrators decide the case by majority — a higher level of scrutiny that can benefit a respondent with a strong but nuanced defense.

When does escalation make sense? Four fact patterns justify the cost in most cases we handle. First, the complainant's trademark is weak — descriptive, geographically limited, or registered after the domain. Second, the respondent has a documented legitimate interest under Paragraph 4(c): a business using the name before any notice of the dispute, a personal name, or a genuine noncommercial use. Third, the complaint appears designed to deprive a legitimate registrant rather than to enforce a real trademark right — the hallmark of a reverse-domain-name-hijacking attempt. Fourth, the domain has significant commercial or portfolio value, and the asymmetry between the filing fee and the domain's worth justifies the extra scrutiny.

A three-member panel does not guarantee a better outcome. What it does is reduce the variance. One panelist can surprise. Three panelists, each required to write to the majority position, tend to produce decisions that track the UDRP consensus more closely. For a borderline case, that consistency is worth paying for.

If you are unsure whether your .io dispute warrants escalation, the answer usually lies in the strength of your legitimate-interest evidence. For an assessment of your domain dispute, contact info@cognomenlaw.com.

How do you build the legitimate-interest record before filing?

The Paragraph 4(c) safe harbors are the core of any respondent defense, and the evidence supporting them must be assembled before the response is submitted — not after. Panels do not generally reopen the record, and WIPO's supplemental filing rules are strict. This step is where most self-represented respondents lose time they do not have.

The three safe harbors under Paragraph 4(c) are: (i) use of the domain in connection with a bona fide offering of goods or services before any notice of the dispute; (ii) the registrant is commonly known by the name; (iii) legitimate noncommercial or fair use of the domain. Each maps to a specific evidence type.

For the bona fide offering harbor: gather dated screenshots of the site as it existed before the complaint was filed, any archived pages from services such as the Wayback Machine, invoices or purchase orders dated prior to the notice, incorporation documents, business licenses, or correspondence with customers that predates the dispute. The earlier the evidence, the stronger the showing.

For the "commonly known by the name" harbor: registration documents, email signatures, professional directories, press coverage, or third-party references using the respondent's name. The key is that the name must have been in use before the dispute notice — recent rebranding timed to the complaint will not help.

For fair use: the analysis is more fact-specific. A criticism site, a fan site, or a commentary domain may qualify, but the content must genuinely reflect that purpose, and any commercial element weakens the argument considerably. Panels look carefully at whether monetization is present alongside the claimed fair use.

One trap at this step: the date of registration alone does not establish legitimate interest. A respondent who registered a domain years before the complainant's trademark issued still needs to show what the domain was being used for — not just when it was registered. Build the use record, not only the registration record.

What are the step-by-step mechanics of requesting a three-member panel?

The procedural path is more structured than most respondents expect. Each step carries a trap. Here they are, in sequence.

Step 1 — Identify the provider and the commencement date. The complaint will specify which WIPO or other approved provider is administering the case. Confirm the commencement date — the formal start of the response clock — in the provider's written notification. The 20-day response deadline runs from commencement, not from when the complaint was first filed. Missing this distinction costs days. Most WIPO commencement notices arrive by email; check spam filters immediately.

Step 2 — Review the complaint for panel composition. Identify whether the complainant has requested a single-member or three-member panel. If the complainant already requested three, the fee structure is already at the higher tier and no escalation request is needed. If the complainant selected a single panelist, you have the right to request three — but the cost consequence is triggered by your request.

Step 3 — Make the election in writing within the response. The request for a three-member panel is not a separate form. It is a specific declaration inside the response document itself. WIPO's filing system asks for this election during the online submission process. The election must be unambiguous; an ambiguous or conditional request may be treated as a single-panel default.

Step 4 — Calculate and pay the fee differential. At WIPO, a single-member panel for one to five domains costs the complainant USD 1,500. A three-member panel costs USD 4,000. When the respondent escalates, the parties split the higher fee: the complainant keeps their USD 1,500 credit, and the respondent pays the difference — typically around USD 1,250, depending on the exact allocation and how many domains are in the complaint. Confirm the precise amount with WIPO before filing; the payment deadline is tight and non-compliance can forfeit the request.

Step 5 — Nominate a panelist. When either party requests a three-member panel, each party nominates one panelist from the provider's list. WIPO then appoints the third, presiding panelist. Your nomination is consequential: review the list, look at publicly available prior decisions by each candidate, and select someone with a track record of balanced analysis in disputes involving the type of defense you are running — legitimate interest or RDNH. This step is often skipped or done in minutes. It should not be.

Step 6 — Submit the full response simultaneously. The three-member-panel election and the substantive response are filed together in a single submission before the 20-day deadline. There is no separate extension granted for choosing three. Do not reserve the full response for after the panel is constituted. The response is your only guaranteed opportunity to present your case; supplemental filings are disfavored and rarely granted.

Trap at Step 6: respondents sometimes request a three-member panel and then file a thin response, reasoning that the panel will ask for more. That reasoning is wrong. Panels do not routinely solicit additional submissions. A thin response filed under three-member proceedings is no more persuasive than a thin response before a single panelist.

How do you build the RDNH argument, and when is it realistic?

Reverse domain name hijacking — a finding that the complaint was brought in bad faith to deprive a legitimate registrant of a domain — is the strongest outcome a respondent can achieve beyond a simple denial of transfer. An RDNH finding carries reputational weight: it is publicly recorded in the WIPO database and follows the complainant into future proceedings. It is not, however, a monetary remedy. The UDRP does not award costs.

When is RDNH realistic? Panels have consistently held that RDNH requires more than a lost complaint. The consensus view under the Policy is that the complainant must have known — or should clearly have known — that it could not succeed on the three-element test, yet filed regardless. The clearest patterns include: a complainant with a trademark registered after the domain; a complainant who knew of the respondent's legitimate business before filing; use of the UDRP procedure against a registrant with obvious descriptive or generic rights to the name; or a complaint containing material misrepresentations about the domain's use.

In a recent matter (a .io domain dispute, spring 2025), we built an RDNH defense for a technology firm that had operated under its domain name for several years before the complainant even applied for the trademark at issue. The panel denied the transfer and issued an RDNH finding, noting that the complainant's trademark registration postdated the domain by a significant margin. The case illustrated that a three-member panel — which we had requested — was better positioned to articulate the RDNH reasoning in a formal, majority-signed decision.

To build an RDNH record, flag in the response: the chronology of trademark registration versus domain registration; any pre-filing communications showing the complainant was aware of the respondent's use; any evidence that the complainant engaged in bad-faith pre-complaint conduct such as unsolicited lowball offers or litigation threats lacking factual foundation; and any material factual inaccuracies in the complaint itself. Each of these becomes part of the written record the panel reviews.

What evidence actually decides the outcome?

A three-member panel applies the same evidentiary standard as a single panelist: a preponderance of the evidence on elements one and three, and a rebuttable prima facie showing on element two (legitimate interest) once the complainant makes its initial case. The difference in practice is that three panelists who each read the record independently are less likely to overlook weak evidence on either side.

The evidence categories that consistently move panels in a respondent's favor follow a clear pattern. Documented pre-dispute use of the domain — active website, business correspondence, registered company name matching the domain — is the most powerful single category. Registration date alone, as noted above, is not sufficient without evidence of use. The second category is third-party corroboration: press coverage, supplier invoices, customer emails, social-media accounts predating the complaint. The third is the absence of indicia of bad faith: no pattern of registering marks as domains, no pay-per-click content targeting the complainant's customers, no history of offering the domain for sale at an inflated price.

Evidence that does not help — and may actively harm — includes post-filing changes to the website, unsupported denials, and bare assertions of legitimate use without documentary support. Panels have consistently noted that a respondent who claims a legitimate interest but produces no corroborating documents raises its own credibility concerns.

One practical note on format: WIPO's online filing system accepts PDF annexes. Annex every document rather than summarizing it in the body of the response. A referenced exhibit the panel cannot verify carries less weight than the document itself. Number your annexes sequentially and reference them precisely in the argument section.

If a prior response produced an unfavorable result, or if you are now facing a complaint and weighing how to structure the defense, email info@cognomenlaw.com to review the record.

How does the .io zone compare to .com and other ccTLDs for this purpose?

The right route depends on the zone, the registry rules, and the goal. For .io, the UDRP path is the governing procedure — the same three-element test, the same WIPO forums, the same timeline of roughly two months. That alignment makes .io procedurally straightforward relative to many ccTLDs, where the respondent must work under a distinct national procedure with different rules, different providers, and sometimes different remedies.

Consider the contrast with .uk, which operates under Nominet's DRS — a separate body with a distinct "abusive registration" test, a free mediation stage before any expert decision, and appeal fees of GBP 3,000 + VAT for a three-expert panel. The DRS test reads "registered or used" abusively, a lower bar than the UDRP's cumulative "registered and used in bad faith." A respondent defending a .uk domain faces a structurally different fight from a respondent defending a .io domain, even if the underlying facts look similar.

For .de, neither the UDRP nor a UDRP-variant applies: disputes generally proceed through the German courts, with a DENIC DISPUTE entry available to block transfer while the court action runs. The .eu procedure under EURid uses the Czech Arbitration Court's ADR.eu platform with its own eligibility and remedy rules.

What does this mean in practice? A registrant holding both a .io and a .de version of the same name, facing complaints in both zones simultaneously, is managing two entirely different procedural tracks. The .io defense runs through WIPO under the UDRP. The .de defense runs through local litigation counsel in Germany. Neither informs the other procedurally, though the factual record built for one can support the other if the underlying facts are the same.

For .io specifically, the UDRP's three-member panel option is a genuine procedural tool — one that the .de route does not offer and the .uk DRS offers only at the appeal level, at substantially higher cost. That availability is an advantage worth using when the facts support it.

Related at COGNOMEN

• Respondent defense and RDNH — how we assess and build a defense across gTLDs and ccTLDs
• How to respond within the UDRP deadline — a step-by-step guide to the response window
• UDRP versus national ccTLD procedure — comparing routes across zones