Assess the three services separately

The domain is the address people use. Hosting is the environment that serves your website files and, where needed, runs the application and database. Business email lets you send and receive messages using that domain. One provider may supply everything, or different providers may handle each service.

Ask the proposal to specify the domain extension and registration period, hosting plan and number of email mailboxes. If email is included, establish whether that means a real mailbox or forwarding to another address. Those arrangements are not interchangeable in everyday use.

Include account control in the handover

Prefer domain and hosting accounts under business control. An agency can receive the technical access required through an authorised user. A setup tied only to an employee’s personal account may become difficult to manage when that person leaves.

Record the recovery contact, authorised account owner and renewal responsibility. Use an appropriate password manager and supported account-sharing features rather than putting passwords in a shared document. Know which permissions should be removed when a supplier changes.

Choose hosting around the actual workload

A brochure site, membership application and extensive product catalogue may require different resources. Storage allowance alone is not enough to compare plans. Ask about backup frequency, the restoration process, support responsibilities and compatibility with the application you intend to run.

An illustrative decision note might say: “Launch includes five content pages and an enquiry route, without payments or member accounts.” That makes a proposal easier to assess. A larger hosting package does not automatically create a faster website; the design and software workload still matter.

Keep website and email changes distinct

MX records identify the mail servers that receive email for a domain. Moving the website to another server therefore does not require changing the email provider. Existing routing records should not be deleted together without understanding the current setup.

A launch plan should include a record of the existing DNS configuration, the web records being changed and a person responsible for testing email. Test both sending and receiving. This guide is not a panel-specific DNS recipe: the appropriate records depend on the providers and configuration in use.

Discuss renewal costs alongside setup

List domain, hosting, email and any licence renewals separately from the initial website build. Promotional and renewal prices may differ; confirm current charges with the provider. Check where payment and expiry notifications will arrive and who will act on them.

A useful supplier question is: “Which accounts will we control, who renews each service, and who can restore a backup?” Read our website proposal guide to compare the wider scope, or discuss implementation through our web design service.

Frequently asked questions

Does changing hosting also move business email?

Not automatically. Website hosting and email must be planned separately. Agree whether existing mail accounts and routing will be preserved or migrated before changing the setup.

Must the agency own the domain account?

No. A business-controlled account with appropriate agency permissions is an option. Check the existing provider’s transfer and access arrangements for your particular account.

Sources & further reading

Cloudflare — DNS MX records
Web design & developmentLet’s discuss this service