Domain vs Hosting: What Is the Difference?
One is the address. The other is the building. They are sold together so often that most people never learn they are separate purchases, and that confusion is what makes migrations painful.
September 9, 20265 min readHosting · DNS · Beginners
The short answer. A domain is your address. Hosting is the building. The domain does not store your website, and the host does not own your name. You need both, they are separate purchases, and buying them separately is usually the better decision.
Almost everyone meets these two things bundled together on a checkout page, which is why so many people believe they are one product. They are not, and knowing the difference is what turns "my site is down and I do not know who to call" into a two-minute fix.
The analogy that actually holds
Think of a shop.
| The thing | In the real world | On the internet |
|---|---|---|
| Domain | The street address on the sign | yourbusiness.com |
| Hosting | The building the shop occupies | A server with your files on it |
| Website | The stock, shelves and staff | Your pages, images and code |
| DNS | The postal service directory | Records pointing the name at the server |
You can own an address with no building. You can rent a building nobody has an address for. Neither is much use alone.
What each one actually gives you
The domain gives you a name and the right to point it wherever you like. That is genuinely all it does. It stores no files, serves no pages and holds no email. It is a pointer.
The hosting gives you a machine with an IP address that answers requests. It has your files on it. Without a domain, that machine is reachable only by typing a string of numbers.
How they connect
The link between them is DNS, and specifically two settings.
- Nameservers, set at your registrar, decide which servers are allowed to answer questions about your domain.
- DNS records, held by whoever runs those nameservers, say where each kind of traffic goes. An
Arecord points the web at your host's IP address.MXrecords point email somewhere, often somewhere completely different.
This is the bit that surprises people. Your website and your email are routed independently. Your site can be on one provider and your mail on another, and neither knows the other exists. That is why deleting the wrong record breaks your email while your homepage keeps working perfectly.
If you want the full sequence of what happens between someone typing your name and your page appearing, we walk through it step by step.
Do you always need both?
No, and this is where people overspend.
You need hosting if you are running a site with your own files, a database, or an application.
You do not need traditional hosting if you are using a platform that includes it. Shopify, Squarespace, Webflow, Substack, Notion sites and most site builders host the thing for you. You bring a domain and point it at them. Buying separate hosting alongside one of these is pure waste, and it happens constantly.
You do not need hosting at all if you only want email at your own domain, or if you are parking a name for later. A domain on its own is a perfectly reasonable thing to hold.
The reverse case
You can also have hosting without a domain, though only briefly. Most hosts give you a temporary address like yoursite.hostingcompany.net so you can build before your name is ready. It works, but never launch on one: every link anyone shares becomes worthless the day you move.
Should you buy them from the same company?
Usually not, and the reason is asymmetry.
Your hosting is replaceable. Your domain is not. You can move hosts in an afternoon and nobody notices. A domain carries every link, every bookmark, every business card and every search ranking you have ever earned. It is the one asset that cannot be swapped out.
Keeping them separate means the company you are unhappy with is never the company holding your name hostage. When a host is slow, expensive or unreliable, you move, and your domain is not part of the argument.
There is a second, quieter reason. Bundled "free domain for the first year" offers are a retention device. The domain is free while you host with them and renews at an unattractive rate afterwards, and some make the transfer out deliberately tedious. You are trading a small discount for switching costs later.
What a sensible setup looks like
- Registrar: whoever is cheapest at renewal and does not upsell, holding only your domain
- DNS: your registrar's nameservers, or a dedicated DNS provider
- Hosting: chosen purely on what your site needs
- Email: a provider chosen for mail, which is rarely your host
Four separate things, each replaceable without touching the others.
The three failures this causes
"I moved hosts and my site went down." The A record still points at the old server. Update it, and expect the change to take as long as the record's TTL allows.
"I transferred my domain and my email stopped." The DNS records lived at the old registrar and did not travel with the registration. This is the single most common transfer disaster, and it is entirely avoidable by copying your records before you start.
"I cancelled my hosting and lost my domain." Bundled purchases sometimes cancel together. Check what a cancellation actually terminates before you click it.
Costs, honestly
| Item | Typical yearly cost | Notes |
|---|---|---|
| Domain | 10 to 60 dollars | Depends heavily on the extension |
| Shared hosting | 30 to 150 dollars | Fine for most small sites |
| Managed platform | 150 to 500 dollars | Hosting included, no separate purchase |
| Static hosting | Often free | Generous free tiers for simple sites |
| Email at your domain | 12 to 90 dollars per user | Separate from all of the above |
The domain is nearly always the smallest line and the most important one. It is also the only one where the price you were quoted in year one may not be the price in year two, so compare renewal rates rather than headline offers.
What to do next
If you have neither yet, get the domain first. Names run out, hosting never does. Check what is available, or generate candidates from your concept if you do not have a word yet.
Then pick hosting based on what you are actually building, and keep the two accounts apart. Future you, migrating something at an awkward moment, will be grateful.
Put the research to work.
Check your shortlist across the extensions that matter, then save the strongest names to a project.
Check a domain