BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Escrow.com Walkthrough: How to Buy a Domain Safely, Step by Step, With Fees and Timing in 2026
Escrow.com is the neutral third party that holds a buyer’s money while a domain changes hands, then releases it only once the transfer is verified. For a private domain purchase between two strangers, it is the mechanism that stops a buyer paying first and receiving nothing, or a seller transferring first and getting stiffed.
This walkthrough runs the full transaction from both seats. It covers the five phases Escrow.com defines, the exact eight steps to complete a purchase, the three ways a domain moves, the inspection period, the fee schedule with a worked total, and the one ICANN rule that surprises buyers after the deal closes. Every figure is cited to a real source.
It also marks the line that matters to anyone sourcing a domain for SEO. Escrow protects a private deal with an unknown counterparty. When the name comes from a screened catalogue with accredited transfer built in, that protection is already part of the purchase. SEO Domains operates that marketplace, so you know which tool the moment calls for.
What is Escrow.com, and why route a domain purchase through it?
Escrow.com is a licensed online escrow service that sits between a domain buyer and seller. The buyer pays Escrow.com instead of the seller, Escrow.com holds the funds in a trust account, the seller transfers the domain, and the money is released only after the transfer is confirmed. It removes the trust gap in a private deal between two parties who do not know each other.
The problem escrow solves is old. In a direct deal one side has to move first. If the buyer pays first, a dishonest seller can vanish with the cash. If the seller transfers first, a dishonest buyer can take the domain and never pay. Escrow.com breaks that standoff by holding the money in the middle, so neither party is ever exposed to the other.
The trust-account model
Escrow.com describes itself as the largest online licensed and audited escrow operator, and states that more high-value domains are sold through it than anywhere else. The mechanism is a trust account. Funds enter that account, sit outside the seller’s reach, and leave it only when Escrow.com is satisfied the domain has moved to the buyer. The buyer can confirm ownership directly with the registrar before the seller is ever paid.
When a buyer reaches for it
Escrow earns its fee in a private, peer-to-peer purchase: you found a domain owner directly, agreed a price over email or a forum, and now have to exchange a four-figure or five-figure sum with someone you have never met. That is the canonical case. A purchase already running through a managed marketplace or a registrar with built-in payment protection is a different situation, covered in the final section.
Escrow earns its fee here
A private deal with an unknown counterparty, a high-value name, a wire or international payment, or any situation where one party would otherwise have to move first and trust the other to follow.
Escrow is already handled here
A purchase through a managed marketplace, a registrar with native buyer protection, or a screened catalogue where accredited transfer and payment safety are built into the listing.
The Escrow.com domain transaction, end to end
Escrow.com runs every domain deal through five phases: both parties agree to terms, the buyer pays Escrow.com, the seller transfers the domain, the buyer inspects and accepts, and Escrow.com releases the funds to the seller. The buyer’s money is never with the seller until the transfer is verified, and verification runs through a WHOIS lookup or buyer confirmation.
The five phases are the spine of the whole service. Each phase has a clear hand-off, and the transaction cannot advance until the current phase closes. Reading them in order is the fastest way to see why the model is safe for both sides.
Agreement. Both parties register on Escrow.com and agree to the terms, which include the domain name or names, the sale price, the inspection period, and who pays the fee. Source: Escrow.com, how-it-works.
Buyer pays. The buyer submits payment to Escrow.com for the agreed amount. Once the payment is verified and secured in the trust account, the seller is instructed to begin the transfer.
Domain transfer. The seller transfers the domain to the buyer and notifies Escrow.com, or hands the name to Escrow.com’s concierge service to deliver. The transfer itself runs at the registrar.
Inspection and acceptance. When the buyer reports possession, or Escrow.com confirms the change through a WHOIS lookup, the inspection period begins. The buyer accepts once the agreed terms are met.
Disbursement. Escrow.com releases the funds to the seller once the transfer is verified or the inspection period ends. The transaction is then complete. Source: Escrow.com, how-it-works.
Step by step: completing a domain purchase on Escrow.com
From a buyer’s seat, a domain purchase on Escrow.com runs in eight concrete steps: agree the deal, start the transaction, set the terms, fund the escrow, prompt the seller to transfer, receive the domain, inspect it, and accept. Each step has a matching seller action and a specific point where deals go wrong. This is the practical execution behind the five phases.
The five phases describe the structure. The eight steps below are how a buyer clicks through it in practice, with the failure point flagged at each one. Read it as the checklist to run a deal start to finish.
-
Agree the deal in writing first
Before touching Escrow.com, settle the price, the exact domain, and anything bundled with it, such as a logo, content, or a secondary name. DomainSherpa advises naming every included asset in the agreement so the inspection later has a clear standard to check against.
The mistake: a vague verbal price with no written scope. If the buyer expected the logo and the seller did not include it, the dispute lands in the inspection period with no agreed terms to settle it.
-
Start the transaction and invite the other party
Either party opens the transaction on Escrow.com and invites the other by the email tied to their account. Both must register. Confirm the counterparty has received and accepted the invitation before going further.
The mistake: inviting the wrong email address. A typo sends the invitation into the void, and the deal stalls before it starts.
-
Set the terms: price, fee split, inspection period
Enter the agreed price, choose who pays the escrow fee, and set the inspection period in days. The fee can fall on the buyer, the seller, or split between both, and that choice is part of the negotiation, not a fixed rule.
The mistake: setting a long inspection period out of caution. A 14-day window means the seller waits 14 extra days for payment, which sours an otherwise clean deal.
-
Fund the escrow
The buyer pays Escrow.com using an approved method. Wire transfer, check, and money order sit in the standard fee tier. Credit card and PayPal sit in the higher premier tier and add cost, a difference the fees section sets out in full.
The mistake: paying by card without checking the premier surcharge. The convenience fee can dwarf the base escrow fee on a small transaction.
-
Prompt the seller to transfer
Once Escrow.com confirms the funds are secured, the seller is cleared to move the domain. The buyer supplies whatever the chosen transfer method needs, usually the receiving account email for a push or the receiving registrar for an authorization-code transfer.
The mistake: the buyer giving the seller a registrar account email that does not exist or is mistyped. A push to a wrong address can strand the name in a third party’s account.
-
Receive the domain
The domain arrives by registrar push, by authorization code, or by handover of login credentials. Confirm it now sits in your own registrar account under your control, not merely promised.
The mistake: reporting possession on the seller’s word alone. Possession means the name is in your account, visible in your registrar dashboard, not an email saying it is on its way.
-
Inspect against the agreed terms
Check the domain matches the agreement: the right name, the full registration period, any bundled assets, and a clean WHOIS now showing the buyer. This is the only window to raise a problem before the money is released.
The mistake: skipping inspection to be polite. Once you accept, the funds release, and the leverage to fix a shortfall is gone.
-
Accept and close
When everything checks out, accept the transaction. Escrow.com releases the funds to the seller, and the deal is complete. If the inspection period ends with no action, Escrow.com can close it automatically once transfer is verified.
The mistake: accepting before the WHOIS reflects you. Accept only when the registrar record confirms the change, because acceptance is the irreversible step.
Choosing the transfer method: push, auth code, or login
A domain moves through Escrow.com in one of three ways: a registrar push between accounts at the same registrar, an authorization-code transfer to a different registrar, or a handover of the seller’s login credentials. A push is the fastest and cleanest, the authorization code is the standard cross-registrar route, and a credential handover is the weakest option, used only as a last resort.
The method decides how fast the domain arrives and how much can go wrong. Escrow.com’s concierge accepts a name by push or by authorization code, and DomainSherpa notes a push is the quicker route when both parties sit at registrars like GoDaddy or Enom. The matrix below sets out the trade-off.
| Method | How it works | Speed | When to use it |
|---|---|---|---|
| Registrar push | Seller pushes the domain to the buyer’s account at the same registrar. No registrar change. | Minutes to hours | Both parties hold accounts at the same registrar. The cleanest route. |
| Authorization code | Seller unlocks the domain and shares the EPP authorization code. Buyer initiates a transfer to a new registrar. | Up to several days | Buyer and seller are at different registrars. The standard cross-registrar method. |
| Login credentials | Seller hands over the account username and password so the buyer takes control directly. | Immediate but risky | Last resort only. Mixes the seller’s other assets and security into the deal. |
The inspection period and how ownership is verified
The inspection period is the window after the domain reaches the buyer in which they confirm it matches the deal before accepting. Escrow.com verifies the transfer through a WHOIS lookup that shows the buyer as the new registrant, or through the buyer’s own confirmation. Once the buyer accepts or the period ends with the transfer verified, the funds release and the deal is irreversible.
This is the buyer’s safety valve, and it is the phase where the value of escrow becomes concrete. The buyer holds the leverage of an unreleased payment until the domain is confirmed in their name. Used well, it guarantees the buyer never pays for a name they did not receive.
How the transfer is verified
Escrow.com confirms the change through WHO.IS, the public record of who holds a domain. When the buyer reports possession, or the WHOIS lookup shows the registrant has changed to the buyer, the inspection clock starts. The buyer then has the agreed number of days to check the name against the terms and accept.
The ICANN 60-day lock that follows the deal
One rule catches buyers after a clean close, and competing walkthroughs skip it. Under the ICANN Transfer Policy, in effect since 1 December 2016, a registrar must apply a 60-day lock that prevents transferring the domain to a different registrar for 60 days after a change of registrant. The lock exists to give the previous owner time to spot an unauthorized change, and it cannot be shortened once it applies.
The practical effect is that a name received by authorization-code transfer, then re-registered under the buyer, can be frozen against a further registrar transfer for two months. A buyer who plans to consolidate the name elsewhere right away needs to plan around that window. The lock does not block DNS changes, renewals, or use of the domain, only the move to a new registrar.
| After a change of registrant | Status |
|---|---|
| Transfer to a new registrar | Locked for 60 days, and the lock cannot be shortened |
| Changing DNS or nameservers | Allowed, the lock does not touch DNS |
| Renewing the domain | Allowed |
| Using or building on the domain | Allowed, ownership is fully yours |
| Opting out before the change | Some registrars allow it, but they are not required to |
What it costs: the Escrow.com fee schedule and who pays
Escrow.com charges a tiered fee that falls as the transaction value rises: 2.6% with a $50.00 minimum on the $0 to $5,000 band, down to 0.7% above $10 million. Card and PayPal payments sit in a higher premier tier. The fee can be paid by the buyer, the seller, or split, and that split is set when the terms are agreed.
The headline question every buyer asks is the cost, and the answer is a published schedule, not a quote. The table below is the standard tier, taken directly from Escrow.com’s fee schedule. The concierge service, where Escrow.com handles the transfer itself, adds a separate charge covered in the next section.
| Transaction value (USD) | Escrow fee | Minimum fee |
|---|---|---|
| $0 to $5,000 | 2.6% | $50.00 |
| $5,000.01 to $50,000 | 2.4% | $130.00 |
| $50,000.01 to $200,000 | 1.9% | $1,200.00 |
| $200,000.01 to $500,000 | 1.5% | $3,800.00 |
| $500,000.01 to $1,000,000 | 1.2% | $7,500.00 |
| $1,000,000.01 to $5,000,000 | 1.0% to 0.95% | $12,000.00 and up |
| Above $10,000,000 | 0.7% | Enquire for a quotation |
A worked total on a real deal
Take a $2,000 domain, a typical range for a private SEO purchase. The deal sits in the $0 to $5,000 band at 2.6%, which works out to $52, above the $50.00 minimum, so the fee is $52. If buyer and seller split it, each pays $26. Pay by wire and that is the whole cost. Pay by credit card and the premier tier applies, roughly doubling the percentage, so the fee on the same deal climbs toward $104 before the split.
Who pays the fee
The fee is not fixed to one side. Escrow.com lets the buyer, the seller, or both share it, and the choice is part of the negotiation. DomainSherpa notes that offering to split or absorb the fee is a recognised tactic to close a deal that is stalling. On a high-value name where the percentage is small, the fee rarely decides anything. On a low-value name where the $50.00 minimum bites, who pays it is worth settling up front.
The concierge and domain-holding service: when it earns its fee
The Escrow.com Domain Concierge Service has Escrow.com hold the domain in its own registrar account during the transaction and manage the transfer to the buyer, instead of leaving it to the seller. It works with all major registrars, accepts a domain by push or authorization code, and charges a separate fee on top of the standard escrow fee. It earns that fee on complex, high-value, or cross-registrar transfers where a mistake is costly.
The concierge exists for the deals where the transfer itself is the risk, not the payment. Instead of trusting the seller to move the name correctly, the parties hand it to Escrow.com, which holds it securely and delivers it. The trade is a smoother, supervised transfer for an added charge.
What the concierge does
Escrow.com’s concierge takes receipt of both the funds and the domain, verifies the name against the purchase agreement, and completes the transfer to the buyer. It holds the domain in Escrow.com’s registrar account throughout, accepts delivery by push or by authorization code, and works across all major registrars. The buyer gets a transfer managed by the service instead of by a counterparty they cannot vouch for.
Self-managed transfer
The seller moves the domain directly to the buyer. Lowest cost, the standard escrow fee only. Best for straightforward, same-registrar, lower-value deals where both parties are confident with a push or an authorization code.
Concierge-managed transfer
Escrow.com holds and delivers the domain. Higher cost, a premier and concierge charge on top of the escrow fee. Best for high-value names, cross-registrar moves, or a seller who is unfamiliar with the mechanics.
Every layer of cost and risk in this section, the premier surcharge, the concierge fee, the transfer mistakes, exists to make a cold private deal safe. A purchase from a screened catalogue removes that overhead at the source: when an aged or expired domain is acquired from the SEO Domains marketplace, the transfer already runs under ICANN-accredited handling and the protection escrow adds is part of the purchase, so the concierge math rarely applies.
Common Escrow.com mistakes and how to avoid them
The mistakes that derail an Escrow.com domain deal are a short, repeatable list: a vague written agreement, a wrong account email on a push, paying by card without checking the premier surcharge, setting the inspection period too long or too short, accepting before WHOIS confirms the transfer, and forgetting the 60-day post-transfer lock. Each has a one-line fix, and the fixes describe a clean deal.
The table below consolidates every failure point flagged in the steps above into one scannable reference. The left column is the mistake, the centre column is why it bites, and the right column is the fix. Run it as a pre-flight checklist before you open a transaction.
| The mistake | Why it bites | The fix |
|---|---|---|
| Vague or verbal agreement | The inspection has no agreed standard, so a bundled-asset dispute cannot be settled | Name the price, exact domain, and every included asset in writing before opening the deal |
| Wrong account email on a push | A push to a mistyped or non-existent account can strand the domain with a third party | Confirm the receiving account email character by character before the seller pushes |
| Paying by card without checking fees | The premier tier on card and PayPal can double the escrow fee on a small deal | Pay by wire for the base tier unless the card surcharge is worth the convenience |
| Inspection period set too long | The seller waits the full window for payment, which sours a clean deal | Set the shortest period that still lets the buyer verify the transfer |
| Inspection period set too short | A slow registrar transfer can outrun the window before the buyer can verify | Leave enough room for a cross-registrar transfer, which can run for days |
| Accepting before WHOIS confirms | Acceptance releases the funds and is irreversible | Accept only when the registrar record shows the buyer as the new registrant |
| Reporting possession on a promise | An email saying the name is on its way is not possession | Confirm the domain sits in your own registrar account before reporting it received |
| Forgetting the 60-day lock | A planned move to another registrar is frozen for 60 days after the registrant change | Plan any onward registrar transfer around the ICANN 60-day lock window |
Escrow.com domain frequently asked questions
The questions buyers and sellers raise when they search how to run a domain deal through Escrow.com, answered against the published process and fee schedule.
Q1How does Escrow.com work for a domain purchase?
The buyer pays Escrow.com, which holds the money in a trust account. The seller transfers the domain, Escrow.com confirms the change through a WHOIS lookup, the buyer inspects and accepts, and only then are the funds released to the seller. Neither party is exposed to the other, because the money sits with a neutral third party until the transfer is verified.
Q2What fees does Escrow.com charge?
A tiered fee that falls as the value rises: 2.6% with a $50.00 minimum on the $0 to $5,000 band, 2.4% from $5,000.01 to $50,000, and down to 0.7% above $10 million, per the Escrow.com fee schedule. Credit card and PayPal payments sit in a higher premier tier. The fee can be paid by the buyer, the seller, or split between both.
Q3How long does a domain transfer through Escrow.com take?
It depends on the registrar. Escrow.com states the transfer can run from minutes to up to six weeks, driven by how quickly the registrar moves the domain from seller to buyer. A same-registrar push is fastest; a cross-registrar authorization-code transfer takes longer. The inspection period the parties set adds to that timeline before the funds release.
Q4Is Escrow.com trustworthy?
Escrow.com describes itself as the largest online licensed and audited escrow operator, and it is a long-established name in domain transactions, discussed across DomainSherpa and NamePros community threads. The trust model rests on holding funds in a regulated trust account and releasing them only on verified transfer. As with any service, a buyer confirms ownership directly with the registrar before accepting.
Q5Why can I not transfer my domain after buying it through escrow?
Because of the ICANN 60-day lock. Under the ICANN Transfer Policy, in effect since 1 December 2016, a registrar applies a 60-day lock against transferring a domain to a new registrar after a change of registrant. The lock protects against unauthorized changes and cannot be shortened once it applies. It does not block DNS changes, renewals, or use of the domain, only the move to a different registrar.
Where escrow fits: a screened domain versus a private deal
Escrow protects a private deal with an unknown counterparty, which is exactly the situation it was built for. When a domain is acquired from a screened catalogue with accredited transfer built into the purchase, that protection is already part of the transaction. Knowing which situation you are in decides whether escrow is the right tool to add or a safeguard you already have.
This walkthrough exists because the private peer-to-peer deal is genuinely risky without a neutral party, and escrow removes that risk cleanly. The point worth being honest about is the other path. Not every domain purchase is a cold deal between two strangers, and the protection escrow provides is sometimes already in place.
The two situations, side by side
A private deal is the cold case: you found an owner, agreed a price directly, and now have to exchange money and a domain with someone whose only reputation is a forum handle. Escrow.com is the right answer there. A managed acquisition is different: the name comes from a curated marketplace where the backlink profile is screened, the transfer runs under an ICANN-accredited registrar, and payment safety is part of the listing instead of a service you bolt on.
Sourcing the asset, not just protecting the deal
The legitimate demand behind an Escrow.com search is a safe domain purchase. Escrow secures the exchange, but it does nothing about the quality of the name you are exchanging money for. A cleanly transferred junk domain is still a junk domain. That is why sourcing matters as much as the safe handover, and why a screened catalogue solves both at once: the name is vetted before listing, and the transfer is accredited.
The SEO Domains marketplace screens aged and expired domains across their backlink profiles and authority metrics before they are listed and priced, and every transfer runs under ICANN-accredited handling. When you buy a screened name there, the buyer protection escrow provides for a private deal is built into the purchase, so you spend the diligence on the domain instead of on the counterparty.
