How to choose between WIPO and the Forum for a .dev dispute

How to choose between WIPO and the Forum for a .dev dispute. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

A developer brand registers its product name as a .dev domain, only to find a third party has already taken it — and is sitting on it. The question arrives immediately: which forum handles this? And does the choice of forum change the odds?

For a .dev domain dispute, both WIPO and the Forum (formerly the National Arbitration Forum) apply the UDRP — because .dev is a generic top-level domain operated by Google Registry and subject to standard ICANN-accredited registrar obligations. That means you must prove all three elements of Paragraph 4(a): confusing similarity to your mark, no legitimate interest in the registrant, and registration and use in bad faith. A standard case resolves in approximately two months; the only remedies are transfer or cancellation of the domain.

This page explains how the two forums differ, which facts push you toward one over the other, what the .dev zone adds to the analysis, and how to move from decision to filing.

Why .dev Domains Fall Under the UDRP

.dev is a gTLD delegated by ICANN and operated under a registry agreement that requires all accredited registrars to incorporate the UDRP into their registration contracts. Every .dev registrant therefore agrees, at the moment of registration, that a dispute may be resolved under the Policy. There is no separate ccTLD procedure and no national registry arbitration to navigate. The UDRP applies in full — Paragraph 4(a) elements, Paragraph 4(b) bad-faith factors, Paragraph 4(c) safe harbors, and all.

One .dev-specific feature does shape the evidence analysis. Google Registry enforces HSTS preloading for .dev, which means every .dev domain is served over HTTPS. That technical constraint sometimes bears on bad-faith arguments: a registrant who has never configured a TLS certificate and points the domain at a parking page has made an affirmative technical choice — it does not just sit idle. Panels have noted passive holding as a badge of bad faith where the registrant cannot credibly explain the absence of use. With .dev, the absence of a functioning site is therefore highly visible.

Because both WIPO and the Forum apply identical substantive rules — the UDRP and its associated Rules — the choice between them is procedural, tactical, and economic. It is not a choice between different legal standards.

How Do WIPO and the Forum Differ in Practice?

The two providers share the same Policy but diverge on administration, panelist pools, filing interface, and cost structure — and those differences are material when you are choosing where to file a .dev complaint.

WIPO — headquartered in Geneva — is the largest UDRP provider, handling roughly 97% of all proceedings together with the Forum. WIPO's filing fee for a single-domain, single-member panel case is USD 1,500; a three-member panel costs USD 4,000. WIPO also offers an expedited option that delivers a decision within approximately one month for single-panel cases covering up to five domains. The WIPO online filing system is mature; its case management portal tracks every procedural step in real time. WIPO's panelist pool skews toward practitioners with international IP and technology backgrounds — an advantage in a .dev dispute where the complainant's mark may be known primarily in a developer or SaaS context rather than in mass-market consumer goods.

The Forum starts its filing fee at approximately USD 1,300 for one to two domains on a single-member panel — a modest saving over WIPO. The Forum's panelist pool is deep in US-based practitioners and has historically processed a high volume of cases in straightforward cybersquatting fact patterns. For a .dev complainant whose mark is a registered US trademark and whose facts are clear-cut — a parked domain, no response filed, obvious intent to sell — the Forum is a workable option. Process-wise, the Forum's online system is reliable and its case management is efficient.

In our practice, the clearest differentiator is not cost but panel composition. A .dev dispute often involves a technology-oriented complainant — a software company, a developer-tools brand, an open-source project with community recognition — whose rights may rest partly on unregistered trademark use or trade name recognition. WIPO panelists are, as a group, more experienced with international unregistered rights arguments. That can matter at Paragraph 4(a) when the complainant's mark is a SaaS product name known in developer circles globally rather than a registered trademark in every jurisdiction.

The right forum choice depends on your mark, your evidence, and the registrant's conduct. To assess the three UDRP elements and select the optimal provider for your .dev dispute, contact info@cognomenlaw.com.

What Are the Three UDRP Elements You Must Prove?

To prevail under the UDRP — at either WIPO or the Forum — a complainant must satisfy all three elements of Paragraph 4(a) on the balance of probabilities. Failing any one of them ends the case in the registrant's favor.

Element one: confusing similarity. The domain must be identical or confusingly similar to a trademark or service mark in which you have rights. For .dev disputes, this element is typically the easiest to clear. The generic string ".dev" is disregarded in the comparison — panels treat the TLD as a functional suffix, not a distinguishing component. If the second-level label matches or closely resembles your mark, element one is met. Rights include registered trademarks and, in appropriate circumstances, unregistered marks that have acquired distinctiveness through use. A complainant relying on an unregistered mark must demonstrate that the mark had acquired secondary meaning before the domain was registered.

Element two: no legitimate interest. You must show the registrant has no rights or legitimate interests in the domain. Paragraph 4(c) sets out three safe harbors a registrant may invoke: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; and legitimate noncommercial or fair use. In .dev disputes, the common-knowledge safe harbor rarely applies unless the registrant has an independent basis for the string — a developer whose actual given name or handle matches the domain, for example. Panels look for evidence of pre-dispute use. A parking page monetizing the developer community's traffic is not a bona fide offering.

Element three: registered and used in bad faith. This element is cumulative — both registration in bad faith AND use in bad faith must be shown. Paragraph 4(b) lists illustrative circumstances: registration primarily to sell to the mark owner at a profit; registration to disrupt a competitor; attraction of users through confusing similarity for commercial gain; and a pattern of abusive registrations. In .dev disputes, the passive-holding argument carries particular weight. A registrant who secured a developer-brand .dev domain and pointed it at a parked page — generating click revenue from developer traffic seeking your product — fits squarely within the Paragraph 4(b)(iv) commercial gain scenario. Panels have also found bad faith where a registrant's WHOIS/RDDS data was masked and the registrant failed to respond to pre-complaint outreach.

What Evidence Decides a .dev Dispute?

Evidence is the practical battlefield, and assembling it correctly before filing determines whether a complaint succeeds or produces an unnecessary default decision that still looks thin on the record.

For element one, the complainant needs trademark certificates or, for unregistered rights, evidence of market presence — press coverage, GitHub stars, product download figures, developer-community mentions, and dates of first use. The earlier in time the rights evidence predates the domain registration date, the stronger the case.

For element two, the complainant needs to show the registrant has no plausible independent claim to the string. A reverse WHOIS search showing the registrant holds multiple developer-brand domains supports a pattern argument. Screenshots of the domain resolving to a parking page or a for-sale landing page are essential; capture them with a timestamped tool that preserves the full page source. Email or social-media records of a buy-back demand from the registrant are highly probative — panels treat an unsolicited demand to sell at a price exceeding registration cost as near-conclusive evidence of bad-faith purpose.

For element three, the registration date matters. If the registrant registered the .dev domain after your product launched and gained community recognition, the sequence strongly implies awareness at registration. WIPO panels in particular have been willing to draw the inference of registration in bad faith from the combination of timing, registrant history, and the domain's commercial deployment against the very audience your product serves.

In a recent matter — a .dev dispute involving a developer-tools brand and a portfolio registrant, spring 2025 — we assembled a record showing the domain was registered within days of a public product announcement and immediately redirected developer traffic to a competing tool. The panel transferred the domain without requiring supplemental submissions. The total elapsed time from filing to transfer order was approximately eight weeks at WIPO.

How Does the Decision Matrix Work? WIPO vs. the Forum for .dev

The situation-based comparison is the core of the forum-selection decision. Here is how we approach it in practice.

If your .dev dispute involves an international technology mark — registered in multiple jurisdictions, or unregistered but widely recognized in the global developer community — WIPO is the preferred forum. Its panelist pool has the deepest bench of practitioners who understand international IP rights in technology contexts. The USD 1,500 single-panel fee is modest relative to the value of a developer brand. WIPO's expedited option, delivering a decision in approximately one month, is worth requesting when reputational or commercial harm is acute.

If your dispute involves a registered US trademark, a simple fact pattern (parked domain, no prior use, no response filed), and cost sensitivity is a factor, the Forum at approximately USD 1,300 is a reasonable alternative. The savings are not dramatic — roughly USD 200 on the forum filing fee alone — but for a portfolio complainant with multiple .dev domains, the difference accumulates. Note that if the registrant requests a three-member panel after you file for a single panelist, the parties typically split the three-member fee; at WIPO that higher fee is USD 4,000, meaning your exposure rises.

If the registrant is likely to fight — if the .dev domain is a common descriptive term in the developer space, if the registrant has a plausible fair-use or first-use argument, or if the domain predates your trademark registration — a three-member panel at WIPO reduces the risk of a split decision and provides a fuller written record. A three-panel WIPO case costs more upfront, but a single-panel loss in a genuinely contested dispute costs more in the long run: you lose the filing fee, lose the domain, and hand the registrant a decision they can publicize.

If the domain is also registered in another zone — a parallel .com or a ccTLD — a combined UDRP complaint covering multiple domains registered by the same holder consolidates the proceeding. WIPO and the Forum both allow multi-domain complaints where the registrant is the same holder. A .dev dispute that also involves a .com variant under the same registrant is a strong candidate for a joint filing to control cost and avoid inconsistent decisions.

Court action is rarely the starting point for a .dev dispute. The UDRP is faster and cheaper. If the registrant has engaged in fraudulent conduct — identity theft, unauthorized transfers, account hijacking — the domain recovery and theft route is more appropriate than a standard UDRP complaint, because the complaint mechanism is not designed for stolen registrations.

If your .dev dispute also involves a .com, a ccTLD variant, or a registrant with a history of abusive registrations, the strategy shifts. For a read on whether the three UDRP elements are met and which forum fits your fact pattern, reach us at info@cognomenlaw.com.

What Is the Process and Timeline for a .dev UDRP Complaint?

A UDRP case proceeds through five defined stages regardless of whether you file at WIPO or the Forum: complaint → response period → panel appointment → decision → registrar implementation.

The complaint is filed electronically through the chosen provider's online portal and must identify the domain, the trademark rights, and the evidence supporting all three Paragraph 4(a) elements. Both WIPO and the Forum conduct a formal compliance review before commencement — a step that catches deficient annexes or missing mark evidence. Once the case commences, the registrant has 20 days to file a response. Silence during that window is a default, but a panel may still examine the record independently rather than simply granting transfer on the complainant's say-so.

After the response period closes, the provider appoints a panelist (or three, if requested). The panel issues a written decision, which is published on the provider's website. If transfer is ordered, the registrar implements it after a brief waiting period — during which the registrant may seek a court stay, though this is rare in practice.

The full cycle from filing to a registrar-implemented transfer typically runs about two months for a single-member panel case without procedural complications. WIPO's expedited option compresses this to approximately one month. Neither forum charges a separate fee for the registrar's implementation step; that is handled as part of the standard process.

In a second recent matter — a .dev typosquat targeting a SaaS company, autumn 2024 — the registrant filed a late response claiming fair use. The panel rejected the claim on the record before it and ordered transfer. The case ran approximately ten weeks from filing, extended slightly by a supplemental filing the respondent requested. The SaaS company recovered the domain without further proceedings.

Can a Respondent Defend a .dev Dispute — and What Is RDNH?

Respondent-side defense in a .dev dispute is viable where the registration is genuine. A developer who registered a .dev domain for an active project, a portfolio investor who held the name before the complainant's mark gained traction, or an individual whose real name or recognized handle matches the domain — each has a path to defeating the complaint under Paragraph 4(c).

The most powerful defense is often a dated record of actual use or demonstrable preparation to use the domain before the complainant sent any notice of dispute. Development logs, GitHub commit history, product roadmap documents, and domain-registration invoices predating the complainant's trademark filings all contribute to a legitimate-interest showing.

Where a complaint is filed against a respondent with clear rights — and the complainant knew or should have known the claim was weak — the panel may issue a Reverse Domain Name Hijacking (RDNH) finding. RDNH means the panel has determined the complaint was brought in bad faith, an attempt to use the UDRP to deprive a legitimate registrant of a domain. The remedy is reputational — the Policy provides no monetary penalty — but RDNH findings are published, and they follow complainants and their counsel. In our practice, we have successfully sought RDNH findings for registrants who held .dev and related gTLD domains against complainants that filed without adequate trademark rights or with no credible bad-faith argument.

We act on both sides of .dev disputes. That means a brand owner consulting us on a complaint and a developer registrant defending one against a larger brand are equally within our scope. The analysis starts from the same place: the record, the dates, and the three elements.

Related at COGNOMEN

• UDRP domain recovery — recovering a domain through a UDRP complaint across all gTLD zones
• Recovering a typosquat .co domain — strategy and evidence for confusingly similar registrations
• ccTLD mediation for .cn disputes — national procedure, eligibility, and cross-zone considerations