Short answer: After your payment clears into escrow, the seller either pushes the domain to your account at the same registrar (minutes to a few hours) or gives you an authorisation code so you can pull it to a different registrar (typically five to seven days, sometimes faster). You then confirm receipt, escrow releases the money, and the domain is locked against further transfer for 60 days. Almost every delay in this sequence comes from the buyer not having an account ready, or from an ICANN lock the seller forgot to mention.

The escrow sequence

A properly run domain sale through Escrow.com or a marketplace’s built-in escrow follows a fixed order, and you should not agree to any deviation from it.

  • Agreement. Price and terms are set, and both parties accept the escrow transaction. The escrow service typically charges a fee that is either split or paid by the buyer; who pays is part of the negotiation.
  • Buyer pays escrow. You wire funds or pay by card to the escrow company, not the seller. The escrow service confirms when funds have cleared, which for a wire is usually one to three business days.
  • Seller transfers the domain. Only after funds are confirmed does the seller move the domain, by push or by releasing the authorisation code. The seller is protected because the money exists; you are protected because the money has not moved.
  • Buyer confirms receipt. Once the domain shows in your registrar account, you confirm with the escrow service. Most services give you a short inspection window, and if you do not respond they will chase, then release after a set period.
  • Escrow releases funds to the seller. Done. Total elapsed time, from first payment to funds released, is typically three to ten business days.

The sequence is covered in more detail in how to buy a domain safely. The point here is what happens inside step three, because that is where timelines diverge.

Push versus transfer

Registrar push (account change) Registrar transfer (auth code)
When it applies Buyer and seller use the same registrar Buyer wants the domain at a different registrar
Mechanism Seller moves the domain to your account ID or email within the registrar’s panel Seller unlocks the domain and gives you an EPP/authorisation code; you initiate a transfer-in at your registrar
Time Minutes to a few hours; some registrars require you to accept the push Up to 5–7 days by default; many registrars complete in under an hour if the losing registrar approves immediately
Cost Usually free You pay a transfer fee at the new registrar, which typically includes a one-year renewal
Expiry date Unchanged Usually extended by one year
Post-move lock Often a 60-day transfer lock at the registrar’s discretion A mandatory 60-day lock under ICANN rules

If you do not have a strong preference about registrars, accepting a push is the fast path: open a free account at the seller’s registrar, receive the push, and transfer out later at your leisure once the 60 days have elapsed. For a four-character name like vuoq.com bought on a Monday, a push can have it live under your control by lunchtime.

The authorisation code and the ICANN transfer process

An authorisation code (also called an EPP code, auth-info or transfer key) is a password attached to the domain that proves whoever holds it is entitled to move it. The seller generates it in their registrar panel after removing the transfer lock, and gives it to you, ideally through the escrow service’s secure messaging rather than by email.

You then go to your chosen registrar, start a transfer-in, enter the domain and the code, and pay the transfer fee. The gaining registrar sends a request to the losing registrar. Under ICANN’s Transfer Policy, the losing registrar has up to five days to respond; if it does nothing, the transfer completes automatically. Most reputable registrars now let the current registrant approve immediately from their panel, which collapses the five days to minutes, so ask the seller to do that.

Two ICANN rules routinely surprise buyers. First, a domain cannot be transferred within 60 days of its initial registration or of a previous registrar transfer. If the seller moved the name to a new registrar last month, you must wait or accept a push instead. Second, after any change of registrant contact details, many registrars impose their own 60-day lock, so if the seller “tidied up” the WHOIS before the sale they may have inadvertently locked it. Check the status codes in WHOIS before agreeing a timeline. For context on how the extension affects none of this, see .com vs .io vs .ai vs .co; country-code extensions have their own transfer rules, but every .com follows the process above.

What the buyer must have ready

Most transfer delays are on the buyer’s side. Before funds clear, have the following in place.

  • A registrar account, verified and with a payment method attached. If accepting a push, this must be at the seller’s registrar; ask which one before you pay. If transferring, it can be any ICANN-accredited registrar you trust.
  • Accurate contact details on that account, because ICANN requires the registrant email to be verified; an unverified account can have the domain suspended within 15 days of the transfer.
  • Access to the email inbox on the account. Both pushes and transfers generate confirmation emails that sometimes require a click within a time limit. Check the spam folder.
  • Two-factor authentication switched on, since a freshly acquired premium domain is exactly what account thieves look for.
  • Your DNS plan. After a transfer, nameservers usually carry over, but after a push they may reset to the registrar’s defaults. Know where you want the domain pointed and have the zone ready.

Common failure points

  • Domain still locked. The seller sends an auth code without removing clientTransferProhibited. The transfer is rejected and nobody tells you why for a day. Confirm the lock is off in WHOIS before you submit the transfer.
  • Wrong or expired code. Some registrars expire auth codes after a short period or regenerate them on request. If the transfer fails with an authorisation error, ask for a fresh code rather than retrying the old one.
  • Within the 60-day window. As above. The fix is a push or patience; there is no override.
  • Privacy service blocking emails. If WHOIS privacy forwards confirmation emails to a proxy address the seller does not monitor, the approval email vanishes. The seller should disable privacy for the duration of the transfer.
  • Push to the wrong account. Account IDs at large registrars are easy to mistype. Give the seller your exact account identifier in writing, and confirm the domain’s arrival before confirming to escrow.
  • Buyer confirms too early. Do not release escrow because the seller says the push is “done”. Release when the domain is visible in your account and you have logged in to see it.
  • Expiry during transfer. A domain inside 30 days of expiry can get stuck in a pending-renew state at the losing registrar. Have the seller renew it first, or accept that a transfer adds a year anyway.

At a glance

  • Funds go to escrow first; the domain moves second; money is released last.
  • A push within the same registrar takes minutes; a transfer with an auth code takes up to a week, often less.
  • ICANN imposes a 60-day transfer lock after registration, after a transfer, and often after a registrant change.
  • Have a verified registrar account with 2FA ready before you pay, not after.
  • Confirm to escrow only when the domain is visible in your own account.

Frequently asked questions

Can I move the domain to my preferred registrar straight after a push?
Usually not for 60 days. Most registrars apply a transfer lock after an account change, and ICANN requires one after a registrant change. Plan to live with the seller’s registrar for two months; it is a minor inconvenience against the speed of a push.

Does the domain’s expiry date change when I buy it?
After a push, no; you inherit whatever is left and should renew promptly if it is short. After a registrar transfer, the transfer fee normally adds a year to the existing expiry, so a domain due in March becomes due the following March.

What if the seller disappears after I have paid escrow?
You are protected, which is the whole point of the sequence. The escrow service holds your money until the domain is delivered; if it is not delivered within the agreed window, the transaction is cancelled and funds return to you, less any non-refundable escrow fee. This is why paying a seller directly to “save the escrow fee” is a false economy.

From payment to control in days, not weeks

Sales on brandable.forsale run through escrow with the transfer method agreed upfront, so you know before paying whether to expect a same-day push or a standard transfer.

Browse domains ready to transfer →

Comments are disabled