Web hosting is the service that puts a website on an internet-connected server so people can visit it. When you type a website address into a browser, several systems work together: the domain name identifies the site, DNS helps find the server, the browser sends a request, and the hosting server sends the website’s files and data back.
The easiest way to understand web hosting is to think of a website as a building. The domain name is the street address, DNS is the system that directs you to the right location, and web hosting is the physical space where the website’s files and applications live. The browser is the visitor, and the web server is the system that receives the visitor’s request and delivers the requested content.
Once those roles are clear, most of the terminology surrounding hosting becomes much easier to understand.
What happens when you visit a website?
Suppose you type:
example.com
into your browser.
It looks simple, but several things happen before the homepage appears.
The process can be reduced to these steps:
- Your browser receives the website address.
- DNS helps translate the domain into an IP address.
- Your browser connects to the appropriate server.
- It requests a webpage.
- The web server processes the request.
- The server sends the required files or generated content back.
- Your browser assembles everything into the webpage you see.
Let’s look at each stage.
Step 1: You enter a domain name
A domain name is the human-friendly name of a website, such as example.com.
Computers communicating across the internet ultimately use IP addresses to identify network destinations. DNS exists partly because remembering numerical IP addresses for websites would be impractical. It connects domain names with the relevant IP information.
This is why a domain name and web hosting are not the same thing.
ICANN compares the domain name to an address: having the address does not mean you automatically have a building at that address. You still need hosting or another service to make a website available there.
So:
Domain name = the address people remember
Hosting = the infrastructure where the website lives
Step 2: DNS finds the server
This is where the Domain Name System, or DNS, enters the picture.
When you request a domain, your device needs to determine where that domain currently points. Your device can use cached DNS information, while a DNS resolver can query authoritative DNS servers when it does not already have the required information.
Think of DNS as an internet directory.
You ask:
“Where is example.com?”
DNS provides the information needed to locate the appropriate destination.
The result is not necessarily a simple permanent relationship between one domain and one physical machine. DNS records can point domains toward different infrastructure, and the underlying hosting arrangement can change without requiring visitors to learn a new domain name.
Step 3: Your browser contacts the server
Once the browser has the necessary network information, it can communicate with the server hosting the website.
The browser sends a request for a resource, commonly beginning with the webpage you asked for.
For example, it might request:
The important part is that the browser is no longer asking the internet to find a human-readable name. It now has information that allows it to communicate with the appropriate destination.
Step 4: The server receives the request
A web server is software running on a computer or virtual machine that is configured to receive and respond to web requests.
The physical infrastructure might be located in a data center hundreds or thousands of kilometres away from the person visiting the website.
When the request arrives, the server determines what needs to be returned.
For a simple static webpage, this could mean retrieving HTML, CSS, JavaScript and image files.
For a dynamic website, considerably more can happen.
Static versus dynamic websites
This distinction explains why hosting can involve much more than simply storing files.
A static website
A static website can consist largely of files that are already prepared.
For example:
- HTML
- CSS
- JavaScript
- Images
- Fonts
The server can retrieve and send those files to the browser.
A dynamic website
A dynamic website may generate content when somebody requests it.
A WordPress website, online store or membership platform might need to:
- Run application code
- Query a database
- Check whether a user is logged in
- Retrieve a product or article
- Process settings
- Generate HTML
- Return personalized information
That means hosting is providing computing resources as well as storage.
This is one reason CPU, memory and database performance can matter just as much as storage capacity.
Step 5: The server sends the website back
Once the server has processed the request, it returns a response.
That response might contain the HTML for the page or instructions telling the browser where to retrieve additional resources.
The browser may then request:
- Images
- CSS files
- JavaScript
- Web fonts
- Videos
- Other page resources
A modern webpage can therefore involve many individual requests rather than one enormous file being sent all at once.
Step 6: Your browser builds the page
Your browser takes the resources it receives and uses them to construct the webpage.
It interprets HTML to understand the page structure, CSS to determine presentation and JavaScript to provide interactive behaviour.
This is why the hosting server is only one part of website performance.
A powerful server cannot automatically make a poorly optimized website fast.
Large images, inefficient code, excessive JavaScript, database queries and third-party services can all affect how quickly a page becomes usable.
Where does the website actually live?
When you buy hosting, you are generally paying for access to computing infrastructure.
That infrastructure might consist of:
- Physical servers
- Storage systems
- Network connections
- Databases
- Virtual machines
- Containerized environments
- Security systems
- Backup systems
- Caching infrastructure
The exact architecture depends on the hosting provider and hosting type.
A shared hosting account, for example, can place multiple websites within the same broader server environment. A dedicated server gives one customer an entire physical server. Cloud and VPS environments use different forms of virtualization and resource allocation.
The important point is that “hosting” is an infrastructure service, not simply a folder on the internet.
What does a hosting company actually do?
A hosting provider operates infrastructure designed to keep websites accessible.
Depending on the service, the provider may supply:
- Server hardware
- Internet connectivity
- Storage
- Operating systems
- Web-server software
- Databases
- Backups
- Security tools
- Monitoring
- SSL/TLS certificates
- Control panels
- Technical support
- Website migration services
- Caching and CDN integrations
The exact division of responsibility varies.
With basic hosting, the provider may manage the server while you manage your website.
With managed hosting, the provider may take responsibility for considerably more of the technical environment.
That distinction is important because you’re not simply paying for “space.” You’re also paying for varying amounts of infrastructure management.
What happens when you use HTTPS?
You will often see websites beginning with:
https://
rather than:
http://
HTTPS uses HTTP over an encrypted TLS connection.
In practical terms, this helps protect information travelling between the browser and website from being read or modified by someone who should not have access to that communication.
This is particularly important when websites handle passwords, personal information, payment information or other sensitive data.
HTTPS does not, however, make the entire website automatically secure.
A website can still have vulnerable software, compromised accounts or insecure plugins even when HTTPS is correctly configured.
Where do databases fit in?
Many modern websites use databases.
Imagine an online store with 50,000 products.
It would be impractical to create a separate manually maintained webpage for every possible piece of information. Instead, product information can be stored in a database.
When a visitor opens a product page, the application can request the relevant information from the database and generate the page.
The simplified process becomes:
Visitor → Browser → Server → Application → Database → Application → Server → Browser
That is why database performance can become important as websites become more complex.
Where does a CDN fit in?
A content delivery network, or CDN, adds another layer.
Instead of making every visitor retrieve every static file directly from the primary hosting server, a CDN can cache and deliver eligible content from locations distributed around the world.
Imagine your main hosting server is in Europe and someone visits your website from Kenya.
The website’s underlying application may still run on the primary hosting infrastructure, but static resources such as images, CSS and JavaScript may be delivered through a CDN location closer to the visitor.
This can reduce network distance for cached resources and can also help handle large volumes of requests.
A CDN does not replace hosting. It works alongside it.
What happens if thousands of people visit at once?
This is where hosting resources become particularly important.
Suppose a website normally receives 100 visitors at a time.
Then an article suddenly goes viral and thousands of people arrive within minutes.
The hosting environment may have to process far more:
- Web requests
- Database queries
- PHP or other application processes
- Images and other resources
- Network traffic
- Logged-in sessions
If the available resources are insufficient, pages can become slow or the website can become unavailable.
Caching and CDNs can reduce some of this workload, while larger or more scalable hosting environments can provide additional capacity.
But there is no universal amount of hosting required for a particular number of visitors. The workload generated by each visitor matters.
Why websites sometimes go down
A website can become unavailable for many different reasons.
The problem might involve:
- Hosting infrastructure
- DNS configuration
- Expired domain registration
- Application errors
- Database failures
- Software vulnerabilities
- Traffic spikes
- Incorrect configuration
- Network problems
- Failed deployments
- Security incidents
This is another reason why “99.9% uptime” should not be interpreted as a guarantee that nothing will ever go wrong.
Hosting providers can reduce infrastructure-related failures, but website owners remain responsible for parts of the overall system.
What happens when you move to a new host?
Moving a website does not necessarily mean changing its domain.
The basic idea is:
Old hosting → New hosting → DNS updated → Visitors reach the new hosting
You can transfer the website’s files and database to the new environment while retaining the same domain name.
Once the DNS configuration is changed appropriately, visitors can be directed toward the new hosting infrastructure.
This is one reason the domain name and hosting service should be understood as separate components. ICANN notes that domain registration and web hosting are distinct services, even though the same company may offer both.
Migration can nevertheless become complicated when databases, email, DNS records, SSL certificates, application configuration or large amounts of data are involved.
The easiest way to visualize web hosting
Think of the whole system as a delivery chain:
You type a domain
↓
DNS finds where the domain should go
↓
Your browser connects to the hosting infrastructure
↓
The web server receives your request
↓
The application and database do any necessary work
↓
The server returns the requested content
↓
Your browser builds the webpage
That is web hosting in plain English.
The hosting provider supplies much of the infrastructure in the middle of that chain, while the domain, DNS, website software, browser and internet connection perform other parts of the job.
Why this matters when choosing hosting
Once you understand the process, hosting plans become easier to evaluate.
Storage matters because your website needs somewhere to keep its files and data. CPU and memory matter because applications need computing resources. Databases matter because dynamic websites depend on them. Backups matter because failures happen. Security matters because hosting infrastructure is only one part of the website’s security model.
And price matters—but the cheapest plan is not necessarily the least expensive option if it cannot handle your workload or requires substantial technical work that you cannot perform yourself.
For readers ready to compare current plans and introductory offers, current SiteGround hosting offers provide one current example of how hosting companies package infrastructure, management and website features.
The part of hosting that is easiest to misunderstand
The most important thing to remember is that a website is not a single thing sitting on a server.
It is a collection of connected systems.
The domain provides the human-friendly name. DNS helps translate that name into the information needed to reach the destination. Hosting provides computing infrastructure. The web server handles requests. Applications generate or retrieve content. Databases store information. CDNs can distribute cached resources. The browser turns the returned resources into the page you actually see.
Once you understand those relationships, terms such as shared hosting, VPS, cloud hosting, DNS, CDN, SSL, bandwidth and server resources stop looking like unrelated technical jargon. They become different pieces of the same process: getting the right information from a server to a visitor’s browser reliably, securely and quickly.