Case study: act on a .dev domain flagged by a Trademark Clearinghouse…

Case study: act on a .dev domain flagged by a Trademark Clearinghouse. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your ca…

A software company's brand appears in a .dev registration it does not own. The Trademark Clearinghouse (TMCH) has already flagged the domain during the claims period, sending a notice to the registrant that a matching mark exists. The registrant proceeded anyway. Now the brand owner wants the domain transferred — and wants to know whether the URS or the UDRP is the right tool to get there.

When a registrant ignores a TMCH claims notice and registers a .dev domain that matches a trademark, the brand owner has two primary routes: the Uniform Rapid Suspension system (URS), which can suspend the domain within the registration term at a lower cost but cannot transfer ownership, or a UDRP complaint at WIPO, which can order a transfer but requires satisfying all three elements of Paragraph 4(a). For .dev — a gTLD operated by Google Registry — the UDRP applies in full. The claims notice itself becomes a significant piece of bad-faith evidence.

This case study walks the situation, the strategy chosen, and the outcome — anonymized, with no real names or case numbers.

The Situation: a Developer-Facing Brand in a Developer Zone

In autumn 2025, a mid-sized US software company discovered that a third party had registered a .dev domain combining the company's registered mark with a generic software term. The registration had occurred during the .dev claims period — meaning the registrant had received, reviewed, and affirmatively acknowledged a TMCH claims notice before completing the registration. The domain resolved to a parking page displaying pay-per-click links that targeted the company's own product category.

The company's trademark had been registered for several years. The mark was well recognized in the developer community — precisely the audience that .dev domains are designed to reach. This mattered: .dev enforces HTTPS by default and carries strong association with software products and services. A parked page in that zone, bearing a confusingly similar name, created a real risk of consumer confusion and diverted developer traffic.

The company had not authorized the registration, had no prior relationship with the registrant, and had not received any buy-back demand — yet. The audience pain here is real: a brand owner in a technical zone faces a registrant who, by acknowledging the claims notice, knowingly assumed the risk that the registration might be abusive. That acknowledgment is not innocuous. It is documentary evidence of awareness.

The Strategy: Why We Chose UDRP Over URS

The instinct for many brand owners receiving a TMCH flag is to pursue the URS first, because it is faster and cheaper. That instinct is understandable but not always right. The URS remedy is suspension only — the domain is taken offline for the remainder of its registration term, then returns to the registrant. No transfer occurs. For a brand owner that wants the domain pointed at its own site, or that needs to prevent re-registration after the term expires, the URS delivers an incomplete result.

The URS also applies a clear and convincing evidence standard — meaningfully higher than the UDRP's preponderance model. In practice, a panel applying that standard will require compelling, unambiguous proof on each element. Where the factual record is strong, that bar is meetable. Where any element carries nuance — a descriptive term, a shared phrase, a registrant with any colorable claim — the margin for error is narrow.

In this matter, we assessed the record and concluded that a UDRP complaint at WIPO was the correct route. Three factors drove that conclusion. First, the brand owner's goal was transfer, not suspension — only the UDRP delivers that. Second, the TMCH claims notice acknowledgment, combined with the pay-per-click parking page, produced a clear and documented bad-faith pattern consistent with Paragraph 4(b) of the Policy: registering a confusingly similar domain to attract users for commercial gain by creating a likelihood of confusion with the complainant's mark. Third, the mark was distinctive and long-established, making element one straightforward.

We assembled the complaint to address each of the three UDRP elements in sequence. On similarity: the domain combined the company's registered mark with a generic term; panels have consistently held that adding a descriptive suffix does not dispel confusing similarity. On legitimate interest: the registrant had no known connection to the mark, no bona fide offering under the domain, and no plausible fair-use basis. On bad faith: the parking page content, the TMCH acknowledgment, and the zone-audience overlap (a developer-targeted domain used to capture traffic from a software brand's customers) all pointed in one direction.

If you have received a TMCH claims notice flag, or discovered a .dev registration that mirrors your mark, the choice between URS and UDRP turns on your goal and your evidence. For an assessment of your domain dispute, contact info@cognomenlaw.com.

The Outcome: Transfer Ordered

The WIPO panel transferred the domain. The registrant did not file a response — a default that panels do not treat as automatic proof of the complainant's case, but which, combined with the affirmative evidence on record, left no competing account of legitimate interest. The TMCH claims notice acknowledgment received explicit attention in the analysis: the panel noted that proceeding with registration after receiving notice of a matching trademark is a recognized indicator of bad-faith intent under the Policy.

The entire proceeding ran approximately nine weeks from filing to transfer implementation — consistent with the standard UDRP timeline, which typically completes within about two months. The company now holds the .dev domain and has it redirected to its product page.

A common misconception in this area is that a TMCH flag alone resolves the dispute. It does not. The flag triggers a notice mechanism; it does not block the registration or guarantee a complaint succeeds. The brand owner still bears the burden of proving all three UDRP elements. What the acknowledgment does is make bad-faith registration substantially easier to demonstrate — the registrant cannot claim ignorance of the mark's existence.

If a prior filing or response produced an incomplete result, a focused second read can identify the element that was missed. To discuss next steps, email info@cognomenlaw.com.

Related at COGNOMEN

• URS and new gTLD disputes — when to file and which forum to use
• Acting on a TMCH claims notice for a .org domain registration
• Defending a domain registered before the complainant's trademark existed