Update: changes affecting how to bring a court action when UDRP cannot reach a .dev domain
A brand owner discovers that its .dev domain – the technical hub for an entire developer product line – has been hijacked or registered in bad faith by a third party. The UDRP offers no relief because .dev is a Google Registry-operated new gTLD that does not participate in UDRP proceedings in the conventional sense. The question becomes urgent: what legal route actually reaches a .dev domain, and has anything changed in how that route works?
When UDRP cannot reach a .dev domain, the operative path is a court action – typically US anticybersquatting litigation – combined with registrar-lock escalation and, where the domain was stolen rather than squatted, a transfer-reversal procedure. Recent practice developments have sharpened the evidentiary threshold registrars apply before accepting a court-ordered transfer, meaning that how you document your claim from day one now materially affects how quickly you recover.
Below: what changed, who is affected, and the concrete steps to take now.
What Changed?
Registrar compliance teams handling .dev transfer orders have raised the documentation bar in recent months. A court order alone – even a US federal order – is now routinely held pending verification of the full chain of title for the domain, the registrant account credentials at the time of the compromise or abusive registration, and confirmation that the receiving party meets the technical requirements for .dev eligibility. Where those documents are missing or inconsistent, registrars are pausing implementation, sometimes for several weeks.
At the same time, Google Registry's TMCH claims-notice and new-gTLD framework for .dev has not been relaxed – it never provided a full arbitral remedy comparable to UDRP. The practical effect is that brand owners who assumed a URS filing or a standard UDRP complaint could recover a .dev domain have sometimes arrived at the court route already behind. Starting with the right route shortens the entire timeline.
Who Is Affected?
Any brand owner or registrant holding rights in a name that is registered as a .dev domain without authorization – or whose .dev registration was compromised through account takeover – needs to assess this update now. The affected group is broader than it might appear.
Developer-tool companies, SaaS brands, and technology vendors are the obvious constituency. But any trademark owner whose mark was registered as a .dev by a third party – including a domain investor holding a .dev for speculative resale – faces the same procedural gap: no UDRP, no quick suspension via URS (which offers suspension but not transfer), and therefore a court action as the primary recovery vehicle. For those whose domain was stolen rather than cybersquatted, the theft-and-hijacking route involves registrar escalation first, but court action may still be required to force compliance.
What Should You Do Now?
The threshold decision is whether the situation is cybersquatting, theft, or both – because the procedural steps differ at the outset, though they converge on court action when registrar escalation stalls.
For cybersquatting: the first step is to document the trademark rights that predate the .dev registration. Registration certificates, use evidence, and priority dates all matter. A US anticybersquatting action requires showing a bad-faith intent to profit – the statutory factors map closely onto the UDRP's Paragraph 4(b) bad-faith indicators, so a UDRP-style evidence assembly is a useful starting point even though the filing is in court.
For domain theft: registrar lock and transfer-reversal mechanics come first. Document the account compromise – authentication logs, unauthorized access timestamps, outbound transfer confirmations – and escalate immediately to the registrar's abuse team. Where the registrar does not act within a commercially reasonable window, a court injunction ordering the registrar to freeze or reverse the transfer is the available lever. In our practice, we have seen registrars respond to a well-documented escalation letter before any court filing was necessary; we have also seen them hold firm until a court order arrived.
In either scenario, the evidence of compromise or bad faith assembled early determines the speed of resolution. Waiting to collect that evidence until after filing costs time that the adversary uses to monetize or further transfer the domain.
For a read on whether a court route or a registrar-escalation path fits your .dev situation, reach us at info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What changed?
Registrar compliance teams now require fuller documentation – chain of title, account compromise evidence, and .dev eligibility confirmation – before implementing court-ordered domain transfers. A court order alone is no longer sufficient to trigger immediate action at the registrar level. This raises the evidential preparation required before and during a court filing.
Who is affected?
Brand owners, technology companies, and SaaS vendors whose marks appear in .dev registrations held by third parties – whether through cybersquatting or account-based theft – are directly affected. Any party that previously assumed the UDRP or URS covered .dev recovery should reassess: neither delivers a transfer for this zone in the way a court order can.
What should you do now?
Audit your .dev registration status and account security immediately. If the domain is squatted, begin assembling trademark priority and bad-faith evidence now. If the domain was stolen, document the compromise and escalate to the registrar without delay. Where escalation stalls, a court injunction is the practical next step. Early evidence collection is the single factor most likely to shorten the overall timeline.
Author: Adrian Harland — Court anticybersquatting and domain theft recovery. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.