
Your domain is the address customers use. Hosting is where the website runs or where its files are served. Maintenance is the ongoing work that keeps the website and its dependencies working. One provider may bill for all three. Each still needs an owner and a clear responsibility.
Domain registration and DNS
A domain is registered through a registrar and renewed for continued use. The Domain Name System, or DNS, helps computers look up information about that domain, including where to send website requests. The domain can also have records that help route business email.
Changing web hosts usually means changing relevant DNS records, while keeping registration at the existing registrar if you choose. Record how the current settings work before a move. Ask whoever manages email to verify its records and test inbound and outbound mail when DNS changes are involved.
Source: MDN guide to domain names
Hosting provides the environment
A host can serve static files, run a server application or manage a platform that includes editing and commerce. What you need depends on what the site does. A portfolio may need fewer services than a storefront with order processing, customer accounts and integrations.
Ask where the site runs, what the plan includes and which limits matter to your project. Review storage, traffic or request allowances if they apply. Find out how the site is deployed, where media and data live, and who is alerted if it becomes unavailable.
Source: Next.js deployment options
Maintenance keeps the service usable
A maintenance agreement may include checking dependencies, verifying backups, monitoring availability and testing essential user flows. Read the scope carefully. Content changes and redesign work may have separate estimates. Ask what happens after hours and how work is prioritized when a customer-facing feature breaks.
Backups deserve a separate conversation. Ask who can restore them and whether the backed-up material covers the whole site. A site export that contains page content may omit media, uploaded files or customer records. A restore rehearsal shows what is actually available.
Source: Canadian Centre for Cyber Security baseline controls
Review the agreement before a renewal or supplier change
An invoice described as a website plan can bundle different things. Ask for a list of the services it covers, renewal dates, what happens if payment is missed and what constitutes additional work. Where one vendor handles billing on your behalf, check how another authorized person could verify each service’s status.
If someone manages the domain for you, confirm the business has appropriate registrant details and an accessible recovery contact. If you move the website, give the old and new providers an agreed handoff window where they can coordinate. Test the public site and business email afterward and document the updated contacts and responsibilities.
Build a simple ownership register
List the registrar, DNS provider, host, email service, source repository and platforms the business depends on. Record the billing owner, renewal dates and recovery contacts. Give authorized staff secure account access and keep credentials in the organization’s approved systems.
If you change providers, review the register together before ending service. Check which subscriptions continue, which data or settings can be transferred, and who verifies the site and email after the handoff. These checks turn a complicated transition into a series of decisions with named owners.
Trace an ordinary hosting move
Imagine a shop moving its website to a new host while keeping its business email provider. The owner confirms who can access DNS and the accounts being moved. The team records existing DNS settings, reviews which records the new host needs and agrees on who can verify email. A test plan covers both the old website links customers share and the shop’s most important forms.
Before handing off support, ask the new provider to identify where the site, content and backups are managed. Write down the process for restoring the site or reporting downtime. Treat the account register as a document staff can use when a supplier changes.
Your Action Checklist
- Record domain, DNS, hosting and maintenance responsibilities.
- Confirm authorized staff can recover access to each critical account.
NSBDA can help you clarify hosting, domain and maintenance responsibilities before a migration or provider handoff.
Explore Website Maintenance

