Shared web hosting is a web hosting service in which many websites reside on one web server connected to the Internet. The cost of server maintenance is divided among the customers, and each site draws on the same pool of Random Access Memory (RAM) and Central Processing Unit (CPU) time.
History of Shared hosting
Creator: No single creator; the model grew from early web hosting services.
Early web hosting gave customers space on their own servers. Not every company could buy and run a server. Shared hosting builds on that idea. Many customers share one server. The cost of running it is split among them all.
In shared hosting, the provider manages the servers. It installs the server software. It applies security updates and gives technical support. Most such servers run Linux and the LAMP stack. LAMP is a mix of Linux, Apache, MySQL and PHP. Some providers offer servers that run Microsoft Windows or FreeBSD.
Shared hosting costs less than dedicated server hosting. It usually has usage limits. The service often includes web statistics, email and webmail, script installers, current PHP and MySQL versions, and support after the sale. Shared hosting does not suit customers who need software development beyond what the provider supports.
There are thousands of shared hosting providers. They range from small design firms to providers with hundreds of thousands of customers. Shared hosting can also be cooperative. In a cooperative, several parties share the cost of one server. The server sits in a colocation center.
Two methods map many sites to one server. In name-based virtual hosting, one IP (Internet Protocol) address serves many host names. The browser names the site in each HTTP/1.1 request. In IP-based virtual hosting, each site has its own IP address. Domain Name System (DNS) records tie each domain to its provider's name server.
Changelog and latest update
The Apache HTTP Server project documents name-based virtual hosts. These hosts serve many sites on one address. The Apache Software Foundation publishes this guide. It is in the version 2.4 documentation. The server reads the Host request header. It uses that header to choose the site.
RFC 9110 defines the Host header. The RFC carries a 2022 copyright year. A shared server reads this header on each request. It answers for the correct domain. Without the header, one IP address could not serve several sites with different names.
The cPanel documentation lists change logs for cPanel and WHM (Web Host Manager) releases. cPanel is a control panel that many shared hosts install. These logs show the release cycle of that control panel. Each log lists the cases and bugs that the release cycle worked on.
Providers market unlimited plans. Shared hosting usually has usage limits, as the Wikipedia article on shared hosting states. A customer should read the usage terms before buying. Usage limits help a shared server. They keep one site from using the resources that the other sites need.
Latest update: Apache HTTP Server 2.4.69, 2026-10-01
The Apache Software Foundation announced version 2.4.69 of the Apache HTTP Server. The download page dates it 2026-10-01. Apache is the A in LAMP. LAMP is the software stack that Wikipedia names for most shared servers. The announcement describes this release as part of the 2.4.x stable branch.
Usage examples
Shared hosting depends on three things. It uses name-based virtual hosts. It uses DNS name servers. It uses separate folders for each account. The examples show an Apache configuration with two sites on one server. They show a curl test that targets the shared address. They show a disk usage check for one cPanel account. They also show the name server records that point a domain to its host.
<VirtualHost *:80>
ServerName site-one.example.com
DocumentRoot "/home/user1/public_html"
</VirtualHost>
<VirtualHost *:80>
ServerName site-two.example.net
DocumentRoot "/home/user2/public_html"
</VirtualHost>Each VirtualHost block answers for one host name. All blocks use the same IP address. Apache picks the block whose ServerName matches the Host header of the request. The DocumentRoot line sets the folder that holds each site's files. Each account owns its own folder.
curl -I --resolve site-one.example.com:443:203.0.113.50 https://site-one.example.com/
curl -I --resolve site-two.example.net:443:203.0.113.50 https://site-two.example.net/The --resolve option sends each request to the shared server address. It keeps the host name in the request. Both commands should return the same server address but different sites. The test works before the DNS change reaches the public resolvers.
du -sh /home/user1/public_html
du -sh /home/user1/mailThe du command reports the disk space used by a folder. The -s option prints one total. The -h option prints sizes in units such as megabytes. Shared plans often set a disk quota. The administrator checks these totals before the quota is reached.
example.com. 3600 IN NS ns1.webhost.example.
example.com. 3600 IN NS ns2.webhost.example.NS records tell the rest of the Internet which name servers answer for example.com. The two names point to the hosting provider. The provider's name servers then return the shared server address for the site.
References
These sources are outside Websnoogie and were checked on 2026-10-12.
Shared web hosting service
Wikipedia
The encyclopedia article on shared hosting. It describes many websites on one server, the provider duties, the Linux and LAMP server stack, name-based and IP-based virtual hosting, and how DNS points a domain to the host's name server. The article is the main reference for the shared hosting model in this entry.
Name-based Virtual Host Support
Apache Software Foundation
The Apache HTTP Server guide to name-based virtual hosts, which let one IP address serve many host names. The guide explains how the server uses the Host header of an HTTP/1.1 request to choose the site that answers. The guide is cited here for the name-based setup shown in the first example.
HTTP Semantics (RFC 9110)
IETF, RFC Editor
The HTTP standard that defines the Host header field. A shared server reads this field on each request to find the correct website. The RFC Editor page shows a copyright year of 2022. The standard is cited here for the header rule used in the changelog section.
cPanel products
cPanel
The product page for cPanel and WHM, the control panels that shared hosts commonly install. The page describes how servers and sites are set up and managed, including the accounts that a provider creates for each customer. The page is cited here for the control panel named in the usage section.
When shared space stops being enough for your site
When a hosting plan is ignored, a site slows down, runs out of room and stops answering visitors at the worst times. Shared hosting puts many sites on one server and splits its power among them. That works well for a small site, but the limits are real. We review your plan with you before a problem shows up, so the site stays fast for every visitor who finds it.
We offer two shared plans. CMS hosting costs $149 a year for WordPress sites you edit yourself. Non-CMS hosting costs $129 a year for plain HTML or PHP sites with no database. Each plan includes daily backups, security checks, free SSL and 99.999% uptime. We set up both plans for you, so you never manage the server yourself.
Building a fresh site with us is a $300 job, paid once, covering five pages and a contact form. Typical timing is 3 to 5 days from start to launch. If your site is already live elsewhere, a normal-size WordPress site moves for free, and a larger one costs $199 one time. We test each page after the move.
Send a note about your site and how many visitors it gets. Answers come back in plain words. Our number is 402-813-4034, open 7 am to 10 pm, seven days a week.
