Soapybusiness.eu

Buying a Domain Name vs Buying a Website: What Is Included?

A domain name can lead to a shop, a publication, a booking service—or simply a page inviting offers. Buying the name does not establish what else comes with it. When comparing buying a domain vs a website, the key question is which assets and rights the seller has agreed to transfer. A clear asset list helps prevent you from paying for a working business and receiving only its address.

What does a domain-only purchase include?

A domain-only purchase generally transfers the seller’s registration rights in a specified domain name. You become the recorded holder, subject to the applicable registration rules and ongoing renewal requirements.

The agreement should identify the exact domain, the purchase price, the transfer process, and who pays any transaction or transfer fees. Confirm the renewal date and your ability to manage the domain through an account you control.

A change of domain holder and a move between registrars are distinct steps, even when completed together. For a .eu purchase, ask the receiving registrar to confirm your eligibility and the required transfer procedure before payment.

A domain transfer does not itself deliver a website. Hosting, page content, software, branding, and email services need their own treatment in the agreement.

A page displaying a logo or an attractive design is not evidence that either asset is included.

What changes when you buy a website?

Buying a website usually means acquiring an agreed collection of assets that enables you to continue publishing or trading online. That collection might include the domain, website files, content, software, databases, and operating documentation.

However, “complete website” is too vague to define a purchase. A functioning site may depend on subscriptions, licences, or service accounts that belong to the seller and cannot simply be handed over.

Buying website assets also differs from buying the company that operates them. Company ownership, contracts, and liabilities require a broader review.

An asset checklist for domain sale inclusions

Use this checklist when discussing domain sale inclusions. Mark each asset as included, excluded, or dependent on permission, then attach the completed list to the agreement.

Asset Domain-only purchase What to confirm in a website purchase
Domain registration The central asset Exact domain, holder change, account control, and renewal date
Hosting and DNS services Usually arranged separately Migration responsibilities, settings, service continuity, and ongoing costs
Written content and media No automatic inclusion Specific files and the rights to publish, edit, and reuse them
Source code and design No automatic inclusion Repositories, editable files, dependencies, and applicable licences
Trademarks and brand assets No automatic inclusion Ownership, assignment or licence terms, and any required formalities
Email services and archives No automatic inclusion Mailboxes, messages, migration scope, and permitted access
Customer and subscriber data No automatic inclusion Lawful disclosure, intended uses, notices, security, and retention
Analytics and commercial accounts No automatic inclusion Provider transfer rules, historical access, and replacement accounts

A seller’s promise to provide login details is not a substitute for confirming ownership, permission, and transferability.

Where separate agreements or permissions matter

Separate treatment does not always mean a separate contract. Some assets can be covered by detailed clauses or schedules in the main purchase agreement. Others may require an assignment, a fresh licence, or approval from an outside provider.

Content, photographs, and code

Ask who created the articles, product descriptions, photographs, illustrations, and software. Then establish what rights the seller actually holds.

A seller may have permission to display a photograph without having permission to transfer that licence. Similarly, an agency may have supplied a website under terms that limit ownership or reuse of its code.

For content and custom software, specify whether you receive ownership of transferable rights or permission to use the material. Identify any limits on modification, duration, territory, or further transfer.

For technical delivery, request the source files, repository access, database structure, deployment instructions, and a list of dependencies. Commercial themes, plugins, fonts, and external services may require new subscriptions or licences. Open-source components remain subject to their applicable licences.

Trademarks and branding

Acquiring a domain does not automatically give you trademark rights in the matching words. It also does not establish that your intended use is free from third-party claims.

If the purchase includes a brand, identify the relevant trademarks, logos, design files, and associated rights. Confirm who owns them and whether the agreement provides an assignment or a licence.

Treat a trademark search and a check of the seller’s ownership as distinct tasks. A seller can control a domain without owning the corresponding brand rights.

Email addresses, accounts, and old messages

Control of a domain can allow you to configure new email addresses once you arrange an email service. It does not automatically provide the seller’s existing mailboxes or message history.

If email is included, define which accounts, aliases, archives, and address books will move. Check the provider’s transfer rules and agree how unrelated or private correspondence will be excluded.

Plan the change carefully: existing addresses may also receive password resets, invoices, or messages intended for the previous operator. The seller should update their own account recovery details before handover.

Customer records and mailing lists

Customer data requires more than a line saying “database included.” Distinguish order records needed to continue providing a service from subscriber information intended for future marketing.

The European Commission’s guidance on using contact data received from another organisation explains that buyers must check how marketing data was obtained and whether its proposed use is permitted. Where consent is relied upon, its scope matters; objections to direct marketing must also be respected.

Before transferring personal data, establish the lawful basis for disclosure and subsequent use, required privacy information, and secure delivery arrangements. Consent is not the only possible lawful basis, but a sale agreement alone does not supply one.

During initial due diligence, use aggregated or anonymised information where practical instead of requesting an identifiable customer database.

Make the handover measurable

The purchase agreement should connect each promised asset to a delivery method and an acceptance check. A practical handover plan covers:

  1. Included assets and exclusions: Name the domains, files, rights, accounts, and data involved.
  2. Permissions and dependencies: Record which licences, provider approvals, or replacement services are needed.
  3. Delivery and timing: Assign responsibility for domain transfer, file delivery, hosting migration, and any support period.
  4. Verification: Check domain control, site functionality, permitted account access, and the completeness of agreed files.
  5. Payment conditions: Define when funds are released and what happens if an agreed asset cannot be delivered.

For an operating website, also verify claimed revenue and costs against appropriate records. Historical performance can help assess value, but it is not a promise of future earnings.

Before making an offer, ask the seller for a written inventory. Price the assets you can verify, budget for services you must replace, and make completion depend on delivery of the specific package you agreed to buy.