How to structure escrow for a .com domain purchase

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

A seller holds the .com that matches your brand. The price is agreed. The only thing standing between you and the transfer is the question nobody on either side wants to answer out loud: who moves first? Structured escrow exists precisely to resolve that impasse – and to surface every problem with the domain before the money leaves your account.

To structure escrow for a .com domain purchase, a neutral third-party escrow service holds the buyer's funds while the domain is verified, locked to the seller's account, and pushed to the buyer's registrar. The transfer must be confirmed before funds are released. Before any escrow instruction issues, pre-acquisition due diligence should cover chain of title, prior UDRP dispute history at WIPO or the Forum, any active registrar lock or UDRP lock, and whether the domain carries trademark risk that could expose the buyer to a complaint within the UDRP's two-month decision window. The WIPO filing fee for a future challenge against the buyer begins at USD 1,500.

This page covers the due diligence that must precede escrow, how to sequence the mechanics correctly, what can go wrong at each stage, and what a tainted domain looks like before you own it rather than after.

Why escrow mechanics alone do not protect a .com buyer

Escrow moves money safely. It does not check whether the domain is safe to own. Those are separate problems, and conflating them is the most common error we see in private .com transactions.

A domain can transfer without incident through escrow and still arrive encumbered. The seller may have registered it while aware of a competing trademark. A prior UDRP complaint may have been filed, withdrawn by settlement, and never disclosed. The domain may sit inside a brand owner's watch portfolio, with a complaint ready to file the moment ownership changes hands. None of that appears on a WHOIS/RDDS record. None of it surfaces in the escrow flow. The buyer's only protection is a diligence read conducted before the escrow instruction is signed.

In our practice, roughly a third of .com transactions we review contain at least one latent risk item – an undisclosed prior dispute, a senior trademark registration in a key market, or a registrar flag that would block the transfer mid-escrow. Finding those items before closing is the work. Clearing them, or pricing them into the deal, is the judgment call.

What does a pre-acquisition chain-of-title check cover for a .com domain?

Chain-of-title review for a .com domain traces the registration history, verifies current registrant identity against the transacting party, confirms there is no active UDRP proceeding or pending arbitration lock, and establishes whether any prior transfer could be challenged as involuntary.

The WHOIS/RDDS record is the starting point, not the finish line. ICANN-accredited registrars are required to maintain registration data, but privacy proxy services obscure the underlying registrant's identity. Before committing funds to escrow, the buyer should require the seller to lift any privacy proxy and confirm registrant identity in writing. That confirmation becomes part of the escrow instruction documentation.

The historical record matters as much as the current record. A domain that has changed hands three times in four years warrants scrutiny. Rapid-turnover registration histories sometimes indicate a domain that has been monetized in ways – pay-per-click parking on a third party's trademark, for example – that could give a brand owner standing to file a UDRP complaint against the incoming buyer. Panels have consistently held that a buyer who takes a domain with knowledge of the prior abusive use cannot insulate itself from a bad-faith finding simply by virtue of having paid for it.

Confirm that no UDRP proceeding is pending at WIPO, the Forum, CAC, or ADNDRC. Each provider maintains a public case database. A proceeding filed before the transfer closes does not automatically void the transfer, but it complicates it: the gaining registrar may impose a transfer lock, and the panel will decide who the relevant respondent is under the Rules.

For a pre-acquisition read on a .com domain's dispute history and trademark exposure, contact info@cognomenlaw.com before you issue the escrow instruction.

How does the escrow structure itself work for a .com domain transfer?

A correctly structured .com domain escrow runs in six stages, and the sequence is not negotiable: any deviation creates a window in which either party bears the full risk without the offsetting protection.

The six stages are as follows. First, the buyer deposits funds with the agreed escrow service. Second, the escrow service notifies the seller that funds are held. Third, the seller initiates the domain push or transfer at the registrar level, moving the domain to a registrar account confirmed by the buyer. Fourth, the buyer verifies the domain is in the receiving account and that it matches the agreed specification – same second-level label, same TLD, no pending lock or hold. Fifth, the buyer accepts the transfer through the escrow platform. Sixth, the escrow service releases funds to the seller.

The escrow instruction document should specify the exact domain name, the target registrar and account, the acceptance window (typically five business days from confirmed receipt), and the conditions under which funds are returned – including any failure of the domain to arrive free of UDRP lock, registrar hold, or active dispute.

One structural point that is routinely omitted: the escrow instruction should address what happens if a UDRP complaint is filed during the acceptance window. The UDRP Rules impose a transfer lock on a domain once a proceeding commences. A buyer who has released funds but not yet received a clean transfer has no straightforward recourse through the escrow channel. The instruction should treat a post-funds, pre-acceptance UDRP filing as a dispute-triggering event that suspends the closing clock and preserves the right to rescind.

What trademark and UDRP exposure does a buyer inherit on a .com transfer?

A .com buyer inherits the domain's history, not a clean slate. The critical question is whether the incoming registration, under the buyer's intended use, satisfies or violates Paragraph 4(a) of the UDRP – because a brand owner watching that domain can file against the new registrant the day after transfer.

The three UDRP elements that a complainant must satisfy are: (1) the domain is identical or confusingly similar to a trademark in which the complainant has rights; (2) the buyer has no rights or legitimate interests in the domain; and (3) the domain was registered and is being used in bad faith. For a buyer who intends to use the domain legitimately in connection with a real business, the second and third elements are defensible. For a buyer whose plan is to park the domain, re-sell it at a premium, or redirect it to a site with no evident connection to the name, the exposure is material.

The trademark search is not optional. A buyer acquiring a .com that is identical or nearly identical to a registered mark in any major market should understand the risk profile before closing. That does not mean the transaction cannot proceed. It means the buyer needs to know whether they are acquiring a domain they can use without interference, or one they will need to defend within months of closing.

We have advised buyers who discovered, mid-escrow, that the domain matched a recently registered trademark in the EU – a registration the seller had not disclosed and that the buyer's team had not checked. The transaction closed on adjusted terms after a risk allocation clause was added to the purchase agreement. The domain transferred. The buyer held it without a complaint being filed. But without that clause, the buyer would have had no contractual recourse had a transfer order issued.

To weigh UDRP against a court action for your case, or to assess trademark exposure before a .com acquisition closes, email info@cognomenlaw.com.

How should the purchase agreement address dispute risk and representations?

The escrow mechanics govern movement of money and domain. The purchase agreement governs everything that can go wrong before, during, and after that movement. For a .com transaction with any dispute history or trademark adjacency, a bare domain purchase agreement is not adequate.

The seller should represent and warrant, at minimum, that the domain is not subject to any pending or threatened UDRP, URS, or other dispute proceeding; that no demand letter or cease-and-desist has been received relating to the domain; that the seller is the beneficial owner with full authority to transfer; and that the registration was not acquired in bad faith in respect of any third-party trademark rights. Those representations carry weight only if the agreement specifies what happens when they are false – return of funds, indemnification of defense costs, or both.

For higher-value transactions, the agreement should also address the UDRP's narrow remedy scope: a UDRP panel can order transfer or cancellation, but cannot award damages or costs. If the buyer ends up defending a UDRP complaint because the seller misrepresented the domain's history, the cost of that defense falls on the buyer unless the agreement expressly allocates it otherwise. The Forum and WIPO filing fees alone are material at USD 1,300 to USD 1,500 for a single-member panel, before legal fees.

In a recent matter (a .com acquisition, spring 2025), a buyer came to us after closing without a dispute-risk clause. A brand owner filed a UDRP complaint at WIPO within six weeks of the transfer. The buyer had a legitimate-interest defense, and we built one. The complaint failed. But the buyer bore the full cost of the defense – a cost the purchase agreement could have allocated to the seller.

What is the difference between acquiring a clean .com and one with prior dispute history?

A domain with no prior dispute history and no trademark adjacency is the simplest acquisition: diligence is confirmatory, the escrow instruction is standard, and the purchase agreement representations are low-risk. A domain with prior dispute history requires a different approach at every stage.

If a UDRP complaint was filed against the domain and transferred to the current seller, that transfer order is public. Any subsequent buyer acquiring the domain faces a panel that, in a future proceeding, may note the transfer in the context of a bad-faith analysis. Panels have been willing to draw adverse inferences from a domain's registration and transfer pattern, even where the current registrant was not party to the prior proceeding.

If a prior complaint was denied – meaning the complainant failed on one or more elements – the buyer should read the decision. A denial on the third element (bad faith) is relatively protective for an incoming buyer with different intended use. A denial on the second element (legitimate interest), where the panel found the prior registrant had a genuine claim, is stronger still. A denial grounded in a finding of Reverse Domain Name Hijacking (RDNH) – meaning the prior complaint was itself abusive – can be a positive signal: the brand owner overreached once and a panel said so.

A domain with a withdrawn or settled prior complaint requires the most scrutiny. The underlying dispute never went to a decision. The brand owner may have settled on terms that restrict transfer or use. Those terms are not public. The seller must disclose any settlement agreement relating to the domain, and the purchase agreement should include a specific representation on that point.

How does the .com zone compare to ccTLDs and new gTLDs for transaction risk?

The .com zone carries the highest transaction volume and the most developed UDRP precedent. That cuts both ways. Brand owners are more likely to monitor .com. Panels deciding a .com dispute have a deep body of consensus decisions to draw from, making outcomes more predictable – which helps both buyers assessing their defense position and sellers pricing risk into negotiations.

Country-code zones introduce separate complexity. A buyer acquiring both a .com and a corresponding national ccTLD in the same transaction faces two distinct dispute regimes. The .eu zone, for example, is governed by the EURid/ADR.eu procedure, and .eu registrant eligibility requires an EU/EEA nexus – a requirement that must be verified before the acquisition closes, not after. The .de zone has no administrative dispute procedure: a brand owner challenging a .de registration goes to the German courts, and a DENIC DISPUTE entry can block transfer while the claim proceeds. Acquiring a .de alongside a .com means understanding both tracks simultaneously.

New gTLDs under ICANN's post-2012 program carry URS exposure in addition to UDRP. The URS remedy is suspension for the registration term rather than transfer, and the evidentiary standard is higher. A buyer acquiring a new gTLD should confirm whether any URS proceeding has been filed or resolved against the domain, just as they would check for UDRP history on a .com.

The rule of thumb in our practice: diligence scope tracks dispute-procedure complexity, and complexity tracks the number of zones in the transaction. A single .com acquisition is the baseline. Add a ccTLD and the diligence budget roughly doubles. Add a portfolio of mixed gTLDs and ccTLDs and a systematic procedure – trademark clearinghouse search, zone-by-zone dispute history, eligibility verification – is the only way to catch what a point-in-time check misses.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand protection services
• Domain assignment agreements for .ca and cross-border transactions
• FAQ: what if the domain was registered before the trademark?