Step-by-step: recover a lapsed .cloud domain that was re-registered

Step-by-step: recover a lapsed .cloud domain that was re-registered. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your ca…

Your brand's .cloud domain expired — a billing lapse, an administrative gap, a registrar notification that never arrived. Within days, a third party picked it up. Now it resolves to a pay-per-click page or a competitor's storefront, and the new registrant wants five figures to walk away. The question is whether you can get it back, and what the fastest, cleanest path looks like.

To recover a lapsed .cloud domain that was re-registered by a third party, the standard route is a UDRP complaint before WIPO, which administers disputes for .cloud under the standard three-element test: confusing similarity to your trademark, no legitimate interest in the registrant, and registration and use in bad faith. A WIPO case typically resolves in about two months, with a filing fee starting at USD 1,500 for a single-member panel on one domain. The only remedies are transfer or cancellation — there is no damages award.

This guide walks every step, flags the trap each one conceals, and closes with the evidence and the realistic next step for a .cloud recovery.

Step 1: Confirm that .cloud uses the UDRP — and what that means for your case

The .cloud registry has adopted the UDRP, making WIPO the natural dispute-resolution forum for this zone. That means the full Policy and its procedural Rules apply, including the 20-day response window available to the registrant after a case commences. It also means the standard WIPO filing fee of USD 1,500 for a single-member panel covers one to five domains.

Why does the zone matter? Some new gTLDs use the URS — a suspension-only mechanism with a higher evidentiary standard — rather than the full UDRP. The .cloud registry is not in that category. A successful UDRP complaint here can result in an outright transfer, not merely a temporary suspension. That distinction is worth confirming before you invest in preparation.

The trap in this step: assuming the procedure is identical to .com practice without verifying the current registry rules. Registry policies occasionally change. We always check the current registry agreement with ICANN and the relevant WIPO supplemental rules before filing a .cloud complaint, because an overlooked amendment can affect eligibility or the remedies available.

Step 2: Audit your trademark rights — the first UDRP element

The first element of Paragraph 4(a) of the UDRP requires that the disputed domain be identical or confusingly similar to a trademark in which you hold rights. This is typically the easiest element to satisfy, but it harbors a specific trap for lapsed-domain situations: your trademark must still be alive and valid at the time you file the complaint.

Run a thorough rights audit before any other step. Confirm that your registered trademark is current, not cancelled, not abandoned, and not under challenge. If your mark lapsed around the same time as the domain, the weakness is compounded. Common-law rights — established through genuine use rather than registration — can support a UDRP complaint, but the evidentiary burden is heavier and the standard of proof more demanding. In our practice, we see complaints fail at this first element not because the brand lacks value, but because the trademark record had not been maintained.

Also check whether the domain is precisely identical to your mark or carries a variation — a prefix, a suffix, or a typo. Confusing similarity is a low bar under the UDRP, but "identity" and "confusing similarity" call for different evidence. The .cloud TLD suffix is disregarded in the comparison, so yourbrand.cloud is typically treated as identical to the mark YOURBRAND. Document that comparison clearly in your evidence file.

How does the "lapsed" history affect the bad-faith analysis?

A domain that lapsed and was re-registered by a third party creates a nuanced bad-faith question. Panels have consistently held that a registrant who acquires a lapsed domain with constructive or actual knowledge of the prior owner's trademark rights can be found to have registered in bad faith — even though the registrant did not target the prior owner from scratch. The critical inquiry is what the new registrant knew, or should have known, at the time of acquisition.

Evidence of knowledge typically includes: the trademark's registration or visibility in the relevant market, prior use of the domain in connection with the brand, WHOIS history showing the prior ownership, and the registrant's subsequent conduct — particularly parking the domain on a pay-per-click page that monetizes user confusion, or offering to sell the domain to the brand owner for a price far exceeding registration costs.

The trap here is assuming that a lapsed domain is automatically a "clean slate" for the new registrant. It is not. Panels have also declined to find bad faith where the new registrant acquired a common-word domain that happened to coincide with a trademark and used it for a genuinely unrelated purpose. Your ability to demonstrate that the registrant targeted your brand — rather than coincidentally held a common word — is frequently the factor that decides a .cloud recovery case. We regularly advise clients to build the targeting evidence first, before investing in filing fees.

If you are weighing whether the bad-faith element is met in your .cloud situation, email info@cognomenlaw.com for an assessment of the three UDRP elements against your specific facts.

Step 3: Run a chain-of-title and prior-dispute history check

Before filing — and even before deciding whether to pursue the UDRP — run a complete chain-of-title check on the disputed domain. This step is often skipped by complainants eager to file quickly. Skipping it is a mistake. It can also save you from the costlier mistake of pursuing a domain that carries hidden problems.

What to check:

• WHOIS and RDDS history — current and historical registrant data, including registrar, registration date, and any recorded transfers.
• Prior UDRP or URS decisions — the WIPO case database and the Forum's published decisions are searchable by domain name. If the domain has been through a prior complaint that resulted in a finding for or against the current registrant, that history is directly relevant to your filing.
• Whether a prior complaint resulted in a Reverse Domain Name Hijacking (RDNH) finding against a previous complainant — an RDNH finding by a prior panel signals that a prior attempt to claim this domain was itself found abusive. It does not bar your complaint, but it signals the need for stronger evidence and a more precisely scoped argument.
• Any trademark opposition or cancellation proceeding touching the underlying mark.

The trap: discovering after filing that a previous UDRP complaint on the same domain produced an adverse decision that the registrant's defense counsel will deploy against you. Panels do not treat prior decisions as binding, but they are persuasive. A prior panel finding that the registrant has a legitimate interest substantially complicates a second complaint on identical facts. Know the history before you commit to the filing.

Step 4: Decide between WIPO, the Forum, and the alternative of direct purchase

Once you have confirmed the legal basis and the factual record, the route decision comes next. Three realistic paths exist for a .cloud domain dispute, and the right one depends on your evidence, your urgency, and the registrant's profile.

Path A — WIPO UDRP complaint. The standard route. Filing fee of USD 1,500 for a single-member panel on one to five domains. A decision typically within about two months. If the evidence is strong across all three elements, this is almost always the most cost-effective path. WIPO handles roughly half of all UDRP volume and has deep .cloud and new-gTLD experience.

Path B — The Forum UDRP complaint. The Forum is the second major provider, with a filing fee beginning around USD 1,300 for one to two domains and a single-member panel. Timeline and procedural rules are substantially similar. The choice between WIPO and the Forum is often a matter of counsel preference, panel-pool familiarity, and sometimes strategic considerations about the specific case.

Path C — Negotiated purchase. If the registrant acquired the domain opportunistically but is not a professional monetizer or a direct competitor, a negotiated purchase through a structured escrow can sometimes close faster than two months and at lower total cost than combined legal and filing fees. This path is viable only if the registrant is responsive, the price is realistic, and the domain has not been heavily used in a way that could damage your brand during the negotiation period.

What should rule out the purchase path? Any sign of deliberate targeting — a demand to the brand owner, pay-per-click pages keyed to your brand's search terms, or evidence that the registrant registered multiple domains matching your trademark family. In those situations, the UDRP is the cleaner route and the evidence will support it.

There is no court route for .cloud in the way there is for, say, .de (where DENIC disputes are resolved through German courts). A US anticybersquatting action remains available in principle for any gTLD domain, but it is substantially more expensive and time-consuming than the UDRP, and is worth considering only where damages are also sought or where the UDRP is unavailable for procedural reasons.

Step 5: Assemble the evidence file — what decides the outcome

The outcome of a UDRP complaint turns on the evidence more than on the procedural choices. A well-chosen forum with a weak evidence file loses. A straightforward forum choice with a complete, well-organized evidence file usually wins.

The evidence file for a .cloud lapsed-domain recovery should include:

• Trademark certificates and prosecution history — certificates of registration, the filing date (pre-dating the disputed domain registration), and any renewals confirming current validity.
• Historical domain-use evidence — screenshots, archived web pages (via the Wayback Machine or similar archives), product materials, or press coverage showing your prior use of the exact domain for your brand.
• WHOIS history — records showing your organization or predecessor as prior registrant, the lapse date, and the third party's registration date.
• Post-registration conduct evidence — screenshots of the domain as currently resolved: pay-per-click pages, competitive advertising, offers to sell, or any communication in which the new registrant demanded payment.
• Correspondence — any email, letter, or broker communication in which the new registrant quoted a transfer price. A demand substantially above registration cost is a recognized indicator of bad faith under Paragraph 4(b) of the UDRP.

In spring 2025, we advised a technology company in a .cloud lapsed-domain dispute where the new registrant had parked the domain on a pay-per-click page advertising the brand's competitors. The archived web pages showing several years of the brand's prior use at that domain — combined with a WHOIS history unambiguously connecting the registrant to a portfolio of similar opportunistic registrations — provided a complete bad-faith record, and the complaint was prepared accordingly.

The trap in the evidence step: relying solely on the trademark certificate and ignoring the use record. The confusing-similarity element may rest on the mark alone, but the bad-faith and legitimate-interest elements are decided on conduct evidence. A panel that cannot see what the registrant is doing with the domain, and cannot see what the brand owner was doing before the lapse, has a much harder time finding in the complainant's favor.

If a prior filing produced an adverse result or the evidence file is incomplete, a focused second read can find the element that was missed. Email info@cognomenlaw.com to discuss your .cloud recovery matter.

Step 6: File the complaint — process, timing, and the default trap

Once the evidence file is complete and the forum is chosen, the complaint is drafted and filed with WIPO or the Forum through their respective online filing systems. The complaint must identify the disputed domain, name the complainant and respondent, state the legal grounds under each element of Paragraph 4(a), and attach the evidence as annexes.

WIPO conducts a formal compliance review after filing. If the complaint is deficient — an incorrect registrant name, missing contact information, or an incorrect statement of the remedy sought — WIPO issues a notice of deficiency and the complainant has a short window to remedy it. Deficiencies extend the timeline, so a complete first filing matters.

Once the case commences, the registrant has 20 days to respond. In lapsed-domain cases, default — no response at all — is relatively common. The registrant acquired the domain opportunistically and may not contest the complaint. A default does not mean automatic transfer. The panel still examines the complaint on its merits, and panels have denied transfer even in default where the evidence did not support all three elements. Do not treat default as a guaranteed win; treat it as a reduced evidentiary burden, but not an eliminated one.

If the registrant does respond, the response may raise a legitimate-interest defense — for example, that the registrant acquired the lapsed domain not knowing of your trademark, or that it is a generic or descriptive word used for a genuinely unrelated purpose. Anticipating those defenses in the complaint itself is standard practice. A complaint that pre-empts the expected response narrows the panel's discretion in the registrant's favor.

Step 7: After the decision — registrar implementation and escrow for purchased domains

A UDRP panel that orders transfer does not itself move the domain. The WIPO decision goes to the concerned registrar, which is required by its ICANN accreditation to implement the transfer within a set period — commonly around ten business days — unless the respondent files a court action in the relevant jurisdiction to stay implementation. That stay right is narrow and rarely exercised in practice, but it exists. In the absence of a court challenge, the domain transfers to the registrant nominated in the complaint.

After transfer, secure the domain immediately: update the registrar account to confirmed contact details, enable two-factor authentication, set a registrar lock, and renew for at least two years. A domain recovered through the UDRP that lapses again re-enters the same vulnerability. The recovery cost should motivate better domain-management practice going forward.

Where the path chosen was negotiated purchase rather than UDRP, escrow is not optional — it is the structural safeguard that makes the transaction safe for both sides. The buyer releases funds into escrow, the registrar transfer is initiated and confirmed, and escrow releases funds to the seller only upon confirmed transfer. Skipping escrow in a domain purchase introduces the risk of payment without transfer, or transfer without payment. We structure these transactions through established domain-escrow services and document the assignment through a written domain assignment agreement that records the transfer of any associated goodwill.

In a recent matter (a .cloud purchase negotiation, autumn 2024), we structured an escrow-based acquisition for a SaaS company that had allowed its domain registration to lapse. The registrant who had picked it up was willing to sell at a price considerably below what a UDRP would have cost in combined filing and legal fees. The deal closed in under three weeks. The key was confirming, before any payment, that the domain carried no prior UDRP proceedings and no trademark disputes that could expose the buyer to a subsequent complaint from a different trademark holder in the same space.

That chain-of-title check — carried out before funds move — is the non-negotiable due-diligence step for any purchased domain. It applies equally to .cloud acquisitions as to .com or any other zone.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring services
• Domain assignment agreements: what they must cover and why
• Alert: reversing an unauthorized domain transfer in the US