3.5 Web Hosting and Web Servers
In the previous sections, we learned about domain names and DNS.
A domain name gives people a readable name to type.
DNS helps find the technical information connected to that name, but DNS does not store the website.
DNS helps the browser find where to go. Web hosting is where the website actually lives.
What Is Web Hosting?
Web hosting is the service that makes a website available on the Internet.
When someone creates a website, the website’s files need to be stored somewhere. These files may include text, images, videos, HTML, CSS, JavaScript, documents, application code, and database information. For other people to visit the website, those files need to be available from a computer connected to the Internet.
That computer is called a server.
The service of storing the website and making it available online is called web hosting.
One way to think about it is like this:
- A domain name is the readable name people type.
- DNS helps the browser find the correct location.
- Web hosting is where the website lives.
- A web server responds when the browser asks for the website.
What Is a Server?
A server is a computer that provides information, resources, or services to other computers.
The word “server” can sound mysterious, but the basic idea is simple.
A regular personal computer is usually used by one person sitting in front of it. A server is usually designed to respond to requests from other computers over a network.
For example, a server might:
- Send a webpage to a browser
- Store files
- Run an application
- Manage user accounts
- Send or receive email
- Store information in a database
Servers can be physical machines in data centers, or they can be virtual machines running on shared cloud infrastructure. In both cases, the server’s job is to provide something other devices are requesting.
What Is a Web Server?
The phrase “web server” can mean two closely related things:
- First, it can mean the computer or virtual machine that stores and delivers website content.
- Second, it can mean the software running on that machine that handles web requests.
The phrase can be confusing because sometimes people are talking about the server computer. Other times, they are talking about the web server software.
Web server software listens for requests from browsers and sends back responses.
Common web server software includes Apache, Nginx, Microsoft IIS, and other server platforms.
For example, when a browser asks for a webpage, the web server receives the request, finds or creates the correct content, and sends a response back to the browser.
The basic process looks like this:
- A person types a website address into a browser.
- DNS helps the browser find the correct server.
- The browser sends a request to the server.
- The web server receives the request.
- The web server sends back the webpage or resource.
- The browser displays the result.
This usually happens very quickly; sometimes within milliseconds. Heavier websites may take a few seconds.
What Web Servers Send to Browsers
A website is usually not one single file.
When a browser loads a webpage, it may receive many different resources from one or more servers.
These resources can include:
- HTML, which gives the page its structure
- CSS, which controls the visual style
- JavaScript, which adds behavior and interactivity
- Images, videos, fonts, and documents
- Data from APIs
- Redirects, error messages, and status codes
The browser takes these pieces and uses them to build the page the user sees.
This is why a webpage may partly load even if something goes wrong. The browser may receive the main page but fail to load an image, font, script, or external service.
Static Websites
Some websites are static. A static website serves files as they already exist.
For example, a static website may be made of HTML files, CSS files, JavaScript files, images, and documents. When someone visits a static webpage, the server sends back the file that was already created.
Static websites are often simpler, faster, cheaper, and easier to secure than complex dynamic websites. A personal portfolio website, a documentation site, a simple course page, or a basic information page can often be static.
Static does not mean boring. A static website can still look modern, beautiful, and interactive in the browser. The word “static” simply means the server is mostly sending prebuilt files instead of building a custom page on the server for each visitor.
Dynamic Websites
Other websites are dynamic. A dynamic website can generate or change content based on data, user accounts, search results, purchases, comments, or other conditions.
For example, an online store is usually dynamic. It may need to show product availability, shopping carts, user accounts, payment status, shipping information, and order history.
A social media platform is dynamic. Different users see different feeds, messages, notifications, and profiles.
A learning platform is dynamic if it tracks student progress, logins, assignments, quizzes, or certificates.
Dynamic websites often use application code and databases.
A database stores organized information that the website can retrieve, update, and display. For example, a blog may store posts, authors, comments, tags, and user accounts in a database.
When someone opens a dynamic page, the web application may ask the database for the right information, build the page, and send the result back to the browser.
Dynamic websites are powerful, but they are usually more complex to build, maintain, and secure.
Many Websites Use Both
Many modern websites use both static and dynamic content. For example, a website might serve static images, fonts, and style files while also using dynamic code to handle logins, shopping carts, contact forms, dashboards, or account pages.
A business website may have mostly static information pages but a dynamic contact form.
A school website may have static course descriptions and dynamic student account features.
A news website may use static files for its design and dynamic content for current articles.
The important distinction is this:
- Static content is served as-is.
- Dynamic content is generated, customized, or updated based on data or user activity.
Origin Servers
The main server that hosts the original website or application is often called the origin server. The origin server is the source of the original content or application response.
As websites become more advanced, visitors may not always connect directly to the original web server.
Many websites use services such as CDNs, reverse proxies, security filters, or load balancers between the user and the website’s main server.
For example, a CDN may store copies of images or files closer to users around the world. But if the CDN does not have the needed content, it may ask the origin server for it. We will look at CDNs in section 3.7.
Uptime, Performance, and Reliability
Good web hosting is not only about storing files. Hosting also affects uptime, speed, reliability, backups, and security.
Uptime means the amount of time a website is available and working.
If a website is down, users may not be able to visit it.
Performance refers to how fast the website loads and responds.
A slow website can frustrate users, hurt search visibility, reduce sales, and make a project look less professional.
Reliability means the hosting environment can keep working through normal traffic, updates, hardware issues, or traffic spikes.
Backups are copies of website files and data that can be restored if something breaks, gets deleted, or is attacked.
For a small website, these things may seem invisible, but they matter because a website is not just content. It is also infrastructure.
Web Hosting and Security
Web hosting is an important part of Internet security.
A website can have a good domain name, a good design, and good content, but still be unsafe if the hosting environment is poorly secured.
Common hosting security concerns include:
- Weak passwords
- Outdated software
- Insecure plugins or themes
- Poorly configured permissions
- Exposed admin panels
- Missing backups
- Misconfigured cloud storage
- Unpatched servers
- Poor access control
- No HTTPS
HTTPS is especially important because it helps protect the connection between the user’s browser and the website. It helps prevent others from easily reading or changing information while it travels across the network.
Most modern websites should use HTTPS.
However, HTTPS does not automatically mean a website is honest. A scam website can also use HTTPS.
HTTPS protects the connection. It does not prove the owner’s intentions.
This distinction will matter later when we study phishing, scams, encryption, and digital trust.
Why This Matters
Web hosting is what makes a website available to the world.
- A domain name gives people a readable name.
- DNS helps find the correct destination.
- Web hosting stores and serves the website.
- A web server responds to browser requests.
Together, these systems make the web feel simple from the user’s perspective.
A person types a name, presses enter, and sees a page. Behind that simple action are domain names, DNS records, servers, hosting providers, software, databases, security settings, and network infrastructure.
Understanding web hosting helps explain why websites load, why they fail, why they can be slow, why they can be attacked, and why security is not only about the user’s device.
In the next section, we will look at different types of web hosting, including shared hosting, VPS hosting, dedicated hosting, cloud hosting, serverless hosting, and managed hosting.