How to structure escrow for a .cloud domain purchase

How to structure escrow for a .cloud domain purchase. UDRP and ccTLD domain recovery and defense across .cloud. Email the firm to assess your case.

A domain listed at five figures looks clean on the surface. Then due diligence surfaces a prior UDRP filing, a disputed chain of title, and a seller whose identity shifts between registrar records. At that point the question is no longer whether to buy the .cloud domain – it is whether the transaction can be built on a foundation that survives the scrutiny a registrant's history invites.

To structure escrow for a .cloud domain purchase you need three things working in parallel: a verified chain of title confirming no outstanding dispute, a neutral escrow arrangement that releases funds only on confirmed registrar transfer, and a pre-acquisition review of any prior UDRP or ccTLD proceeding that touched the name. The .cloud registry operates under accredited registrars and the UDRP applies to .cloud domains – meaning a clean purchase today can still be challenged tomorrow if a trademark holder claims the name was registered in bad faith at any point in its history. Escrow cannot cure a tainted domain; it can only protect the buyer if the deal is built correctly from the start.

This page covers the full structure: due diligence on .cloud title, how escrow mechanics work for domain transactions, the evidence that decides whether a name is safe to acquire, and the realistic next steps if complexity surfaces.

Why .cloud transactions carry specific escrow risk

The .cloud generic top-level domain is a delegated new-gTLD operating under ICANN's standard registry agreement, which means the UDRP applies in full, and any accredited registrar can hold the registration. That is the same legal infrastructure as .com – and it carries the same dispute exposure. A buyer who acquires a .cloud domain through a private sale or broker transaction takes the name as it stands, including any prior bad-faith history that a future complainant can use as evidence against the new registrant.

Is the new owner really insulated from the prior registrant's conduct? Not entirely. Panels assessing bad faith under Paragraph 4(a)(iii) of the UDRP routinely examine the registration history of a domain, not merely the current registration date. If the name was previously pointed at a competitor's lookalike site, or was used to monetize traffic from a well-known mark, that history follows the domain into the new ownership. It does not automatically make the new owner a bad-faith registrant – but it creates a record the seller's counsel will need to explain, and that a complainant's counsel will certainly surface.

For a .cloud domain specifically, a second risk layer is the sector association. Many .cloud names carry technology or cloud-services connotations that overlap with established marks in the SaaS and infrastructure sectors. Brand owners in those sectors monitor .cloud registrations actively. A domain that appears dormant may already be on a watch list. Escrow structure that ignores this risk is escrow structure that protects only the payment – not the investment.

For an assessment of your domain transaction – including chain-of-title review and escrow structuring – contact info@cognomenlaw.com.

Chain-of-title checks: what must be verified before escrow opens

A chain-of-title review for a .cloud domain purchase means tracing the full ownership history of the registration and resolving every gap or inconsistency before the escrow instruction is issued. That review covers four areas: registration history, WHOIS and RDDS records over time, any prior dispute filings, and the seller's entitlement to transfer.

Registration history is the starting point. When was the domain first registered? By whom? Was it allowed to expire and re-registered by a third party, or has it been held continuously? A gap in registration – a deletion and re-registration event – resets the registration date in the WHOIS record but does not erase the prior history from WIPO's published case database or from archived RDDS snapshots. Panels have considered historical use when assessing whether a current registrant inherited an abusive registration. A buyer who takes that domain without reviewing what the name was used for pre-deletion carries that exposure forward.

UDRP and ccTLD dispute history is the second check. WIPO and the Forum both maintain searchable public databases of filed complaints. A domain that appears as a respondent in a prior proceeding – whether the complaint was filed, decided, or withdrawn – is a domain with a documented adversarial history. That history is material to the buyer's due diligence and should be disclosed in the purchase agreement. Where the prior proceeding resulted in a transfer order that was overturned, reversed, or otherwise not implemented, counsel should obtain the decision and assess why. Where the prior proceeding was withdrawn, the reason for withdrawal matters; settlement terms may survive and bind the current registration.

Seller entitlement to transfer is the third area. The seller must be the registrant of record, must have admin access to the account, and must not be subject to a registrar lock, a UDRP lock, or an interim court order preventing transfer. A domain in active dispute is locked by the registrar pending the outcome of the proceeding. An escrow instruction issued during a lock period will fail at implementation – the registrar cannot transfer. Confirming the lock status before escrow opens is not a formality; it is a precondition.

Trademark clearance is the fourth check. The buyer should conduct a trademark search on the dominant element of the domain name across the relevant jurisdictions – particularly in sectors where the .cloud namespace is commercially active. A buyer who acquires a name that is confusingly similar to a registered mark, even innocently, starts the clock on the two-year period within which a complainant may file a UDRP complaint citing bad faith. If the buyer intends to use the domain commercially, that use is evidence. If the intended use is resale, panels have addressed whether passive holding of a confusingly similar name constitutes bad faith under Paragraph 4(b) of the Policy.

How to structure the escrow mechanics for a .cloud transfer

Domain escrow for a .cloud purchase operates through a neutral third-party escrow service that holds the purchase funds until both the domain transfer is confirmed at the registrar level and any agreed conditions precedent are satisfied. The mechanics are straightforward in a simple transaction and become more complex when conditions – such as completion of due diligence, regulatory clearances, or staged payments – are layered in.

The core sequence runs as follows. The parties agree on the purchase price and the escrow terms in a written domain purchase agreement. The buyer deposits funds into the escrow account. The seller initiates the domain transfer at the registrar, generating an authorization code (commonly called an EPP code or auth-info code). The buyer's gaining registrar uses the code to pull the transfer. Once the transfer is confirmed in the gaining registrar's system – typically within five days under ICANN's inter-registrar transfer policy – the escrow service releases funds to the seller.

Where does this structure commonly break down? Three points of failure appear regularly in our practice. First, the auth-info code is issued before the registrar lock is confirmed as clear, and the transfer fails because a UDRP lock was still active. Second, the parties use an informal payment method – cryptocurrency sent directly, wire transfer without confirmation – rather than a formal escrow service, and the seller receives payment before the transfer is verified. Third, the purchase agreement is silent on what happens if the transfer is challenged under the UDRP within a defined period after closing, leaving the buyer without a contractual recourse against the seller's representations and warranties.

A well-drafted domain purchase agreement for a .cloud name should include: representations that the seller has clear title and no knowledge of pending or threatened disputes; a warranty that the domain has not been used in violation of any trademark holder's rights during the seller's ownership; an indemnity running in favor of the buyer for claims arising from pre-closing conduct; and a condition precedent confirming that the domain is not subject to any registrar lock at the time of transfer initiation. Without those provisions, escrow protects only the payment mechanics – not the legal position of the buyer after transfer.

In a recent transaction (a .cloud domain in the technology sector, spring 2025), we identified a prior UDRP complaint that had been withdrawn before a decision, with no public record of the withdrawal reason. We obtained the seller's file, confirmed the withdrawal was settled on terms that did not survive to bind subsequent registrants, and structured the escrow with a condition precedent requiring the seller to produce the settlement correspondence before funds released. The buyer closed with a clean record confirmed.

To weigh escrow structure against pre-acquisition dispute risk for your .cloud purchase, email info@cognomenlaw.com.

What evidence decides whether a .cloud domain is safe to acquire?

The evidence that matters most is the evidence a future complainant would assemble – which means the buyer's due diligence should anticipate and answer it before the purchase closes. The relevant framework is Paragraph 4(a) of the UDRP, and specifically whether a future complainant could credibly argue that the domain was registered and is being used in bad faith.

Confusing similarity to a registered mark is typically the easiest element for a complainant to establish. If the .cloud domain incorporates a distinctive trademark – whether as an exact match, a close phonetic variant, or a typosquatting form – that element is met regardless of the buyer's intent. The buyer's due diligence must assess the trademark landscape around the domain's dominant string before closing, not after a complaint arrives.

The harder question is whether the buyer can establish a legitimate interest in the domain after acquisition. Paragraph 4(c) of the UDRP sets out the safe harbors: a bona fide commercial use before any notice of the dispute; being commonly known by the domain name; or a legitimate noncommercial or fair use without intent to mislead. A buyer who intends to develop the .cloud domain commercially, and whose intended use is genuinely distinct from any trademark holder's goods or services, can build a legitimate-interest record from the date of acquisition. That means documenting the business purpose, the intended use, and the absence of any intent to target a mark holder – contemporaneously, not retrospectively.

Bad faith under Paragraph 4(b) is assessed against both the registration event and the ongoing use. A buyer who registers a .cloud domain at a price far below market, knowing it matches a well-known mark, starts with a problem under Paragraph 4(b)(i) – the inference of registration for resale to the mark owner at a profit. A buyer who then parks the domain at a pay-per-click page serving advertising related to the mark's industry compounds that under Paragraph 4(b)(iv) – attracting users for commercial gain through confusion. Due diligence that identifies these risks pre-closing allows the buyer to adjust the intended use, adjust the price, or walk away. It cannot retrofit intent after the fact.

The evidence that most reliably supports a safe acquisition is, in order of weight: a trademark clearance showing no registered marks confusingly similar to the domain string in the buyer's sector; a chain-of-title review showing no prior dispute history; a UDRP and ccTLD database search showing the domain has not been named in any prior proceeding; and a purchase agreement with the seller representations described above. No due diligence process eliminates risk entirely – a mark could be registered after the purchase, or a complainant could argue common-law rights. But documented pre-closing diligence is the strongest foundation for a legitimate-interest defense if a challenge arrives.

UDRP exposure after closing: what happens if a complaint is filed?

If a UDRP complaint is filed against the buyer's .cloud domain after closing, the buyer becomes the respondent in the proceeding and has 20 days from commencement to file a response. A standard case is normally completed within about two months. The only remedies under the UDRP are transfer or cancellation – the panel cannot award damages against the buyer or impose costs.

What options does a respondent have? The response must address all three UDRP elements. Specifically, the respondent must undermine the complainant's case on at least one of: confusing similarity to a mark, absence of legitimate interest, or bad faith registration and use. Where the buyer's acquisition was clean – supported by trademark clearance, a chain-of-title review, and documented business use – the legitimate-interest defense under Paragraph 4(c) is the primary line of argument.

If the complaint is filed against a registrant with a clean acquisition record and the complainant's mark post-dates the registration, the respondent has a strong argument that the third UDRP element cannot be met – you cannot register a domain in bad faith targeting a mark that did not yet exist. Panels have consistently held that bad faith under Paragraph 4(a)(iii) requires that the registrant knew of the mark at the time of registration and targeted it. A purchase supported by prior trademark clearance showing no such mark at the time of acquisition is powerful contemporaneous evidence on this point.

Where a complaint appears abusive – filed by a complainant with a weak or post-dating mark, seeking to recover a legitimately held domain – a respondent may seek a finding of Reverse Domain Name Hijacking. An RDNH finding is a reputational sanction against the complainant. It carries no monetary penalty under the UDRP, but it is a published finding in the case record and can be material in subsequent proceedings or negotiations. We regularly defend respondents in proceedings of this kind, including .cloud domains where the complainant's trademark claim was thin or its evidence of bad faith was circumstantial.

The WIPO filing fee for a .cloud complaint against the buyer is USD 1,500 for a single-member panel (1–5 domains). A respondent's defense costs are separate from and additional to any forum fee. The cost to defend is comparable in range to the cost to prosecute, and the buyer's pre-closing due diligence record is directly relevant to the strength and cost of that defense – a clean file requires less defensive work than a transaction assembled without it.

Cross-zone considerations: what if the dispute spans .cloud and a ccTLD?

A .cloud domain purchase does not exist in isolation. A brand owner asserting trademark rights over the domain string may hold registrations in multiple zones – .com, .cloud, and a national ccTLD. A UDRP complaint covers only the specific domain named in the complaint. A buyer who acquires the .cloud domain but holds no rights in the .com or relevant ccTLD is exposed to parallel proceedings in each zone.

The right structure depends on the zone and the goal. For a .com companion domain, a UDRP complaint at WIPO or the Forum is the standard route for any future complainant, with the same three-element test and the same USD 1,500 base filing fee at WIPO. For a .eu companion domain, the ADR.eu procedure at the Czech Arbitration Court applies – the test and the remedies differ from the UDRP, and the complainant's eligibility requirements reflect EU nexus rules. For a .uk companion, Nominet's DRS applies, with a free mediation stage before any expert decision and a test of "abusive registration" rather than the UDRP's three elements. For a .de companion, neither the UDRP nor any UDRP-variant applies – disputes over .de domains proceed through the German courts, with a DENIC DISPUTE entry available to block transfer while litigation is pending.

A buyer assembling a brand presence across zones should model the dispute exposure in each zone as part of the acquisition due diligence. Acquiring the .cloud name without clearing the .com – or without understanding that the .com is held by a potential adversary – is a position that limits the investment's value. We advise on cross-zone portfolio structuring, including pre-acquisition dispute history review across gTLD and ccTLD zones, as part of the transaction due diligence process. See also our analysis of court action for cybersquatting on .com domains for the litigation route available in parallel with or instead of UDRP proceedings.

Portfolio implications: protecting a .cloud acquisition over time

Buying a .cloud domain is an event. Protecting it is a continuous process. The registrant who acquires a name in good faith, documents the acquisition, and then allows the domain to drift – into parking, into an inactive status, or into use that drifts toward another party's mark – creates conditions that a future complainant can exploit.

Passive holding of a domain is not automatically bad faith under the UDRP. But panels have found that passive holding of a domain confusingly similar to a well-known mark, with no documented business use and no plausible explanation for why the registrant holds the name, satisfies the bad faith element in specific fact patterns. The practical implication for a .cloud domain buyer is straightforward: document the intended use, develop the intended use, and monitor the trademark landscape around the domain string to identify any new filings that might alter the risk profile.

Brand protection monitoring for a .cloud domain covers two directions. Outward monitoring tracks whether third parties are registering similar names in the same or adjacent zones – typosquats, prefix variations, or ccTLD companions – that could be used to divert traffic or to dilute the brand the buyer is building. Inward monitoring tracks whether the buyer's own domain is flagged in any trademark watch service or watch alert, indicating a mark holder is watching the registration. Early identification of inward monitoring allows a registrant to take a considered position before a complaint is filed, rather than receiving the complaint as the first signal. Our domain transactions and brand protection services include portfolio monitoring as a standalone service for active registrants.

In a second recent matter (a .cloud portfolio acquisition covering eight domains in the technology space, autumn 2024), a buyer's pre-acquisition review identified that two of the eight names had been used by the prior registrant in a way that generated pay-per-click revenue from searches for a named software product. We advised the buyer to exclude those two domains from the purchase, restructure the escrow to cover only the six clean names, and obtain the seller's representations specifically addressing the excluded domains' history. The buyer closed on the six; the two excluded names were subsequently named in a UDRP complaint by the software mark holder, confirming the pre-closing risk assessment.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring – escrow, pre-acquisition review, and portfolio services across gTLD and ccTLD zones
• How to verify chain of title before a domain purchase – the full due diligence process for domain acquisitions, including dispute history and WHOIS analysis
• Court action for cybersquatting on .com domains – when UDRP is insufficient and US anticybersquatting litigation is the right route