How to act on a .dev domain flagged by a Trademark Clearinghouse claim

How to act on a .dev domain flagged by a Trademark Clearinghouse claim. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your c…

A .dev registration triggers a Trademark Clearinghouse (TMCH) claims notice, and suddenly a brand owner must decide: acknowledge the notice and move on, or escalate to a formal dispute procedure? For registrants on the receiving end, the notice itself feels like a legal threat. Both readings miss the point. The notice is a disclosure mechanism, not a decision – what happens next depends entirely on evidence and procedure.

When a .dev domain is flagged by a Trademark Clearinghouse claim, the governing dispute procedures are the Uniform Rapid Suspension system (URS) and the UDRP, both administered through WIPO for new gTLDs including .dev. The URS delivers a suspension of the domain for the remainder of the registration term – not a transfer of ownership – under a clear-and-convincing evidentiary standard. The UDRP, which carries a higher filing fee starting at USD 1,500 at WIPO, can deliver an outright transfer. The right route depends on what the brand owner actually needs.

This page covers the .dev procedural landscape, the legal tests under URS and UDRP, the evidence that decides outcomes, and how to assess which route fits your situation.

What does a Trademark Clearinghouse claims notice actually mean for .dev?

A TMCH claims notice in .dev signals that a registered trademark in the Clearinghouse database matches or closely resembles the string being registered. The notice does not block the registration. It informs the registrant that a trademark exists and requires an acknowledgment before the registration can complete. For brand owners watching the Clearinghouse feed, a claims period notification confirms that someone is attempting to register a domain that matches their mark – after the notice window, the claim may be raised through a formal dispute.

The .dev zone is operated by Google Registry and runs under ICANN's standard new-gTLD framework. That means the URS and the UDRP both apply as dispute mechanisms. .dev is also a technical zone – registrations are limited to developers and require HTTPS – which shapes the realistic universe of registrants. In our practice, a TMCH notice in a technical zone like .dev more often involves a deliberate registration by a party who knows the mark than an innocent collision with a common word.

Does the notice itself create any obligation on the brand owner? No. The claims notice period is a rights-protection mechanism at the registry level. If the registrant proceeds despite the notice, they cannot later claim ignorance of the trademark. That acknowledgment is useful evidence if a dispute follows. It does not, however, guarantee a win under either procedure – the substantive tests still apply.

How do the URS and the UDRP differ when you act on a .dev domain flagged by a Trademark Clearinghouse claim?

The URS and the UDRP share a common legal ancestry but deliver different remedies and operate under different evidentiary thresholds. Choosing the wrong route wastes time and filing fees; choosing the right one depends on what you are trying to achieve.

Under the URS, a complainant must show: (1) the domain is identical or confusingly similar to a mark in the Clearinghouse; (2) the registrant has no legitimate interest; and (3) the domain was registered and is being used in bad faith. The standard of proof is clear and convincing evidence – a higher bar than the balance-of-probabilities approach that operates informally under the UDRP. The remedy if the complainant succeeds is suspension for the registration term: the domain resolves to a holding page, and the registrant loses operational control, but ownership does not transfer to the complainant. URS fees are lower than UDRP fees, and the process is faster.

Under the UDRP at WIPO, the same three elements apply but the evidentiary standard is effectively a balance of probabilities, and the available remedies include an outright transfer of the domain to the complainant. A standard case is normally decided within about two months. If a brand owner wants to own the domain – not merely take it offline – the UDRP is the correct route.

A practical comparison: if the .dev domain is being used for active phishing, a URS suspension can disrupt the harm quickly. If the domain is a parked page with a buy-back offer, a UDRP complaint is more appropriate because the brand owner can acquire the name. We regularly advise clients to consider both in sequence when the situation involves ongoing consumer harm and a long-term ownership goal.

The procedure above is the standard path. Your mark, your evidence, and the registrant's conduct decide which route fits your situation. For an assessment of your domain dispute, contact info@cognomenlaw.com.

What does the legal test require under each procedure?

Both the URS and the UDRP require the complainant to satisfy all three elements before any remedy is granted. Each element has established panel reasoning behind it, and weakness on any single element defeats the complaint.

Element one: identical or confusingly similar. For a TMCH-flagged .dev domain, this element is often straightforward – the claims notice itself confirms a match in the Clearinghouse. The comparison strips the TLD (.dev) and applies the remaining string to the mark. Typosquats – transpositions, added hyphens, extra characters – are generally treated as confusingly similar under the consensus approach. The mark must be one in which the complainant holds rights: a registered trademark or, in many panels' view, a sufficiently established unregistered mark. In .dev, registrations that exactly replicate a registered mark are the clearest cases.

Element two: no rights or legitimate interests. The complainant makes a prima facie case; the burden shifts. The registrant may invoke the safe harbors in Paragraph 4(c) of the UDRP: a bona fide offering of goods or services before notice; being commonly known by the name; or legitimate noncommercial or fair use. In .dev, a developer who registered a domain for a genuine open-source project using a common descriptive term can build a credible legitimate-interest record. A registrant holding a parked page or a pay-per-click redirect will struggle.

Element three: registered and used in bad faith. This is cumulative under the UDRP – both limbs must be met. The Paragraph 4(b) factors are illustrative: registration to sell back to the mark owner at above cost; a pattern of abusive registrations; using the domain to disrupt the complainant's business; or attracting users for commercial gain through confusion. The TMCH acknowledgment at registration is strong evidence of knowledge – a registrant who acknowledged the claims notice and registered anyway will find it difficult to argue they did not know the mark existed.

In a recent matter – a .dev typosquat targeting a software company, spring 2025 – we assembled the bad-faith record around the TMCH acknowledgment, the parking-page PPC revenue, and a prior transfer demand from the registrant. The panel found all three elements met. The case resolved by transfer within the standard UDRP window.

Which forum should you file with for a .dev dispute?

WIPO is the primary forum for .dev disputes under both the URS and the UDRP. Google Registry designates WIPO as its approved dispute-resolution provider, making WIPO the natural starting point for both procedures. The Forum (formerly the National Arbitration Forum) is also an ICANN-accredited UDRP provider for new gTLDs, with filing fees beginning around USD 1,300 for one or two domains under a single-member panel.

What drives the forum choice? WIPO's caseload in the new-gTLD space is the largest, its decisions are publicly searchable, and its panelist pool is deep in technology-sector marks – relevant for .dev. In 2025, WIPO administered a record 6,282 domain-name cases, a figure that reflects both its market position and the breadth of its panel experience. For a high-value brand dispute in .dev, WIPO's institutional familiarity with the technology sector matters.

Filing a three-member panel at WIPO costs USD 4,000, compared to USD 1,500 for a single-member panel. Where the registrant's bad faith is clear-cut and the mark is registered, a single-member panel is usually sufficient. Where the registrant is likely to mount a legitimate-interest defense – for example, a developer claiming prior use of the string in an open-source project – a three-member panel reduces the risk of an idiosyncratic decision.

Cross-zone consideration: if the same registrant holds both the .dev domain and a matching .com, a single UDRP complaint can cover multiple domains in the same filing, provided the registrant is the same holder. That consolidation keeps costs proportionate and delivers a single decision on the evidence.

If a prior filing produced an unfavorable outcome or you are weighing URS against a UDRP complaint, a focused second read often finds the element that was under-built. Email info@cognomenlaw.com to discuss.

What evidence decides the outcome of a .dev Trademark Clearinghouse dispute?

Evidence is the core of any domain dispute. The legal test is fixed; the facts that satisfy it are not. A complaint with clean legal analysis but thin evidence will lose; a complaint with strong, well-organized evidence frequently succeeds even against a contested defense.

For the first element, the evidence stack is: a current trademark registration certificate (or, for unregistered marks, sales data, press coverage, and market use evidence establishing acquired distinctiveness), plus a side-by-side comparison of the mark and the domain string. The TMCH claims notice itself is supporting evidence but not a substitute for a registration certificate.

For the second element, a clean WHOIS/RDDS record showing no prior association of the registrant with the mark is standard. Screen captures of the domain resolving to a parking page, a redirect, or a phishing page are the most common exhibits. A developer claiming legitimate interest will typically present GitHub repositories, commit histories, or user-facing product documentation predating the dispute notice.

For bad faith, the TMCH acknowledgment is uniquely powerful in the new-gTLD context. Unlike a .com registrant who might claim ignorance of a mark, a .dev registrant who cleared the TMCH claims process has confirmed in writing that they saw the trademark notice. That acknowledgment, combined with a parking page or a buy-back demand, is a strong bad-faith package.

What about passive holding? Panels have consistently held that passive holding – a domain resolving to a blank page with no active use – can still constitute bad faith where the mark is well-known and no plausible legitimate use is conceivable. In .dev, a domain that does nothing is harder to explain as a development project. That asymmetry favors the complainant on the passive-holding question.

We have built bad-faith records around a combination of: the TMCH acknowledgment, reverse-WHOIS data showing the registrant's prior domain history, archived screenshots from the Wayback Machine, and where relevant, email evidence of a solicitation to sell. Each element of evidence maps to a specific legal conclusion; the complaint is organized to make that mapping explicit.

What does a .dev URS or UDRP complaint cost, and how do fees split?

Fees in a domain dispute break into two distinct categories: the official forum filing fee, and the legal fee for drafting and filing the complaint. These are always separate. Conflating them is one of the most common sources of confusion when a brand owner first explores the process.

At WIPO, the filing fee for a UDRP complaint covering one to five .dev domains under a single-member panel is USD 1,500. A three-member panel for the same number of domains costs USD 4,000. If the complainant requests a single panelist but the respondent requests three, the parties generally split the higher three-member fee. WIPO also offers a partial refund – commonly around USD 1,000 of the USD 1,500 fee – if the case is withdrawn or settled before panel appointment. For the Forum, the single-member filing fee starts at approximately USD 1,300 for one or two domains.

Legal fees for preparing a UDRP complaint on a straightforward single domain typically fall in a range commonly cited in the market as USD 3,000 to USD 7,000, separate from the filing fee. URS proceedings carry lower official fees and, given the streamlined nature of the process, often carry proportionally lower legal fees as well. More complex matters – multiple domains, a contested respondent defense, or a case requiring cross-zone coordination – will run higher.

The COGNOMEN approach to fees is straightforward: we publish ranges rather than requiring a separate call to get a number. For an assessment of your .dev dispute and a fee indication for your situation, contact info@cognomenlaw.com.

When is court action the right alternative to URS or UDRP for a .dev domain?

URS and UDRP are the standard routes for .dev disputes, but neither is always sufficient. Two situations push a brand owner toward court.

First, if monetary damages are required – for example, where the .dev domain was used to divert sales or to conduct phishing that caused measurable losses – neither the URS nor the UDRP can award them. Both procedures deliver only transfer or suspension. US anticybersquatting litigation is the only path that reaches money, and that route is handled with local litigation counsel in the relevant jurisdiction.

Second, if an injunction is needed before a UDRP decision can be obtained – typically where the domain is being used in an active fraud campaign and a two-month window is too long – a court can grant interim relief that the arbitral procedures cannot. The UDRP registrar lock provides some protection during the pendency of a filed complaint, but it is not an injunction and does not address harm already occurring at the domain.

In our practice, we assess whether the registrant's conduct crosses the threshold where arbitral relief is structurally insufficient. Most .dev TMCH situations do not reach that point. When they do, coordinating the UDRP filing with parallel court action requires careful timing to avoid conflicting orders.

What is the respondent's position when a .dev TMCH claim escalates?

Not every .dev domain flagged by a TMCH claim is registered in bad faith. Legitimate registrants – developers who built a genuine product on a string that happens to match a trademark, open-source project contributors, or businesses that adopted a name independently – face complaints that are factually contested or, in some cases, abusive.

A respondent in a .dev UDRP or URS has 20 days to file a response after the case commences. That window is short. Evidence of legitimate interest must be assembled quickly: development histories, registration rationale documentation, business correspondence, and any prior use of the name before the complainant's trademark priority date.

Where a complaint is filed by a brand owner with no plausible trademark claim over the specific string, or where the complainant's mark postdates the registration, panels are prepared to find Reverse Domain Name Hijacking (RDNH). An RDNH finding is a formal conclusion that the complaint was brought in bad faith to deprive a legitimate registrant. The finding carries no financial penalty under the UDRP, but it is publicly recorded in the WIPO decision database and is a reputational consequence the complainant's counsel should not overlook.

We handle respondent-side defense in .dev and other new-gTLD disputes with the same structure as a complaint: element-by-element analysis, a clear legitimate-interest record, and where the facts warrant, an affirmative RDNH argument. In a recent matter – a .dev dispute, autumn 2024 – we successfully defended a developer who had built a genuine product on the contested string, securing a denial and an RDNH finding against a complainant who had acquired its trademark after the domain registration date.

Related at COGNOMEN

• URS and new-gTLD dispute services – full practice overview for generic top-level domain disputes
• How to suspend a domain under the URS in tech zones – step-by-step filing guide
• ccTLD transfer remedies – how country-code procedures compare to new-gTLD routes