VDNX
ESLet’s talk

Web design & development·6 min read

Before commissioning a website: who should control the domain, hosting and code?

Your business should control the domain and recovery routes. A supplier can run the technology, but continuity should not depend on their account alone.

The short answer: business control, professional access

Before commissioning the work, make sure the business controls the domain and the recovery routes for critical accounts. Your supplier can administer hosting, the code repository and everyday tools, but should not be the only party able to renew, export, restore or authorise a handover. The owner does not need to become the technician; the point is to keep the business operational if the team changes.

Not every service must sit in one company account, and not every line of code can be ‘owned’ without qualification. A platform may contain licensed components, while a managed service may run inside a supplier's infrastructure. The useful question is what the business receives, what can move, who pays, who administers and how each asset can be recovered. Legal ownership of code, copy and licences depends on the agreement and applicable law. This is an operational-control guide, not legal advice.

Separate four roles that are often blurred

For every asset, name four roles. The account holder or contractual party is recognised by the service. The payer keeps the subscription or renewal active. The administrator configures the service. The recovery contact receives alerts and can restore access. One person may fill several roles, but treating them as interchangeable creates blind spots.

Paying a development invoice does not, by itself, reveal who is recorded at the domain registrar or what licence applies to the source code. Knowing a hosting password does not prove you can change its recovery email. Ask for a compact responsibility matrix containing company names or roles—not passwords—plus a documented substitute for each critical function.

  • Holder or contractual party: the person or entity recognised by the account or agreement.
  • Payer: receives invoices and renews; expiry warnings need a monitored destination.
  • Administrator: configures, publishes and maintains; this can be the supplier.
  • Recovery: a business-controlled route, with a documented backup contact.

Map the four assets before work starts

Domain: the business should control the registrar account, renewal details and recovery route. MDN explains an important nuance: a domain is not purchased forever; you pay for the right to use it for a period and can renew that right. A brand name on the site is therefore not enough. Record the registrar, renewal date and monitored contact for notices.

Hosting can live in a business account or in a supplier's managed environment. Either way, agree what copy the business can obtain, what an export contains, how long data is retained and how an exit works. For code and content, define repository access or an equivalent delivery, the agreed rights or licence, third-party components and anything that cannot transfer. For external services, inventory analytics, search tools, forms, transactional email, maps, fonts and integrations, including the account holder and recovery route.

  • Domain and DNS: registrar, renewal, responsible parties and change procedure.
  • Hosting and data: plan, backups, export, restoration and closure.
  • Code and content: repository or delivery, agreed rights and licensed dependencies.
  • External services: primary account, billing, administrators and recovery.

Three workable models—and each one's limit

In a business-owned model, the company subscribes to the domain, hosting and services, then grants professional access. This improves visibility and makes handover easier, but someone inside the business must own renewals, security and user changes. In a managed model, the supplier operates some infrastructure in its own account. That can reduce internal workload, provided there is a defined exit, export and delivery timescale.

An integrated website platform combines building, hosting and maintenance. It can be a sensible choice when convenience matters more than portability, as long as everyone understands which content can be exported and which design or functions depend on the platform. No model is automatically right. The warning sign is being unable to explain what happens if the supplier stops trading, a payment card expires or the sole administrator loses access.

A hypothetical handover for a consultancy

Imagine a fictional consultancy commissioning a service website. Under the first proposal, the agency would register the domain using its own email, host the site in a shared account and provide only CMS access. Analytics and the enquiry form would also sit under team members' personal accounts. The arrangement may produce a working website, but it does not explain how the business continues if the relationship ends.

Before accepting, the consultancy requests a revised arrangement. It registers the domain in a business account with two responsible people and automatic renewal; the agency retains technical DNS access. Hosting remains managed by the agency, but the agreement identifies which files and data are exportable, their delivery format, retention period and transition assistance. The company can read the repository, and third-party dependencies are listed. Analytics and forms begin in company accounts with the agency as administrator.

A year later, the consultancy appoints a different maintenance provider. It does not expect an instant switch. The team prepares new infrastructure, copies and tests pages, images, forms and downloads, preserves Search Console verification, then changes DNS when the replacement is ready. This follows Google's hosting-move sequence. The example succeeds not because everyone shares every password, but because control, exports and responsibilities were agreed before the handover was needed.

What to put in the proposal and how to verify it

Add an asset table to the proposal with holder, payer, administrator, recovery contact, renewal frequency, copy format and exit condition. State what happens to domains, repositories and services at termination: timescales, any charge, included assistance and anything that cannot move. ‘You will own everything’ is not a substitute for a specific inventory.

Verification should be practical. The business should be able to sign in to the registrar or confirm its recorded role, receive renewal notices, view authorised users, locate a recent copy and know how to request restoration, and confirm the repository or deliverable scope. Do not put passwords in the matrix. Use individual accounts and access-management tools where available, and test recovery without locking anyone out or changing the live environment.

When professional help is worth bringing in

Get technical help when nobody can identify the domain, DNS and hosting providers; when a move affects email, forms, databases or several integrations; or when no one can produce and restore a copy. Google advises preparing and testing replacement infrastructure before changing DNS, monitoring both environments and retaining verification. An improvised move can disrupt users as well as search visibility.

Seek appropriate legal advice if the dispute concerns intellectual property, licensing, data obligations, breach or contractual transfer. When commissioning the website, ask the professional for two deliverables from the outset: the four-asset control matrix and an exit procedure proportionate to the project. A healthy supplier relationship does not hide the keys; it makes clear who holds them, why they use them and how access can be recovered.

Sources and documentation

Content created with AI assistance. Check the sources, date and scope of each guide.

Let’s define the next step for your website.

Tell us what your business needs and where your current website falls short. We can help you define the scope.

Let’s talk about your idea