Hosting & VPS Guides

Web Hosting vs Email Hosting: Key Differences

Learn the difference between web hosting and email hosting, which DNS records control each service, and how to avoid breaking email during website migrations.

By CheckDomainHealth Editorial Team Reviewed by Dionis Ceban Updated Jun 28, 2026 7 min read Beginner

Introduction

Web hosting and email hosting are related, but they are not the same service. Web hosting stores and serves your website files, while email hosting manages mailboxes, incoming mail, outgoing mail and email authentication.

A domain can use one provider for the website and another provider for email. For example, your website can be hosted on a VPS or shared hosting plan, while email is handled by Google Workspace, Microsoft 365, Zoho, cPanel mail or another mail provider. The important part is DNS configuration.

Quick answer

Quick answer

Web hosting is where your website runs. Email hosting is where your mailboxes send and receive email. A and CNAME records usually point the website to hosting, while MX records route email to the mail provider. SPF, DKIM and DMARC help email authentication and deliverability.

Web vs email hosting

Web hosting and email hosting use the same domain name, but they handle different services.

Web hosting

  • Stores website files, databases, applications, images and pages
  • Controls what visitors see when they open your domain in a browser

Email hosting

  • Manages mailboxes, mail routing, sending and receiving
  • Controls whether addresses like info@example.com can send and receive mail
  • Handles spam filtering and email authentication

Your website can work while email is broken, and email can work while the website is down. That is because they depend on different DNS records and server services.

Web hosting

Web hosting makes your website available online.

It usually handles:

  • website files
  • WordPress or CMS files
  • databases
  • images and media
  • web server response
  • HTTPS/SSL for the website
  • website redirects
  • control panel access
  • FTP/SFTP or deployment
  • website backups
  • website performance

Common DNS records for web hosting:

  • A record
  • AAAA record
  • CNAME record
  • CAA record
  • TXT verification records

When you change web hosting, you usually update A, AAAA or CNAME records. You should not change MX records unless you also want to move email.

Email hosting

Email hosting manages email addresses and mail flow for your domain.

It usually handles:

  • mailboxes
  • incoming mail
  • outgoing mail
  • SMTP
  • IMAP/POP3
  • spam filtering
  • webmail
  • email forwarding
  • mail storage
  • email security
  • email authentication
  • mail logs depending on provider

Common DNS records for email hosting:

  • MX records
  • SPF TXT record
  • DKIM TXT or CNAME records
  • DMARC TXT record
  • Autodiscover records
  • mail CNAME or A records
  • reverse DNS for mail servers

When email is hosted externally, your website hosting provider does not need to receive mail for the domain.

DNS records

Website records

  • A — points root domain to website IP
  • AAAA — points root domain to IPv6 website IP
  • CNAME — points subdomain such as www to another hostname
  • CAA — controls which certificate authorities may issue SSL
  • TXT verification — used by hosting, CDN or search tools for ownership verification

Email records

  • MX — routes incoming email to mail servers
  • SPF — authorizes sending servers
  • DKIM — adds cryptographic email signing
  • DMARC — defines policy and reporting for SPF/DKIM alignment
  • Autodiscover — helps email clients find settings
  • PTR/rDNS — matches mail server IP identity for deliverability

Changing the wrong DNS record can break the website, email or both.

Example DNS records 
Website records:

example.com.      A      192.0.2.10
www.example.com.  CNAME  example.com.

Email records:

example.com.      MX     10 mail.example.com.
example.com.      TXT    "v=spf1 include:_spf.examplemail.com ~all"
selector._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=..."
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

These records are examples only. Replace them with values from your real web and email providers.

Separate providers

Yes — website and email can be hosted separately. This is common and often recommended.

Examples:

  • Website on shared hosting, email on Google Workspace
  • Website on VPS, email on Microsoft 365
  • Website on WordPress hosting, email on Zoho
  • Website on CDN/VPS, email on cPanel mail
  • Website on Webflow or Shopify, email on external mail provider

Benefits:

  • better email reliability
  • easier website migrations
  • specialized spam filtering
  • better mailbox management
  • fewer risks when moving website hosting
  • more flexible provider choices

The domain connects these services through DNS. The providers do not need to be the same.

Website migration

During a website migration, you usually move the website files, database and web server destination. Email should remain unchanged unless you intentionally move email too.

Safe website migration usually changes

  • A record
  • AAAA record
  • CNAME for www
  • SSL/HTTPS setup
  • website redirects

It should usually not change

  • MX records
  • SPF record unless sending source changes
  • DKIM records
  • DMARC record
  • mail autodiscover records

Many email outages happen because someone changes nameservers or DNS zones during a website migration and forgets to copy email records.

Website migration checklist without breaking email

Use this checklist before and after moving website hosting.

Identify website host

Confirm where the site files and database currently live.

Identify email host

Confirm which provider handles mailboxes and MX routing.

Export current DNS zone

Save a full copy of all records before changes.

Copy MX records

Keep incoming mail routing unchanged unless moving email.

Copy SPF record

Preserve authorized sending sources.

Copy DKIM records

Keep signing records for the active mail provider.

Copy DMARC record

Preserve policy and reporting settings.

Copy autodiscover records

Keep email client auto-configuration working.

Copy verification TXT records

Include hosting, CDN and tool verification records.

Lower TTL if needed

Reduce TTL before migration for faster propagation.

Change only website records

Update A, AAAA or CNAME for the new web host.

Test website after change

Check status, SSL, redirects and www behavior.

Test email after change

Send and receive test messages.

Monitor bounces and forms

Watch contact forms and delivery after DNS updates.

Do not delete the old DNS zone until the new zone contains all required records.

Nameserver changes

Changing nameservers moves DNS control to another provider. If the new DNS zone does not include the old email records, email can stop working even if the website works.

Before changing nameservers, copy:

  • A/AAAA records
  • CNAME records
  • MX records
  • SPF TXT record
  • DKIM records
  • DMARC record
  • verification TXT records
  • autodiscover records
  • subdomain records

A nameserver change is not only a website change. It can affect every DNS-based service on the domain.

Why this matters

Why this matters

Understanding web hosting vs email hosting matters because website changes can accidentally break email. A business may move a website to a new server, update nameservers, or change DNS records, then discover that mailboxes no longer receive messages.

Keeping website and email records separate helps avoid downtime, lost emails, failed contact forms and deliverability issues.

How to check setup

Use Domain Health Checker, DNS Lookup and MX Lookup to see how the domain is configured.

  1. Website destination — check A, AAAA and CNAME records.
  2. Email routing — check MX records and confirm they point to the correct mail provider.
  3. SPF — confirm the SPF record includes all legitimate sending services.
  4. DKIM — confirm DKIM is published for your mail provider.
  5. DMARC — confirm DMARC exists and has a suitable policy.
  6. SSL — check the website certificate and HTTPS setup.
  7. Nameservers — confirm DNS is managed by the expected provider.
  8. Mail subdomains — check mail, autodiscover or provider-specific CNAME records.

Run Domain Health Check

Use Domain Health Checker to review DNS, MX, SPF, DKIM, DMARC, SSL and website status for your domain.

Run Domain Health Check →

Common problems

Website moved but email broke

High

DNS or nameservers changed and old MX records were not copied.

Next step: Restore correct MX, SPF, DKIM and DMARC records.

MX records point to wrong provider

High

Incoming mail is routed to the wrong mail servers.

Next step: Update MX records according to the active email provider.

SPF missing new sending source

Medium

Website forms, CRM or SMTP provider may send mail but are not authorized.

Next step: Add the legitimate sending service to SPF without creating multiple SPF records.

DKIM not configured

Medium

Outgoing email is not cryptographically signed by the mail provider.

Next step: Publish the DKIM record provided by the email service.

DMARC missing

Medium

The domain has less control over spoofing and email authentication reporting.

Next step: Add a starter DMARC record and monitor results.

Nameserver change lost mail records

High

The new DNS zone does not include required email records.

Next step: Copy all DNS records from the old zone before switching nameservers.

Website contact form does not send

Medium

The website server may not be authorized to send email or SMTP is misconfigured.

Next step: Use authenticated SMTP and update SPF/DKIM if needed.

Mail subdomain points to web server

Medium

mail.example.com may point to the wrong server.

Next step: Set mail-related records according to the email provider.

Email hosted on shared server with poor reputation

Medium

Shared IP reputation can affect deliverability.

Next step: Check SPF, DKIM, DMARC, rDNS and provider reputation.

Web and mail SSL confused

Low

Website SSL and mail server TLS are different services.

Next step: Check SSL for website and mail service separately if needed.

How to manage safely

  1. Step 1: Identify current providers

    Find where the website is hosted and where email is hosted.

  2. Step 2: Export DNS records

    Before migration, copy the full DNS zone.

  3. Step 3: Protect email records

    Keep MX, SPF, DKIM, DMARC and autodiscover records unchanged unless moving email.

  4. Step 4: Change website records only

    Update A, AAAA or CNAME records for the website destination.

  5. Step 5: Test website

    Check status, SSL, redirects and www/non-www behavior.

  6. Step 6: Test email

    Send and receive test emails after DNS changes.

  7. Step 7: Check authentication

    Verify SPF, DKIM and DMARC after changes.

  8. Step 8: Monitor for issues

    Watch email bounces, contact form delivery and DNS propagation.

Example web and email setups 
Example 1: Website and email on same cPanel hosting

Website:
A record → shared hosting IP

Email:
MX → same hosting server
SPF/DKIM/DMARC → cPanel mail records

Best for:
Simple small business setup.

Example 2: Website on VPS, email on Google Workspace

Website:
A record → VPS IP

Email:
MX → Google mail servers
SPF/DKIM/DMARC → Google Workspace records

Best for:
Website control with professional email hosting.

Example 3: Website on WordPress hosting, email on Microsoft 365

Website:
CNAME/A record → WordPress host

Email:
MX → Microsoft 365
SPF/DKIM/DMARC → Microsoft records

Best for:
Managed website with separate business email.

Examples are illustrative. Always use the exact DNS values provided by your hosting and email providers.

Contact forms

A website contact form is where web hosting and email hosting often overlap.

A form may send email using:

  • local server mail
  • authenticated SMTP
  • external email API
  • CRM integration
  • WordPress SMTP plugin
  • transactional email provider

Use authenticated SMTP or a transactional email service instead of relying on unauthenticated local mail.

If your website sends mail, make sure the sending service is included in SPF and uses DKIM where available.

Frequently asked questions

Is web hosting the same as email hosting?

No. Web hosting serves your website. Email hosting handles mailboxes, sending, receiving and mail routing.

Can my website and email be hosted by different providers?

Yes. This is common and often recommended for business email reliability.

Which DNS records control the website?

Usually A, AAAA and CNAME records.

Which DNS records control email?

MX records route incoming email. SPF, DKIM and DMARC support authentication and deliverability.

Will changing website hosting break email?

Not if DNS is handled carefully. Email can break if MX or mail-related records are removed or changed.

What happens if I change nameservers?

All DNS control moves to the new nameservers. You must copy website, email and verification records.

Should I host email on the same server as my website?

It can work for simple setups, but dedicated email providers often offer better reliability, spam filtering and mailbox features.

Use these free tools to verify your configuration after applying changes.

Domain Health Checker DNS Lookup MX Lookup SPF Checker DKIM Checker DMARC Checker SSL Checker Website Status Checker
Shared Hosting vs VPS vs Dedicated Hosting 8 min read Setting Up Your First VPS: Beginner Guide 10 min read Sending Email from Shared Hosting: Limits and Best Practices 8 min read Dealing with Hosting Provider Limits and Throttling 8 min read Setting Up a Self-Hosted Mail Server on a VPS 11 min read
Browse all Hosting & VPS guides →

Need help applying this fix?

Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.

Get Help Run Domain Health Check

Was this guide helpful?

Your feedback helps us improve our guides for everyone.