Buying a domain name from another owner can be straightforward, but only when payment, ownership, transfer control, and legal use are checked in the right order. This reusable checklist explains how to buy a domain name safely, choose a suitable escrow process, verify the seller’s authority, negotiate clear terms, and accept the transfer without exposing your business to avoidable risk.
Overview
A private domain purchase is more than an agreement on a price. The buyer must receive control of the correct domain, while the seller must be confident that payment will be released under fair conditions. A safe domain purchase therefore has four parts: investigation, written agreement, controlled payment, and verified transfer.
Before contacting a seller, decide what you are actually buying. A domain-only transaction should identify the exact domain name and extension. It should not accidentally imply the purchase of a website, logo, social media account, customer list, trademark, content library, or other digital asset. If any of those items are included, list them separately and describe how they will be delivered.
Use a reputable marketplace escrow service or another independently verified payment process rather than sending an irreversible payment directly to an unfamiliar party. Confirm the service’s current fees, supported countries, identity checks, dispute process, and release conditions before committing. Procedures can change, particularly in cross-border transactions.
For broader research, the domain name due diligence checklist can help organize ownership, history, traffic, and transfer checks. Treat every document or screenshot supplied by the seller as evidence to verify, not as a substitute for independent confirmation.
Checklist by scenario
Buying from a private owner
- Confirm the exact asset. Copy the domain precisely, including its extension and spelling. Check whether similar domains are being confused with the intended purchase.
- Verify the seller’s authority. Ask the seller to identify the current registrar account or provide a registrar-generated view showing control of the domain. Do not rely solely on an email address that resembles the domain.
- Check the registration record where available. Public registration data may be limited or privacy-protected, so use it as one part of the verification process. Ask for information that can be confirmed through the registrar or an established marketplace.
- Review transfer readiness. Ask whether the domain is locked, subject to a recent transfer restriction, involved in a pending change, or governed by registrar-specific approval steps. The seller should explain which actions they will take and which actions the buyer must complete.
- Screen the name for conflicts. Search relevant trademark databases and check the proposed business use in the countries that matter to you. A domain purchase does not automatically grant trademark rights, and a desirable name can still create legal exposure.
- Investigate history. If the domain has been used before, review available records for spam, misleading redirects, malware warnings, reputation problems, or activity that could affect your intended use. A clean-looking landing page is not proof of a clean history.
- Agree on value and terms. Compare the price with the name’s relevance, length, spelling, commercial use, comparable marketplace listings, and any verifiable history. Avoid treating an automated valuation as a final answer; it is only one input.
Buying through a marketplace or broker
Confirm whether the platform is acting as a listing venue, negotiation intermediary, broker, or escrow provider. These roles can involve different fees, responsibilities, and dispute procedures. Review the full transaction summary before bidding or accepting an offer. The domain marketplace fees comparison can help you map buyer, seller, auction, and transfer costs.
Check whether the marketplace has already verified ownership, or whether you must perform that check yourself. Also confirm how the platform handles a failed transfer, an unresponsive seller, a domain that does not match the listing, and a disagreement over release of funds. Do not assume that every marketplace offers the same buyer protection.
Buying from another country
Establish the transaction currency, identity requirements, tax responsibilities, payment route, and governing terms before negotiating the final amount. Confirm that both parties and the chosen payment provider can transact in the relevant countries. A bank transfer, card payment, or digital payment may have different reversal, conversion, and fraud characteristics.
Use a written agreement that states which party pays marketplace, escrow, conversion, and transfer fees. Keep communications and invoices together. If the value is material or the transaction has unusual legal or business implications, obtain professional advice in the relevant jurisdiction.
What to double-check
Ownership and account security
- Verify the domain name character by character before payment.
- Ask the seller to use the registrar’s normal transfer or push procedure, not an improvised link or unfamiliar login page.
- Do not request or accept the seller’s password. The transaction should transfer the domain through approved account controls.
- Use a new, protected buyer account with a unique password and multi-factor authentication where available.
- After transfer, replace recovery details, review delegates and users, and confirm that no unwanted access remains.
Escrow and release conditions
Read the escrow workflow before depositing funds. Identify the event that starts the seller’s delivery period, the evidence required to confirm delivery, the time allowed for inspection, and the process for reporting a problem. A sensible release condition should relate to your control of the domain, not merely to the seller’s promise that a transfer was attempted.
Use only contact details obtained from the provider’s official website or your verified marketplace account. Phishing messages can imitate escrow instructions and redirect payment. If payment instructions change during a deal, pause and verify them through an independent channel.
Transfer acceptance and post-transfer testing
Once the domain arrives, confirm that it appears in your registrar account and that you can manage its nameservers, contacts, renewal settings, and security controls. Review DNS records before making changes, especially if the domain supports email or an existing website. Test the web address, email routing, redirects, and certificate configuration after any planned migration.
For a broader handover sequence, use the domain and website transfer checklist. Keep the purchase agreement, receipts, registrar confirmations, and transfer dates in a permanent ownership file.
Common mistakes
- Sending money directly because the seller seems credible. Familiar conversation, a professional website, or urgency does not replace controlled payment.
- Skipping trademark research. A domain can be available for purchase while its intended commercial use still conflicts with another party’s rights.
- Assuming a transfer lock is a scam. Registrars may apply different controls and eligibility rules. Ask the seller and registrar what applies, then confirm the current procedure rather than guessing.
- Accepting a screenshot as ownership proof. Screenshots can be old, edited, or taken from an account that does not control the domain. Prefer live, registrar-based confirmation.
- Leaving the scope vague. State whether the deal includes only the domain or also websites, content, trademarks, accounts, data, or other assets.
- Ignoring renewal and expiration dates. Confirm the current expiration information and make a renewal plan immediately after acquisition.
- Changing DNS too early. Do not disrupt an existing site or email service until ownership is confirmed and you understand the current configuration.
- Relying on outdated instructions. Registrar workflows, identity checks, transfer requirements, fees, and supported countries can change.
If you are evaluating a larger online asset rather than a domain alone, use the website acquisition due diligence playbook and review financial, traffic, technology, and operational evidence separately.
When to revisit
Run this checklist before every private domain acquisition, even if you have used the same registrar or escrow provider before. Revisit the process before seasonal planning cycles, when buying across borders, when a domain has changed hands recently, or when the purchase price or intended use is significant.
Review the workflow whenever a registrar, marketplace, or escrow provider changes its procedures. Recheck current fees, supported countries, identity verification, transfer requirements, transfer-lock rules, and dispute conditions immediately before payment. ICANN-related policies and registrar implementation details may also change, so confirm the current requirements with the relevant registrar or provider.
Before acting, save a dated copy of this final checklist and mark each item complete:
- Exact domain and transaction scope confirmed.
- Seller authority independently checked.
- History and trademark concerns reviewed.
- Price, fees, currency, and responsibilities written down.
- Escrow provider and release conditions verified.
- Transfer procedure and acceptance window understood.
- Buyer account secured before the domain arrives.
- Ownership, DNS, renewal, and access controls tested after transfer.
If any item remains unclear, pause the transaction and resolve it before sending funds. A short delay is usually easier to manage than recovering a payment, repairing a compromised account, or unwinding a domain purchase that was never properly documented.
