How to recover a lapsed .dev domain that was re-registered

How to recover a lapsed .dev domain that was re-registered. UDRP and ccTLD domain recovery and defense across .dev. Email the firm to assess your case.

Your .dev domain lapsed – a missed renewal, a billing failure, a lapsed registrar account – and within days a stranger held it. Now that name anchors your developer portal, your API documentation, or your brand's technical identity, and the new registrant is either parking it or demanding a price you did not expect to pay for something you once owned. The question is whether you can get it back, how quickly, and what the realistic cost looks like.

To recover a lapsed .dev domain that was re-registered, the primary route is a UDRP complaint filed before WIPO, because .dev operates under ICANN's generic top-level domain rules and accepts the UDRP as its dispute-resolution mechanism. You must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark you hold, no legitimate interest in the registrant, and registration and use in bad faith. A standard WIPO case runs roughly two months, with a filing fee of USD 1,500 for a single-member panel covering one to five domains. Transfer and cancellation are the only remedies; no damages are available through this route.

This page covers the legal test, the evidence that decides .dev cases, the forum and fee structure, the cross-zone considerations a brand owner should review, and the realistic next step if you are ready to act.

What makes .dev a gTLD and why that controls the route?

.dev is a generic top-level domain operated under ICANN's new-gTLD program, which means every accredited registrar for .dev is bound by the UDRP. That is the decisive fact for recovery strategy. Unlike a ccTLD – .de, .uk, or .fr – where national procedures and eligibility rules govern disputes, .dev sits squarely within the UDRP's reach. A brand owner who holds a registered trademark, or in many cases a common-law mark with sufficient demonstrated use, can file a complaint at WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC without first establishing any geographic nexus.

That broad access matters when the prior registrant is in a different country from the new holder. The UDRP is forum-neutral and requires no service abroad, no local counsel filing, and no translation of pleadings into the respondent's language. It is also the reason why .dev disputes tend to resolve faster than equivalent national court actions covering the same name.

One caution specific to .dev: Google's registry operates this zone and enforces HTTPS across the entire TLD. The technical profile of .dev sites – developer tools, open-source projects, SaaS portals – often makes bad-faith use fact-patterns slightly different from a generic .com parking page. A respondent holding a .dev and posting code snippets, or running a developer forum under a slightly different project name, may argue a legitimate interest more colorably than a registrant who simply parked the domain. That is a reason to assess the specific fact pattern before filing.

What does the UDRP test require in a lapsed-domain scenario?

The UDRP's three-element test under Paragraph 4(a) applies identically to lapsed domains as to any other disputed registration – but the lapsed-domain context changes which facts are easy and which are contested.

The first element – confusing similarity to a trademark – is typically the least difficult. If the domain matches or closely tracks your registered mark or your prior domain name, panels consistently find similarity. Your prior ownership of the exact name is strong corroborating context, but it does not substitute for trademark rights. You must have a mark: registered, or common-law where panels accept them.

The second element – no legitimate interest – is where lapsed-domain cases diverge. A new registrant who acquired the domain at drop-catch, parked it, or pointed it at a pay-per-click page almost certainly lacks any legitimate interest. A registrant who is genuinely known by the name, or who began a bona fide project before notice of the dispute, may have a colorable defense under Paragraph 4(c). In our practice, we routinely encounter registrants who argue that a lapsed domain is, by definition, fair game, and that the prior owner's failure to renew breaks any chain of legitimate ownership. Panels do not generally accept that framing – but the new registrant's conduct after acquisition remains the controlling factor.

The third element – registration and use in bad faith – is the most contested in lapsed-domain cases. The key word is and: both limbs must be proved. Registration in bad faith typically means the registrant knew of your mark when they acquired the domain. Evidence: the mark's fame or registration predating the drop, the proximity of the domain to the mark, any communications about a buy-back, and the registration price paid relative to the domain's generic value. Use in bad faith includes parking with click-through revenue, redirection to a competitor, or passive holding where the circumstances as a whole point to opportunistic acquisition. Panels have consistently held that passive holding can constitute bad faith use where no plausible legitimate purpose exists.

If you are still weighing whether the three elements are met on your facts, reach us at info@cognomenlaw.com for a structured assessment before any filing commitment.

How strong is a lapsed-domain bad-faith argument at WIPO?

The lapsed-domain scenario sits in a genuinely contested area of UDRP jurisprudence. Panels take different positions on how much weight to give the prior owner's history – and understanding that split is essential before committing to a filing.

The majority view, which is reflected in the WIPO Jurisprudential Overview, is that prior ownership of a domain is relevant but not determinative. What matters is whether the new registrant targeted your mark. If the drop-catcher monitored the expiry and registered immediately after deletion, specifically because the name carried value derived from your brand, bad faith at registration can be established. Drop-catch services that operate systematically across hundreds of lapsing domains are not, in that framing, innocent acquirers; panels have examined the registrant's portfolio and business model as part of the bad-faith inquiry.

The minority view gives more weight to the free market in expired domains. Some panels reason that a registration made without actual knowledge of the complainant's mark – or where the mark is not particularly famous – may not satisfy the bad-faith-at-registration limb even if post-registration use is opportunistic. A complainant in that scenario can still win on the use limb if the registrant subsequently adopted conduct that exploited the mark, but the argument is more demanding.

What decides the outcome, in our experience, is the specificity of the targeting. A registrant who acquired one .dev matching your brand name is in a worse position than a registrant who acquired fifty generic or developer-themed domains in the same week. The narrower the registration, the cleaner the inference of targeting.

A second contested point in lapsed-domain cases: some respondents raise a procedural argument that the prior owner's loss of the domain breaks any trademark-derived rights. Panels have consistently rejected that argument where the complainant still holds the underlying mark. The UDRP protects trademark rights, not ownership of a specific domain registration.

Which forum should you choose – and does it matter for .dev?

WIPO and the Forum together handle roughly 97% of all UDRP proceedings. For a .dev dispute, either is available and technically capable. The choice turns on cost, speed, panel culture, and your specific evidence profile.

WIPO offers an expedited option for single-panel cases covering up to five domains, delivering a decision in roughly one month rather than the standard two. If time is the primary concern – you are losing customer traffic or developer trust while the domain is held by a stranger – that expedited path may justify the preference for WIPO. The standard WIPO filing fee is USD 1,500 for a single-member panel covering one to five domains, rising to USD 4,000 for a three-member panel in the same range.

The Forum's entry-level fee for one to two domains begins around USD 1,300, making it marginally less expensive for a straightforward single-domain case. CAC starts lower still – around USD 500–800 – though it is the least used of the four accredited providers and panel depth for .dev-specific cases may be thinner. ADNDRC starts around USD 1,300 for one to two domains and is most commonly chosen when both parties have an Asia-Pacific connection.

A practical note on panel selection: if you anticipate a contested response and the bad-faith argument is at the margin, consider requesting a three-member panel from the outset. Three panelists reduce the variance in outcome in close cases. The cost – USD 4,000 at WIPO for one to five domains – is substantially less than the legal cost of relitigating a lost single-panelist case. If you request a single panelist but the respondent requests a three-member panel, the parties generally split the higher three-member fee.

What evidence decides a .dev lapsed-domain recovery?

Evidence in a lapsed-domain UDRP complaint falls into three groups: rights evidence, targeting evidence, and conduct evidence. Building a strong record in all three groups is what separates a complaint that transfers the domain from one that stalls or loses on the bad-faith element.

Rights evidence means your trademark: a registration certificate, the goods and services class, and the registration date relative to the domain's drop date. If you rely on common-law rights, you need demonstrated use in commerce – revenue figures, user counts, or media references that predate the lapse – because panels examining common-law claims apply genuine scrutiny. Your prior registration history of the exact .dev domain is corroborating but not a substitute for a mark.

Targeting evidence is the fact-pattern that shows the new registrant chose your domain because of your brand. Useful exhibits: screenshots of the registrant's landing page (parking ads, references to developer tools, links to competitors), the timing and price of the drop-catch relative to the expiry date, WHOIS or RDDS records showing rapid post-drop registration, and any communications from the registrant or a broker naming a sale price. A demand for five figures on a domain that cost registration-fee-level to drop-catch is itself a bad-faith indicator under Paragraph 4(b).

Conduct evidence covers what happened after registration. Pay-per-click revenue from developer-related search traffic, redirection to a competing product, or simply sitting on the domain in silence while the complainant's brand remains active – all of these support the use-in-bad-faith limb. Passive holding is viable in .dev disputes where no plausible alternate use exists.

A practical point on RDDS and chain of title: before filing, run a full registration history on the domain. A domain that has changed hands more than once since the drop may have a more complex fact pattern. If the current registrant acquired it from the drop-catcher through a secondary market transaction, that is not necessarily a defense – panels look at the state of knowledge at the time of the current registrant's acquisition – but it does change what you need to prove about targeting at registration.

If a prior filing did not produce a transfer, or if you received a complaint and need to assess your options, email info@cognomenlaw.com – a second review of the record often surfaces the element that was thin the first time.

What is the realistic cost structure for a .dev UDRP recovery?

The cost of a .dev domain recovery through the UDRP has two distinct components: the forum's filing fee and the legal fee for preparing and filing the complaint. They are always separate, and conflating them is the most common source of cost surprise for brand owners who have not run a UDRP before.

Forum filing fees are fixed and published. WIPO charges USD 1,500 for a single-member panel on one to five domains. The Forum's comparable rate begins around USD 1,300. If you file and then withdraw before panel appointment – for instance, because the registrant agrees to transfer during the response period – WIPO commonly refunds approximately USD 1,000 of the USD 1,500 fee.

Legal fees for a straightforward single-domain UDRP complaint – one registered mark, clear parking conduct, no prior dispute history on the domain – typically fall in the USD 3,000–7,000 range in the market, separate from the forum fee. The range reflects the complexity of the bad-faith argument, the volume of exhibits required, and whether a reply submission is needed. Lapsed-domain cases where the bad-faith argument requires documentary reconstruction of the drop-catch timeline will sit toward the upper end of that range.

If the matter cannot be resolved by UDRP – because the complainant lacks trademark rights, because the registrant has a genuine legitimate interest, or because the bad-faith element cannot be established on the available facts – the alternative routes carry substantially higher costs. A US anticybersquatting action in court is the path that reaches monetary damages, but it is hourly-fee litigation with a significantly longer timeline. If the new registrant is in a jurisdiction where no UDRP or court route is practicable, negotiated acquisition is the remaining option; that is a domain purchase transaction, not a dispute, and the cost is whatever the registrant will accept plus transaction and escrow costs.

What if the UDRP route is not available or is unlikely to succeed?

Not every lapsed-.dev situation supports a UDRP complaint. The test is demanding: you need trademark rights, you need to prove no legitimate interest, and you need to prove bad faith at registration and in use. If any of those three elements is genuinely weak, filing creates a risk of an RDNH finding – a panel declaration that the complaint was brought in bad faith to deprive a legitimate registrant. An RDNH finding is a reputational consequence with no monetary penalty, but it goes on the public record and complicates any future action against the same respondent.

Where the UDRP route is unavailable or unlikely, consider these alternatives. First, negotiated acquisition: if the registrant is willing to sell and the price is acceptable relative to the domain's value to your business, a structured purchase with proper escrow is a cleaner resolution than contested litigation. We handle domain purchase, sale, and escrow and can run the transaction with chain-of-title verification included.

Second, pre-acquisition due diligence if you are considering purchasing the domain from the new registrant: the domain may carry a prior dispute history that survives the transfer. A domain that was the subject of a prior UDRP proceeding – particularly one where the respondent's legitimate interest was questionable – can be difficult to hold cleanly. We review domain due diligence, including prior dispute records, to flag tainted domains before a client commits to a purchase price.

Third, court action: in the United States, anticybersquatting litigation is available where the domain was registered with a bad-faith intent to profit from a mark. Unlike the UDRP, a court action can award damages and attorneys' fees and reaches registrants who have deliberately evaded arbitration. The costs are substantially higher than a UDRP proceeding and the timeline is measured in months or years rather than weeks. For a .dev domain with significant commercial value and a registrant whose conduct is egregious, it may be the right path.

A worked example: in a matter we handled (a .dev domain, early 2025, a SaaS brand owner in the developer-tools sector), the registrant had acquired the lapsing domain and immediately pointed it at a competing product's affiliate page. The trademark registration predated the drop by several years. We filed at WIPO, chose the single-member panel, and secured a transfer order within approximately eight weeks of filing. No supplemental submissions were required; the targeting was clear from the initial registration timing and the affiliate redirect.

A second example illustrates the limits. In a different engagement (a .dev domain, summer 2025, an open-source project owner relying on common-law rights), the registrant was a developer who had independently built a tool under a similar name before ever encountering the complainant's project. The common-law mark evidence was thin, and the registrant had GitHub activity predating the drop. We advised the client against filing and assisted with a negotiated acquisition instead. The domain transferred by escrow within three weeks at a price the client considered fair, with no RDNH risk on the record.

Cross-zone considerations: what if the same name is registered in other TLDs?

A lapsed .dev domain rarely exists in isolation. The same name may be live in .com, .io, .app, or a national ccTLD – each under a different registrant or the same bad actor who captured multiple drops simultaneously.

The UDRP allows a single complaint to cover multiple domains where the registrant is the same holder. If the same entity holds your lapsed .dev and the corresponding .com, a consolidated complaint at WIPO can address both in a single proceeding at the single-domain filing fee tier if the total is within five domains on a single-member panel. That consolidation saves both time and forum fees and simplifies the bad-faith argument by showing a pattern of registrations – which is itself a Paragraph 4(b) factor.

Where the multi-zone registrant has distributed holdings across different registrant names – a common tactic – the UDRP's single-proceeding rule does not apply. Each registrant must be addressed separately. However, evidence of coordination across accounts can still support the bad-faith finding in each individual case.

If the corresponding ccTLD – say, a national .dev equivalent or a related country code – is registered by the same actor, the governing national procedure applies. .de sits entirely outside the UDRP and requires a German court action, with a DENIC DISPUTE entry available to block transfer during litigation. .uk is handled under Nominet's DRS, which uses an "abusive registration" test rather than the UDRP's cumulative bad-faith requirement. .eu disputes go through ADR.eu, where the remedy may be transfer or revocation depending on the complainant's EU eligibility. For any zone not listed here, confirm the current registry rules with counsel before assuming the UDRP or any single procedure applies.

A cross-zone check is standard in our pre-filing review. We run the WHOIS / RDDS data on all related domains before recommending a filing strategy, because the zone determines both the procedure and the cost structure of the full recovery effort. For the cross-zone picture, see our analysis of UDRP versus national procedures in practice.

Related at COGNOMEN

• Domain purchase, sale, escrow, and brand-protection monitoring – the full transactions practice
• AI-assisted domain due diligence – prior disputes, chain of title, and tainted-domain risk
• UDRP versus national procedures – a comparative case analysis across zones