Most people never think about hosting until something goes wrong, an invoice arrives, or they want to move their site somewhere else. Then they discover the whole thing is described in words nobody explained — hosting, domain, DNS, server, CDN — and it all sounds like the same thing.
It is not, and the differences are simple once someone lays them out.
Three things that get muddled together
Almost every confused conversation about websites is really a confusion between these three. They are separate, they are often bought from three different companies, and that is normal rather than a sign something is wrong.
- ✓Your domain name — the address people type. You rent it yearly from a registrar. It is a name and nothing more; no part of your website is stored in it.
- ✓DNS — the phone book. It says "when someone types this name, send them to that computer." Changing DNS is how a site moves house without changing its address.
- ✓The hosting — the computer that actually holds your files and hands them out.
So when you ask "where is my website?", the honest answer usually has three parts. And when a site goes down, knowing which of the three broke is most of the fix.
The question that decides everything
There is really only one: does anything need to happen on the server?
If every visitor sees the same thing — your services, your story, your contact details — then the pages can be built once and handed out identically forever. That is called a static site, and hosting one costs almost nothing.
If something has to actually run — someone logs in, a form saves to a database, a payment is taken, an email goes out on a schedule — then you need a machine that executes code. That costs money, because the machine has to be ready and someone has to keep it working.
Most small business websites are the first kind and are quietly hosted as though they were the second. It works, but it is worth knowing which you have.
The kinds of hosting there are
Roughly seven families. Most arguments about which host is "best" are really people comparing two of these as if they were competing, when they are for different jobs.
1. Static hosting
Hands out pages built in advance. Free or nearly free at any volume a small business will reach, and very fast because there is nothing to work out. Right for brochure sites, marketing sites and articles. It cannot run anything — no logins, no database, nothing on a schedule.
2. Platform hosting
Runs your code on demand without you ever seeing a server. Right for anything with logins, databases, scheduled jobs or paid services behind it. Usually has a free tier, then a flat monthly fee. The trade-off is that individual jobs get cut off after a short time limit, so anything long-running does not fit.
3. Traditional shared hosting
A slice of an ordinary always-on server, typically with a control panel, a database and email included. This is still what most of the web runs on, and it is what WordPress expects. Predictable flat cost. You share the machine, so a busy neighbour can affect you, and keeping things updated is more your responsibility.
4. Managed WordPress
Shared hosting with WordPress specifically looked after — updates, caching, backups handled for you. Costs noticeably more, and is only worth it if you are on WordPress. Some plans restrict which plugins you may install, which is occasionally a problem.
5. A server you rent
A whole machine that is yours, running whatever you install. Right when a job runs too long for a platform host, when the software is unusual, or when large files have to live alongside the site. Cheap for what you get — but it is genuinely yours to run, including the security updates and the 3am outage.
6. The big clouds
Every building block there is, assembled by you. Right for large systems or when a client's procurement insists on a particular provider. Real complexity, priced per use, and easy to overspend on before you understand it.
7. Website builders
Here the hosting comes bundled with the tool that builds the site and cannot be separated. Genuinely the right answer for someone who wants to edit their own site and never think about any of this. The trade-off is real: you are renting the whole thing, and you cannot take the site elsewhere.
The rule that catches people out
A secret key can never sit in a web page.
Anything sent to a browser can be read by anyone who looks — there is no hiding it, however cleverly it is written. So the moment your site needs a password, an API key, or access to a database, it needs somewhere private to keep that. Which means a server.
This is usually what turns a "simple" website into one that needs proper hosting. Not the design, not how many visitors you get — one form that has to save something somewhere.
It does not have to be all or nothing. A static site can hand just that one job to a small service elsewhere and stay static itself, which keeps the pages free and puts only the part that genuinely needs a server on one. If your site has a contact form and someone tells you the whole thing therefore needs expensive hosting, that is worth questioning.
Where your data physically sits
Your website and your data are usually in different places, and they can be in different countries. For a brochure site that is irrelevant. For anything holding personal details about people in Singapore, it is not.
- ✓The PDPA does not forbid sending personal data overseas, but it does require comparable protection wherever it goes — so you are expected to know where that is.
- ✓If you are a clinic, a financial firm, or you work with anyone who has a compliance department, you will eventually be asked. "I'm not sure" is a poor answer.
- ✓Most serious hosts let you choose a region. Choosing Singapore usually costs nothing extra and removes the question entirely.
- ✓Being able to name the country, the provider and the backup arrangement is worth more in that conversation than any technical detail.
What to ask whoever built your site
You do not need to understand the answers technically. You need them written down somewhere you can find, because the day you need them is usually a day something has gone wrong.
- ✓Who holds the domain, and whose name is it in? It should be yours. This is the single most important one.
- ✓Where are the files hosted, and where is any database? Which company, and which country.
- ✓Who renews the domain, and when? Put the date in your own calendar regardless of the answer.
- ✓If I wanted to move to someone else, what would I be given? A straight answer is a good sign. Hesitation is informative.
- ✓What exactly does my monthly fee cover? If the site is only pages, hosting genuinely is close to free — so the fee should be for something else, and that something should be nameable.
That last one is worth asking plainly, and a good supplier will welcome it. There is usually a real answer — a database, backups, monitoring, someone on hand when it breaks. The problem is not being charged; it is being charged for something nobody will describe.
Who is responsible for what
The host keeps the machines on, renews the security certificate that gives you the padlock, serves your site from somewhere near your visitors, and absorbs a sudden rush of traffic. That is genuinely all they do.
Everything else is yours or your developer's: the domain being renewed, DNS pointing at the right place, keys kept out of pages, backups of your data, and the site itself being correct. Hosts do not back up your database for you unless you have specifically arranged it — that assumption has cost a lot of people a lot of work.
When someone says "the website is down"
Almost every time, it is one of two things, and neither is the hosting:
- ✓The domain quietly expired. A renewal email went to an address nobody reads any more.
- ✓A DNS record was changed. Often while setting up email, which points the name at the wrong place.
Check those two before anyone starts investigating servers. It will save hours, and it is the reason knowing your own setup is worth twenty minutes of your time — once, in writing, while nothing is on fire.
Common questions
No, and this is the most common mix-up. The domain is the address people type, rented yearly from a registrar. Hosting is the computer that actually holds your files. You can keep your domain and change hosts, or keep your host and change domains — they are bought separately and often from different companies.
You already have it — it is included in what you pay, which is why it is never mentioned separately. The trade-off is that it cannot be separated either. You are renting the builder and the hosting as one thing, so moving to another provider means rebuilding rather than transferring.
Because free hosting only covers pages. If your site has anything behind it — a database of enquiries, a login, a booking system — that part needs a machine that runs code, plus backups and someone keeping it working. Ask what specifically the fee covers. If the site is genuinely only pages and nobody can name what you are paying for, that is a fair question to press.
It depends entirely on how it was set up, and it can be a different country from the website itself. It matters if you hold personal data about people in Singapore: the PDPA allows sending data overseas but expects comparable protection there, so you are meant to know where it goes. Most hosts let you choose Singapore at no extra cost, which is the simplest way to make the question disappear.
Usually yes, and it is a smaller job than people expect — for a normal site it is a DNS change rather than a rebuild. The exception is website builders, where the site cannot be exported in a usable form. The thing that actually determines how easy it is: whether the domain is in your name and whether you can get a copy of the files.
Only indirectly, and less than people are told. Google cares that your site loads quickly and stays available, and truly bad hosting can hurt on both. But moving from decent hosting to expensive hosting will not move you up the results. Content and relevance do that.
I build websites and run SEO & AEO for Singapore businesses. HeyAda is my Singapore web studio — design, copywriting, code and SEO, handled end to end. I write these guides to share what actually works, in plain English. If your site isn't getting found, say hi.
Sources
- Personal Data Protection Commission (PDPC) — pdpc.gov.sg (Transfer Limitation Obligation — sending data overseas)
- Google Search Central — Page experience & Core Web Vitals (why hosting speed & uptime matter)
Not sure what you actually have?
If nobody has ever told you where your site lives, who holds the domain or what your monthly fee covers, send me the address and I will look and tell you plainly — no charge, and no pitch attached to it.