FAQ: recover a lapsed .dev domain that was re-registered

When can I recover a lapsed .dev domain that was re-registered?

Recovery is available when the three UDRP elements are met – a trademark right, no legitimate registrant interest, and bad-faith registration and use. A lapse alone does not justify transfer. The timing of the re-registration and the registrant's conduct are central to the bad-faith analysis.

The fact that you previously held the domain does not, by itself, establish a right to reclaim it. What matters is whether you hold a trademark – registered or, in some cases, unregistered – that the domain infringes. If the name corresponds to a mark you have used in commerce, that is the starting point.

What happens after the lapse matters too. Did the new registrant park the domain with pay-per-click ads targeting your sector? Did the domain redirect to a competitor? Did the registrant contact you to sell the name at a premium? Each of those scenarios feeds into Paragraph 4(b) bad-faith analysis. Mere re-registration of a dropped name, with no evidence of targeting, is a harder case – but not always an impossible one.

We regularly advise developers and brand teams who discover a lapsed domain in a third party's hands within weeks of the drop. Speed matters: the more quickly you document the registrant's conduct, the stronger the evidentiary record for a complaint.

Who can recover a lapsed .dev domain that was re-registered for a .dev domain?

Any person or entity with trademark rights in a name confusingly similar to the disputed .dev domain may file a UDRP complaint. Unlike some ccTLD procedures, the UDRP imposes no geographic or industry eligibility requirement on the complainant.

The trademark right can be a registered mark in any jurisdiction, or – where well-established – an unregistered common-law mark built through actual use. Brand owners, software companies, open-source foundations, and individual developers who have commercialized a product name under a recognizable mark all potentially qualify as complainants.

One important nuance: the complainant's trademark rights must predate the disputed registration, or at minimum, the registrant must have had those rights in mind when acquiring the domain. A mark registered after a good-faith re-registration by a third party does not retroactively create UDRP grounds.

Before filing, a chain-of-title and prior-dispute history check is essential. If the domain carried a prior UDRP complaint – even one that was withdrawn – that history is visible and may affect both strategy and panel perception. Our case study on verifying chain of title illustrates why that due diligence step cannot be skipped.

What is the deadline once a case starts?

Once WIPO formally commences the proceeding, the respondent has 20 days to file a response. Missing that deadline does not result in automatic transfer – the panel still reviews the complaint on its merits – but a default significantly limits the respondent's ability to present evidence.

For the complainant, timing is about filing quality, not speed. The complaint itself has no external deadline beyond any applicable statute of limitations in parallel court proceedings. That said, delay allows the registrant to build a more substantial use record, which complicates the legitimate-interest element. Filing promptly, with complete evidence, is almost always preferable to filing quickly with a thin record.

A standard WIPO case is typically decided within about two months of filing. WIPO also offers an expedited option, delivering a decision within approximately one month, available for single-panel cases covering up to five domains.

Does WIPO or a court decide a .dev dispute?

WIPO is the primary forum for .dev UDRP disputes, but a court action remains available as a parallel or alternative route. The two tracks are not mutually exclusive in all scenarios, though commencing a court action after a UDRP complaint may affect the arbitration proceeding.

For most .dev disputes, the UDRP at WIPO is the fastest and most cost-effective route. The filing fee is USD 1,500 for a single domain with a single-member panel. A three-member panel costs USD 4,000. Those are forum fees only; legal fees are separate and vary by case complexity.

Court becomes relevant when the complainant also wants monetary damages – the UDRP awards none – or when the facts raise questions the Policy cannot resolve, such as contract claims or competing trademark rights that require evidentiary hearings. In those situations, US anticybersquatting litigation may run alongside or instead of the UDRP. We work with local litigation counsel in the relevant jurisdiction for any court-based recovery action.

The decision matrix in practice: if you want the domain transferred and that is the primary goal, the UDRP is almost always the right starting point. If the registrant's conduct caused quantifiable harm and you want compensation, a court action is a necessary addition. If the name also appears in a .com or other gTLD, those registrations each require a separate complaint or action, because a single UDRP complaint can cover multiple domains only when the registrant is the same holder across all registrations.

What if the registrant does not respond?

A registrant's failure to respond – a "default" – does not mean the complainant wins automatically. The panel must still find that the complaint establishes all three UDRP elements. However, the panel may draw reasonable inferences from the default, and complainants with strong evidence routinely prevail in uncontested cases.

In our practice, defaults occur more frequently than contested responses. That does not mean cases are simple. A panel reviewing a default complaint still scrutinizes the trademark evidence, the similarity analysis, and the bad-faith record. A thin complaint filed in haste, assuming the other side will not appear, can result in a denial – or, in more egregious cases, a finding of Reverse Domain Name Hijacking (RDNH) against the complainant, even without a respondent present to argue it.

If you receive a UDRP complaint and are considering whether to respond, the 20-day window is short. Failing to respond waives the opportunity to present legitimate-interest evidence, rebuttal evidence on bad faith, and – critically – any RDNH argument. The reputational impact of an RDNH finding falls entirely on the complainant; it carries no monetary penalty but is publicly published and indexed.

Can the decision be appealed or challenged?

A UDRP decision is not directly appealable within the UDRP system. However, either party may challenge the outcome in a court of competent jurisdiction, typically within a short post-decision window before the registrar implements any transfer.

When a transfer is ordered, the registrar typically imposes a brief implementation hold. That window is the respondent's last opportunity to seek a court injunction staying the transfer. If no court challenge is filed in time, the registrar proceeds with the transfer.

Courts in several jurisdictions have reviewed and reversed UDRP outcomes – usually on grounds that the panel misapplied the elements or that new evidence not available during the proceeding is now determinative. This route is substantially more expensive and slower than the original arbitration. It is a realistic option primarily when the domain has significant commercial value that justifies the litigation cost.

Complainants can also face judicial challenge if the respondent files first. We have defended registrants in post-UDRP court proceedings, building on the same legitimate-interest record assembled for the original response. If you are a registrant who received an adverse panel decision, an assessment of the decision's reasoning – and whether it reflects a genuine legal error – is the first step before committing to court action.

What evidence decides a .dev recovery case?

Trademark registration certificates, prior registration history for the domain, and evidence of the registrant's post-acquisition conduct are the three categories that most directly determine the outcome of a .dev UDRP complaint.

For similarity: screenshots of the domain as it was used during the complainant's prior ownership are helpful context, though the similarity analysis focuses on the text of the mark versus the domain string, not on design or trade dress.

For legitimate interest: check what the registrant has done with the domain since re-registration. A blank page, a parking page with ads, or a redirect to a competitor all favor the complainant. An actual development project or content genuinely related to the domain's dictionary or industry meaning can support a registrant's defense.

For bad faith: timing is powerful evidence. A re-registration within days of the drop, particularly where the name is not a common word, strongly suggests the registrant knew whose name it was. A buy-back solicitation – "I noticed this domain dropped; I'd consider offers" – is close to dispositive. Document every contact and preserve the domain's DNS and content history through screenshots and archive captures.

Chain-of-title and prior dispute history should be checked before filing. A domain that was the subject of a prior UDRP proceeding – especially one where the complainant prevailed – signals to a panel that the current holder acquired with knowledge. Conversely, a prior case where the UDRP was denied weakens the current complainant's bad-faith argument unless the facts have materially changed. Our cloud-sector chain-of-title case study shows how that history can reshape an otherwise straightforward complaint.

If you are weighing whether the three UDRP elements are met for your .dev domain, reach us at info@cognomenlaw.com for an initial assessment.