Once a buyer and seller agree on a price, the next priority is documenting the deal before either side sends funds or begins a transfer. A domain purchase agreement gives both parties one written reference for the name being sold, the payment obligation, the transfer route, and the outcome if something does not go as planned. It is not a substitute for qualified legal advice, registrar requirements, or payment-provider instructions. It is the record that helps the parties avoid relying on scattered emails, chat messages, and assumptions.
For a direct sale, plain language is usually more useful than a long document filled with vague boilerplate. Each clause should answer a practical question: who is responsible, what must happen, by when, and what evidence shows that it happened? Review deal-specific language with a qualified attorney, especially for high-value names, company purchases, international payments, or transactions involving other intellectual-property assets.
Start with the exact deal and the people making it
Identify the seller and buyer by their legal names, business names if applicable, physical addresses, email addresses, and a reliable notice method. If a company is buying or selling, identify the individual signing and their authority to act for that company. State the exact domain in full, including its extension, such as example.com. If more than one name is included, attach a complete list. Also state whether the sale covers only the registration rights to the domain or specifically includes other assets.
Separate the agreement from escrow instructions
A domain name sales agreement records the bargain between buyer and seller. Escrow instructions, when the parties elect to use an escrow provider, tell that provider how to handle funds and what release conditions apply. They serve related but different purposes. The agreement should name the selected payment or escrow method, identify who opens the transaction, state who pays any applicable charges, and say which written instructions control if the documents differ. Do not assume an escrow workflow resolves every issue about ownership promises, deadlines, refunds, or disputes; address those items expressly.
Use this core agreement checklist
The following sections form a practical starting point. They should be tailored to the domain, registrars, payment method, parties, and applicable law rather than copied blindly from another sale.
| Section | What to state clearly |
|---|---|
| Parties and notices | Legal names, contact details, authorized signers, and where formal notices must be sent. |
| Domain and included assets | The exact domain name, current registrar, and whether websites, email, content, trademarks, or accounts are excluded or included. |
| Price and currency | Total purchase price, currency, deposit if any, payment deadline, and allocation of escrow, registrar, bank, or other transaction charges. |
| Payment conditions | When payment is due, when funds are considered cleared, and the event that permits release to the seller. |
| Transfer method | Whether the name will be pushed between accounts at the same registrar or transferred to another registrar, plus the required account details and approvals. |
| Seller representations | The seller’s stated authority to transfer the name, present control of the registration, and any disclosed restrictions, claims, or pending disputes. |
| Failure and remedies | Deadlines, cure periods, cancellation rights, refund handling, and who takes the next step if payment or transfer stalls. |
| Completion record | The evidence required to confirm delivery, receipt, payment release, and the date the transaction is complete. |
Write the transfer plan as a sequence, not a promise
A transfer clause should read like a short operational checklist. Specify the current registrar, the intended destination account or gaining registrar, the person responsible for unlocking the name, the party who supplies account details or an authorization code, and the deadline for each action. For many generic top-level domains, ICANN’s Transfer Policy includes rules affecting authorization codes, transfer locks, and changes of registrant. A change of registrant can trigger a 60-day inter-registrar transfer lock unless the registrar offers, and the registrant uses, an available opt-out. Confirm the registrar’s current process before choosing the sequence. ([icann.org](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy?utm_source=openai))
For a secure domain name transaction, neither side should treat an email saying “transferred” as the finish line. The buyer should confirm that the domain appears in the intended registrar account with the expected control. The seller should confirm that the agreed payment condition has been met. Both parties should retain the agreement, payment record, registrar notices, and a written completion confirmation.
Allocate problems before they happen
Good documentation anticipates ordinary friction. State what happens if the domain is locked, expires during the process, has an incorrect account destination, or cannot be transferred by the stated deadline. A sensible clause identifies who must cure the issue, how long they have, whether the other party may cancel, and how funds are handled after cancellation. Avoid declaring that a domain comes with trademark rights, a logo, website content, customer data, or social accounts unless those items are specifically identified and properly documented. The USPTO notes that trademark ownership changes have their own assignment and recordation considerations. ([uspto.gov](https://www.uspto.gov/trademarks/trademark-assignments-change-search-ownership?utm_source=openai))
Close the file with a short written confirmation
After the transfer and payment conditions are satisfied, exchange a dated written confirmation that identifies the domain, confirms completion, and notes any remaining administrative step. This creates a clean record for the buyer’s asset files and the seller’s transaction records. Parties who negotiate directly through a marketplace can keep the discussion organized from the outset: browse domain listings, use a DomainsNoBroker account to communicate around owner-listed opportunities, and consult the DomainsNoBroker blog for additional direct-sale guidance. Payment, escrow, legal review, and transfer arrangements remain matters for the parties to choose and document.
Frequently Asked Questions
Do both parties need to sign a domain sale agreement?
A signed writing or another clearly documented acceptance method can help show that both parties agreed to the same terms. The appropriate signing process depends on the parties, jurisdiction, transaction value, and legal advice. For a company, confirm that the person signing has authority to bind the business.
Does an agreement replace using escrow for a domain sale?
No. The agreement documents the parties’ deal, while escrow instructions govern the selected escrow process. If escrow is used, make the payment milestones, release conditions, fees, and any conflicting instructions consistent with the agreement before funds are sent.
Should the agreement include a registrar transfer deadline?
Yes. Set realistic deadlines for unlocking the domain, providing destination-account details, initiating the transfer, confirming receipt, and releasing payment. Build in time to address registrar requirements, account verification, and any transfer lock that may apply.
What should happen if the seller cannot transfer the domain?
The agreement should state whether the seller receives a cure period, what proof is required, when the buyer may cancel, and how any held funds are returned or released. A lawyer can help tailor this clause to the payment structure and governing law.