How Domain Escrow Works:
A Complete Buyer's Guide

Domain escrow exists because domain transfers involve a fundamental trust problem: the buyer doesn't want to pay until they have the domain, and the seller doesn't want to transfer the domain until they have the money. Without a neutral intermediary, one party has to go first and assume the risk.

Escrow solves this by holding the funds while the transfer is completed. The buyer deposits money into the escrow account; the seller pushes the domain; the escrow service verifies the transfer; funds are released to the seller. Both parties are protected throughout.

For any domain transaction above $2,000, escrow is not optional. It is the standard practice and refusing to use it is a red flag on a seller's part.

The Step-by-Step Escrow Process

• 1

  Agree on terms

  Before escrow is initiated, both parties agree on price, currency, timeline, and which party pays the escrow fee. This should be confirmed in writing — an email exchange is sufficient, though a formal agreement is better for large transactions.

• 2

  Create the escrow transaction

  Either party initiates the transaction on the escrow platform (Escrow.com is the most widely used). The transaction is set up with the agreed price, the domain being transferred, and the inspection period (typically 5 business days).

• 3

  Buyer deposits funds

  The buyer transfers the agreed amount to the escrow account. Escrow.com accepts wire transfer, credit card, and PayPal. Wire transfer is standard for transactions above $5,000 as it has the lowest fees and fastest clearance for large amounts.

• 4

  Escrow confirms receipt

  Once the funds clear, the escrow service notifies the seller that payment is secured and instructs them to proceed with the domain transfer.

• 5

  Seller initiates the domain transfer

  The seller unlocks the domain at their registrar and provides an auth code (EPP code) to the buyer. The buyer uses this code to initiate a transfer to their registrar. Transfer times vary: .com transfers typically take 5–7 days; some other extensions are faster or slower.

• 6

  Buyer verifies and accepts

  Once the domain appears in the buyer's registrar account, the buyer verifies that DNS works correctly and accepts the transaction in the escrow platform. This starts the inspection period clock.

• 7

  Funds released to seller

  After the inspection period (typically 5 business days from buyer acceptance), funds are released to the seller. If the buyer reports a problem during the inspection period, the escrow service mediates. If no problem is reported, funds release automatically.

Which Escrow Service to Use

There are several escrow services in the domain market. Here are the main options:

• Escrow.com — the industry standard. FDIC insured, used by Sedo and other major platforms, supports most domain extensions. The go-to for professional transactions. Fees: 0.89% to 3.25% of transaction value depending on payment method and transaction size.
• Sedo Escrow — built into the Sedo marketplace. Good if the transaction originated on Sedo or if the seller is a Sedo partner. Slightly higher fees than Escrow.com for off-platform transactions.
• Dan.com — now part of GoDaddy's portfolio. Supports outright purchase and payment plan structures. Useful for transactions where the buyer needs to pay over time.

We always use Escrow.com for QuietClose-managed acquisitions. It is the most trusted, most liquid, and most widely accepted by sellers globally.

Who Pays the Escrow Fee?

This is negotiable. Common arrangements:

• Buyer pays — most common. The buyer is receiving the asset and is the party with the most to lose from an unsafe transfer.
• Seller pays — sometimes offered by motivated sellers as an incentive to close.
• Split equally — a fair compromise that works well when both parties want the deal done.

For QuietClose-managed acquisitions, we negotiate the escrow fee arrangement as part of the deal terms. For most transactions we recommend the buyer pays — it keeps the purchase price clean and the seller has one less reason to resist escrow.

What Can Go Wrong and How Escrow Protects You

Without escrow, the domain transfer process exposes both parties to significant risk:

• Seller disappears after payment. Without escrow, a seller who receives payment has no obligation to actually push the domain. With escrow, payment is never released until the domain transfer is confirmed.
• Domain has encumbrances or disputes. If the domain is subject to a trademark dispute or other legal issue, this may surface during the inspection period. Escrow protects the buyer by holding funds until the inspection period closes.
• Transfer fails technically. DNS issues, registrar problems, auth code expiry — these are common. If the transfer fails during the inspection period, the buyer reports the issue, the escrow service mediates, and funds are returned if the domain cannot be delivered as agreed.
• Seller provides wrong auth code. Deliberate fraud is rare but exists. The escrow structure means the seller doesn't receive funds until the correct domain is in the buyer's account.

Live Site Acquisitions: Additional Considerations

When the domain being acquired points to a live website, escrow covers the domain transfer — but you also need to manage:

• Email continuity. If the domain has active email (MX records), transferring without a plan disrupts all email. Agree on a transition period or migration plan before transfer.
• DNS and hosting. What happens to the existing website? Is it part of the acquisition or not? This needs to be clear in the agreement.
• SEO equity. If the domain has inbound links and search rankings, an abrupt change in DNS or content can damage that equity. Work with the seller on a staged transition.

We structure live site acquisitions with a phased escrow release where appropriate — typically 50% on domain transfer, 50% on completion of the agreed transition assistance period.