What is a web server?

A web server stores web content and ensures it is con­stant­ly ac­ces­si­ble. So, whenever you enter a website address in your browser, it’s a web server that sends the in­di­vid­ual website com­po­nents to your device. For the site to be available at all times, the web server in question must be online around the clock.

De­f­i­n­i­tion and history of a web server

A web server (also called an HTTP server) refers to a server that delivers web content on the internet or an intranet. As part of a computer network, it transfers documents to so-called clients—like a web browser.

The term can refer to two things: the web server software itself (the actual program), or the computer running the web server software. The latter is also called a host (a host may run multiple server ap­pli­ca­tions). Below, we’ll refer to web server software/HTTP server software (or program) or a host when one of the meanings is intended ex­plic­it­ly.

The de­vel­op­ment of HTTP servers is closely linked to British physicist and computer scientist Tim Berners-Lee. In 1989, he proposed sim­pli­fy­ing in­for­ma­tion exchange at CERN (the European Or­ga­ni­za­tion for Nuclear Research) using a hypertext system. Together with Robert Cailliau, he presented a project plan in 1990 that even­tu­al­ly produced the first web server, “CERN httpd,” the first web browser, and several core Web tech­nolo­gies (like HTML and HTTP). Berners-Lee is therefore con­sid­ered the founder of the World Wide Web.

How web server tech­nol­o­gy works

The software of an HTTP server primarily exists to serve data for rendering web content. The program com­mu­ni­cates with a web client—typically a browser or a search engine crawler.

When you visit a website, you enter its address in your browser. The browser sends a request to the web server, which replies with, for example, an HTML page. This can be a static document stored on the host or dy­nam­i­cal­ly generated—meaning the web server executes code (in PHP, Java, etc.) before replying. The browser in­ter­prets the response, often trig­ger­ing ad­di­tion­al requests for things like images or CSS files.

Data transfer uses the HTTP protocol (or its encrypted form, HTTPS), built on the network protocols IP and TCP (less commonly, UDP). A web server can deliver content to many browsers at once. How many requests can be handled and how fast depends on the host’s hardware and load. Com­plex­i­ty also matters: dynamic content uses more resources than static content.

Choosing the right host system—whether virtual, dedicated, or cloud-based—helps prevent overload. However, even with a well-suited server, outages can occur due to hardware issues or power failures in the data center. While rare, downtime results in a website going offline, es­pe­cial­ly if it’s hosted on a single device without a content delivery network (CDN)—which is typical for smaller websites.

Ad­di­tion­al web server functions

Although content delivery is a web server’s main job, many HTTP server programs offer ad­di­tion­al features:

A host can run not only web server software but also other types of server ap­pli­ca­tions—for example, an FTP server for file uploads or a database server for dynamic content. (In most cases, a pro­fes­sion­al internet service provider will use separate hardware for these.) In general, there are many different types of servers used for various purposes—in addition to those mentioned, mail servers, game servers, and proxy servers are also widely used.

Web server vs. web hosting

What role do web servers play in web hosting? And what is web hosting anyway? Es­sen­tial­ly, web servers are a fun­da­men­tal part of web hosting. But many people confuse the two terms. Here’s the dif­fer­ence:

Web hosting means storing and providing web content. A website’s files are stored in web space (online storage for websites). The web space is like a hard drive, and it must be connected to a web server to make the website content ac­ces­si­ble online.

A host (the web server computer) and its connected web space are provided by a web hosting provider (or simply “hoster”). Many internet service providers—such as IONOS—also offer web hosting. If you choose a self-managed server, you’ll need to install web server software yourself.

Popular (free) web server software

Many programs allow you to operate your own web server—often for free. The HTTP server software must be com­pat­i­ble with the host’s operating system. Most web server programs are built on Unix or Linux, though many also run on Windows. The main exception is Microsoft IIS, which runs only on Windows.

Some of the most widely used web server programs include:

Apache HTTP server

The Apache HTTP Server is free and developed as open source. Its modular design works on nearly every OS and it’s the most used HTTP server globally. It supports dynamic content well and can integrate scripting languages like PHP or execute other programs via CGI.

In­te­grat­ing software like PHP and MySQL (which are required for dynamic content) into an Apache web server can be complex. However, this process becomes much easier with software bundles like XAMPP. These packages sig­nif­i­cant­ly simplify setup by including Apache along with the necessary database tools and various scripting languages.

Apache Tomcat

This is an open-source, free web server software from the Java ecosystem. Anyone looking to generate server-side web content using Java will find Apache Tomcat to be a suitable web container. It can also be in­te­grat­ed into another web server—such as the Apache HTTP Server or Microsoft IIS—via an AJP connector.

NGINX

NGINX is also free and more than just a web server. It includes features like a reverse proxy, which reduces load on the HTTP server and improves speed. Its pop­u­lar­i­ty has grown steadily in recent years.

Microsoft IIS

Microsoft Internet In­for­ma­tion Services (IIS) is a server software suite that includes a web server component. In the past, IIS was a built-in feature of Windows Server systems, but today it can be installed manually on certain Windows operating systems as needed. Un­sur­pris­ing­ly, Microsoft IIS can only be used on Windows servers.

LiteSpeed Web Server

This is an HTTP server software for Linux and Unix that offers an open-source version, a free standard edition, and an en­ter­prise edition. LiteSpeed Web Server is par­tic­u­lar­ly known for its high-speed data transfer—per­for­mance that is, as expected, highest in the paid en­ter­prise version.

How to choose a server and set up a web server

To host your online presence, you need a host with enough web space. Renting server resources from a provider is common. Those with little to no server ad­min­is­tra­tion ex­pe­ri­ence can use shared hosting or managed cloud hosting to get started.

Unlike a server with root access—where you have full control but also full re­spon­si­bil­i­ty for server security—a managed server shifts most of the basic ad­min­is­tra­tion tasks to the hosting provider. Security patches and software updates are largely handled for you, while you still have the freedom to install your preferred software. With shared hosting, you don’t need to manage software updates at all, but your access is limited to the web space and the con­fig­u­ra­tion options provided by the host.

When you rent a server, you typically pay a monthly fee. The cost depends on the per­for­mance and scope of the in­di­vid­ual com­po­nents—such as CPU and RAM, web space, and the type of storage drive (SSD or HDD). If you want more flex­i­bil­i­ty, consider cloud hosting, which lets you scale various resources at any time to meet the demands of your project.

The per­for­mance required for each hosting setup depends on the needs of your website: simple projects like a small blog or digital business card work well with af­ford­able, lower-per­for­mance hosting packages. Large websites or resource-intensive ap­pli­ca­tions, on the other hand, place much higher demands on specific com­po­nents. Some web ap­pli­ca­tions also require higher data transfer volumes. To ensure con­sis­tent per­for­mance, many providers offer packages with a traffic flat rate, guar­an­tee­ing enough bandwidth for your site at all times.

Once you’ve found the right server, you can install your preferred HTTP server software on it. Even with a managed server, however, there are some important security con­sid­er­a­tions to keep in mind when hosting a website.

Web server security

Once your web server is set up and running, it’s essential to ensure that it always has the latest updates installed. Outdated software versions can expose vul­ner­a­bil­i­ties that, in the worst case, allow cy­ber­crim­i­nals to take control of your server. With shared and managed hosting, the hosting provider typically handles security updates—but otherwise, the re­spon­si­bil­i­ty falls on you.

In addition to keeping every­thing updated, using a firewall provides effective pro­tec­tion against attacks. Setting up a de­mil­i­ta­rized zone (DMZ) is also rec­om­mend­ed. You can also use tools like Fail2ban, a framework designed to block unau­tho­rized access attempts.

Another key principle of web server security is: Only allow what is ab­solute­ly necessary for your server to function. Close all unused ports and shut down any nonessen­tial services. Setting strong passwords is also a fun­da­men­tal best practice for managing server security. In case of questions or emer­gen­cies, having reliable and knowl­edge­able customer support is extremely valuable—es­pe­cial­ly for less ex­pe­ri­enced ad­min­is­tra­tors.

If your hosting provider doesn’t fully manage your server’s pro­tec­tion, you should have at least basic knowledge of server main­te­nance and a fun­da­men­tal un­der­stand­ing of how a host functions. You can gain this knowledge by ex­per­i­ment­ing and learning in a closed network en­vi­ron­ment, where you don’t have to worry about cy­ber­at­tacks.

Example of how a web server works

Once your HTTP server is set up and your website content has been uploaded, the server can begin operating. It functions based on the client-server model. Here’s an example: If you want to visit the IONOS website and enter the domain www.ionos.com into your browser (the client), the following sequence of events is triggered:

1. As soon as you begin typing, your browser first sends the web address to a name server (also known as a DNS server). As part of the Domain Name System (DNS)—the internet’s directory service—the name server es­sen­tial­ly has access to the entire address book of the web. The al­phanu­mer­ic domain name (www.ionos.com) is trans­lat­ed into a numeric IP address (e.g., 74.208.255.134), which is sent back to the browser. The browser then sends a request for the web page content by con­tact­ing the IP address—that is, the web server hosting the website content.
2. The web server responds by sending back a document from the requested site to the browser. The browser then sends another request—this time for another document that is part of the web page (such as an embedded image). This process repeats until all com­po­nents of the page have been delivered, and the full website appears in your browser window. If you then click a link on the IONOS website, the browser requests another page from the web server, and the process starts over—except the DNS lookup is skipped because it has already been cached.