What Should a Domain Purchase Agreement Include?
Agreeing on a price is only part of buying a domain name. The buyer also needs a clear route to receiving control, while the seller needs certainty about payment. A well-drafted domain purchase agreement connects those obligations and explains what happens if the transaction stalls, a representation proves inaccurate, or the parties disagree.
Identify the parties and the exact asset
Record each party’s full legal name, contact details, and, where relevant, company registration information. If a broker or employee signs, establish their authority to bind the buyer or seller.
Spell out the complete domain name, including its extension. For an internationalised domain, consider recording both its displayed form and its ASCII-compatible representation to prevent ambiguity.
Define the scope of the sale. Specify whether the price covers only the domain registration rights or also includes website content, trademarks, source code, customer data, or other assets. List any additional assets separately and describe how they will be delivered.
Also record the registrar and registration expiry date, and allocate responsibility for renewal if the domain could expire before completion.
Connect payment to a verifiable transfer
The payment clause should state the price, currency, payment method, and responsibility for escrow charges, transfer fees, bank costs, and applicable taxes. Explain whether a deposit is refundable and under what circumstances.
If the parties use escrow, align the agreement with the provider’s actual procedures. Specify when the buyer must fund the transaction, when the seller must begin the transfer, and what evidence permits payment release.
Define completion through registration and control. Sending an authorisation code alone should not satisfy the seller’s delivery obligation. The agreed evidence might include registrar confirmation that the buyer is the registered holder and can manage the domain through an account under the buyer’s control.
Distinguish a change of registrant from a move between registrars. Confirm which steps the transaction requires before setting deadlines.
Set workable deadlines
Use separate milestones for funding, initiating the transfer, completing required verification, and releasing payment. Define “business day” and the relevant time zone.
Include a final completion deadline, together with a procedure for documented registrar or registry delays. Avoid allowing either party to extend the transaction indefinitely.
For a .eu purchase, buyer eligibility deserves an explicit check: the EU regulation governing .eu domain names permits transfers only to parties eligible to register them. Make eligibility verification a condition of completion and allocate responsibility for supplying the necessary information.
Make seller representations specific
Seller representations describe facts the buyer is relying on. Useful provisions address whether the seller is the current registered holder, has authority to transfer the registration rights, and has already promised those rights to another buyer.
Ask the seller to disclose pending disputes, written infringement allegations, court orders, security interests, and restrictions that could prevent transfer. Attach relevant disclosures to the agreement so both parties can identify the exceptions.
Distinguish an absolute statement from a knowledge-qualified statement. “No claim has been received” and “the seller is unaware of any potential claim” cover different ground.
A seller’s assurance also cannot replace the buyer’s trademark investigation. Address the buyer’s intended use and relevant searches separately rather than treating the purchase as a guarantee of unrestricted commercial use.
Annotated clause checklist
Use this checklist to review the main domain sale contract clauses before signing. Each provision should describe an obligation or outcome that the parties can verify.
| Clause | What to include | Why it matters |
|---|---|---|
| Parties and authority | Legal identities, notice details, and signing capacity. | Identifies who owes the contractual obligations. |
| Domain and sale scope | Exact domain, extension, included assets, and exclusions. | Prevents disagreement over what the price buys. |
| Price and expenses | Currency, payment schedule, fees, and tax allocation. | Reduces unexpected costs and payment shortfalls. |
| Conditions before completion | Eligibility, identity checks, approvals, and required documents. | Establishes what must happen before closing. |
| Transfer procedure | Responsible parties, registrar steps, and required cooperation. | Turns a promise to transfer into actionable duties. |
| Completion and payment release | Objective evidence, inspection period, and escrow instructions. | Connects delivery with the release of funds. |
| Seller representations | Authority, registration status, competing commitments, and disclosed claims. | Records the facts supporting the buyer’s decision. |
| Interim obligations | Renewal, preservation of registration, and restrictions on further sales or changes. | Protects the domain while the transaction is pending. |
| Deadlines and termination | Milestones, permitted extensions, final deadline, and cancellation rights. | Provides an exit if completion becomes impossible. |
| Remedies and liability | Refunds, damages, claim procedures, limits, and relevant exceptions. | Allocates the consequences of breach. |
| Disputes and governing law | Applicable law, chosen forum, escalation steps, and urgent relief. | Gives the parties a defined route for resolving disagreements. |
| Notices and surviving duties | Notice method, confidentiality, post-transfer assistance, and surviving provisions. | Clarifies responsibilities that continue after completion. |
Explain what happens when something goes wrong
A remedies clause should distinguish between buyer non-payment, seller refusal to transfer, an inaccurate representation, and a transfer blocked by an external restriction. Those situations may justify different outcomes.
State when a party can terminate, whether a breach must first be notified, and how long the other party has to correct it. Address the return of funds, allocation of transaction costs, and any steps needed to unwind an incomplete transfer.
If compensation, indemnities, or liability caps are negotiated, define their scope and any exceptions. Specify how long relevant representations survive completion and when claims must be notified. Their enforceability requires assessment under the applicable law.
Escrow instructions should also explain what happens to held funds during a dispute. A contract between buyer and seller should not assume the escrow provider will follow instructions outside its accepted terms.
When jurisdiction-specific legal advice is useful
Legal review is particularly valuable when the parties are in different countries, the price is substantial, or the domain is essential to an established business. Advice can help determine whether the chosen law, court, or arbitration arrangement is effective and practical to enforce.
Seek tailored advice where:
- The buyer may be acting as a consumer.
- Payment involves instalments, financing, or retained security.
- A trademark complaint, insolvency, or disputed authority affects the seller.
- The transaction includes customer data, intellectual property, or a functioning website.
- The agreement contains non-refundable deposits, fixed breach payments, indemnities, or extensive liability exclusions.
Keep contractual disputes and domain registration disputes distinct when drafting the dispute clause. Ask counsel how the chosen process interacts with any applicable registry procedures and third-party rights.
Before signing, walk through the proposed transaction from funding to completion. Every step should identify who acts, by when, what evidence confirms success, and what happens if that step fails.