How to recover multiple .dev domains in one UDRP complaint

A developer brand discovers that a single registrant has captured a cluster of .dev domains – all confusingly similar to its trademark, all pointing at parked or ad-laden pages, all demanding a price. The registrant holds five, six, perhaps a dozen variants. Filing one complaint at a time would take months and cost a fortune. There is a better path.

Under the UDRP, a single complaint may cover multiple domains provided every domain is registered by the same holder. Google's .dev registry operates under ICANN's accredited-registrar framework, which means the UDRP applies in full. A complainant must still satisfy all three elements of Paragraph 4(a) – confusing similarity, no legitimate interest, and bad faith registration and use – but the forum filing fee is assessed per complaint, not per domain, up to defined band thresholds. At WIPO, a single-member panel covers one to five domains for USD 1,500; six to ten domains cost USD 2,000.

This page covers the consolidation rule, the three-element test as applied in .dev disputes, the evidence that decides outcomes, the cost structure for multi-domain complaints, and the practical next step for a brand owner ready to act.

Does the UDRP apply to .dev domains, and can one complaint cover a cluster?

Yes – .dev is a generic top-level domain launched by Google Registry, and every accredited registrar offering .dev registrations is bound by ICANN's Registrar Accreditation Agreement, which incorporates the UDRP by reference. The same rules that govern .com disputes govern .dev disputes: the Policy, the Rules, and the Supplemental Rules of the chosen provider forum.

The consolidation right is stated directly in the UDRP Rules: a single complaint may relate to multiple domain names, subject to the condition that the disputed domains are registered in the name of the same holder. Panels enforce this strictly. If the WHOIS records – now the RDDS data – show different registrant names or different registrant organizations, consolidation in one filing is not available as of right. A complainant may petition for consolidation on equitable grounds (arguing common control, pattern of registration, or obvious structuring to evade the rule), but that argument is harder and unreliable. The cleanest path is a single registrant, confirmed before filing.

Practically, this matters a great deal for .dev disputes. Technology brands that attract squatters often find the same actor registering a systematic sweep of variations: brandname.dev, brandnameapp.dev, getbrandname.dev, brand-name.dev, and similar. When all are held by one registrant, all can travel in one proceeding – a material efficiency gain on both cost and timeline.

If you have identified a cluster of .dev domains registered by a single holder, COGNOMEN can assess the three UDRP elements, confirm registrant identity across the set, and advise whether consolidation is available before you commit to filing. Contact us at info@cognomenlaw.com.

What are the three UDRP elements a .dev complainant must prove?

Every UDRP complaint – single-domain or multi-domain – must satisfy all three elements of Paragraph 4(a) of the Policy. A failure on any one element means the complaint fails for all domains in the set. The panel does not average results across the portfolio; if even one domain in the complaint survives on a single element, the overall complaint can produce mixed results domain by domain.

Element one: confusing similarity. The complainant must hold rights in a trademark and show that each disputed domain is identical or confusingly similar to that mark. For .dev complaints this step is typically straightforward: the .dev suffix is treated as a technical necessity and largely disregarded, just as .com is disregarded for gTLD disputes. The meaningful comparison is between the second-level string and the mark. Common patterns – the mark plus a generic term ("get", "app", "shop"), or the mark with a character substitution – are routinely found confusingly similar by panels. A registered trademark is the strongest footing, but rights in an unregistered mark can also satisfy this element where secondary meaning is clearly established.

Element two: no rights or legitimate interests. The complainant bears the initial burden of making a prima facie case that the registrant lacks any legitimate basis for the registration. Once that showing is made, the burden shifts to the respondent. Paragraph 4(c) of the Policy provides three safe harbors the respondent can invoke: a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; or legitimate noncommercial or fair use without intent to mislead. In multi-domain complaints, a parking page monetizing traffic across a dozen .dev variants rarely qualifies for any of these defenses.

Element three: bad faith registration and use. This is cumulative – both registration and use must be shown. Paragraph 4(b) enumerates non-exhaustive bad-faith indicators, of which the most relevant in bulk-registration .dev cases are: registration primarily to sell the domain to the mark owner at above cost; registration to disrupt the complainant's business; and attracting users for commercial gain by creating confusion with the complainant's mark. A portfolio of systematically registered .dev variants – especially where the registrant made no use of the names beyond parking – provides strong pattern evidence of bad faith. Panels treat a pattern of abusive registrations as an independent indicator under Paragraph 4(b).

Which forum should you choose for a multi-domain .dev complaint?

For a cluster of .dev domains, WIPO and the Forum are the two realistic choices; together they account for roughly 97% of all UDRP proceedings. CAC offers a lower entry-level fee – beginning around USD 500–800 – but is less frequently used for multi-domain technology-brand disputes, and the body of available panel decisions at WIPO and the Forum is richer for precedent on developer-sector squatting patterns.

At WIPO, the fee bands for a single-member panel are USD 1,500 for one to five domains and USD 2,000 for six to ten domains. A three-member panel doubles the cost: USD 4,000 for up to five domains and USD 5,000 for six to ten. Those are official forum fees only; legal fees for preparing the complaint are separate. If you have more than ten domains in the set, WIPO quotes individually.

The Forum's fees begin around USD 1,300 for one to two domains on a single-member panel and scale from there. For very large clusters, WIPO's documented band structure gives more cost predictability.

The decision matrix in practice looks like this. If you have two to five .dev domains, all held by one registrant, and the bad-faith evidence is clear, a single-member panel at WIPO is usually the most cost-efficient path – fast, well-precedented, and final within approximately two months. If you have six or more domains, the WIPO six-to-ten band captures the full set at USD 2,000 and avoids sequential filings. If the registrant's identity is contested or the case turns on credibility, a three-member panel at the USD 4,000–5,000 level provides the safeguard of a majority decision rather than a single arbitrator's call. If the registrant is also spreading into other zones – say, the same actor holds .com and .dev variants – a combined or parallel complaint covering the common registrant may be possible under WIPO's multi-domain rules.

Court is rarely the first route for .dev disputes unless you require monetary damages or the registrant is beyond the Policy's reach for procedural reasons. A US anticybersquatting action in court is the path that reaches money, handled with local litigation counsel in the relevant jurisdiction; the UDRP itself awards only transfer or cancellation.

What evidence actually decides a multi-domain .dev complaint?

Evidence quality determines outcomes more reliably than the strength of the trademark. A complainant with a well-known mark and weak evidence can lose; a complainant with a modest mark and a tight evidentiary record can prevail. In a multi-domain .dev complaint, the record must cover every domain in the set, not just the most obvious one.

The following categories of evidence carry the most weight in our practice on multi-domain gTLD complaints:

• Trademark registration certificates or, where rights are unregistered, substantial evidence of secondary meaning (press coverage, market data, years of use). The mark must predate at least the earliest disputed registration date.
• RDDS/WHOIS records for each domain, printed at the same moment, confirming identical registrant name, registrant organization, or registrant contact detail. Minor variation in punctuation can be explained, but material differences in registrant identity are a risk to consolidation.
• Screenshots of each domain's resolving content, with metadata (URL bar, timestamp, HTTP header). Parking pages with pay-per-click links on the complainant's own brand are particularly strong bad-faith evidence.
• Registration date data for each domain, showing registration post-dating the mark – or, if the registration is contemporaneous with a publicized product launch, showing the registrant could not plausibly have chosen the name independently.
• Pattern evidence: a table or exhibit listing all the disputed domains side by side, showing the systematic variation from the mark (prefix, suffix, hyphen, character swap). This is the exhibit that makes the bad-faith pattern visible to the panel.
• Communications from the registrant, if any, especially any demand for payment above out-of-pocket registration cost. Such communications are a textbook Paragraph 4(b)(i) indicator and should be preserved in full.

In a recent matter (a .dev cluster dispute involving approximately eight typosquatted variants, spring 2025), we assembled the registrant-identity confirmation and resolving-content evidence for every domain in the set and filed a consolidated complaint. The panel addressed each domain individually in its analysis but applied the same bad-faith finding across the cluster, given the systematic registration pattern. Transfer was ordered for the entire set.

What can defeat a multi-domain complaint? The most common failure modes are: a gap in the RDDS confirmation for one domain (leaving a consolidation crack); evidence of use that could plausibly support a Paragraph 4(c) defense (even a rudimentary development site can complicate the legitimate-interest element); and an incomplete trademark record that does not predate the registrations. We have also seen complaints fail because the complainant filed against seven domains but submitted screenshots for only five.

If you have the domains identified and are ready to assess whether the evidence is sufficient to file, email COGNOMEN at info@cognomenlaw.com. We will read the registrant-identity data and the resolving content before advising on whether a consolidated filing is the right move.

What is the timeline from filing to transfer?

A standard multi-domain UDRP case at WIPO follows the same procedural stages as any UDRP, and the timeline is set by the Rules, not by the parties. The stages are: complaint review and commencement, the 20-day response window, panel appointment, the decision, and registrar implementation of the transfer or cancellation order.

End to end, a straightforward case is typically concluded within approximately two months of filing. WIPO also offers an expedited option – a decision within about one month – available for single-panel cases of up to five domains. For a .dev cluster of two to five domains where speed matters (for example, where the domains are actively redirecting traffic), the expedited path is worth considering at the outset.

What can extend the timeline? A respondent who files a response and requests a three-member panel adds time: panel recruitment takes longer, and the parties generally split the higher three-member fee in that scenario. A request for supplemental filings – granted at the panel's discretion – adds further delay. Default by the respondent (failure to file a response) does not guarantee a faster decision; panels still conduct a full substantive review, but there is no response-side delay and often no need for a three-member panel.

During the proceeding, the domain is typically locked at the registrar – it cannot be transferred to a third party – from the time the complaint commences. That lock is a practical protection while the case is pending. It does not suspend the domain or affect the registrant's technical use of it.

After a transfer order is issued, the registrar implements it within a short window defined by the UDRP Rules, absent an appeal to a competent court by the respondent. A court appeal stays the transfer; this is rare in practice, but the possibility is real for high-value or contested domains.

How does the cost structure work for a multi-domain .dev filing?

The total cost of a multi-domain .dev complaint has two components: the forum filing fee and the legal fee for preparing and managing the complaint. They are entirely separate and should be budgeted separately.

Forum filing fees at WIPO are tiered by domain count and panel composition. For the most common scenario – one to five domains, single-member panel – the WIPO fee is USD 1,500. For six to ten domains on a single-member panel, the fee is USD 2,000. Three-member panels cost USD 4,000 (one to five domains) and USD 5,000 (six to ten). If the complainant selects a single panelist but the respondent requests a three-member panel, the parties generally split the additional cost of the higher-fee composition.

WIPO offers a partial refund – commonly around USD 1,000 of the USD 1,500 fee – if the case is withdrawn or terminated before panel appointment. This is worth noting if a settlement is reached early in the process.

Legal fees for preparing a UDRP complaint – evidence organization, the complaint document itself, ongoing procedural management – typically fall in the USD 3,000–7,000 range for a straightforward single-domain matter in the broader market. A multi-domain complaint with a large evidence set and a complex registrant-identity question will sit toward the higher end of that band or above it, depending on the number of domains and the depth of the record. We quote transparently based on the specific facts before filing.

The efficiency argument for consolidation is clear in cost terms. Five separate single-domain UDRP filings at WIPO cost USD 7,500 in forum fees alone. One consolidated complaint covering those same five domains costs USD 1,500. The legal preparation cost for a consolidated complaint is also lower than preparing five separate filings, because the trademark foundation and the registrant-identity record are built once and applied across the set.

What are the realistic outcomes of a multi-domain .dev UDRP complaint?

The UDRP offers exactly two remedies: transfer of the domain to the complainant, or cancellation of the registration. There are no monetary damages, no costs award, and no injunction. If you need financial compensation for losses caused by the registrant's conduct, a UDRP is not the route; a court action is.

In a multi-domain complaint, the panel evaluates each domain individually against the three-element test, even where the analysis is largely repetitive across the set. A panel may order transfer of some domains and deny transfer of others if the evidence is not equally strong across the cluster. This is another reason why evidence coverage for every domain matters.

RDNH – Reverse Domain Name Hijacking – is a finding available to a respondent panel if the complaint was brought in bad faith to deprive a legitimate registrant of its domain. An RDNH finding carries no financial penalty, but it is a reputational mark against the complainant and the law firm that filed. We assess the RDNH risk as part of the pre-filing review, particularly when a registrant can show prior rights, long use, or a plausible independent basis for the registration. Filing a weak complaint against a multi-domain holder who has a credible story for even one of those domains is a real risk; consolidation amplifies it because the RDNH finding covers the whole complaint.

In a second matter from our practice (a .dev brand-protection filing, autumn 2024), the registrant defaulted on a six-domain complaint. The panel transferred five domains and cancelled one – the sixth domain had been registered before the complainant's trademark filing date, and the panel found the complainant had not established rights predating that registration. The lesson is that each domain's registration date must be checked against the trademark timeline before inclusion in the complaint.

How does a .dev multi-domain complaint compare to other routes?

The audience for this comparison is a brand owner who is deciding whether to file a UDRP, wait for the registrant to use the domains actively, pursue the registrant in court, or simply buy the domains back. Each path has a different cost, timeline, and risk profile.

The UDRP at WIPO or the Forum is typically the fastest and most cost-efficient route to domain transfer where the three elements are clearly met. The two-month timeline and the fixed filing fee make the cost predictable. The limitation is the remedy: transfer or cancellation only, no damages.

Buying the domains back from the registrant avoids a proceeding but rewards the squatter, sets a precedent for further registrations, and typically costs far more than a UDRP filing for a multi-domain set. If the registrant's opening demand is a five-figure sum, a UDRP filing is almost always more economical and more permanent as a resolution.

Waiting is the most dangerous strategy. Passive holding by a registrant – domains parked with no active use – does not defeat the UDRP. Panels have consistently held that passive holding can constitute bad faith use. But waiting gives the registrant time to build a use record that could complicate the legitimate-interest element, and it leaves the domains available for use against the brand in the interim.

Court action – US anticybersquatting litigation, handled with local litigation counsel in the relevant jurisdiction – is available where you need damages or where the registrant operates in a way that places them within a court's personal jurisdiction. It is substantially more expensive and slower than a UDRP proceeding. For pure transfer relief, the UDRP is the standard and the more efficient path.

URS is a separate mechanism available for new gTLDs, including .dev. The remedy is suspension of the domain for the registration term, not transfer, and the evidentiary standard is higher – clear and convincing evidence. For a brand that needs a temporary suspension quickly and at lower cost while building a UDRP record, URS is an option; for permanent transfer of a .dev cluster, a full UDRP complaint is the appropriate vehicle. See our service page on group URS suspension for new gTLDs for more on that parallel route.

For brands managing a wider portfolio across zones, the .dev UDRP may need to be paired with separate filings or monitoring programs for the same registrant's holdings in other gTLDs or ccTLDs. A registrant who systematically squats on .dev may hold the same variations on .com or country-code extensions, each requiring its own forum and its own procedural approach.

Related at COGNOMEN

• UDRP domain recovery: complainant services across gTLDs and ccTLDs
• Alert: recovering phishing domains in the .jp zone
• Group URS suspension: suspending new-gTLD domains at scale

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.