Reaching agreement is not the same as completing a domain sale. The operational handoff deserves its own plan: verify the deal details, establish the registrar path, coordinate the release of control, and leave a clear record of what happened. This guide explains how to transfer a domain to a buyer without turning the transfer itself into another negotiation.
Keep commercial decisions and transfer actions separate. Price, payment method, tax treatment, and any written agreement should be settled before you expose an authorization code or start an ownership change. The steps below focus on the seller’s operational responsibilities after those decisions are in place.
Start with a pre-transfer confirmation
Before changing a setting at the registrar, send one concise written recap through the communication channel you have already used with the buyer. Include the exact domain name, agreed price and currency, the selected payment or escrow process, the buyer’s receiving registrar or account identifier, who pays any registrar transfer fee, and the intended handoff method. Ask the buyer to confirm those details from the same verified contact point.
A practical domain transfer checklist begins with these items:
- The domain spelling, extension, and current registrar are correct.
- The buyer’s recipient email or account ID has been checked character by character.
- The agreed payment-release event is written down.
- The domain is not being renewed, edited, or moved in another pending process.
- You have access to the registrant email address and registrar security settings.
Check eligibility before promising a transfer date
Log in to the registrar and review the domain’s status, expiration date, transfer lock, and any pending ownership or contact changes. For applicable gTLD transfers, ICANN’s Transfer Policy addresses AuthInfo codes, transfer locks, and approval steps. Rules and terminology can differ for country-code domains, so use the current registrar and registry guidance for that extension.
Do not change registrant contact information casually just before an inter-registrar transfer. ICANN notes that a change of registrant can trigger a 60-day transfer lock, subject to the applicable policy and any registrar opt-out option. Review the timing before making the change, rather than discovering the lock after the buyer has initiated a transfer request.
Choose the handoff path: account push or registrar transfer
There are usually two workable paths. If the buyer has an account at the same registrar and that registrar supports it, an internal account change or “push” may move the name without an inter-registrar transfer. Confirm the buyer’s account identifier directly and follow the registrar’s recipient-acceptance process. Never give the buyer your login credentials.
If the buyer wants the name at another registrar, the buyer normally starts an inter-registrar transfer after you unlock the domain and provide the authorization code. An AuthInfo code is a credential used in gTLD transfer processes; ICANN’s registrant transfer FAQ explains its role and common transfer restrictions. Generate or retrieve the code only when the deal is ready to proceed, and send it through the agreed secure channel.
Coordinate payment confirmation with the release of control
Agree in advance on the exact sequence: for example, payment confirmation first, then account push; or escrow confirmation, then authorization code; or buyer transfer initiation, then seller approval. The appropriate order depends on the parties’ chosen transaction arrangement. Do not rely on a forwarded email, edited screenshot, or unexpected message asking you to redirect the domain or change payment instructions.
Use the contact details already confirmed in the written deal recap if anything changes. A legitimate buyer can wait while you verify a new destination account, revised payment instruction, or unfamiliar email address. Pausing is usually less costly than trying to reverse an unauthorized handoff.
Execute the transfer and keep a simple event log
Complete only the actions required for the selected method. For an account push, capture the confirmation screen or email, then wait for any buyer acceptance requirement. For an inter-registrar move, unlock the name, obtain the authorization code, provide it as agreed, and monitor the registrar notices for a required approval or a denial reason.
Create a short event log with timestamps: payment or escrow milestone, unlock time, authorization-code delivery, buyer initiation notice, seller approval, and completion confirmation. Save PDFs or screenshots of registrar notices where permitted. This record is useful if the buyer asks about status or if a registrar support case becomes necessary.
Verify completion before closing the file
Completion means more than sending a code. Confirm that the registrar shows the domain in the buyer’s account or that the inter-registrar transfer has completed. Tell the buyer that the handoff is complete and ask them to confirm receipt. At that point, retain the agreement, correspondence, payment evidence, registrar notices, and your event log in one transaction folder.
Retention helps establish a clean transaction history, but it does not replace professional legal or tax advice. Preserve only the records you need, protect them with account security, and follow your own recordkeeping requirements.
Common delays and the seller response
| Delay | What to check | Seller response |
|---|---|---|
| Transfer cannot start | Lock status, recent registration, prior transfer, or contact change | Confirm the stated restriction and give the buyer a realistic next update. |
| Buyer did not receive a push | Recipient account ID, email address, and acceptance notice | Cancel or resend only after reconfirming the destination with the buyer. |
| Unexpected payment change | Whether the request came through a verified contact channel | Stop and verify independently before releasing control of the domain. |
| Transfer remains pending | Registrar notices, required approvals, and domain status | Document the status and contact registrar support with the event log if needed. |
Use direct communication without skipping controls
On a direct marketplace, the buyer and seller can agree on terms without inserting a broker into routine communication. After a buyer inquiry, you can browse domain listings, use the DomainsNoBroker blog for marketplace guidance, or contact DomainsNoBroker about the platform. The actual registrar handoff should still follow your documented sequence, verified counterpart details, and the applicable registrar rules.
The core principle of how to transfer a domain safely is simple: release control only when the agreed transaction milestone has occurred, and keep evidence of every meaningful step.
Frequently Asked Questions
How long does a domain transfer take after a sale?
Timing depends on the extension, registrar procedures, transfer method, and whether either side must approve a notice. An internal account push may follow a different timeline than an inter-registrar transfer. Check the current registrar workflow before committing to a completion date.
Do I need an authorization code to transfer a sold domain?
An authorization code is generally used for an inter-registrar transfer of an applicable gTLD. It may not be needed for an internal account push at the same registrar. Confirm the buyer’s intended destination and the registrar’s current instructions before generating or sharing it.
Should I change the buyer to the registrant before moving the domain?
Not automatically. For applicable gTLDs, a registrant contact change can create a 60-day transfer lock unless an available opt-out was selected. Review the registrar’s process and decide whether the inter-registrar move should happen before any registrant change.
What should a seller retain after the domain is transferred?
Keep the written deal terms, payment or escrow confirmation, buyer destination details, registrar emails, transfer timestamps, and final completion notice. These records help answer later status questions and may be relevant to your business, accounting, tax, or legal recordkeeping obligations.