A domain transaction has two separate things to coordinate: payment and control of the registration. Escrow or a marketplace workflow can help hold or verify funds while a transfer is completed, but the parties still need to use the correct provider, follow its instructions, and protect account credentials.
Quick answer: agree on an independent, reputable transaction process before transferring the domain. Verify the provider’s official site and the transaction status in your account. Transfer control only at the step specified by the verified workflow; never rely on a payment screenshot or an unexpected email.
What escrow does—and does not do
In a typical escrow workflow, a buyer submits payment to a provider; the provider confirms the required condition; the seller transfers the domain; and the provider releases payment according to the agreement. The exact sequence, fees, service availability, and dispute process vary by provider and transaction.
Escrow does not automatically confirm that a domain is free of legal disputes, guarantee a particular transfer speed, or protect parties who ignore the instructions. Some marketplaces operate their own transaction service; others use an outside provider. Read the agreement before accepting.
Same-registrar push vs. inter-registrar transfer
A registrar account push moves a domain from one customer account to another within the same registrar. It can be convenient, but the seller must verify the recipient account and the registrar’s process.
An inter-registrar transfer moves management to a different registrar. It may require an authorization code, a transfer lock change, contact verification, or other steps under extension policy. It can take a different path from a same-provider push. Neither method should be started from an unverified email link.
Before the transaction, confirm the exact domain, extension, registrar, recipient, DNS plan, and which party initiates the process. Save the existing DNS zone and note whether email or a live website depends on it.
A safe transaction sequence
- Agree in writing. Confirm the domain, gross price, currency, fees, included services, payment route, and transfer method.
- Select the provider together. Verify the official provider domain independently. Be alert to look-alike URLs and sponsored search results.
- Read the terms. Check identity requirements, fee responsibility, release conditions, timelines, cancellation, and dispute procedures.
- Open the transaction in the official account. Use a bookmarked provider address or type it yourself; do not trust only an emailed link.
- Verify payment status. The seller should confirm funds in the official transaction account, not from an image, PDF, or forwarded email.
- Transfer through authorized controls. Use the provider’s transfer steps; never share the registrar password. If a code is required, send it only through the approved channel and when instructed.
- Confirm receipt. The buyer checks registration control and records; the seller checks that the domain has left the account and waits for the provider’s release condition.
- Close the record. Save receipts, agreement, transfer confirmation, and applicable tax documents.
Scam patterns to watch
- A buyer sends a fake escrow link that imitates a known company.
- A message says payment cleared and pressures the seller to transfer immediately.
- A buyer requests the registrar password or asks to bypass the marketplace.
- A seller is told to pay a “release fee” to an unrelated address.
- A fake appraisal or inspection request asks for a paid service before the buyer will continue.
- A look-alike email domain spoofs a marketplace employee.
Verify every instruction from inside the provider’s official site or through a known support channel. Do not scan QR codes or open unexpected attachments to check payment. Keep account credentials and recovery codes private.
Protect the services that use the domain
The registration transfer may not change DNS, but confirm the plan. A new owner may need the domain pointed to different nameservers or kept unchanged temporarily. The seller should remove personal data and migrate email or site accounts as agreed. The buyer should check DNS, certificate, redirects, and service access after control is transferred.
If the name is tied to user accounts, a business email, or a production application, make a migration plan before closing. A domain transfer is not a data transfer, and escrow does not migrate website content or mailboxes.
Frequently asked questions
Can I use a normal bank transfer instead of escrow? It depends on trust, jurisdiction, transaction size, reversibility, and the parties’ risk. Understand the method and document terms; consider professional advice for a material transaction.
Does escrow guarantee payment? It follows its agreement and workflow; read the exact terms and verify the provider. No service eliminates every risk.
Should a seller provide the authorization code before payment? Follow the verified provider’s process. Do not send credentials or codes to an unverified person.
Who pays escrow fees? The parties should agree in writing and check the provider’s current schedule.
Is an account push safer than a registrar transfer? The appropriate method depends on provider support and the transaction. Verify recipient details and use the agreed secure workflow.
This is general transaction guidance, not legal or financial advice. Fee structures, identity checks, and transfer procedures change; consult the selected provider’s current documentation.