Business owners checking control and long-term responsibilities

Domain and Website Ownership: Accounts, Access and Handover

Owning a business name, registering a domain and controlling a website are separate matters. Make an inventory of the accounts, assets and access needed to operate your site. This guide describes questions to resolve; it does not replace your agreement or create new LBYS ownership terms.

Published 2026-10-04 · Updated 2026-10-05 · Published by Let’s Build Your Site · Meet Ferdinand Munoz

Website responsibilities — illustrative flow

1.Domain registration: who owns the address and renewal
2.DNS: directs web and mail traffic; changes need an owner
3.Hosting: serves website files and any application data
4.Email: separate service with its own accounts and routing

Account ownership and handover

Edit the example for your project. Changes stay in this page until you navigate away or reload. Download CSV or print a copy to keep your work. Do not enter passwords, patient information or sensitive account details.

Choose a row to editEdit one row at a time. Your download includes every row.

Account ownership and handover — editable planning example
Account / asset	Owner	Recovery contact	Renewal date	Access role	Handover deliverable
Account / assetDomain registrationDomain registration	OwnerCustomerCustomer	Recovery contactRecord privatelyRecord privately	Renewal dateConfirmConfirm	Access roleRegistrant / delegated adminRegistrant / delegated admin	Handover deliverableRegistrar access and renewal responsibilityRegistrar access and renewal responsibility
Account / assetDNSDNS	OwnerConfirm responsible accountConfirm responsible account	Recovery contactRecord privatelyRecord privately	Renewal dateIf applicableIf applicable	Access roleDNS administratorDNS administrator	Handover deliverableZone export and record explanationZone export and record explanation
Account / assetHostingHosting	OwnerConfirm agreementConfirm agreement	Recovery contactRecord privatelyRecord privately	Renewal dateConfirm billing cycleConfirm billing cycle	Access roleDeployment accessDeployment access	Handover deliverableBuild / deployment instructions where transferableBuild / deployment instructions where transferable
Account / assetBusiness emailBusiness email	OwnerCustomer / agreed tenantCustomer / agreed tenant	Recovery contactRecord privatelyRecord privately	Renewal dateConfirmConfirm	Access roleMailbox / tenant administratorMailbox / tenant administrator	Handover deliverableAccess and routing documentationAccess and routing documentation
Account / assetWebsite files and licensed assetsWebsite files and licensed assets	OwnerPer project agreementPer project agreement	Recovery contactNot applicableNot applicable	Renewal dateLicense-dependentLicense-dependent	Access roleRepository / asset accessRepository / asset access	Handover deliverableAvailable transferable files and license restrictionsAvailable transferable files and license restrictions
Account / assetAnalyticsAnalytics	OwnerBusiness property ownerBusiness property owner	Recovery contactRecord privatelyRecord privately	Renewal dateIf applicableIf applicable	Access roleOwner / delegated analystOwner / delegated analyst	Handover deliverableProperty access and tracking inventoryProperty access and tracking inventory

0 of 8 checklist tasks complete. Checks stay in this page until you navigate away or reload; print a copy to keep them.

Separate the accounts and assets

The registrar controls domain registration and renewal. DNS controls where the domain sends website traffic and email. Hosting runs the site. A single provider may handle several of these, but a change to one can affect another.

Source code, website content and licensed assets also differ. An agreement may grant ownership, a license or access to a hosted platform. Confirm which rights apply and whether there is a usable export or migration path. Do not assume that controlling the domain means owning every software component.

Responsibility table

Record the actual owner, administrator and recovery method for each item. Share access through appropriate roles rather than sending passwords in ordinary project notes.

Responsibility table
Item	What to clarify	Ongoing responsibility
Domain registration	Registrant, recovery contact, renewal access	Renew registration and maintain accurate contact details
DNS	Who can change records and approve changes	Preserve website and mail routing; record changes
Hosting	Account owner, deployment access, cancellation	Renew service, monitor availability and maintain backups
Source code	Rights, repository access and transfer terms	Keep recoverable versions and document deployment
Content and assets	Authorship, usage permissions and licenses	Maintain accurate content and renew relevant licenses
Business email	Account administrator, recovery and billing	Protect mail routing, renew service and manage users
Analytics	Property owner, access roles and consent setup	Retain report access and review collection settings

Access and renewal decisions

Use business-controlled recovery contacts where practical, enable appropriate account protection and document who is authorized to change settings. Decide how an external developer receives and later relinquishes access.

Record renewal dates and the party responsible for payment. Domain, hosting, email and licensed tools may renew separately. Understand cancellation effects before replacing a provider, particularly where DNS or email is bundled.

A practical handover checklist

Confirm the domain registrant and business recovery contact.
List administrative accounts and the roles granted to each person.
Receive the agreed code, content and asset deliverables, subject to the actual contract and licenses.
Record hosting, deployment, backup and restoration instructions.
Confirm renewal responsibilities and any ongoing maintenance arrangement.
Test important contact paths and confirm where inquiries and analytics reports arrive.
Document any restrictions on exports, third-party services or licensed assets.
Remove unnecessary access only after the handover and recovery paths are verified.

What to confirm with LBYS

Ask for the ownership, licensing, handover and support provisions that apply to your written project agreement. The public package descriptions identify service scope; they do not by themselves establish every transfer right or cancellation term. Resolve those details before committing to a platform or integration.

Continue your planning

Put your planning into action

Bring your goals, existing website and any scope questions. We’ll discuss the scope and next steps before preparing a proposal.

Ask About Your Website Setup