Domain Name vs Web Hosting: What Is the Difference?

TLDR: A domain name is the address people enter to reach your website. Web hosting is the server or platform that stores and serves the site. DNS supplies the routing instructions that connect the domain to the host and other services, including email. You can buy, renew, transfer or replace these services separately, even when one company bundles them together.

The easiest way to understand domain name vs web hosting is to picture a business location. The domain is the public address, hosting is the building and its contents, and DNS is the set of directions telling visitors and deliveries where to go. A website normally needs all three functions, but one provider does not have to perform all of them.

That distinction matters when you renew a domain, move a website, change email providers or transfer registration. Changing the wrong setting can leave the site online but stop email, or leave the hosting account active while the domain no longer leads visitors to it.

Domain name vs web hosting at a glance

Component	What it does	Typical owner task	Can it move independently?
Domain name	Provides the human-readable address, such as example.com	Register, renew or transfer it	Yes
Domain registrar	Manages the domain registration account	Maintain access, billing, locks and transfer details	Yes
DNS and nameservers	Route the domain to website, email and verification services	Add records or delegate DNS to a provider	Yes
Web hosting or website platform	Stores and serves the website and its application data	Publish, back up, secure or migrate the site	Yes
Business email	Receives and sends mail using the domain	Manage mailboxes and email DNS records	Yes

A domain gives people a memorable way to request a site, while a web server responds with the files or application output that forms the site. MDN’s website publishing overview explains this relationship between hosting content and connecting a domain.

Do you need both a domain and hosting?

You can register a domain before building a website. It can remain reserved for a future project, redirect elsewhere or be used for email. Registration alone, however, does not create a website.

To publish a site at that address, you need a destination that can serve it. That might be conventional shared hosting, a managed WordPress host, an ecommerce platform, a site builder or a static hosting service. The packaging differs, but the operational model remains similar: the domain’s DNS must point web requests toward the platform.

Buying the domain early can be sensible if the name is central to the business. It also gives you a stable address while you decide which pages your small-business website needs. Just record where the domain is registered, who controls the account and when it renews.

What the registrar controls

A registrar is the company through which you register and manage a domain. Its account commonly controls renewal, contact and recovery details, registrar locks, nameserver delegation and transfer authorization. The registrar might also sell hosting, but domain registration and hosting remain separate services.

Paying a hosting invoice does not necessarily renew the domain. If the domain expires, the hosting server may continue running while visitors and email systems can no longer reach it through the expected name. Recovery conditions and timing vary by top-level domain, registry and registrar, so do not depend on a universal grace period. ICANN advises registrants to contact their registrar for renewal help and notes that a gTLD in Redemption Grace Period must be restored before it can be transferred. ICANN’s domain renewal and expiration FAQ provides the relevant general guidance.

For a business domain, keep the registration in an account the business controls. Use a durable recovery email, enable available account security, document billing responsibility and avoid tying all recovery access to an employee or contractor who may leave.

DNS connects the domain to hosting and email

DNS records describe where different requests for the domain should go. Nameservers identify the service responsible for answering DNS queries, while individual records handle specific destinations. The registrar, DNS provider and web host can therefore be three different companies.

A and AAAA records point a hostname toward an IPv4 or IPv6 address.
A CNAME record makes one hostname an alias of another hostname.
MX records identify the systems that receive email for the domain.
TXT records often carry ownership verification and email-security policies.
Other provider-specific records may support services such as certificate validation or automatic configuration.

Before changing nameservers, export or otherwise record every existing DNS entry. A new nameserver provider does not automatically know about records held by the old provider. Recreating only the website records can make the site work while breaking mail, verification or another subdomain. Cloudflare’s DNS record documentation is a useful reference for the purposes and settings of common record types.

Why business email is a separate concern

Using an address such as hello@example.com does not mean the mailbox lives on the website’s server. MX records tell sending mail systems which provider receives mail for the domain, and those records are managed in DNS.

This separation lets you move a website while leaving business email with its existing provider. In that situation, change only the records needed for web traffic and preserve the MX records plus related TXT and CNAME records. Those supporting records may be involved in sender authentication, verification or mail client configuration.

DNS changes are not always visible everywhere immediately because providers and resolvers cache answers according to record settings and their own behavior. For example, Google Workspace says recognition of newly configured MX records can take up to 72 hours in its setup workflow, but that figure is not a universal promise for every DNS change.

How to move web hosting but keep the domain and email

A hosting migration copies the website to a new server or platform. It does not inherently require transferring the domain to another registrar or moving email. WordPress documentation explicitly distinguishes moving a site to a new server while keeping the same domain and URLs from a migration that also changes the domain and URLs.

For a typical migration, use this sequence:

Identify the current registrar, authoritative DNS provider, web host and email provider. Do not assume they are the same company.
Inventory all DNS records before editing anything. Include web, mail, verification and subdomain records.
Create a current backup and copy the website, database and required configuration to the new host. Follow the platform’s migration process rather than assuming every site works like WordPress.
Test the new copy using a temporary URL, preview facility or local hosts-file override when the provider supports it.
Configure HTTPS on the new destination and test pages, forms, checkout, logins, uploads and scheduled or transactional messages.
Change only the web-related DNS records unless the migration plan explicitly includes DNS or email.
Check the site from more than one network and verify that inbound and outbound business email still work.
Keep the old hosting account available until traffic is reaching the new service and you have confirmed that no required files, mailboxes or background jobs were left behind.

If you also change nameservers, first reproduce the entire DNS zone at the new DNS provider. Treat a nameserver change as a broader routing change, not merely a hosting switch.

How to transfer a domain without moving the website

A registrar transfer changes who manages the registration. It does not have to change the website’s host, DNS provider or email provider. The key is to preserve the existing nameserver configuration unless you deliberately intend to move DNS too.

For a gTLD transfer, check eligibility and account access, confirm that you can receive required messages, unlock the domain where applicable and request the authorization code, sometimes called an auth or EPP code. ICANN says an authorization code is required for a gTLD registrar transfer. If the registrant cannot generate it in the control panel, the registrar must provide it within five calendar days of a request. ICANN’s authorization-code guidance explains the requirement.

ICANN’s standardized authorization form says a completed transfer generally occurs within five calendar days unless it is denied and normally results in a 60-day restriction on another registrar transfer. These rules concern covered gTLD transfers; country-code domains can follow different registry policies.

After the transfer, confirm that the nameservers did not change, DNS still answers correctly, renewal settings are appropriate and the registration account has secure recovery details. Do not cancel an unrelated hosting or email account merely because the registrar changed.

The mistakes that cause most disruption

Letting the domain expire while assuming an active hosting subscription keeps the address working.
Replacing nameservers without copying the old DNS records first.
Changing MX records during a website migration even though email is staying with the existing provider.
Treating a registrar transfer as if it automatically copies the site or database.
Canceling the old host before checking forms, HTTPS, background jobs and production traffic.
Giving a contractor permanent ownership of the registrar account instead of delegated access where available.
Keeping no written inventory of providers, renewal dates, nameservers and critical DNS records.

Should one company manage everything?

A single provider can be simpler for a small site because billing and support are concentrated in one account. The tradeoff is that an account-access problem or poorly planned cancellation can affect several services at once. Bundling also makes it easier to forget which technical function each product performs.

Using separate providers offers flexibility. You can replace an underperforming host without disturbing domain registration, or move email without rebuilding the website. It also creates more accounts and documentation to maintain.

Either arrangement can work. The important controls are business ownership of the registrar account, reliable recovery access, clear billing responsibility, a current DNS inventory and backups that are not dependent on the hosting account you may need to leave.

Common questions

Can I buy a domain without hosting?

Yes. You can register the name now and connect it to hosting later. Registration reserves the domain under the applicable terms, but it does not build or publish a site.

Can I change web hosts and keep my domain?

Yes. Copy and test the site at the new host, then update the appropriate web DNS records. The registrar and email provider can remain unchanged.

Can I transfer a domain without moving the website?

Yes. Keep the same nameservers and DNS records during the registrar transfer. The site should continue pointing to its existing host, subject to normal transfer and provider procedures.

Why did email stop after a DNS change?

The most likely cause is that the new DNS configuration lacks the correct MX or supporting records. Compare the current zone with the email provider’s required configuration and with the inventory taken before the change.

How long do DNS updates take?

There is no single guaranteed period. Record TTLs, resolver caches, provider activation and configuration all affect when a new answer appears. Plan changes with overlap time instead of assuming every visitor and mail system will switch at the same moment.

Know who controls each layer before making a change

The practical answer to domain name vs web hosting is that the domain identifies the site, hosting serves it, and DNS connects the address to the correct website, email and supporting services. Those functions may share a provider, but they do not become the same product.

Before renewing, migrating or transferring anything, write down four answers: who registers the domain, who hosts DNS, who serves the website and who handles email. Once those layers are clear, you can change one deliberately without accidentally dismantling the others.