How to choose between URS and UDRP for a .dev domain

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

A developer-tools company discovers that its registered brand name has been registered as a .dev domain by a third party who had no involvement in building it. The domain points at a pay-per-click parking page. The brand owner wants it gone – fast. Two administrative routes are available under ICANN's rules: the Uniform Rapid Suspension procedure (URS) and the Uniform Domain Name Dispute Resolution Policy (UDRP). Knowing which one to file, and when, can mean the difference between a suspension that expires and a permanent transfer.

For a .dev domain, both the URS and the UDRP are available as administrative remedies, because .dev is a new generic top-level domain subject to ICANN's full dispute-resolution framework. The core difference is the remedy: the URS suspends a domain for the remaining registration term, while the UDRP transfers ownership permanently. The URS applies a clear-and-convincing evidentiary standard, which is higher than the UDRP's preponderance-based approach. If you want the domain back and in your name, the UDRP is almost always the right choice; the URS is the right tool when you need speed and suspension will fully neutralize the harm.

This page explains the applicable rules in .dev, the exact mechanics of each procedure, the evidence that decides the outcome, the cost structure, and the decision logic that tells a brand owner or registrant which route to file – or whether to file at all.

Why does .dev fall under both URS and UDRP?

.dev is a new gTLD operated by Google Registry LLC, delegated during the ICANN new-gTLD program, and as such it is subject to the full suite of ICANN-mandated dispute procedures. Every accredited registrar offering .dev registrations must, as a condition of ICANN accreditation, comply with both the UDRP and the URS. That means a brand owner whose mark appears in a .dev registration can choose either mechanism – or, in some fact patterns, run them in sequence.

This is meaningfully different from the position under a country-code TLD such as .uk or .de. A .uk dispute goes to the Nominet DRS and a .de dispute goes to the German courts. Neither the URS nor the UDRP applies by default. In .dev, by contrast, the complainant has genuine optionality. The choice is not procedural formality. It determines the available remedy, the evidentiary burden, and the timeline.

One practical note: because .dev is a gTLD, the relevant forum will be WIPO, the Forum (formerly the National Arbitration Forum), or the Czech Arbitration Court (CAC), all of which administer UDRP proceedings. The URS is administered by WIPO and the Forum for new-gTLD domains. Filing a complaint under either procedure requires identifying the correct forum at the outset, and the choice of forum within the UDRP affects cost and average decision time.

If you are ready to assess whether the URS or the UDRP is the right route for your .dev situation, contact us at info@cognomenlaw.com. We assess the three UDRP elements, review your trademark record, and identify the filing strategy that matches what you actually need.

What does the URS actually do in a .dev dispute – and when is suspension enough?

The URS suspends a .dev domain for the remainder of its registration term. It does not transfer the domain to the complainant. When the registration expires, the domain re-enters the pool and becomes available again – unless a renewal is also blocked, which URS decisions do address. Suspension means the domain stops resolving, the parking page goes dark, and the registrant loses use of the name. But the registrant keeps formal ownership of the registration until it lapses.

The URS also applies a higher evidentiary standard than the UDRP. The complainant must prove each of the three elements (confusing similarity, no legitimate interest, bad faith) by clear and convincing evidence, not merely on the balance of probabilities. In practice, this means a URS complaint requires a stronger, cleaner fact pattern. A heavily documented cybersquatting situation – a domain that is letter-for-letter your registered trademark, held by someone with no plausible connection to it, pointing at advertising links in a directly competing field – will meet that bar. A more ambiguous case, with some colorable argument from the registrant, likely will not.

When is suspension enough? Consider a situation in which a brand owner's .dev domain is actively directing traffic to a phishing page mimicking the brand's developer portal. The harm is immediate and reputational; the brand owner does not need to own the domain, it needs the domain offline, quickly. URS achieves that. It is also a lower-cost procedure in terms of official fees, and decisions typically issue faster than in a standard UDRP. For a brand owner facing an acute, clear-cut infringement where transfer is not the priority, URS is a rational first step.

In a matter we handled in late 2024, a software company identified a .dev domain that was a letter-for-letter copy of its registered trademark, used to serve advertising links targeting its own customer base. We advised URS rather than UDRP: the evidence was unambiguous, suspension was all the client needed, and speed was the primary concern. The domain was suspended within weeks without a contested response.

When should you file a UDRP instead – and what does the UDRP require for a .dev domain?

The UDRP requires proof of all three elements under Paragraph 4(a): the domain is identical or confusingly similar to a trademark in which the complainant has rights; the registrant has no rights or legitimate interests in the domain; and the domain was registered and is being used in bad faith. That final element is cumulative – both registration in bad faith and use in bad faith must be shown. A domain registered in bad faith but now used neutrally raises a harder argument.

The key advantage over URS is the remedy. A successful UDRP complaint results in transfer of the domain to the complainant. That is a permanent resolution. The complainant owns the .dev domain going forward, can deploy it, develop it, and control its future. No expiry, no re-registration risk, no need to monitor whether the registrant renews. If recovering the domain for active use is the goal, the UDRP is the right tool.

The standard is also lower. The UDRP does not require clear-and-convincing evidence; a panel weighs the record on a balance, assessing whether the complainant's case is more probable than not. That means cases with a stronger registrant-side argument – where the registrant can point to some legitimate interest or some pre-registration use – can still succeed for the complainant where a URS might fail.

Paragraph 4(b) of the UDRP sets out non-exhaustive bad-faith circumstances relevant to a .dev dispute: registration primarily to sell the domain to the mark owner at a profit; registration to disrupt a competitor's business; registration to attract users by creating confusion with the complainant's mark for commercial gain; or a pattern of abusive registrations. In .dev disputes, the "commercial gain through confusion" ground is particularly apt where a domain resolves to advertising links or impersonates a developer-facing product.

Paragraph 4(c) safe harbors protect a registrant who can show a bona fide offering of goods or services before any notice of the dispute, common knowledge by the domain name, or legitimate noncommercial or fair use. A registrant who is a genuine developer using a descriptive .dev name for an actual development project has a real argument under Paragraph 4(c). That argument may not defeat a URS, but it certainly changes the UDRP calculus.

If you have already received a notice of complaint – whether URS or UDRP – and need to assess whether a response or an RDNH filing is appropriate, email info@cognomenlaw.com. We build the legitimate-interest record, document good-faith registration, and where the facts support it, seek a finding of reverse domain name hijacking.

How does the decision matrix work – which route fits your situation?

The right route depends on what you need and how clean your fact pattern is. Here is the decision logic in plain terms.

If you need the domain permanently transferred to you, and you hold a registered trademark that clearly corresponds to the domain, file the UDRP. The WIPO filing fee starts at USD 1,500 for a single-member panel covering one to five domains. A standard case resolves in approximately two months. The complainant bears the cost; the respondent bears no filing fee but pays for counsel if represented.

If you need the domain suspended quickly – because active harm is occurring right now and ownership matters less than neutralization – the URS is a viable alternative, subject to the higher evidentiary bar. Official URS fees are lower than UDRP fees, and the timeline is faster. But if the registrant files a response, the evidentiary standard demands a stronger record, and you cannot get a transfer even if you win.

If the .dev domain is one of many in an abusive campaign – a portfolio of typosquats or variations across new gTLDs – the UDRP allows a single complaint to cover multiple domains where the same registrant holds them. That efficiency argues for UDRP in multi-domain situations.

If the registrant's interest is genuinely ambiguous – if there is a plausible legitimate interest argument that the registrant could raise – the UDRP's lower standard is more favorable to the complainant. The URS, with its clear-and-convincing threshold, may fail on the same facts that would succeed in a UDRP.

And if you are the registrant facing a complaint, the two procedures impose different response burdens. A URS response must be filed within 14 days; a UDRP response is due within 20 days of commencement. The UDRP allows a more developed factual record and a better opportunity to build a legitimate-interest defense or an RDNH argument. Respondents who believe they hold the domain in good faith should almost always engage in the UDRP, and should carefully evaluate whether the complaint itself qualifies as reverse domain name hijacking – a finding available under the UDRP where the complaint is filed to deprive a legitimate registrant of their domain.

There is also a sequencing option. Some brand owners file URS first, obtain a suspension, and then file UDRP to secure the transfer. That path makes sense where immediate neutralization is urgent and the registrant's conduct is clear. We can advise whether that sequence fits your specific .dev situation.

What evidence decides the outcome in a .dev proceeding?

Evidence in a .dev dispute follows the same structure for both URS and UDRP, but the weight required differs. For the first element – confusing similarity – the complainant must produce proof of trademark rights. A registered trademark is the cleanest evidence; a national registration predating the .dev registration is ideal. Unregistered common-law rights require evidence of secondary meaning and commercial use, which requires more documentation. A .dev domain that is letter-for-letter the trademark satisfies the similarity threshold readily; a domain that adds a generic word requires more argument.

For the second element – no legitimate interest – the complainant must make a prima facie showing, after which the burden shifts to the registrant. Panels consistently treat a lack of any known connection between the registrant and the trademark as sufficient prima facie evidence. What matters most at this stage is the registrant's use of the domain: a parking page, a pay-per-click landing page, or a site that mimics the complainant's developer tools all cut against legitimate interest. A .dev domain pointed at an active, independent development project is a harder case for the complainant.

For the third element – bad faith – the most probative evidence in .dev disputes tends to be: the composition of the domain itself (is it the trademark, nothing else?); the timing of registration relative to the complainant's mark and public profile; the content at the URL (advertising, competitor links, or a demand for payment); and any communications in which the registrant offered to sell the domain at a price exceeding registration costs. Panels have consistently held that passive holding of a domain that is identical to a well-known mark can itself constitute bad faith use, even where the domain does not actively resolve to a problematic page.

In a UDRP matter we managed in spring 2025, a .dev registration of a software brand's exact trademark was held by a registrant who had never made any use of it. The domain had been parked for over a year. We assembled the trademark registration history, the brand's development community presence, and WHOIS data showing registration had occurred shortly after the brand's public product launch. The panel transferred the domain on all three elements without needing evidence of an explicit sale demand.

What does a .dev proceeding cost, and how are fees structured?

Forum filing fees and legal fees are separate, and understanding the distinction matters at the outset. The forum filing fee goes to the administering institution; the legal fee goes to counsel. The two are independent. Filing without counsel is possible under both procedures, but doing so – particularly in a contested UDRP – materially increases the risk of an adverse outcome or, for a complainant, an RDNH finding where the complaint was assembled without sufficient care.

For the UDRP at WIPO, the filing fee is USD 1,500 for one to five domains with a single-member panel. A three-member panel costs USD 4,000. If the complaint covers six to ten domains, the single-member fee rises to USD 2,000. WIPO offers an expedited option for single-panel cases of up to five domains, typically resolving in about one month, which can be valuable in active-harm situations. If the case settles or is withdrawn before panel appointment, WIPO typically refunds approximately USD 1,000 of the filing fee. The Forum's fees begin around USD 1,300 for one to two domains. CAC is the lowest-cost option, with fees beginning around USD 500–800.

URS official fees are lower than UDRP fees, which makes the URS superficially attractive on cost alone. But cost is not the primary variable. If the goal is transfer and the fact pattern supports UDRP, filing URS to save on official fees and then having to file UDRP anyway costs more in total – in fees and in delay – than filing UDRP from the start.

Legal fees in the market for a UDRP complaint covering a single, straightforward .dev domain typically fall in a range of approximately USD 3,000 to USD 7,000, separate from the forum fee. That range is fact-dependent and driven by complexity, the number of domains, whether a response is filed, and whether the case proceeds to panel or settles. We publish our pricing approach openly rather than requiring a call to get a number.

For a brand owner running a portfolio of developer-facing domains across multiple new gTLDs, a single UDRP filing covering all registrations by the same bad actor is more cost-efficient than multiple URS filings. That portfolio dimension is worth raising in any initial assessment.

How does the .dev zone compare to other gTLDs and ccTLDs for dispute purposes?

The procedural comparison across zones is one of the questions we most commonly work through with clients who have a brand registration across several TLDs simultaneously.

For other new gTLDs – .io, .app, .cloud, .ai, .tech – the same UDRP and URS framework applies. The choice logic described above transfers directly. Where .dev is distinctive is in its operator – Google Registry – and in the developer community that uses it, which means some registrants have credible legitimate-interest arguments grounded in genuine technical use. A domain that adds ".dev" to a project name may be genuinely in use as a developer testing environment. That fact pattern is more common in .dev than in, say, .biz or .info, and it sharpens the need for a careful evidence review before filing.

For a .com version of the same brand, the UDRP applies but not the URS – the URS is exclusive to new gTLDs. If the brand owns dispute rights in a .com and a .dev simultaneously, a multi-domain UDRP naming both under the same registrant is possible and efficient. The Forum and WIPO both administer mixed-TLD complaints where the respondent is the same entity.

For a .uk or .eu registration, neither the UDRP nor the URS applies. A .uk dispute would proceed under the Nominet DRS, which uses a different "abusive registration" test and includes a free mediation stage before any expert decision. A .eu dispute would go to the ADR.eu platform at the Czech Arbitration Court. Both are distinct from the ICANN framework and require separate filings, separate counsel analysis, and a separate assessment of the governing test. If you face a multi-zone infringement – .dev plus .uk plus .eu – the most efficient approach is a coordinated strategy that assigns the correct procedure to each zone, rather than treating them as a single undifferentiated filing.

For a .de registration, there is no administrative procedure equivalent to the UDRP. That dispute belongs in the German courts, and DENIC's dispute-entry mechanism can block transfer while the matter is litigated. Cross-border coordination with local litigation counsel in the relevant jurisdiction is required.

The practical upshot: the .dev zone is comparatively straightforward for a brand owner with clear trademark rights, because the full ICANN toolkit applies and the zone is English-language and global. The difficulty lies not in the procedure but in the evidence and in the registrant's possible legitimate-interest defense.

Related at COGNOMEN

• URS and new gTLD disputes – the full service overview across all new gTLD zones
• TMCH claims notice in .dev – what the notice means and how to respond
• ccTLD mediation procedures – how national dispute rules differ from ICANN procedures