How to prove bad faith registration of a .dev domain

How to prove bad faith registration of a .dev domain. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

A developer tool company discovers its product name registered as a .dev by an unknown party who has pointed the domain at a pay-per-click parking page. The registrant has no affiliation with the mark. A five-figure buy-back demand arrives by email within days. The question is immediate: can that .dev be recovered, and what does it take to win?

To prove bad faith registration of a .dev domain under the UDRP, a complainant must satisfy all three elements of Paragraph 4(a): the domain is identical or confusingly similar to a mark the complainant holds; the registrant has no rights or legitimate interests; and the domain was registered and is being used in bad faith. The .dev zone is a new-generic top-level domain whose registrar agreements require compliance with UDRP, so WIPO, the Forum, CAC, and ADNDRC all have jurisdiction. A standard single-member case concludes in roughly two months, with transfer or cancellation as the only available remedies.

This page sets out the legal test, the evidence that decides outcomes, the forum choice, and the practical next step for a brand owner ready to act.

Why .dev domains fall under the UDRP

.dev is a new generic top-level domain operated under the ICANN regime, which means every registrar offering .dev registrations must include UDRP compliance in its registration agreement. That single requirement brings the full Paragraph 4(a) machinery to bear on any abusive .dev registration. WIPO and the Forum together handle roughly 97% of all UDRP proceedings globally and accept .dev complaints without additional eligibility conditions.

There is no separate .dev national procedure. Unlike a ccTLD such as .de or .uk, a .dev dispute does not require recourse to a national court or a country-specific arbitration body. The complainant goes directly to a UDRP provider. That clean access to the UDRP is one reason the .dev zone has become an attractive target for registrants who anticipate ransom or traffic monetization: the zone signals a technology-sector audience, and technology-sector brands often carry strong trademark rights that a resolute bad-faith registrant can exploit for leverage.

If the .dev registration is accompanied by a parallel grab of the brand's .com or .org, a single UDRP complaint may cover all domains held by the same registrant, which can be both more efficient and more compelling on the bad-faith element.

To assess whether your .dev situation meets the three UDRP elements, contact info@cognomenlaw.com.

What are the three UDRP elements you must prove?

All three elements of Paragraph 4(a) are cumulative. A failure on any single element means the complaint fails, even if the other two are overwhelming. Understanding where the dispute actually turns – and in our practice the decisive question is almost always either legitimate interest or bad faith – shapes how you build the file.

Element one: confusing similarity. The domain must be identical or confusingly similar to a mark in which the complainant has rights. For .dev disputes, the panel compares the second-level label (the part before ".dev") to the complainant's mark. The TLD suffix itself is generally disregarded for comparison purposes. Registered trademark rights are the cleanest evidence; unregistered or common-law rights require additional proof of acquired distinctiveness. A complainant whose mark is in the same technology sector as the .dev zone's implied audience has a particularly strong confusing-similarity argument where the label is an exact or near-exact match.

Element two: no rights or legitimate interests. The complainant must show the registrant lacks a legitimate stake. Paragraph 4(c) safe harbors protect a registrant who made a bona fide offering of goods or services before notice of the dispute, who is commonly known by the name, or who is making legitimate noncommercial or fair use. A parking page monetizing the .dev domain rarely qualifies. Neither does holding the name passively with no active development use. The burden shifts in practice: once the complainant makes a prima facie case, the registrant must come forward with evidence of legitimate interest.

Element three: registered and used in bad faith. Both registration and use must be bad faith – the test is conjunctive, not alternative (contrast Nominet's .uk test, which reads "registered OR used"). Paragraph 4(b) provides a non-exhaustive list of circumstances evidencing bad faith: acquiring the domain primarily to sell it to the mark owner at a profit; registering it to disrupt a competitor; using it to attract users for commercial gain through a likelihood of confusion; and a pattern of abusive registrations targeting multiple mark owners. In .dev disputes, a ransom demand, a PPC parking page in the technology space, or a pattern of grabbing developer-brand names are among the most commonly cited bad-faith indicators.

What evidence actually decides a .dev bad-faith dispute?

Evidence is where .dev cases are won or lost. A clean trademark registration certificate is necessary but not sufficient. Panels ask what the registrant knew at the moment of registration – and in the technology sector, a distinctive brand with global web presence and developer community recognition is often the clearest answer to that question.

The following categories of evidence carry weight in UDRP proceedings involving .dev domains:

• Trademark registration records – the certificate, the priority date, and the goods or services description. A registration predating the .dev grab by several years supports the inference that the registrant knew of the mark.
• A direct ransom demand – a buy-back offer at a sum well above registration cost is among the clearest Paragraph 4(b) indicators. Document every communication with timestamps and full headers.
• Screenshots of the live .dev domain – captured with a tool that records the date, the full URL, and the page content. A PPC parking page with links in the complainant's technology category is powerful. A holding page saying "this domain is for sale" is similarly useful.
• WHOIS/RDDS history – registration date, registrant data (even if privacy-shielded), and any transfers. A domain registered the day after the complainant's product launch is difficult to explain innocently.
• Prior abusive registrations – if the same registrant holds other brand-name .dev domains or has been found in bad faith in prior UDRP decisions, that pattern evidence supports Paragraph 4(b)(ii).
• Developer community evidence – press releases, GitHub repository activity, developer conference mentions, or app store listings predating the registration can demonstrate the complainant's mark was well-known in the relevant sector at the time the domain was grabbed.

Evidence of passive holding – where the registrant has done nothing with the .dev domain – can still support bad faith. Panels have consistently held that passive holding combined with a famous or distinctive mark, with no plausible innocent explanation for the registration, satisfies the use-in-bad-faith limb.

In a recent matter (a .dev brand-grab in the developer-tools space, spring 2025), we assembled a file combining a pre-registration product launch record, a documented buy-back demand, and PPC page screenshots. The panel transferred the domain in approximately eight weeks from complaint filing. No extensions were sought.

How does the .dev complaint process work, step by step?

The UDRP process for a .dev complaint moves through five stages, each with fixed time markers set by the Rules – the parties cannot accelerate the registrar-implementation step at the end, but a well-prepared complaint avoids the administrative delays that add weeks to unprepared filings.

1. Complaint drafting and forum selection. The complaint must be complete and formally compliant at first submission. Deficiencies trigger a cure period that delays commencement. Forum selection – WIPO, the Forum, CAC, or ADNDRC – affects the filing fee and, to a lesser degree, panel availability. WIPO's USD 1,500 single-member fee for one to five domains is the published standard rate. The Forum begins at approximately USD 1,300 for one to two domains. CAC offers the lowest entry point for budget-sensitive complainants. All four have jurisdiction over .dev.
2. Commencement and the 20-day response window. Once the provider confirms the complaint is formally complete, it commences the case and notifies the registrant. The registrant then has 20 days to file a response. Non-response (default) does not guarantee transfer; the panel still examines whether all three elements are established on the available record.
3. Panel appointment. For a single-member panel, the provider appoints a panelist from its roster. Either party may request a three-member panel; if the respondent makes that request, the cost is typically shared. A three-member panel adds time and expense but can be tactically appropriate where the complainant's rights are complex or the respondent's defense appears substantial.
4. Decision. The panel issues a written decision. The standard overall timeline from filing to decision is roughly two months, absent procedural complications. WIPO also offers an expedited option targeting approximately one month, available for single-panel cases of up to five domains.
5. Registrar implementation. A transfer order takes effect after a short waiting period during which the registrant may seek court review. The registrar then executes the transfer. Cancellation (rather than transfer) is available where the complainant's only goal is removal of the domain from the registrant.

The timeline is set by the Rules and is largely immune to gamesmanship. What the complainant controls is the quality of the file submitted at step one.

If you have already identified a .dev registrant and have initial evidence in hand, email info@cognomenlaw.com for a structured assessment of the complaint.

Which forum is right for a .dev bad-faith complaint?

The choice of forum for a .dev complaint turns on three variables: cost, panel roster, and the complexity of the fact pattern. In our practice we guide complainants through a straightforward decision matrix.

Where the case is a clean grab with clear bad faith – a ransom demand, a PPC page, a single registrant, strong registered trademark – WIPO or the Forum are the standard choices. WIPO carries the broadest international recognition and the deepest panel pool. The Forum is a credible alternative at a marginally lower entry fee for one or two domains. Either forum reaches a decision in roughly the same window.

Where cost is a priority and the case is relatively uncomplicated, CAC offers the lowest entry point. Less used globally than WIPO or the Forum, CAC nonetheless produces well-reasoned decisions and is a legitimate option for a complainant with a strong factual record who wants to minimize the official filing fee.

Where the .dev registration is one of many – say, a pattern of grabs across .com, .net, .org, and .dev by the same registrant – a single WIPO complaint covering all domains held by that registrant is often the most efficient path. The filing fee scales with domain count but consolidation is more efficient than separate filings.

Where the .dev dispute has a US-based registrant and the complainant also wants monetary damages, UDRP cannot deliver that remedy. Transfer or cancellation is the ceiling. For monetary relief, US anticybersquatting litigation is the only route, handled with local litigation counsel in the relevant jurisdiction. In our practice we assess the cost-benefit of that route against UDRP at the outset, particularly where the ransom demand is large enough to justify the higher cost of court proceedings.

A second recent matter illustrates the cross-zone decision. A technology brand faced .dev and .com grabs by the same registrant, combined with a pattern of similar grabs against three other brands in the same sector. We filed a consolidated WIPO complaint covering all domains. The consolidation argument was accepted; the panel found a pattern of conduct under Paragraph 4(b) and ordered transfer of every domain in the set. The whole matter resolved in approximately ten weeks.

What separates a winning .dev complaint from a losing one?

Panels deny complaints more often than brand owners expect. The most common failure points in .dev bad-faith cases are worth addressing directly because, in our experience, a complaint that loses on the merits could usually have been rebuilt into a winner with better evidence preparation.

The myth that ".dev means developer, so any tech-brand grab is bad faith" is the most costly misunderstanding in this space. The zone's audience does not substitute for evidence. A panel will not presume bad faith from the TLD alone. The complainant must still show, on the record, that the registrant more likely than not knew of the mark at registration and had no plausible legitimate purpose.

Three patterns lead to denial:

• Weak or descriptive mark. If the claimed trademark is a common English word or a generic technical term, the registrant may credibly argue independent interest in the label. A dictionary word registered as a mark for software does not automatically establish confusing similarity in the minds of panels who examine the mark's distinctiveness in context.
• No actual use in bad faith. A parked or undeveloped domain held passively, without evidence that the registrant knew of the complainant's mark or without circumstances pointing to opportunistic registration, is harder to win than a case with a ransom demand or a PPC page targeting the complainant's sector.
• Reverse domain name hijacking risk. Where a complainant files against a registrant with a plausible legitimate interest – a developer who genuinely builds tools under that name, predating the complainant's trademark registration – the panel may find RDNH: a finding that the complaint was brought in bad faith to deprive a legitimate holder. RDNH carries no monetary penalty, but it is a public reputational finding against the complainant. We assess RDNH risk at the pre-filing stage as a standard part of the file review.

The honest pre-filing question is not "can we get this domain?" but "what record supports all three elements, and what can the registrant say in response?" That assessment shapes the complaint, the evidence package, and the forum choice before a single document is filed.

What is the cost structure for a .dev UDRP proceeding?

Cost has two components: the forum filing fee (a published, fixed sum) and the legal fee (variable, dependent on complexity). They are entirely separate and should be budgeted separately.

The WIPO filing fee for a single-member panel covering one to five domains is USD 1,500. A three-member panel at WIPO costs USD 4,000. The Forum begins at approximately USD 1,300 for a single-member panel covering one to two domains. If WIPO is selected and the matter settles before panel appointment, a partial refund of approximately USD 1,000 of the USD 1,500 fee is commonly available.

Legal fees for a straightforward single-domain UDRP complaint – drafting, evidence assembly, and filing – are typically in the USD 3,000 – 7,000 range in the market, separate from the forum filing fee. Complexity factors that push toward the upper end include: multiple domains in the same complaint; a registrant who files a substantive response requiring reply submissions; complex or unregistered trademark rights requiring additional evidence; and multilingual or multi-jurisdiction elements in the evidence record.

Compared to US anticybersquatting litigation, which runs on an hourly basis and routinely reaches five to six figures in legal fees before a judgment, the UDRP is cost-efficient for transfer-only outcomes. The trade-off is that UDRP cannot award damages and cannot enjoin future conduct beyond the domains named in the complaint.

For portfolio-level .dev monitoring – where a brand owner wants systematic alerts on new registrations that match its marks – the cost structure is different again. Brand-protection monitoring provides early warning before a grab matures into a dispute, often at a fraction of the cost of a contested proceeding.

Related at COGNOMEN

• UDRP domain recovery – the full service, gTLD and ccTLD
• Recover a phishing domain in the .ae zone – bad-faith recovery strategy
• Brand-protection monitoring for technology companies – FAQ