Your domain is the address people use to find you. Web hosting runs and serves your website. Paying for one does not automatically give you the other, even when both appear on the same invoice. For a business owner, the useful question is whether you can identify each service, renew it and recover access without depending on one person's inbox.
This guide helps you check an existing arrangement or agree a new handover. It is an operational checklist, not a legal opinion about ownership of code or design. Those rights depend on the agreement and any third-party licences.
1. Separate the services before comparing the bill
An ordinary business website can involve several accounts. They may sit with one provider or several. Ask your supplier to fill in this table using your actual services.
| Service | What it does | Evidence to ask for |
|---|---|---|
| Domain registration | Maintains the registration of your web address | Registrar, registered contact details and expiry date |
| DNS | Directs services using that domain to their destinations | Where records are managed and who can change them |
| Web hosting or website platform | Runs or publishes the website | Account, site identifier, plan and export or recovery options |
| Business email | Provides the mailboxes you use | Email provider, administrator and separate renewal details |
Cloudflare explains the domain name as a memorable address. Its DNS documentation distinguishes the routing system and notes that registration, hosting and DNS can be offered by the same company. A bundled purchase does not remove these separate jobs.
An email address printed on your site does not show who operates the mailbox. A domain renewal receipt does not establish that the website hosting has been renewed.
2. Check control by signing in
My practical recommendation is to keep essential business accounts under business-controlled access, then invite the supplier with the permissions needed for their work where the service supports it. Avoid passing one shared password around when separate users are available.
Open the real account with the supplier present. Check the domain or website shown, account contact, recovery route and who can add or remove users. A screenshot of an account page is useful documentation; a successful business-controlled login is stronger evidence of access.
Some agencies host several clients inside a managed account. That arrangement needs a written explanation of what you receive, how changes are requested and what happens when you leave. You may not receive the agency's entire hosting login. You should still know the recovery contact, the deliverable you can take away and the agreed exit process.
Store passwords and recovery codes securely, outside the public handover document. Arrange a recovery route that remains accessible if the website or its domain email stops working.
3. Put renewals and cancellation in writing
For each service, record the next renewal date, renewal price and currency, who pays, who receives reminders and who checks that payment succeeded. Keep first-term promotions separate from ongoing charges. Do not assume that a paid maintenance invoice covers every supplier subscription.
ICANN's renewal guidance explains the importance of keeping registration current and the consequences of expiration. Check the terms for your registrar and domain ending; do not plan around a universal grace period.
Ask what cancellation removes: only support, the live site, stored backups, mailboxes or some combination. Agree a date for transferring or exporting the necessary material before anything is closed. The maintenance cost guide helps separate recurring services from work on the website.
4. Protect email when changing hosting
Moving a website and moving its email are separate decisions. Before changing DNS or closing an old hosting account, identify the email provider and save the current DNS configuration. Ask the person doing the move which records will change and how existing mail will remain available.
Google's email setup documentation explains that MX records tell senders where to deliver mail. Replacing website settings is therefore not a reason to delete unfamiliar mail records. The safe values depend on the email service already in use.
After an authorised change, test the website and send a test message in both directions with an external mailbox. Also test a website enquiry through its actual destination if the site has a form. A working homepage cannot prove that a mailbox or form notification works. These are suggested acceptance checks, not a complete email migration procedure.
5. Ask for a handover you can use
Keep a private service register containing the provider, account identifier, responsible person, renewal arrangement and support route for each service. Add the agreed website deliverables and the instructions for recovering them. Keep a separate secure record of credentials.
Before accepting the handover, have someone from the business sign in, locate the renewal details and explain how to request a change or recover access. If a backup is included, ask what it contains and what evidence shows it can be restored. Access to a domain account alone does not establish that the website can be rebuilt.
If you are leaving a website builder, check the platform migration guide as well. Having the domain login and being able to export the complete website are different capabilities.
6. Fix the most consequential gap first
Start with access to the domain account and its renewal status. Then identify where DNS is managed, where email lives and how the website is recovered. Keep the current site running while you resolve missing information; do not cancel a service simply because another provider has sent a welcome email.
You should finish with an answer to four questions: Where is each service? Who can access it? Who renews it? What happens if the supplier changes? A clear answer is more useful than a promise that you “own everything” without an account or handover to support it.
