Web Host vs Domain Registrar: What's the Difference?
Updated: 1 day ago
A domain registrar sells you a domain name and manages its registration. A web host stores your website's files and serves them to visitors.
The two are separate services with separate jobs, and a working website needs both. The confusion comes from the fact that most companies now sell both, often on one invoice, which makes them look like a single product.
They are not. Knowing which one does what is the difference between a fifteen-minute fix and a week of support tickets when something goes wrong.
Quick Answer: A domain registrar registers and manages your domain name — the address people type. A web host stores the files that make up your site and delivers them when someone visits that address. You need both, and you can buy them from one company or from two. The domain name belongs to you either way.
What a domain registrar does
A domain registrar is a company accredited to register domain names on your behalf with the organization that operates the relevant extension.
That accreditation is what separates a registrar from a reseller. For extensions like .com and .org, ICANN — the Internet Corporation for Assigned Names and Numbers — accredits registrars and sets the rules they operate under. The registrar submits your registration to the registry that actually runs the extension. Verisign operates .com and .net. Public Interest Registry operates .org.
So every domain registration involves three parties, not two:
The registry operates the extension and holds the authoritative record of who has what.
The registrar is your point of contact, takes your payment, and submits changes to the registry.
The registrant is you — the person or company the name is registered to.
A registrar controls four things on your behalf:
Registration and renewal of the name, for a term you choose.
The WHOIS record, which holds the contact and administrative data attached to the registration.
The nameservers the domain points to, which is how the name gets connected to a host.
Transfer authorization, including the lock status and the code needed to move the name elsewhere.
Registration is a lease, not a purchase. You hold the exclusive right to use the name for as long as you keep renewing it, and ICANN caps generic extension terms at 10 years, so nobody can sell you a name permanently.
The nuance: some registrars advertise very long or even lifetime registrations. What they are actually selling is a prepaid auto-renewal arrangement on their own side — the registry record still maxes out at 10 years, and the promise depends on that company still existing to keep renewing it. A domain is only ever registered as far ahead as the registry says it is.
Checking availability is the first thing anyone does with a registrar, and it is worth doing before you settle on a name rather than after. A domain name search shows whether a name is free across extensions in one pass, which usually changes the shortlist — the .com is gone, but a shorter name you had not considered is available on three extensions.
What a web host does
A web host provides the server space and network connection that store your website's files and deliver them to visitors.
When someone types your domain, their browser ends up requesting files from your host's server. The host returns HTML, images, stylesheets, and whatever else the page needs. Without a host, your domain resolves to nothing at all.
A web host is responsible for:
Disk space for your site's files and database.
Bandwidth to serve those files to visitors.
Uptime — keeping the server reachable.
Server software and, on managed plans, its patching and updates.
Backups, SSL certificate provisioning, and often a content delivery network.
Hosting comes in five broad shapes. The difference between them is how much of a server you get and how much of it you are expected to manage:
Shared hosting puts many sites on one server. It is the cheapest option, and your site's performance depends partly on its neighbors.
VPS hosting gives you a guaranteed slice of a server with isolated resources.
Dedicated hosting gives you the whole machine.
Cloud hosting spreads your site across pooled infrastructure and scales with demand.
Managed or platform hosting bundles the server, the software, and the operations together, so you never see the server at all.
Platform hosting is where most non-technical site owners now land, because the operational work disappears rather than moving somewhere else. Web hosting on Wix works this way — it is not sold as a separate product, but included with the site, with the CDN, SSL, and scaling handled on the platform side. If you want a closer look at how shared, VPS, dedicated, and cloud hosting differ, this beginner's guide to how web hosting works covers each type.
Hosting without your own domain
Every hosted website has an address, but it does not have to be one you registered.
Hosts give new sites a free address on a domain they already own — a subdomain along the lines of yoursite.example-host.com. The site is fully hosted and publicly reachable, with no registrar involved at any point. Wix's free tier works this way, putting the site on a Wix-branded address until you connect a domain of your own.
The arrangement is genuinely useful in three situations, and a bad idea in a fourth:
Testing and staging. You need the site reachable and reviewable before committing to a name.
Short-lived projects. An event page or a one-off campaign does not need a renewable asset attached to it.
Learning. There is no reason to pay for a name while you work out whether the site will exist at all.
Not for a business. A subdomain address cannot be moved. Outgrow the host and the address does not come with you, every link pointing at it breaks, and you cannot run email on it.
That last point is the cleanest illustration of what a registrar actually sells. A host gives you somewhere for the site to live. A registrar gives you an address that stays yours when the place changes.
It also explains why the two services are priced so differently. Hosting is a recurring cost for a consumable resource, so you pay for what you use and stop paying when you stop using it. A domain is a recurring cost for exclusivity, so the price is largely the same whoever you buy it from, and the thing you lose by stopping is the address rather than the storage.
Web host vs domain registrar: side-by-side
Dimension | Domain registrar | Web host |
What you get | The right to use a domain name | Server space and bandwidth |
Governed by | ICANN and the relevant registry | No central authority |
Billing cycle | Annual, up to 10 years prepaid | Monthly or annual |
If you stop paying | The name lapses and anyone can register it | The site goes offline and files may be deleted |
Portable? | Yes — transfer registrars, name unchanged | Yes — move the files, domain unchanged |
Typical cost | $10–$25 a year for a standard .com | A few dollars a month to several hundred |
Needed for a custom address? | Yes | Yes, for the site to exist |
Controls your email? | Controls the records that route it | Only if it also provides the mailbox |
Prices in both columns move, and domain pricing in particular changes when a registry raises its wholesale rate. Treat the ranges as orientation and check current rates before you budget.
What domains and hosting actually cost, separately
The two have different pricing models, and the renewal traps sit in different places.
Domain pricing is largely set by the registry. A .com wholesales at a rate Verisign sets and every registrar pays, with retail sitting above it. That is why .com prices cluster in a fairly narrow band across registrars, and why a first-year offer under a dollar is always subsidized by the renewal. Newer extensions behave differently — many are cheap in year one and several times that afterward, because the registry itself prices them that way.
Hosting pricing is set by the host and reflects real resource cost, so the spread is enormous. Shared hosting starts at a few dollars a month. Dedicated servers run into the hundreds. Managed platforms sit in between and charge for capability rather than raw capacity.
Three pricing details are worth checking before you commit, in either category:
The renewal price, not the introductory one. Both industries discount the first year heavily. On domains, check the specific extension — the renewal multiple varies wildly between extensions at the same registrar.
What the first-year price includes. Privacy, SSL, and email are sometimes bundled at signup and charged separately at renewal.
The refund window. Hosting usually prorates or refunds within a window. Domain registrations generally do not refund at all, because the registry fee is already spent.
Do you own your domain name?
You hold an exclusive, renewable right to use a domain name. You do not own it the way you own a trademark or a piece of equipment.
The practical test is what happens when you stop paying, and for generic extensions that sequence is set by ICANN rather than by your registrar:
The domain expires. Most registrars hold it in an auto-renew grace period first, commonly up to 45 days, during which you can renew at the ordinary price. Your website and email stop working at the start of that period, not the end of it.
The redemption grace period begins. This runs 30 days. The name is pulled from active service but still recoverable — for a redemption fee that is typically many times the renewal price.
Pending delete. A five-day window in which nothing can be done by anyone.
The name drops. It returns to the available pool. For any domain with traffic or backlinks, a drop-catching service will usually register it within seconds of release.
That timeline is the strongest argument for treating domain renewal differently from every other subscription you pay. A lapsed hosting bill takes your site offline and you get it back by paying the bill. A lapsed domain can be gone permanently, and every email address on it goes with it.
Two habits prevent the whole scenario. Register for several years at a time rather than annually, which removes most of the renewal events where something can go wrong. And make sure the registrant email on the WHOIS record is an address that will still be monitored in five years — a role address the business controls, not the personal address of whoever happened to set the site up.
Why domains and hosting are sold together
The handoff between a domain and a host is the single most common place a new site owner gets stuck, and selling both removes it.
Pointing a domain at a host means editing nameserver or DNS records at the registrar to match values the host supplies. It takes five minutes if you have done it before and is genuinely confusing if you have not. A company that sells both can configure it for you, or skip the step entirely because both sides are already on the same account.
That is the real product in a bundle. Not a discount — the removal of a configuration step, plus a single support line when something in that configuration breaks.
Registrars also bundle services that have nothing to do with hosting.
Certain domain registrars offer packages with added security (like WHOIS privacy protection), premium DNS services, SSL certificates or website-building tools. While these extras can increase the annual cost, they offer value in terms of convenience, security and performance. For businesses handling sensitive data or relying heavily on online transactions, these features are crucial.
— Kumar Abhinav, Senior Link Building Analyst, Mavlers
Read that as a caution as well as a recommendation. The extras are genuinely useful, and they are also where renewal prices climb, because an introductory rate rarely includes them at the same price.
Should you buy your domain and hosting from the same company?
Both arrangements work. The decision is really about who you call when something breaks, and what happens if you cannot reach them.
Buying both from one company gives you one bill, one support contact, and DNS that is already configured. It also means a single account controls both your name and your site.
Buying them separately keeps the domain independent of your hosting decisions. Change hosts and you change DNS records, nothing more. Some agencies deliberately register client domains at a registrar they never host with, so a hosting dispute can never hold a client's name hostage.
Here's the subtlety: the case for separating them is usually framed as avoiding vendor lock-in, but domain lock-in is mostly a myth — ICANN's transfer policy obliges any registrar to release your name on request, and the name itself never changes. The real reason to separate them is narrower. It keeps the recovery path clean. If the account holding your hosting is compromised, suspended, or simply locked behind an ex-employee's email, an account somewhere else still holds the name that points to it, and you can repoint it within the hour. That scenario is rare, and it is the one that actually costs businesses their web presence.
How DNS connects your domain to your web host
DNS, the Domain Name System, translates your domain name into the IP address of the server your site lives on.
The connection is made at your registrar, in one of two ways:
Change the nameservers to the ones your host provides. Your host then controls every DNS record for the domain. This is the usual choice and the simpler one.
Keep your registrar's nameservers and edit records directly. You add an A record pointing at the host's IP address, or a CNAME pointing at a hostname the host supplies. This keeps DNS control at the registrar, which matters when other services depend on those records.
Changes do not appear everywhere at once. Every DNS record carries a TTL — a time-to-live value in seconds — telling resolvers how long to cache it. Until cached copies expire, some visitors reach the old server and some reach the new one. This is what people mean by DNS propagation, and it is not one process finishing at a set time but thousands of caches expiring on their own schedules. Lowering the TTL a day before a planned move shortens the window considerably.
What happens if you switch web hosts or registrars
Switching a web host and switching a registrar are unrelated operations, and neither one changes your domain name.
Switching hosts means copying your files and database to the new server, testing there, then updating DNS to point at it. The domain, its registration, and its expiry date are untouched throughout.
Switching registrars means unlocking the domain at the current registrar, getting the authorization code, and submitting a transfer at the new one. Your site keeps serving from the same host the whole time, provided the DNS records travel with the domain or the nameservers stay the same.
Two ICANN rules shape registrar transfers:
A domain cannot be transferred within 60 days of registration, or within 60 days of a change to the registrant's name or email address.
A transfer adds a year to the registration rather than restarting it, so remaining time is not lost.
The gotcha in a registrar transfer is DNS hosting. If your records live on the old registrar's nameservers, moving the domain can take those records with it and your site goes dark while you rebuild the zone. Export the zone before you start, or move DNS to your host first and transfer the name afterward.
Where business email fits between your registrar and host
A domain can carry email as well as a website, and neither your registrar nor your host necessarily provides the mailbox.
Three parties can be involved in a single email address:
The registrar controls the MX records that say where mail for the domain should go.
The mailbox provider actually stores and serves the mail.
The web host is usually not involved at all, unless it bundles mail as part of the plan.
Setting up business email on your own domain therefore means pointing MX records at whichever provider holds the mailboxes. Some registrars and hosts resell mailboxes so those records arrive preconfigured; others leave the records to you. Either way it is the domain that makes the address possible, which is one good reason to register a name before you need a website.
Common mistakes when a web host and registrar are separate
Splitting the two is a sound choice, but it creates four failure modes that a bundle does not have:
Letting the domain lapse while hosting stays on autopay. The site is up, fully paid, and unreachable, because the address stopped resolving. Two vendors means two renewal dates and two payment methods to keep current.
Registering the domain in a contractor's account. The name is an asset. If it is registered to a developer or agency rather than the business, recovering it later depends on their cooperation. Check the registrant with a free WHOIS lookup, not the invoice.
Changing nameservers before the new site is ready. Point the domain at the new host only after the site works there. Nameserver changes propagate at their own pace and are awkward to reverse quickly.
Forgetting email when moving DNS. Switching nameservers to a new host replaces the whole DNS zone, including the MX records. Copy the mail records over first, or the website moves and the email silently stops.
What a registrar can fix, and what a web host can fix
When a site goes wrong, the fastest diagnostic step is working out which of the two you should be contacting.
Contact your registrar when:
The domain has expired, or is about to.
The domain does not resolve at all — no error page, just a failure to connect to anything.
You need to change nameservers, or edit DNS records held at the registrar.
You are transferring the name, or need the authorization code to do it.
The WHOIS or registrant details are wrong.
Email for the domain stops working and nothing about the website changed.
Contact your web host when:
The site loads but returns an error, a blank page, or a server message.
The site is slow, or drops out intermittently under traffic.
SSL is broken and the browser warns about the certificate.
Files, databases, or backups need restoring.
You need a staging environment or server-level configuration.
The dividing line is whether the address resolves at all. If the browser cannot find a server to talk to, the problem is at the registrar or in DNS. If it finds the server and the server answers badly, the problem is at the host. Support agents on both sides run that same test before anything else, so running it yourself saves a round trip and usually a day.
One case genuinely sits between them: a site that works on one network and not another. That is almost always DNS caching rather than a fault at either company, and it resolves itself as records expire.
Web host vs domain registrar FAQ
Do I need both a web host and a domain registrar?
Yes, for a website at your own domain. The registrar gives you the address and the host serves the content at that address. One company can provide both, but the two functions stay separate, and you are always paying for both even when they appear on a single invoice.
Can I buy a domain name without hosting?
Yes. A domain with no hosting attached simply does not resolve to a website, which is a perfectly normal thing to do — people register names to hold them, to run email only, or to redirect to a site that already exists. Registrars sell domains as standalone products.
Can I use a domain from one company with hosting from another?
Yes, and it is common. Change the domain's nameservers to the ones your host provides, or add an A or CNAME record pointing at the host. Both are done in the registrar's DNS settings and usually take effect within a few hours.
How long can I register a domain name for?
Up to 10 years at a time for generic extensions like .com, which is the maximum ICANN allows a registry to record. You can renew before expiry to extend again, but the registry never holds a registration more than 10 years ahead.
What is ICANN and why is there a fee on my domain?
ICANN is the nonprofit that coordinates the domain name system and accredits registrars. It charges registrars a mandatory fee of roughly $0.20 per domain per year, which they pass on to you. It shows up as a small line item, and a registrar that itemizes it is not adding a surcharge of its own.
What is WHOIS privacy and do I need it?
WHOIS is the directory of domain registration contact data, and WHOIS privacy replaces your details with a forwarding service's. Most registrars now redact personal data for individual registrants by default following GDPR, so paid privacy adds less than it once did. It still matters when a domain is registered to a named person rather than a company, or under an extension whose registry publishes full records.
Choosing between bundled and separate domain and hosting
For most site owners, buying the domain and hosting together is the better default. The configuration step disappears, there is one number to call, and the lock-in risk people worry about is largely theoretical.
Separate them when the domain matters more than the site. An agency holding client names, a business whose email is more critical than its website, or anyone who has been locked out of an account once already all have a real reason to keep the name somewhere the hosting cannot reach it.
Either way the name comes first. You can buy a domain name and add hosting later, but you cannot host a site at an address you do not hold.
Comments