Update: changes affecting how to structure escrow for a .cloud domain…

Update: changes affecting how to structure escrow for a .cloud domain. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your…

A buyer completes due diligence, funds escrow, and receives a .cloud domain – only to discover the name carries a prior dispute history that clouds the title. With renewed attention on registry-level policy updates for new-gTLD zones, including .cloud, the mechanics of how to structure escrow for a .cloud domain purchase deserve a direct revisit.

Structuring escrow for a .cloud domain purchase now requires explicit attention to chain-of-title verification, prior UDRP history under the governing WIPO rules, and a registry eligibility check before funds move. The three UDRP elements under Paragraph 4(a) of the Policy apply in .cloud as a new-gTLD zone, meaning any domain carrying a prior complaint or an unresolved dispute history transfers that legal exposure to the buyer. The WIPO filing fee for a single-domain UDRP complaint starts at USD 1,500 – a cost a buyer may face if they acquire a name that draws a fresh complaint post-transfer.

Below: what changed, who is affected, and the practical steps to protect a .cloud acquisition now.

What Changed in .cloud Escrow Practice?

The core shift is not a single registry rule amendment. It is the convergence of two trends hitting new-gTLD transactions simultaneously. First, UDRP complaint volumes are rising – WIPO administered 6,282 domain-name cases in 2025, a record – and new-gTLD zones including .cloud represent a growing share of disputed names. Second, buyers are treating .cloud names as premium commercial assets, often at prices where a failed transaction or a post-sale complaint causes real financial harm.

What that means in practice: an escrow structure that was adequate for a low-value .cloud registration may not protect a five-figure acquisition. The gap is chain-of-title. A standard domain escrow service holds funds and coordinates the registrar push. It does not investigate whether the domain has a prior UDRP history, an active dispute entry, or a URS suspension order that survives transfer. Those checks must happen before escrow is funded – not after.

Who Is Affected?

Brand owners acquiring .cloud names to extend their digital presence are the primary group at risk. If the seller registered the domain in circumstances that a third-party trademark owner could challenge, the buyer inherits a name that can be the subject of a UDRP complaint after the transfer closes. The new registrant becomes the respondent.

Domain investors holding .cloud names for resale face the mirror problem. A buyer who discovers prior dispute history – even a complaint that was denied – may seek to rescind the transaction or discount the price substantially. Sellers who cannot demonstrate a clean dispute record weaken their negotiating position. We regularly advise investors on pre-sale due diligence for exactly this reason: a documented clean history is an asset, not a formality.

Registrants who received a .cloud name as part of a corporate asset transfer or a brand-acquisition deal are also affected. The chain of title runs through every holder, and a weakness at any prior stage is discoverable.

For an assessment of your .cloud domain transaction – whether you are buying, selling, or structuring escrow – contact info@cognomenlaw.com.

What Should You Do Now?

Four steps apply to any .cloud acquisition where the purchase price is material.

First, run a UDRP and URS history check on the specific domain before escrow is funded. WIPO's public case database and the Forum's records are searchable. Any prior complaint – won, lost, or withdrawn – tells you something about the name's dispute exposure. A complaint that was denied does not mean the name is clean; it may mean the complainant had insufficient evidence that time.

Second, verify current registry status with the .cloud registry. A domain subject to a URS suspension order carries a restriction that can survive a registrar transfer. Confirm there is no hold, lock, or pending proceeding at the registry level before funds move.

Third, structure the escrow release on condition of a clean transfer – not merely a completed push. The condition should include confirmation that no UDRP or URS proceeding has been filed between execution and closing, and that the domain arrives in the buyer's account free of any registry-level restriction.

Fourth, assess the name against third-party trademark rights before closing. In a new-gTLD zone like .cloud, the UDRP applies fully. If the domain is confusingly similar to a registered mark held by a third party, a post-transfer complaint is a realistic risk, regardless of the seller's conduct. A pre-acquisition trademark clearance search reduces that exposure materially.

In a recent transaction matter (a .cloud name with a commercial value in the five-figure range, early 2026), we identified a prior UDRP complaint that had been filed and withdrawn before a decision. The withdrawal was not a clean record – it reflected a negotiated outcome between the then-registrant and a trademark owner. That history required an amended escrow structure and a representation from the seller covering the prior dispute. Without that additional step, the buyer would have acquired a name with undisclosed legal exposure.

To weigh UDRP risk against a proposed .cloud acquisition, email info@cognomenlaw.com.

Related at COGNOMEN

• Domain purchase, sale, escrow, and pre-acquisition due diligence services
• Brand protection monitoring for domain portfolios and new-gTLD zones
• Respondent defense and RDNH findings in .com and related zones