How to request a three-member panel to defend a .dev domain

How to request a three-member panel to defend a .dev domain. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

A .dev domain you registered years ago suddenly generates a UDRP complaint. The complainant chose a single panelist. You believe the case is substantively weak — or worse, that it was filed purely to pressure a transfer. The first decision you face is whether to escalate: to request a three-member panel to defend a .dev domain and shift the proceeding onto ground where a fuller record and three independent readers can correct a speculative filing.

Under the UDRP — which governs .dev as a Google-operated new gTLD — a respondent may request a three-member panel in the response, paying the cost difference above the single-member fee. The WIPO three-member filing fee is USD 4,000 for one to five domains, versus USD 1,500 for a single member; when the complainant chose single-member, the parties generally split the higher fee, meaning the respondent's share is roughly USD 1,250. A three-member panel adds depth to a close case and creates the procedural record from which a formal finding of Reverse Domain Name Hijacking can flow.

This page covers the mechanics of that request, the safe-harbor evidence that wins a .dev defense, and the step-by-step path COGNOMEN follows for respondents in this zone.

Why .dev runs under the UDRP — and why that matters for your defense

.dev is a new-gTLD operated by Google Registry; because it is accredited through ICANN, the standard UDRP applies in full. That means your defense rests on the same three-element structure that governs .com disputes, but in a zone almost exclusively used by software developers, open-source maintainers, and technology companies. That technical-community context is not irrelevant to the panel's reading of legitimate interest. A developer who registered a .dev matching their handle, project name, or employer brand has a factual story panels consistently treat as probative under Paragraph 4(c) safe-harbor analysis.

The zone also carries a practical asymmetry. Some complainants — particularly those who monitor trademark portfolios systematically — file UDRP complaints against .dev domains on the theory that any domain touching their mark must be abusive. That assumption often overlooks the genuine developer community that uses .dev for tooling, libraries, or documentation. In our practice, we regularly advise registrants who received a UDRP complaint against a .dev they built out and used actively, where the filing cannot survive scrutiny of the actual registration history.

If you have received a UDRP complaint for a .dev domain, the response deadline is fixed — typically 20 days from commencement. For a rapid read on whether a three-member request makes sense in your case, contact info@cognomenlaw.com.

What does requesting a three-member panel actually do?

Requesting a three-member panel changes the proceeding structurally, not just numerically. A single panelist produces a majority decision by definition; three panelists must reason through divergent views and reach a consensus or a majority opinion, which means weak complainant arguments face a broader challenge. For a respondent with a strong legitimate-interest record, that deliberative friction is an asset.

Three-member panels are also more likely to issue formal RDNH findings when the record supports one. Reverse Domain Name Hijacking is a finding that the complaint was brought in bad faith — typically where the complainant knew or should have known it could not prevail, yet filed to extract a transfer or impose costs on the registrant. An RDNH finding carries no monetary penalty under the UDRP, but it is a matter of public record and carries reputational weight. A single panelist may note abusive filing in passing; a three-member panel that agrees on RDNH typically does so with reasons that stick.

There is a cost consideration. Where the complainant elected a single-member panel, the respondent's request for three members means the parties generally split the fee difference. At WIPO, that arithmetic means the respondent contributes roughly USD 1,250 above the baseline. That is a meaningful line item, but it is not a deterrent when the case justifies it — which is why the first analytical step is always assessing whether the complainant's filing can actually survive three readers.

How do you build the legitimate-interest record under Paragraph 4(c)?

The Paragraph 4(c) safe harbors require evidence, not assertion. Three recognized pathways exist: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; or a legitimate noncommercial or fair use without intent to mislead or divert. For .dev respondents the first and third pathways are most common, and both require contemporaneous documentation.

What does "before notice of the dispute" mean in practice? It means any active use — a deployed site, a public repository, a documentation page, a continuous development log — that pre-dates the complaint by a meaningful margin. Screen captures with server timestamps, Wayback Machine records, GitHub commit histories, and domain registrar creation-date records all contribute. A .dev domain with a multi-year commit history tied to an active open-source project is not the profile of a cybersquatter. It is the profile of a developer.

The complainant's burden is to put the registrant's legitimate interest genuinely in question. Once they do, the burden shifts — in practice — to the registrant to come forward with evidence. That is why assembling the record early matters. Panels look for specificity: a project with a name, a timeline, and third-party corroboration (contributors, issue trackers, package registries) reads as credible in a way that a bare assertion of "we were building something" does not.

In a recent matter — a .dev registration tied to a developer tooling project, spring 2025 — we built a legitimate-interest record from a five-year GitHub history, archived documentation pages, and public package-registry listings. The complaint was denied. The panel's reasoning centered on the registrant's demonstrable use well before any contact from the complainant's legal team.

When is a Reverse Domain Name Hijacking finding realistic?

RDNH is not a default outcome for a lost complainant. Panels require a finding of bad faith on the complainant's side — something beyond a weak case. The consensus view is that RDNH is appropriate where the complainant clearly knew the respondent had legitimate interests and filed anyway, or where the complaint was so facially insufficient that no reasonable complainant could have believed it would succeed.

In the .dev zone, certain complainant behaviors raise that threshold. A trademark registered after the domain's creation date is a structural problem the complainant is expected to notice. A complainant whose mark is descriptive or generic, who files against a developer domain with an active technical use, and who makes no attempt to distinguish the registrant's documented history — that is the profile of a complaint that warrants RDNH analysis. Similarly, a complainant that sent a five-figure purchase offer before filing suggests that the true goal was acquisition at a lower price through procedural pressure, not protection of trademark rights.

We have defended multiple respondents in new-gTLD proceedings where RDNH was both argued and granted. The pattern is consistent: the best RDNH record combines (a) a clear pre-complaint legitimate use, (b) evidence the complainant's mark was weak or junior to the registration, and (c) conduct by the complainant — pre-filing demand letters, aggressive timelines, or overreaching claims — that the panel can read as coercive rather than protective.

A three-member panel is the right venue for an RDNH argument of substance. The finding requires written consensus among independent readers, and three-member panels produce that record far more often than solo decisions.

If the complaint you received reads like a pressure filing — a short demand, a mark registered after your domain, or an offer to buy before litigation — email info@cognomenlaw.com to assess whether an RDNH argument is viable.

What evidence actually decides the outcome of a .dev defense?

Panels in UDRP proceedings weigh evidence rather than argument. The record closes when the response is filed; no new evidence enters after that without leave, and supplemental filings are disfavored. That means the response itself must carry the full evidentiary load. What belongs in it?

First, chain-of-title documentation: the registration record, creation date, renewal history, and any transfer record that establishes when and why the respondent holds the domain. A domain held since the year it was first made available, with consistent renewal, tells a different story than one acquired recently after a complainant's mark became prominent.

Second, use evidence: any public-facing activity — site screenshots, repository links, package-registry entries, forum posts, documentation, correspondence referring to the domain — with timestamps. Where possible, use the Wayback Machine to show the site's state at multiple points in time. Panels give weight to a consistent pattern of use that predates the dispute.

Third, the respondent's background: who they are, why the name made sense to them, and whether they are known in any relevant community by this name or a near equivalent. A developer named by their handle in industry credits, or a company with a product line that maps to the domain string, has a plausible narrative. That narrative needs to be stated plainly in the response, not left for the panel to infer.

Fourth, any evidence of complainant overreach: pre-filing demand letters, purchase offers at below-market prices, timelines that suggest a strategy of deadline pressure, or prior unsuccessful attempts to acquire the domain. These go to bad faith on the complainant's side and directly feed the RDNH analysis.

The response also contains the three-member panel request. It is filed in the same document or accompanying it; it is not a separate motion. Miss the response deadline — 20 days from commencement — and the right to a three-member panel, and to any defense at all, is forfeit by default.

How does the route differ from a Nominet DRS or EURid ADR dispute?

The right route depends entirely on the zone. For .dev, the UDRP applies — there is no separate national procedure, and the dispute goes to WIPO or another UDRP-accredited provider. That is the .com and .org track, not the ccTLD track. Choosing the right procedural framework is the first analytical step any time a domain dispute arises.

For a .uk domain, the governing procedure is the Nominet DRS, which reads "registered or used" abusively — a lower bar for complainants in one sense, but it also incorporates a free mediation stage that can resolve a dispute before any formal decision cost is incurred. For a .eu domain, the EURid ADR procedure applies, with its own eligibility rules and remedy set. For a .de domain, there is no UDRP at all — disputes go to the German courts, with a DENIC DISPUTE entry available to block transfer in the interim.

The .dev zone sits squarely on the UDRP track. That means the three-member panel mechanism described on this page is exactly the procedure to use. It also means there is no mediation stage and no free first step: the response is the defense, and it must be complete and evidenced when filed.

If the same underlying trademark conflict spans a .dev and a national ccTLD — as sometimes happens when a complainant files in parallel across zones — each dispute runs on its own procedural track. The .dev response does not automatically resolve the ccTLD dispute, and the evidence strategies may diverge. We coordinate multi-zone defense regularly and can sequence the filings to support rather than undermine each other.

What is the step-by-step process COGNOMEN follows for a .dev defense?

The moment a complaint arrives, the clock is running. A 20-day response window is not long when the legitimate-interest evidence needs to be located, reviewed, and organized into a coherent legal record. Here is the sequence we follow.

The first step is a rapid case assessment: reading the complaint, identifying the complainant's theory of bad faith, checking the trademark registration date against the domain creation date, and estimating whether the three UDRP elements can credibly be met. That read takes hours, not days, and it informs every decision that follows.

The second step is evidence gathering. We work with the registrant to pull the registration record, identify all use evidence, document any pre-complaint communications, and assess whether third-party corroboration (contributors, clients, package registries, trade publications) is available and collectible within the timeline.

The third step is the three-member panel decision. Not every case warrants the additional cost. A clearly weak complaint against a registrant with an overwhelming use record may be better defended on a single-member track, preserving resources while still winning. A close case, a strategic complainant, or a strong RDNH argument tips the analysis toward three members. We advise that choice clearly and explain the cost arithmetic.

The fourth step is drafting and filing the response. This is the document that does the work. It addresses each of the three UDRP elements, argues the Paragraph 4(c) safe harbors with specificity, introduces the evidentiary exhibits, and where warranted, makes the RDNH argument with its own section. We do not hedge in the response; we state the registrant's position directly and leave the record complete.

The fifth step is monitoring the panel appointment and decision timeline. We track the proceeding, flag any supplemental filing requests, and prepare the registrant for the decision and its implementation at the registrar level.

In a recent matter — a .dev domain contested by a technology brand in summer 2025 — we assembled a response in twelve days, requested a three-member panel, and secured both a denial of the transfer request and a formal RDNH finding. The registrant had held the domain for approximately seven years and operated a publicly documented developer tool under that name throughout.

Related at COGNOMEN

• UDRP respondent defense and RDNH — the full service across all zones
• FAQ: how to respond within the UDRP deadline for tech-zone domains
• FAQ: new gTLD launch protections and group filings explained