Domain Escrow Explained: How to Buy a Domain Safely

Buying a registered domain creates a trust problem. The buyer does not want to send money before receiving control of the domain, and the seller does not want to surrender the domain before payment is secured. Domain escrow places an independent transaction service between those two events.

Escrow does not make a weak domain valuable or remove trademark risk. It protects the exchange process. Use it after completing the commercial and legal checks in the domain aftermarket guide and the domain validation checklist.

What Domain Escrow Does

In a standard domain transaction, the parties agree to written terms, the buyer sends funds to the escrow provider, the provider confirms that funds are secured, and the seller transfers the domain. The buyer then verifies receipt during the agreed inspection period. Funds are released when the acceptance conditions are met.

Escrow.com's documented process follows that sequence: agreement, buyer payment, domain transfer, buyer acceptance, and seller payment. Other providers may use different terminology or evidence, so read the provider's current instructions before opening a transaction.

Standard Escrow vs Domain Holding

Escrow.com distinguishes a standard transaction from its holding service. In a holding transaction, the service receives the domain and retains it while scheduled payments are made. That adds different fees, default rules, and DNS responsibilities.

The Five Stages of a Domain Escrow Transaction

Write the Terms Before Anyone Sends Money

The safest transaction is specific enough that a third party can tell whether it succeeded. Do not rely on email phrases such as transfer the domain promptly. Put the exact domain, currency, purchase price, fee allocation, transfer method, receiving registrar or account, inspection period, deadlines, and included assets into the escrow terms.

• Exact domain name, including extension and any IDN or punycode form
• Purchase price, currency, payment method, and who pays each fee
• Whether the transfer is an internal account push or an inter-registrar transfer
• The buyer's receiving registrar account and required contact details
• A clear definition of delivery and the inspection period
• Whether the sale includes a website, content, logo, social account, email list, or trademark rights
• Responsibility for renewal fees, taxes, broker commissions, and transfer charges
• Deadlines, cancellation rules, and the process for correcting an error

Account Push or Inter-Registrar Transfer?

An account push moves the domain between accounts at the same registrar. An inter-registrar transfer moves it to a different registrar. An internal push can involve fewer steps, but registrar rules vary and a change of registrant can still affect later transfer eligibility. Confirm the current registrar's policy before selecting the method.

For an inter-registrar transfer, ICANN explains that the registrant generally needs an AuthInfo code and that transfers can be blocked by registration, previous-transfer, or change-of-registrant lock periods. Review the current ICANN Transfer Policy before changing the registrant's contact details. Changing ownership first can create a 60-day lock that delays the buyer's intended registrar transfer.

What the Buyer Must Verify During Inspection

The inspection period is not merely time to notice that the domain appears in a dashboard. Verify that the receiving account is controlled by the buyer, the exact domain was delivered, the status and registrar are expected, and no unresolved condition prevents normal management.

• Sign in directly to the registrar rather than following a link supplied by the seller.
• Confirm the exact spelling, extension, expiry date, registrar, and domain status.
• Confirm that the buyer can manage contact details, nameservers, DNSSEC, renewal, and transfer lock settings.
• Check public registration data through ICANN Lookup, allowing for privacy redaction.
• Verify that website and email DNS records still match the agreed configuration.
• Enable the buyer's own two-factor authentication, recovery method, and auto-renewal.
• Retain screenshots, transaction messages, invoices, and the closing statement.

Escrow.com's inspection-period guidance states that its parties agree to a period of 1-30 calendar days and that the period begins after delivery is recorded or verified. If no action is taken before the agreed period ends, funds may be released. Use a period long enough to complete the checks the transaction actually requires.

What the Seller Must Verify

The seller should confirm the transaction inside the escrow provider's own account, not through an email attachment or look-alike website. Do not transfer until the provider marks the buyer's funds as secured and instructs the seller to proceed. Confirm the receiving account carefully; transferring to the wrong registrar account can be difficult to reverse.

Before delivery, preserve evidence of ownership, current DNS, registration status, and communication with the buyer. Remove unrelated products from the registrar account and never share the master account password. Transfer the domain through the registrar's supported push or AuthInfo process.

What Escrow Does Not Protect You From

• Overpaying for a domain with weak commercial value
• Trademark conflict or another party's prior rights
• A spam, malware, backlink, or reputation history
• Restrictions imposed by the registry or top-level domain
• Assets that were discussed but omitted from the transaction terms
• Tax, accounting, or legal consequences of the purchase

Complete the checks in the premium domain guide before agreeing a price. If the purchase will become a core company asset, follow the security controls in How to Protect Your Domain immediately after delivery.

Fees, Timing, and Payment Terms

Fees and payment availability change by transaction amount, payment method, currency, jurisdiction, and service level. Use the provider's live calculator rather than copying an old percentage from a blog. Escrow.com says the parties can agree for the buyer to pay all fees, the seller to pay all fees, or each party to pay half. Record that choice explicitly in the transaction.

Do not promise a closing date until transfer eligibility and the funding method are known. Bank processing, identity verification, registrar approvals, transfer locks, and the inspection period can all affect timing.

Domain Escrow Red Flags

• A seller or broker sends a slightly misspelled escrow URL.
• Either party asks to move payment outside the agreed service after funding begins.
• The seller refuses to prove control or specify the current registrar.
• The transaction description contains a different domain or extension.
• The buyer is pressured to accept before completing inspection.
• The receiving account is changed at the last minute without written confirmation.
• The deal includes a trademark, website, or social account but no separate transfer terms.

The Safe Closing Checklist

• Both parties accepted precise written terms.
• The provider confirmed that buyer funds are secured.
• The correct domain reached the correct buyer-controlled account.
• The buyer completed ownership, status, DNS, renewal, and security checks.
• Any website, trademark, content, or social assets were transferred separately.
• The buyer accepted only after every agreed condition was satisfied.
• Both parties retained the final transaction and closing records.

After closing, secure the wider identity using the domain, social, and trademark checklist. Escrow completes the purchase; it does not complete the brand transition.