Domain, hosting, and website: what each one is, who controls it, and why it matters when something breaks

When something breaks on your site, the first question is rarely “what’s broken?” It’s “who do I even call?”

The website is a blank white page. The domain renewal went to an old email. The contact form stopped working. Each of those is a different layer, owned by a different vendor, fixed in a different place. Knowing which is which saves hours.

What’s the difference between a domain, hosting, and a website?

Three separate things - the domain (your address), the hosting (the server), and the website (the files) - billed separately, fixed separately, stitched together to look like one thing.

Your domain is the address - yourorg.org. You rent it annually from a registrar (GoDaddy, Namecheap, Cloudflare, Porkbun). The registrar is who you pay the renewal invoice to. If the domain expires, everything else goes dark. Your website gets “parked” on a white page. If you’re extra unlucky, someone rents out your domain name while it’s lapsed. Most registrars auto-renew by default, but only if the card on file is current.

Your hosting is the server (computer) the website files live on. When someone types your address, the hosting server delivers the files to their browser. Hosting is a separate service from the registrar most of the time - Dreamhost, Bluehost, SiteGround, Kinsta, Cloudflare Pages, Vercel, or whoever is running the server. Some hosts charge monthly, some annually, some (like Cloudflare Pages and Netlify) are free for small sites. All of them can cancel you if the card fails or the terms of service are violated.

Your website is the files themselves - the HTML, CSS, Javascript, images, content, and code that make the pages look and behave a certain way. Websites are built by designers, developers, or platforms (WordPress, Squarespace, Webflow, Wix). A website can be moved from one hosting service to another. The domain can point at a different host. They are genuinely separate.

The confusion usually comes from buying all three at once. Squarespace will sell you a domain, hosting, and a website builder in the same checkout. WordPress.com does the same. That is fine until you want to change one piece and the vendor makes it painful.

Who controls what, and where do I find out?

One check, ten minutes.

Domain - log into your registrar. If you don’t know which one, go to ICANN Lookup and type your domain. The “Registrar” field is your answer. The “Registrant email” is who gets renewal notices. Make sure that email still exists and is being monitored. Renewal notices going to a long-departed staff member’s inbox is a common way to lose a domain quietly.

Hosting - in your registrar, look at the “nameservers” or “DNS” for your domain. Those point to your hosting provider (e.g., ns1.bluehost.com, ns1.digitalocean.com, or Cloudflare variants). Or ask the person who set up your site and confirm they still have access.

Website - if you can log in and edit content, the platform name is in the admin URL (wp-admin for WordPress, squarespace.com for Squarespace, webflow.com for Webflow). If you can’t log in, you have a credential problem, not a website problem - recover the login before trying to diagnose anything else.

Write the three answers down somewhere a colleague can find them. In six months the person who set this all up might be somewhere else.

What breaks where?

Fast lookup, because this is the reason most people need to know any of this.

• Site totally down, “domain expired” message - registrar, renew the domain
• Site down, “server not responding” or a generic 5xx error - hosting provider, open a ticket
• Contact form not submitting, rest of site working - website platform or form plugin
• Email bouncing but pages load - DNS settings (with whoever hosts your DNS), not hosting
• Page loads but looks broken - website platform, usually a plugin or theme issue
• “Not secure” warning in the browser - SSL certificate, typically renewed automatically by your host. If not, the hosting provider is the ticket.

The layers fail independently. Being able to name the layer cuts your troubleshooting time in half, because you stop calling the wrong vendor first.

What about all-in-one platforms like Squarespace?

Squarespace, Wix, WordPress.com, and similar platforms bundle all three layers behind one login and one invoice. The upside: nobody has to think about this. The downside: moving off later means untangling all three at once - transfer the domain, export or rebuild the content, choose a new host. Some platforms make that exit easy. Some make it hard on purpose.

I’m not arguing against all-in-one platforms, but it’s worth knowing what the exit looks like before you sign up.

---

A website feels like one thing because you see one address. In reality it is three services stitched together, each renewable on its own schedule, each cancellable without the others noticing. Keep track of all three leases.