What is a website? The three things every site is made of

A website is three things

Most people think of a website as "the thing you see when you type an address in a browser." That's the end result — but it's the product of three distinct components working together. Understanding what those components are, and how they relate to each other, helps you make better decisions when building, maintaining, or paying for a website.

The three components are:

• A domain name — your address on the internet
• A server — the machine that stores and serves your content
• An application — the code that makes your website what it is

Each of these is a separate thing. Each is typically provided by a different service. And each needs to be working correctly for your website to be accessible to anyone.

1. The domain name

A domain name is the human-readable address of your website. It's what you type in a browser: yourcompany.com, my-shop.fr,therapist-lyon.com. Without a domain name, your website only has a numeric IP address — something like 185.220.101.42 — which no one could reasonably remember.

Domain names are registered through a domain registrar — companies like OVH, Namecheap, Gandi, or Google Domains. You don't buy a domain name outright; you register it for a period (typically one year at a time) and renew it to keep ownership.

• The domain name must be renewed to stay yours — let it lapse and it can be registered by someone else
• The extension (.com, .fr, .io, .co.uk) is part of the domain — different extensions have different connotations and are managed by different registries
• You can own a domain name without yet having a website — many businesses register their domain early to secure the name

2. The server

A server is a computer — usually one in a data centre somewhere, running 24 hours a day — that stores the files and code that make up your website and sends them to visitors' browsers when requested.

When someone types your domain name and presses enter, their browser sends a request to your server. The server processes that request and sends back the code that the browser then displays as a web page. This happens in milliseconds.

Servers are provided by hosting companies. You typically pay a monthly or annual fee for server space. There are several types:

• Shared hosting: Your site shares a server with many others. Cheapest option, but performance can be affected by other sites on the same server.
• VPS (Virtual Private Server): A portion of a server dedicated to you, with guaranteed resources. More expensive, more reliable. Good for growing sites.
• Dedicated server: An entire physical server just for your site. Most expensive. Relevant for very high-traffic sites or specific security requirements.
• Cloud hosting: Resources are distributed across multiple servers in multiple locations. Highly scalable and resilient. Used by most modern web platforms.

The location of your server matters for speed: a server in Paris will serve pages faster to visitors in France than a server in the United States. Most hosting providers have options to choose your server's geographic region.

3. The application

The application is the code — HTML, CSS, JavaScript, and whatever else is needed — that makes your website look and behave the way it does. It's what determines the layout, the colours, the text, the images, the contact form, the navigation, and every other aspect of what visitors experience.

This is what people colloquially refer to as "the website" — but technically, it's the third piece of a three-part system.

Applications can be built in many ways:

• Entirely by hand, written by a developer from scratch
• Using a CMS (Content Management System) like WordPress, which provides a framework and a UI for managing content without writing code
• Using a website builder like Wix or Squarespace, which handles the technical side while you customise visually
• Using an AI-assisted tool that generates code based on your requirements — faster to deploy and often better for SEO and security out of the box

The application is the part that requires the most decisions. It determines how fast your site loads, how well it ranks in search engines, whether it works on mobile, and how secure it is.

How they connect

The three pieces connect through a system called DNS (Domain Name System). Think of DNS as the phone book of the internet: when you type a domain name, DNS translates it into the IP address of the server where the site is hosted, allowing the browser to find and connect to the right machine.

When you set up a website, you configure DNS records at your domain registrar to point to your hosting provider's servers. Once that's done, anyone who visits your domain name will reach the application that's running on your server.

Changes to DNS records take some time to propagate across the internet — usually between a few minutes and 48 hours, though most updates are visible within an hour.

Why you need all three

Each piece can fail independently, and understanding this helps you diagnose problems when they occur:

• If your domain registration lapses or DNS is misconfigured, visitors can't find your site — even if the server and application are working perfectly
• If your server goes down or your hosting plan expires, your domain name still exists but it leads nowhere
• If your application has a bug or the code is broken, the server and domain are fine — but visitors see an error page

Knowing the three components and who manages each one also tells you who to contact when something breaks, and which part of the system to investigate first.

How Zapia helps

Most businesses deal with three separate providers for these three components — a registrar for the domain, a hosting company for the server, and a developer or platform for the application. This means three sets of credentials, three renewal dates, three support contacts, and three different dashboards to manage.

Zapia handles all three in one place. Domain registration, managed hosting, and website creation — from your business requirements to a live site — without needing to understand DNS records, server configuration, or code.