What is Domain escrow? Definition and meaning

Domain escrow is a neutral third-party arrangement in which the purchase price for a domain name is held in trust until the domain has been successfully transferred to the buyer, at which point the funds are released to the seller.

In a domain transaction, neither party wants to move first. The buyer will not pay before the domain arrives; the seller will not transfer before payment clears. Domain escrow resolves that deadlock by placing funds with an independent escrow provider and releasing them only when a verified transfer is confirmed. It is the standard settlement mechanism for any domain purchase where the parties are not known to each other.

You are about to pay five figures for a domain. The seller is a registrant you found through a broker or a registrar marketplace. You cannot telephone the registry to confirm the transfer will stick. That is precisely the scenario domain escrow is designed for – and the scenario where skipping it creates the greatest exposure.

What domain escrow is – and what it is not

Domain escrow is a financial settlement tool, not a legal due-diligence service. It ensures that money moves only when the domain moves. It does not confirm that the seller holds clear title, that no prior dispute has been filed, or that the name is free of trademark conflict. Buyers routinely confuse domain escrow with domain due diligence – the two are complementary but distinct.

Due diligence examines the chain of title, prior UDRP or ccTLD proceedings, the domain's registration history, and trademark risk before you commit to the price. Escrow executes the payment once you decide to proceed. Running one without the other leaves a gap: escrow without due diligence means you pay safely for something you may later lose.

Domain escrow is also not a domain dispute mechanism. It has no relationship to the UDRP or any ccTLD procedure. A panel deciding a domain dispute does not examine whether the domain changed hands through escrow; the chain of title is relevant, but the payment method is not.

Where domain escrow sits in the governing rules

ICANN's registrar accreditation rules set out the mechanics of a domain transfer between registrars and registrants, but they do not mandate escrow. Escrow is a contractual arrangement between the buyer, seller, and the escrow provider. The provider holds the funds under a written escrow agreement that specifies the release conditions – typically confirmation of a successful registrar-to-registrar transfer or an auth-code push followed by registrant verification through RDAP.

The escrow fee is charged by the provider, not the registrar. COGNOMEN's published fee structure notes escrow costs in the range of 0.89–3.25% of the transaction value, depending on the provider and the deal size, and COGNOMEN works with the buyer and seller to coordinate the arrangement. The exact rate is set by the escrow provider and should be confirmed before contracts are signed.

For high-value names, some transactions also involve a domain purchase agreement – a short-form contract that sets out the purchase price, the escrow conditions, representations about title, and the timeline for transfer. That agreement sits alongside the escrow arrangement and gives both parties a contractual remedy if something goes wrong outside the payment mechanics.

How domain escrow works in practice: three recognizable patterns

The mechanics vary slightly by transaction type, but three patterns cover the majority of domain purchases we handle.

Pattern one: marketplace sale through a broker. The seller lists a name on a domain marketplace. A buyer makes an offer. Both parties are directed to an escrow provider by the broker. The buyer deposits funds; the broker or seller pushes the domain via auth code; the escrow provider verifies the transfer and releases payment. The registrar's transfer confirmation – visible through an RDAP query – is the trigger event. This pattern is the cleanest and accounts for most mid-market transactions.

Pattern two: direct negotiation after a demand letter. A brand owner identifies a domain that conflicts with a registered trademark and approaches the registrant. The registrant agrees to sell. Both parties want certainty: the brand owner wants the domain before paying, and the registrant wants payment before surrendering control. Escrow resolves this. In this context, domain escrow frequently appears alongside domain due diligence – the brand owner commissions a chain-of-title check before placing funds in escrow. We regularly advise brand owners in this exact sequence: identify the risk, assess whether a UDRP complaint would succeed, then decide whether to buy or file.

Pattern three: portfolio acquisition. A single buyer acquires a block of names from an investor. Each domain has its own registration date, registrar, and history. The purchase price is typically a lump sum. Escrow here is structured differently: funds are held against a schedule of transfers, released tranche by tranche as each domain is confirmed moved. This structure protects the buyer from paying the full sum before all names have transferred, and protects the seller from partial non-payment. Due diligence on a portfolio acquisition covers each name individually – prior dispute history, trademark risk, and any DENIC DISPUTE entries or ccTLD holds that could block transfer.

Why domain escrow matters for brand protection

For a brand owner acquiring a conflicting domain, the escrow arrangement does more than protect the payment. It creates a documented record of the transaction: when the domain transferred, to whom, and for what consideration. That record matters if a third party later challenges the acquisition – for example, if a prior claimant argues the domain was transferred in bad faith to defeat a pending complaint.

It also matters in the reverse direction. A domain investor selling a name to a brand owner wants evidence that the transaction was arm's-length and commercially reasonable. A properly documented escrow file – escrow agreement, transfer confirmation, payment record – supports that position if a dispute arises later about the circumstances of the sale.

Brand protection monitoring feeds directly into the escrow decision. If monitoring identifies a domain that is being used to target a mark, the brand owner must decide quickly: file a UDRP complaint, send a demand letter, or negotiate an acquisition. Where negotiation is the chosen route, escrow is the standard closing mechanism. Where a UDRP complaint is filed first and the parties settle mid-proceeding, escrow can be used to implement the agreed transfer while WIPO closes the case.

Many buyers assume that completing a domain purchase clears all legal risk. That assumption is the most common misconception we encounter. Chain of title and prior dispute history remain relevant after closing. If the domain was previously the subject of a UDRP complaint that was suspended for settlement and never formally resolved, a subsequent complaint by the same or a different complainant may still be filed. Due diligence before escrow is the safeguard, not a substitute for it.

COGNOMEN handles domain transactions – including acquisition, sale, due diligence, and escrow coordination – exclusively alongside dispute work, across gTLDs and ccTLDs. To discuss a domain purchase or sale, contact info@cognomenlaw.com.

Related at COGNOMEN

• transactions – domain acquisition, sale, escrow, and due diligence services
• Transfer vs cancellation as remedies: what is the difference? – how UDRP panels choose between the two remedies
• analysis brand protection monitoring info – how ongoing monitoring feeds into brand protection strategy

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.