FAQ: choose between URS and UDRP for a .dev domain

When can I choose between URS and UDRP for a .dev domain?

You can bring either a URS or a UDRP complaint over a .dev domain at any time after the domain is registered, provided you hold trademark rights in the disputed name. The choice is yours as the complainant — both procedures are available simultaneously, though you cannot pursue both on the same domain at the same time.

The UDRP has been the standard mechanism since ICANN adopted it in 1999. It applies to all gTLDs, including new gTLDs such as .dev. You file before an ICANN-accredited dispute-resolution provider — WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC — and, if you satisfy all three elements of Paragraph 4(a) of the Policy, the panel orders transfer or cancellation.

The URS was introduced specifically for new gTLDs. Its threshold is higher: you must establish your case by clear and convincing evidence, a standard that is more demanding than the UDRP's balance-of-probabilities approach. In exchange, the URS is faster and carries lower filing fees. The trade-off is the remedy — suspension only, not transfer. Ownership of the domain does not move to you.

So when does one beat the other? If you need the domain itself — to operate it, to build on it, to keep it permanently — the UDRP is the only route that delivers that result. If you simply need the domain taken offline quickly, and your evidence is overwhelming, URS can accomplish that faster. In practice, brand owners with strong, unambiguous rights and a clear cybersquatting fact pattern often find the UDRP worth the additional cost and a slightly longer timeline.

Who can bring a complaint over a .dev domain?

Any person or entity that holds rights in a trademark — registered or, in some circumstances, unregistered — that is identical or confusingly similar to the disputed .dev domain can bring a UDRP complaint. For the URS the eligibility standard is the same, but the evidentiary bar to succeed is higher once you are in.

There is no geographic restriction. A US company, a European brand owner, or an Asian enterprise can all file — WIPO, the Forum, and the other approved providers accept complaints from parties worldwide. What matters is the trademark right, not where the complainant is incorporated or where the domain is used.

One practical note: .dev is HTTPS-only by design, meaning Google Registry enforces HSTS preloading across the entire zone. A .dev domain in a bad actor's hands cannot serve HTTP traffic at all. That technical fact does not affect your legal eligibility to file, but it is relevant evidence of how the domain is actually used — and use matters to the bad-faith analysis under Paragraph 4(a)(iii) of the UDRP.

Respondents — the registrants defending a complaint — should note that eligibility cuts both ways. Paragraph 4(c) of the UDRP lists safe harbors: 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. These defenses are available on a .dev dispute just as on any other gTLD. We regularly advise registrants who hold .dev names for legitimate development projects and face speculative complaints from brand owners who acted too slowly in registering the zone themselves.

Does WIPO or a court decide a .dev dispute?

For both the URS and the UDRP, the decision-maker is a neutral panel appointed by an ICANN-accredited dispute-resolution provider — most often WIPO — not a court. Court involvement is the exception, not the rule, and it operates on a separate track.

Under the UDRP, either party retains the right to take the matter to a court of competent jurisdiction at any time, including after a panel decision. A complainant who loses a UDRP can sue in court. A registrant who loses a UDRP can seek a court order staying the transfer. That court action is entirely separate from the UDRP proceeding and is governed by whatever national law and jurisdiction the parties can invoke — typically in the registrant's jurisdiction or the registrar's jurisdiction, depending on the registration agreement.

For the URS, the post-proceeding options are more limited. A respondent who loses can seek a de novo review before a UDRP panel within a short window after the URS decision. That review can result in a full UDRP proceeding if the respondent has a genuine defense. Courts can also be engaged, but URS decisions are explicitly framed as provisional — the suspension lasts only for the registration term.

What this means practically: the forum for a .dev dispute is almost always WIPO or one of the other approved providers, resolved without litigation. If the facts are contested and ownership is the goal, a UDRP panel — not a URS examiner, and not a court — is the primary decision-maker at the arbitral level. For matters where panel authority is insufficient or where damages are sought, local litigation counsel in the relevant jurisdiction handles court proceedings.

For an assessment of your domain dispute — whether a URS or UDRP complaint is the right move for your .dev domain — contact info@cognomenlaw.com.

What evidence decides the outcome of a .dev domain dispute?

Under the UDRP, the outcome turns on three categories of evidence: proof of trademark rights, absence of any legitimate interest on the respondent's side, and bad-faith registration and use. Each element must be satisfied independently; a strong case on two elements does not rescue a weak one on the third.

For element one — confusing similarity — you need a trademark registration, an application with priority, or, in some circumstances, documented common-law rights predating the domain registration. A .dev domain that copies your mark character-for-character satisfies this element easily. A domain that abbreviates, transposes, or typosquats the mark may require more analysis.

Element two — no legitimate interests — is typically established by showing that the respondent has no trademark, no business commonly known by the name, and no plausible noncommercial use. The burden shifts in practice: once you make out a prima facie case, the respondent must produce something. A parked page, a pay-per-click site, or a domain that has never resolved to any active content will rarely support a legitimate-interest defense.

Element three — bad faith — is where most disputes are actually decided. Paragraph 4(b) lists non-exhaustive indicators: registering to sell the domain back to the mark owner for a profit above out-of-pocket costs; registering to disrupt a competitor; registering to attract users by confusion for commercial gain; and a pattern of abusive registrations across multiple domains. In a recent matter involving a .dev domain (spring 2026), we assembled a record showing the registrant had acquired the name the day after our client announced a product launch in the developer community — circumstantial evidence that panels have consistently found persuasive on the registration-in-bad-faith limb.

For URS, the same elements apply, but the clear-and-convincing standard means the evidence must leave substantially less room for doubt. If the cybersquatting is blatant — same mark, no conceivable defense, immediate monetization — URS works. If any element requires inference or context, UDRP is safer because the panel has more flexibility in its assessment.

What is the deadline once a case starts?

Under the UDRP, a respondent has 20 days to file a response after the case formally commences. Missing that deadline does not automatically mean the complainant wins, but a panel deciding a default case will still examine the complaint on its merits — and without a response, the registrant loses the opportunity to put any defense on the record.

The overall UDRP timeline from filing to decision is roughly 45 to 60 days for a standard single-member panel case, absent extensions or procedural detours. WIPO offers an expedited option for single-panel cases covering up to five domains, targeting a decision in approximately one month. The Forum and other providers run on broadly similar timeframes under the standard process.

For URS proceedings, the timeline is compressed. URS is designed to move faster than the UDRP — that speed is one of its primary selling points. The respondent's window to answer is shorter, and the examiner is expected to render a decision quickly. The trade-off, again, is the limited remedy: a suspension order, not a transfer.

For complainants: filing promptly matters. A .dev domain can redirect traffic, harvest developer credentials, or be sold to a third party in a matter of days. Neither the UDRP nor the URS provides interim injunctive relief — only the decision at the end of the process. If interim protection is essential, a court application for a temporary restraining order through local litigation counsel in the relevant jurisdiction may be necessary alongside, or instead of, the UDRP filing.

For respondents: the 20-day response window is not negotiable unless an extension is granted. In our practice, we have seen registrants miss the response deadline under the mistaken belief that a default would be disregarded. It is not — panels issue decisions on default, and the absence of a response removes the safe-harbor evidence that might otherwise carry the case.

What if the registrant does not respond?

If the registrant fails to submit a response within the prescribed period, the panel proceeds to a decision based on the complaint alone. A default is not an automatic win for the complainant — the panel still applies the three-element test and may deny the complaint if the facts on record do not support it.

In practice, however, default decisions favor the complainant more often than contested ones. The respondent forfeits any safe-harbor argument under Paragraph 4(c) by not appearing. Panels regularly draw adverse inferences from a registrant's silence where the complaint is otherwise well-supported.

That said, a weak complaint will still fail on default. Panels have denied transfer in default cases where the complainant's trademark evidence was thin, where the domain had obvious descriptive or generic meaning, or where the bad-faith record was circumstantial at best. The complaint must stand on its own.

For URS proceedings, a non-response typically results in a suspension if the examiner finds the required elements are met on the face of the complaint. The standard is high, but a default removes the only realistic counter-argument.

Can a URS or UDRP decision over a .dev domain be appealed or challenged?

Neither the URS nor the UDRP has a formal appeal mechanism in the traditional sense — but each offers a distinct path for the losing party to challenge the outcome.

Under the UDRP, either party may take the dispute to a court of competent jurisdiction, either before the decision or within a short window after it. A respondent who receives a transfer order has ten business days before the registrar implements it; filing a court action and notifying the provider within that window will typically stay the transfer pending the court's ruling. This is the mechanism most often used by registrants who believe a panel got the analysis wrong — or who believe the complaint was brought in bad faith and want an RDNH finding that the panel declined to give.

Reverse Domain Name Hijacking (RDNH) — a panel finding that the complainant brought the case in bad faith to strip a legitimate registrant of a domain — is available under both the UDRP and, in some form, the URS. An RDNH finding carries no monetary penalty, but it is a public record and a reputational consequence for the complainant's counsel and the brand. We have defended registrants against speculative UDRP complaints over .dev names and, where the complaint was transparently abusive, sought RDNH findings on the record. See our work on URS and new gTLD disputes and URS vs. UDRP comparison for more on the respondent-side angle.

For URS decisions, a respondent can seek de novo review by a UDRP panel within a defined period after the suspension order. That review is a fresh look under the UDRP standard — including the balance-of-probabilities threshold — and can result in the suspension being lifted if the registrant establishes a legitimate interest. The practical window for this is short; acting immediately on receipt of a URS decision is essential.

What cannot happen: a panel's transfer order cannot be directly "appealed" to WIPO, the Forum, or ICANN. Those institutions administer the procedures; they do not review the merits of individual decisions. The only post-decision paths are the court route, the de novo URS review (for URS cases), or — in theory — a request for a three-member panel reconsideration where the rules permit. For matters where a UDRP panel decision has been issued and enforcement is the question, see our guidance on enforcing a UDRP decision.

To weigh URS against UDRP for your .dev domain, or to build a respondent defense, email info@cognomenlaw.com.