Who Owns Your Business Website? Domains, Content, Hosting and Access Explained
Understand control of your business website by separating domain registration, content rights, hosting, source files and account recovery.
A business website is a collection of assets, contracts and accounts. Owning the domain does not automatically mean owning the design copyright, controlling the hosting or possessing a recoverable copy of the code.
The practical question is whether the business can use, maintain and move the website on clear terms, including when the current supplier is unavailable.
Start with a control inventory
List the domain registrar, DNS provider, hosting, content-management system, source repository, email service, analytics and connected booking or payment services.
For each, record the business owner, supplier, authorised administrators, renewal method and recovery route. Keep passwords and recovery codes in an appropriate secure store rather than the inventory itself.
A named staff member should know where the inventory lives and when it was last checked.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Domain registration is one part
The registrant is the person or organisation holding the domain registration under the applicable terms. The registrar manages registration services; the registry operates the domain extension.
Check that the business’s registration details and recovery contacts are correct. Paying a designer’s invoice is not sufficient evidence that the domain is registered to your organisation.
See checking domain ownership and whether a designer should register it.
Copyright and licences need a contract
Custom copy, photography, illustrations and code can have different rights holders. Third-party components may be licensed rather than owned.
The Intellectual Property Office explains website ownership and why commissioned work needs clear contractual treatment. Do not assume payment alone transfers copyright.
Ask which rights are assigned, which assets are licensed, what use is permitted and what happens after termination. Obtain legal advice for a disputed or valuable agreement.
AI assistance adds further questions about sources and supplier terms, covered in ownership of AI-created content.
Hosting access is an operational responsibility
A website may run in a business-owned account or an agency’s managed environment. Either can work when responsibilities, continuity and exit terms are explicit.
Know who can change billing, authorise another administrator, restore a backup and move the service. Read who should control hosting before assuming a login is the same as complete control.
Keep recoverable assets
Request the materials needed to maintain the site, not just a screenshot or a copy of the visible pages.
Depending on the platform, that may include source code, content exports, database backups, media, build instructions and a list of dependencies. Some hosted builders do not provide a portable copy of all functionality.
The guide to website file copies explains how to test what a handover actually contains.
Understand technical dependencies
Start by separating the domain name from web hosting. If changes need testing before release, include the staging website and its access arrangements in the same inventory.
DNS directs services associated with the domain. Changing it can affect the website, email and verification records. The DNS guide explains the main record types.
Certificates support encrypted HTTPS connections and need ongoing management. See SSL certificates for their role and limits.
These services may be managed by different suppliers, so document the relationships.
Plan an exit while the relationship is healthy
Ask what can be exported, which licences travel with the site, what notice is required and what handover work costs.
Moving to another agency should be a planned transfer with testing. Vendor lock-in becomes manageable when dependencies and migration costs are known in advance.
An exit plan is also useful if nobody wants to change supplier but a developer becomes unavailable.
Test whether you can recover the website
Have an authorised colleague confirm they can locate the accounts and use the agreed recovery process. Verify that backups can restore the important functions.
Do not circulate shared administrator passwords as a shortcut. Use named accounts and appropriate roles where available.
The guide to a developer disappearing provides a continuity sequence.
Ownership also needs practical safeguards. Review the UK website compliance and security guide and agree a backup and recovery plan before an emergency.
What should a handover contain?
A useful handover includes the asset and account inventory, rights and licence records, recoverable files, deployment instructions, renewal information and named support responsibilities.
Review it after major changes. New forms, hosting moves and booking integrations can create dependencies that the original handover never mentioned.
See the existing guide to website ownership, hosting and changes for the service relationship, or contact AfterWorks to assess practical control of your current website.
