Domain, Hosting, and Business Email: What Do You Actually Need?

What does each service do?

• Domain registration: reserves a name such as example.com for a registration period through a registrar. Keep renewal and registrant contact information current.
• DNS hosting: publishes records that tell other systems where to find the domain’s website, mail servers, and other services.
• Web hosting: serves the files or application visitors see. Cloudflare Pages is one example; it does not replace domain registration.
• Email hosting: provides mailbox storage, sending, receiving, and account administration for an address such as hello@example.com.
• Source storage: keeps website code and revisions, for example in GitHub. It is separate from the registrar and mail provider.

Cloudflare’s DNS explanation describes the lookup between names and their destinations. Its Pages custom-domain documentation describes associating a domain with a published project. Setting up the latter does not automatically create a business inbox.

Do you have to buy everything from one company?

No. You can use one provider for registration, another for DNS and the website, and another for mail. A combined plan may be simpler to administer, while separate services can make individual replacements easier. Compare the actual included features and renewal terms before deciding.

For a first public website, identify the live address, hosting destination, and reliable contact method. A provider’s default website address may be sufficient for an early preview. A custom domain is a separate registration decision. Business email is useful when you want mail at that domain, but a domain purchase alone does not establish a working mailbox.

Check introductory versus renewal prices, mailbox counts and storage, export options, and what happens when a bundle is canceled. There is no universal price or inclusion list that applies to every provider. Read the current offer for the plan you are actually considering.

How do you keep ownership and renewals clear?

Create a private account map before sharing access with a helper. Record service names and recovery routes, not passwords or secret keys in a public document.

Use accounts controlled by the person or business responsible for the website, with provider-supported delegated access for helpers. Keep recovery contact information reachable if the website or its domain email is unavailable. Follow each provider’s supported security and recovery setup; do not solve access sharing by putting a password in the project files.

ICANN’s registrant guidance explains the responsibilities associated with holding a domain name. Our GitHub visibility and ownership guide covers the source account separately.

Will changing website hosting break your email?

Changing the website destination does not inherently require moving mailboxes. Problems arise when DNS changes remove or alter records that the mail service depends on. Before a nameserver move, compare the existing records with the destination DNS zone rather than assuming an automatic scan found everything.

MX records direct incoming mail to the receiving service. Providers also use authentication and verification records, often involving TXT or CNAME records, for SPF, DKIM, DMARC, and domain verification. Keep the values and record names required by your actual provider. Avoid adding a second competing SPF policy or improvising values from another business’s setup.

Cloudflare’s email DNS documentation covers these record roles. Its full DNS setup guidance requires reviewing the records during a move.

If you are connecting Pages, use our custom-domain setup guide for the implementation steps. This account map should be prepared before you change the settings.

What should you test after a DNS or hosting change?

1. Open the preferred website address and an interior page directly.
2. Check any www or other addresses that should redirect or remain available.
3. Send a message from an unrelated external mailbox to the business address and confirm receipt.
4. Reply from the business mailbox and confirm it reaches the external mailbox.
5. Submit a separate website-form test and confirm its destination; form delivery is not the same as ordinary mailbox delivery.
6. Check the mail provider’s domain and authentication status, and resolve reported errors using its documentation.

Record the time, addresses tested, result, and changes made without retaining unnecessary message content. DNS caches can make transitions uneven, so diagnose the affected service and actual record rather than repeatedly changing unrelated settings.

What should you keep before canceling a service?

Confirm exactly what the subscription supplies: registration, DNS, files, databases, mailboxes, forwarding, certificates, or several of these together. Export the information you need and establish a working replacement before canceling a service still in use.

A website archive does not contain a separate email account’s messages. A repository does not renew the domain. Keep an inventory and use our DIY website backup and recovery plan to identify what each provider needs you to preserve.

When a change also replaces the public domain name, follow the domain-change SEO checklist. Moving hosting while keeping the same addresses and changing the domain itself are different projects.