Step-by-step: file a UDRP complaint for a .dev domain

Step-by-step: file a UDRP complaint for a .dev domain. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

A developer-focused brand discovers its exact name registered as a .dev by a stranger who has no plausible connection to the technology space and is parking the domain behind a pay-per-click page. The brand wants it back. The first question is whether the UDRP applies to .dev at all – and if so, how to build a complaint that actually wins.

The .dev zone is a generic top-level domain operated by Google Registry under an ICANN-accredited registry agreement, which means the UDRP applies in full. To file a UDRP complaint for a .dev domain you must satisfy all three elements of Paragraph 4(a): identity or confusing similarity to your trademark, absence of any legitimate interest in the registrant, and registration plus use in bad faith. A standard case runs roughly two months from filing, with the registrant allowed 20 days to respond once the proceeding commences. The only remedies are transfer or cancellation – no damages, no costs award.

This guide walks each step in order, names the trap inside each one, and closes with the evidence and the forum choice that tend to decide the outcome.

Step 1: Confirm that the UDRP governs .dev – and choose your forum

Because .dev is a new gTLD launched in 2019 under the ICANN framework, every .dev registrar is contractually bound to the UDRP. There is no separate ccTLD procedure, no national registry rule to check first. The UDRP is the mandatory administrative route.

Four accredited providers accept .dev complaints: WIPO, the Forum, the Czech Arbitration Court (CAC), and the ADNDRC. In practice, WIPO and the Forum handle roughly 97% of all UDRP proceedings. WIPO is the most frequently selected forum and offers an expedited option – a decision within about one month – for single-panel cases covering up to five domains. The Forum's filing fees start around USD 1,300 for one or two domains on a single-member panel; WIPO's standard fee is USD 1,500 for one to five domains, also single-member.

The trap in Step 1 is assuming the procedure is identical to a .com dispute and skipping the eligibility read. It is identical in substance, but each provider has a slightly different filing portal and a compliance review standard that can delay commencement if the complaint is not formatted to that provider's current template. Confirm the current template before drafting.

To weigh UDRP against a court action for your .dev case, email info@cognomenlaw.com.

Step 2: Establish your trademark rights before the complaint is drafted

The first element of Paragraph 4(a) requires you to hold rights in a mark that is identical or confusingly similar to the disputed .dev domain. Panels read this element generously toward complainants, but it is not automatic. You must demonstrate that the mark exists and that you hold it.

A registered trademark is the cleanest proof. A national or regional registration filed before the domain registration date is powerful because it also speaks to bad faith. But panels have consistently held that common-law trademark rights can satisfy this element too, provided the complainant shows acquired distinctiveness through documented commercial use – sales figures, press coverage, industry recognition, customer correspondence.

What is the trap here? Two traps, actually. First, a trademark application that has not yet matured to registration carries significantly less weight than a granted mark. Second, the panel will compare the textual component of the domain name to the mark, stripping the .dev TLD and any obvious filler words. A mark of "TechCo Holdings LLC" claimed against a domain "techco.dev" will read as confusingly similar; a mark of "TC" claimed against the same domain will face harder scrutiny. Align the mark you put in the complaint with the element of the domain name you want the panel to notice.

In our practice, the single most avoidable delay in drafting a .dev complaint is discovering at this stage that the only registered mark is in a goods class with no plausible connection to technology or software services. The registration still works – the Policy does not require the goods/services classes to match – but expect the respondent to argue lack of overlap if they engage at all.

How do you prove the registrant has no legitimate interest in the .dev domain?

The second element of Paragraph 4(a) asks whether the registrant has rights or legitimate interests in the disputed name. Proving a negative is structurally awkward, so the consensus view under the Policy is that the complainant needs only to make a prima facie showing – enough to shift the burden of production to the registrant to come forward with evidence of legitimate interest.

The three safe harbors in Paragraph 4(c) define what a legitimate interest looks like. A registrant who was making a bona fide commercial offering before notice of the dispute, who is commonly known by the name, or who is making legitimate noncommercial or fair use of the domain without intent to mislead – any one of those is a complete defense. Your complaint should engage with each harbor and explain why the evidence does not support any of them for this registrant.

Practical tools: WHOIS or RDDS history (is the registrant a business known by this name?), the current use of the domain (a pay-per-click page offering competitive links is not a bona fide offering), the timing of registration relative to your trademark use (a .dev registration that post-dates your public launch by three months is hard to explain as independent good faith), and any pre-dispute correspondence. If the registrant offered to sell you the domain before you filed, that correspondence is simultaneously evidence of lack of legitimate interest and evidence of bad faith.

The trap: treating this element as a checklist rather than a narrative. Panels in default cases sometimes deny a complaint precisely because the complainant said nothing about legitimate interest beyond a bare assertion. Write one substantive paragraph for each Paragraph 4(c) harbor and explain, from the facts, why it does not apply.

Step 3: Build the bad-faith record – the element that loses most complaints

The third element is where most contested .dev complaints succeed or fail. Paragraph 4(b) of the UDRP lists four non-exhaustive circumstances that constitute bad faith: registration to sell to the mark owner at a price exceeding out-of-pocket costs; registration to block a trademark owner from reflecting its mark (with a pattern of such conduct); registration to disrupt a competitor; and registration to attract users for commercial gain by creating a likelihood of confusion with the complainant's mark.

For .dev domains, the pay-per-click monetization pattern is common. A .dev domain parked with technology or developer-tools links, operated by a registrant with no evident connection to software or development, fits squarely within the fourth circumstance. Document the page content at the time of filing – screenshots with timestamps, archived captures from a web archive service, metadata. Panels give weight to contemporaneous documentation over post-filing snapshots.

The crucial structural point: both registration and use in bad faith must be shown. They are cumulative, not alternative – this is one of the most frequently misunderstood aspects of the UDRP. A domain registered in good faith that later became problematic does not satisfy the element. Conversely, where the respondent has done nothing with the domain – passive holding – panels have consistently held that passive holding can constitute use in bad faith where the circumstances make legitimate use implausible, the mark is well-known, and the registrant provides no explanation.

In a recent matter (a .dev typosquat, spring 2025), we secured a transfer for a software brand whose mark had been incorporated into a .dev domain by a registrant with a documented pattern of registering brand names across multiple new gTLDs. The panel noted that the .dev zone's implicit association with technology and development made the likelihood of confusion more acute, not less. No single factor was dispositive; the pattern evidence was what turned the outcome.

Step 4: Draft and file the complaint – what the form requires

A UDRP complaint is a structured legal document, not a letter. Both WIPO and the Forum publish current model complaint forms that must be followed for the filing to be formally compliant. A non-compliant complaint will be returned for correction before commencement, which delays the clock.

The mandatory content includes: identification of the disputed domain and the registrant (as it appears in RDDS); identification of the complainant and its authorized representative; a statement of the grounds for the complaint addressing all three Paragraph 4(a) elements; specification of the remedy sought (transfer or cancellation); a certification; and the exhibit list. Exhibits should be numbered, paginated, and referenced in the body of the complaint. A panel reading 50 pages of exhibits with no body-text anchor will not hunt for the relevant screenshot.

The trap here is filing length. A 40-page complaint for a single-domain .dev dispute is almost always counterproductive. Panels are experienced practitioners reading multiple cases simultaneously. A tight, evidence-forward complaint of 12–18 pages, organized element by element, is more persuasive than an encyclopedic submission. Say the dispositive facts clearly, cite the evidence in exhibits, and move on.

Filing fee payment must accompany the complaint or follow within the provider's payment window. At WIPO, the USD 1,500 single-member filing fee is due at submission; WIPO offers a partial refund of approximately USD 1,000 if the case is withdrawn or terminated before panel appointment.

For a read on whether the three UDRP elements are met for your .dev domain, reach us at info@cognomenlaw.com.

What happens after filing – and what can go wrong before the decision?

After the complaint is filed, the provider conducts an administrative compliance check. If compliant, it formally commences the proceeding and notifies the registrant. The respondent then has 20 days from commencement to file a response. That window is fixed by the Rules; extensions are rarely granted and require a showing of exceptional circumstances.

If the registrant defaults – files no response – the panel proceeds on the complaint alone. A default is not automatic transfer. The panel still applies the three-element test and may deny the complaint on the merits. We have seen default cases denied because the bad-faith narrative was conclusory. Do not assume the absence of a response equals a win; write the complaint as if it will be contested.

If a response is filed, the panel appointment follows. Either party may request a three-member panel. If the complainant requested a single panelist but the respondent requests a three-member panel, the parties generally split the higher three-member fee – at WIPO that is USD 4,000 for a single-domain case. A well-resourced respondent can use this cost mechanism strategically. Factor that risk into the decision to file at all.

The panel issues a decision, and assuming the complaint succeeds, the registrar implements the transfer within a short post-decision window. From filing to transfer, the process runs roughly two months under standard conditions. WIPO's expedited option can compress that to about one month for eligible cases.

How does a .dev UDRP compare to other routes for the same dispute?

The decision between UDRP and alternatives depends on what you need. If the domain is a .dev and the goal is transfer, the UDRP is the fastest and most cost-contained route. The UDRP filing fee at WIPO starts at USD 1,500; add legal fee preparation costs (typically in the USD 3,000–7,000 range for a straightforward single-domain complaint, separate from the forum fee) and most complainants have a defined total budget before filing.

If the same registrant also holds the matching .com, .net, and .org alongside the .dev, a single UDRP complaint can cover all four domains in one proceeding, provided the registrant of record is the same across all domains. That consolidation can substantially reduce per-domain cost and is worth evaluating before deciding scope.

What if you also want damages? The UDRP cannot award them. No monetary remedy exists under the Policy – not costs, not lost profits, not attorney fees. If damages matter, US anticybersquatting litigation is the only path that reaches money. That route is substantially more expensive and slower than the UDRP, and it requires the infringing registrant to be subject to US jurisdiction. For a .dev domain operated by an overseas party, that jurisdictional question is real. In our practice, we assess the registrant's apparent location early precisely because it determines whether the court route is viable at all, or whether the UDRP is the practical ceiling.

The URS is not relevant here. The Uniform Rapid Suspension remedy applies to new gTLDs, which .dev is, but the URS remedy is suspension for the registration term – not transfer. If you need ownership, the UDRP is the right tool. If you only need the domain taken down quickly under a clear-and-convincing standard, URS may be faster and cheaper. For most brand-recovery situations the UDRP is preferable.

In a second matter we handled (a .dev impersonation, autumn 2024), the brand owner initially considered a court filing because the registrant had also posted defamatory content. We advised filing the UDRP first for the domain itself, while preserving the court option for the content-related claims handled with local litigation counsel. The UDRP proceeded to decision in approximately eight weeks; the domain transferred without any court involvement. Parallel routes require a sequenced strategy, not a simultaneous one.

What evidence actually decides the outcome?

Across the three elements, the evidence that consistently moves panels in .dev disputes falls into a short list. For the first element: the trademark registration certificate or, for common-law rights, a chronological file of commercial use pre-dating the domain registration. For the second element: RDDS records showing the registrant is not known by the name, documentation of the domain's use (or non-use), and the absence of any pre-complaint offering in the relevant sector. For the third element: screenshots of the parked page with technology or developer-related pay-per-click links, a sell-offer communication, or a pattern of similar registrations by the same registrant.

What evidence panels find insufficient: bare assertions ("the registrant clearly registered this in bad faith"), outdated screenshots that postdate the complaint, and second-hand accounts of what the domain looked like without documentary support. The burden of proof is on the complainant, and that burden is met through contemporaneous documentation – not narrative alone.

One frequently missed piece: the domain registration date relative to the first public announcement of your trademark or product. For .dev disputes in the technology sector, brand launches are often well-documented in press releases, GitHub activity, blog posts, and product-hunt listings. That public digital record is useful corroboration that the registrant could not plausibly have registered the domain in ignorance of your mark. Pull it early and attach it.

Related at COGNOMEN

• UDRP Recovery – full-service complaint filing and strategy across gTLDs and ccTLDs
• Domain recovery after a failed buyback or ransom demand
• Domain assignment agreements – how transfer of title works after a UDRP or private deal