Ownership checklist · reviewed 26 Sep 2026
Who Owns and Controls Your Website?
“The website is mine” can hide several accounts, assets, licences and contract rights. Audit each one separately before a launch, redesign or provider change.
This is an operational checklist, not legal advice; rights depend on contracts, licences and applicable law.
Quick answer
Website control is divided among the domain registration and DNS account, hosting, CMS and source repository, content and media rights, software or theme licences, databases and customer data, analytics and third-party services. Check the named account holder, administrators, recovery methods, billing, transfer rights, licence terms and written handover for each.
A contract and applicable law determine legal ownership; do not infer it from who knows the password.
Domain and DNS
The domain is a renewable registration governed by registry and registrar terms.
Record the registrar account, registrant details where applicable, recovery email and phone, two-factor authentication, renewal date, payment owner, transfer lock, nameservers and DNS administrators. Use delegated access instead of sharing the master password when supported.
Hosting, email and backups
Know whether the business has its own account or space inside someone else's plan.
Record the provider, account owner, plan, billing, server or project identifier, support route, backup location, restore process, DNS and email dependencies, cancellation and export options. Keep an independent current backup when changing providers.
Source, design and content rights
Custom work, reusable components and third-party assets may have different terms.
List the repository or file delivery, design files, copy, photographs, fonts, stock assets, themes, plugins and custom code. The agreement should state usage, modification and transfer rights, exclusions and any reusable provider material. Obtain qualified legal advice for a disputed interpretation.
Business and measurement accounts
The website depends on services outside the hosting login.
Include business email, analytics, Search Console, tag manager, business profiles, payment, shipping, maps, messaging, advertising, CRM and social accounts. Use named individual users with appropriate permissions and preserve at least two business-controlled recovery paths for critical services.
Customer data and privacy responsibilities
An export is not the only handover question.
Record where enquiries, customers, orders, backups and logs are stored; who can access them; retention and deletion responsibilities; processor agreements where applicable; and the safe export or transfer process. Remove former-provider access after verified handover.
Use a signed handover register
Test access rather than accepting a list of usernames.
For each item, record owner, administrator, billing contact, recovery method, URL, renewal, licence, export, responsible person and status. Change credentials safely, test forms and restore, preserve invoices, and confirm that the old provider's access is removed only after the new access works.
Questions
Ownership questions
Does paying for a website automatically transfer all rights?
Should the developer ever access the domain?
Is a WordPress administrator login enough?
What should I collect before changing developer?
Next step
Audit access before changing the site.
Send the current URL and the accounts you can access for a written recovery or migration scope.