How to Draft a Simple Domain Purchase Agreement
A domain name purchase agreement records the essential terms of a digital asset sale in plain language. It can be short, but it should still make clear who is buying, who is selling, which domain is changing hands, how much is being paid and when the transfer will happen.
For an Australian buyer, the agreement may involve an international domain such as .com or .net, an Australian business registered with an ABN or ACN, and a payment made in Australian dollars. The parties may also be located in different states, such as Sydney, Melbourne, Brisbane or Perth, so written terms reduce uncertainty about timing and responsibility.
A parked domain sale often begins through a landing page, email or messaging service. The listing may include the domain’s age, registration history and availability for negotiation. Those details can help establish commercial context, but the final agreement should rely on precise contractual wording rather than informal statements exchanged during price discussions.
A straightforward document is usually sufficient for a modest transaction, provided it identifies the asset and the handover process accurately. For a high-value name, a business-critical web address or a purchase involving several related domains, independent advice from an Australian solicitor and a reputable escrow provider is sensible.
Choose the Deal Structure Before Writing
Start by deciding whether the transaction is an outright domain sale, a lease-to-own arrangement, a licence or a sale bundled with other assets. A simple purchase agreement should state that ownership or registrant control will pass to the buyer after the agreed conditions are satisfied. Avoid describing the arrangement as a “transfer” if the seller is only granting temporary use.
The document should also clarify whether the sale covers the domain alone or includes a website, email accounts, logos, social media handles, databases, content or trademarks. A parked listing generally concerns the domain name only. If the parties have discussed branding materials or a developed website, those items need their own description, price and delivery terms.
The commercial deal may be agreed by email before the formal document is signed. Even then, the written agreement should replace vague references such as “the website” with the exact domain, including its extension. A buyer negotiating from Melbourne for a .net name should see the full spelling in the contract, with no reliance on screenshots or an abbreviated trade name.
Identify the Parties and the Domain
List the seller’s legal name, residential or business address and email address. If the seller operates through an Australian company, include its registered company name and ACN. If the buyer is a company or trust, identify the correct contracting entity rather than naming only an individual employee or trading brand. An ABN can be added where relevant, although it does not replace the legal name.
The domain should appear in a dedicated asset description. Include the exact name, extension, current registrar and, where useful, the expiry date. For a name such as FRANNIELINDSAY.NET, the agreement can state that the asset is the domain registration and associated registrant control, not an assumption that the seller owns every possible trademark or business name containing those words.
A short schedule can record the domain’s current status, registration age and known history. These facts should be checked against registrar records or a recognised history service. General background on building a business around a parked name is available in brand-building context, but marketing potential should not be treated as a promise of future traffic, ranking or revenue.
Set the Price and Payment Terms
State the purchase price in a specific currency, such as AUD $2,500. If the parties are in Australia but the registrar or seller uses another currency, explain who bears exchange-rate movements, bank charges and international transfer fees. A price written as “$2,500” without identifying Australian dollars can create an avoidable dispute.
Specify when payment is due and whether it is paid in one amount or instalments. A common arrangement is a deposit on signing, followed by the balance once the domain has been moved to the buyer’s registrar account. Instalments should include due dates and explain what happens if a payment is late.
For a transaction between Australian businesses, state whether the price includes GST. A seller registered for GST may need to issue a tax invoice, while a private seller may not charge GST. The agreement can say “plus GST if applicable” or specify an all-inclusive price, but the wording should match the seller’s actual tax position.
Payment methods should be described carefully. Bank transfer, card payment, PayID and escrow each have different risks and timing. Escrow is often suitable where the buyer and seller have never dealt with each other: the buyer pays the escrow service, the seller transfers the domain, and funds are released after the agreed verification step. Never treat a payment receipt alone as proof that control has changed.
Define the Transfer Process
The contract should explain exactly how the domain will be delivered. Depending on the extension and registrar, the process may involve unlocking the domain, obtaining an authorisation code, changing the registrant, pushing the domain to another account or transferring it to a new registrar. The seller should identify any transfer lock, privacy setting or verification requirement that could delay completion.
Set a deadline, such as three business days after cleared funds are received. Include the information each party must provide, including registrar account details, transfer codes and identity verification. The buyer should create or nominate an account before completion, using an email address that will remain under the buyer’s control.
For an Australian buyer acquiring a .au domain, eligibility and local presence rules may apply. A .au transfer can require the buyer to satisfy auDA requirements, and the registrar may request evidence of an Australian connection or business identity. A .net domain does not follow those .au rules, but the registrar’s own transfer procedures still matter.
State when completion occurs. It might be when the buyer receives control of the registrar account, when the registrant details are updated, or when the transfer is confirmed by the registrar. The agreement should also say who pays renewal fees due during the transfer and who is responsible for keeping the domain active until handover.
Record Warranties and Risk
The seller should promise that they have authority to sell the domain and that no other person has a conflicting sale agreement, security interest or contractual claim over it. The seller can also confirm that, to the best of their knowledge, the domain is not subject to a registrar suspension, court order or unresolved dispute.
A buyer should avoid asking for absolute promises about search-engine rankings, visitor numbers, backlinks, advertising income or future brand value. A domain’s age may be commercially interesting, but it does not guarantee stronger rankings or a profitable website. Specialist markets illustrate why context matters; an analysis of niche domain value can inform a buyer’s assessment without becoming a warranty in the sale contract.
The agreement can state that the buyer has inspected the domain and accepts it in its present condition, subject to the seller’s express warranties. That clause should not be used to conceal known problems. If the domain has previously hosted content, been used for email or received complaints, disclose material information that could affect the buyer’s decision.
Include a sensible remedy if the seller cannot transfer the domain. The buyer may receive a refund, while a deposit may be retained only if the contract clearly permits it. For a valuable domain, the parties may negotiate a liability cap, but it should not attempt to exclude liability for fraud or deliberate misconduct. Australian legal rules can affect the validity of exclusion clauses, so high-value deals deserve professional review.
Include Practical Protections
Short agreements become more useful when they cover the small operational details that are easy to overlook. The parties should consider electronic signing, notices, confidentiality and the law that governs the contract. An Australian agreement may nominate the law of New South Wales, Victoria or another relevant jurisdiction, along with the courts that may hear a dispute.
A dispute clause can require the parties to communicate in good faith before starting proceedings. It may set a period for resolving registrar problems or payment disagreements. The clause should remain practical: a buyer in Adelaide and a seller in Brisbane should be able to send notices by email and preserve evidence of the transaction.
Useful points to address include:
- The exact domain name, extension, registrar and current expiry date
- The purchase price, currency, GST treatment, deposit and payment deadline
- The transfer method, authorisation code process and completion date
- Responsibility for renewal fees, registrar charges and escrow costs
- Seller warranties about authority, disputes, suspension and competing claims
- Remedies for non-payment, failed transfer, delay or inaccurate information
Avoid copying a lengthy technology contract when the transaction is simple. Overly broad clauses can introduce confusion about intellectual property, personal information or services that are not part of the deal. The best document matches the size and risk of the transaction while leaving little room for disagreement about the handover.
Sign, Store and Complete the Handover
Before signing, compare the agreement with the negotiation record and confirm that the final amount has not changed through an overlooked fee or tax term. Check every character of the domain name, especially hyphens, doubled letters and the extension. A typo in the asset description can undermine an otherwise carefully written sale document.
Electronic signatures are commonly used for commercial transactions in Australia, provided the parties can show who signed and what document was accepted. Each party should receive the same final PDF, with the signing date recorded. Keep payment records, identity checks, registrar messages and transfer confirmations with the agreement rather than relying on a messaging app that may later delete or rearrange the conversation.
After the transfer, the buyer should change the registrar password, enable multi-factor authentication, confirm recovery contacts and review the domain’s nameservers. The buyer should also check that privacy settings, DNS records and renewal notifications are directed to the correct accounts. If email has ever been connected to the domain, inspect the relevant records before changing them.
The seller should remove the domain from personal registrar profiles and confirm that no auto-renewal payment method remains attached. Once both parties have verified control and payment, a brief completion email can record the handover date. That final record helps establish when the simple domain purchase agreement was performed and closes the transaction cleanly.