Websites
Know who controls your domain, hosting and website files
Separate domain registration, DNS, hosting and site files so website ownership and a future handoff are understandable.
By Bridge Builder editorial 3 min read
You can own a business name and still be unsure who controls its website. The domain, DNS, hosting, source files and connected accounts are different pieces. A clear inventory makes a future update or agency change much easier to plan.
You do not need to manage every technical setting yourself. You do need to know which account controls each piece, who pays for it and how access can be recovered.
In this article
Separate the four main pieces
The domain is the registered address. DNS contains the routing records used by services such as your website and email. Hosting runs or serves the website. The site files and content are what get published through that hosting arrangement.
ICANN describes the registrant as the person or entity holding the rights to a registered domain. Check that the account and registration arrangements reflect your business's intended ownership. Paying an agency invoice for a website does not, by itself, explain every account or asset right; those details belong in the actual agreement.
Create an ownership sheet without storing passwords
Record the provider, account owner, renewal responsibility, authorized administrators and recovery contact for each service. Use account names or secure secret references, not passwords pasted into a shared document. Include the business email platform because a domain change can affect more than the website.
Also record the code repository, asset storage and licenses needed to operate the site. A site built inside a hosted platform may have different transfer options from a site delivered as source code. Ask for an exact explanation of what can be exported, transferred or rebuilt before assuming every platform supports the same handoff.
- Domain registrar and intended registrant.
- DNS provider and who can approve record changes.
- Hosting account, plan owner and renewal responsibility.
- Source, images, content and any transferable licenses.
- Forms, calendar, analytics and other connected service accounts.
Give access through roles
Where a provider supports delegated roles, give the builder the access required for the project through their own account. Keep owner recovery under business control. Sharing an owner's login creates uncertainty about who made a change and who still has access later.
Review access when a project ends or responsibilities change. Removing an old agency from one account does not automatically remove it from every integration. Work from the inventory and confirm each change. Keep a record of who will handle updates after the handoff so urgent work does not arrive in an unmonitored inbox.
Discuss the exit before signing
Ask what happens if you stop paying for ongoing service. Separate an unpaid build balance, optional management, hosting charges and any agreed rental or buyout terms. A clear agreement should make it possible to understand what continues and what ends.
Request a practical handoff: account list, source or platform access, current configuration, renewal dates and instructions for common edits. Test that the new responsible person can use the access. Ownership on paper and the ability to operate the website should match before the old arrangement is retired.
Your next step
Keep business ownership clear and delegate operational access. A good website handoff explains accounts, assets, renewals and the exit process.