Industries / Technology / Software and SaaS / Cloud and data centers / Web hosting
Shared hosting
Renting space on a server that holds many other customers' websites, along with the software each customer uses to run their share.
7
Milestones achieved, from 1995 to 2024.
1
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1995
A language for home pages
In June 1995 Rasmus Lerdorf released the source code of "Personal Home Page Tools", small programs he had written to count visits to his online résumé. His rewrites, renamed PHP, could work with databases and let code sit inside an ordinary web page, enough to build simple dynamic applications such as guestbooks. A Netcraft survey in May 1998 found nearly 60,000 domains whose servers reported PHP, by the PHP project's account. In November 2026 W3Techs, a firm that surveys how websites are built, found PHP behind 68.1% of the websites whose server-side language it could detect.
Credit
Rasmus Lerdorf; later the PHP Development Team, including Andi Gutmans and Zeev Suraski
1997
Many sites on one address
Early browsers sent a server only the path of the page they wanted, not the site's name, so each hosted site needed its own IP address, the number that identifies a machine on the internet. On 20 September 1995 Chris Schefler of Web Communications, a hosting company in Santa Cruz, California, asked the HTTP working group for a way to pass the name. One address per site, he wrote, "needlessly consumes IP addresses", and Solaris, a common server operating system, allowed at most 255 per network interface. Lou Montulli of Netscape proposed a header carrying only the host name that day. HTTP/1.1, published as RFC 2068 in January 1997, made the Host header compulsory: a server must answer 400 (Bad Request) to an HTTP/1.1 request that lacks it, so one server on one address can tell many sites apart. This is called name-based virtual hosting. Perry Harrington, a former Web Communications engineer, wrote in 2020 that the company later hosted "70,000 domains on a single IP address"; that figure is his.
Credit
Chris Schefler (Web Communications); Lou Montulli (Netscape); R. Fielding, J. Gettys, J. Mogul, H. Frystyk and T. Berners-Lee (authors of RFC 2068)
2000
A number for every site
China's State Council adopted the Measures for the Administration of Internet Information Services on 20 September 2000; they took effect when published on 25 September, under Premier Zhu Rongji. Commercial online information services need a licence and non-commercial ones must file with the telecoms authorities, and without one or the other a service may not operate. Article 12 requires the licence or filing number to be shown in a prominent place on the site's home page, and Article 22 sets fines of 5,000 to 50,000 yuan for not showing it. Hosts in mainland China enforce the rule: Alibaba Cloud says that if a domain is pointed at one of its mainland servers without an ICP filing, as the record is called, its monitoring system blocks access until the filing is done.
LessonWhere a site's server sits can decide what paperwork it needs before it may go online.
Credit
State Council of the People's Republic of China; provincial telecoms authorities; hosts such as Alibaba Cloud
2008
Sites published by git push
On 18 December 2008 GitHub, a service that stores programmers' code, launched GitHub Pages. A user who pushed files to a repository named after their username saw them published at you.github.com: "No FTP, no scp, no rsync, nothing. Just a simple git push and you're done." Every Pages site ran through Jekyll, which Tom Preston-Werner had written: a static site generator, a program that turns templates and text files into finished HTML pages before anyone visits.
Credit
Tom Preston-Werner and GitHub
2013
One switch, four brands
Endurance International Group grew by buying hosting companies and keeping their brand names; in 2012 it bought HostGator, Data Center Knowledge reported. In August 2013, during network maintenance at its largest data center, two core switches failed. Endurance told investors that at times between one third and one half of its subscribers could not reach their websites and email, for up to 12 hours, that its own support lines were hit too, and that cancellations rose immediately afterwards. Bluehost, HostGator, HostMonster and JustHost went down together from one building near Provo, Utah, and Data Center Knowledge wrote that many of their customers probably did not know they were Endurance customers. In November 2026 W3Techs listed Bluehost and HostGator as brands of Newfold Digital Group, which hosted 2.3% of all websites.
LessonSeparate brand names can hide one shared point of failure.
Credit
Endurance International Group (operator); Data Center Knowledge (reporting)
2019
Control panels priced per account
cPanel is a hosting control panel, the web page through which customers manage their share of a server. Hosts had licensed it per server, with no limit on the number of accounts. On 27 June 2019 cPanel told its partners by email that it was moving to pricing by account. Under the new plans each licence covered a fixed number of accounts, and annual licences were discontinued; NDC Host, a reseller, listed 100 accounts for $45 a month. Hawk Host, a hosting company, wrote that charging for every account a reseller creates would cause "a drastic change in our costs to operate reseller servers" and said it was evaluating other control panels.
LessonA host built on one licensed tool takes on that tool's pricing decisions.
Credit
cPanel, L.L.C
2024
Cut off from updates
WP Engine is a hosting company that serves only WordPress sites. According to its court filings, hours before a keynote on 20 September 2024 Automattic, the company led by WordPress co-founder Matt Mullenweg, sent it a one-page trademark licence demanding 8% of its gross revenue, paid in cash or in staff time spent on WordPress. On 25 September Mullenweg wrote on WordPress.org that WP Engine "no longer has free access to WordPress.org's resources", the servers from which WordPress sites fetch updates, plugins and themes. On 12 October, by WP Engine's account, he took over the listing of Advanced Custom Fields, a WP Engine plugin with more than 2 million active installations, renamed it Secure Custom Fields and changed its listed author to WordPress.org; Mullenweg told the court that the WordPress security team forked the plugin because WP Engine's patch for a security flaw was incomplete. On 10 December 2024 Judge Araceli Martínez-Olguín of the US District Court for the Northern District of California found WP Engine likely to succeed on its claim of interference with its contracts and ordered access restored within 72 hours.
LessonSites built on free software still depend on whoever runs its update servers.
Credit
WP Engine and Automattic (parties); US District Court for the Northern District of California
Watch for
Deploys started by agents
Vercel, a hosting company for websites and web apps, said on 17 June 2026 that AI agents, programs that write and publish code for a person, triggered "around 29%" of the deployments on its platform, up from less than 3% a year earlier, and that it expected half of all deployments to come from agents soon. A deployment is one publication of a new version of a site. In July 2026 Startup Fortune, citing TechCrunch, reported that agents triggered about half of Vercel's 6 million deployments a day, by the account of its chief executive, Guillermo Rauch. Vercel's post does not say how it tells an agent's deployment from a person's.
Achieved whenVercel publishes how it counts agent-triggered deployments, or an outside party, such as an auditor reviewing a stock-market filing, reports the share.
Claimed by
Vercel, June and July 2026
Open
01
Patch speed by host
A public table showing how quickly the 15 largest hosting companies moved the PHP sites they serve onto builds with the 21 October 2026 fixes, and what share of each host's PHP sites still run branches with no security support. The fixes are for CVE-2026-109618 and CVE-2026-109619, two flaws php.net says can let an attacker run code on a server without logging in. Repeat the table for the next critical release, which php.net pre-announced on 18 November 2026.
The briefCredit · unclaimed02
Restore drill, published
A repeatable test of the backups that shared hosts advertise. On the entry plan at each of 15 hosts, set up the same WordPress test site of about 2 GB, break it in three set ways (delete the uploads folder, drop a database table, install a plugin that breaks the site), restore it with the host's own tools or by asking support, and time each step. Also record how long after an account is cancelled its data can still be recovered.
The briefCredit · unclaimed
Open 01 · the brief
Patch speed by host
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public table showing how quickly the 15 largest hosting companies moved the PHP sites they serve onto builds with the 21 October 2026 fixes, and what share of each host's PHP sites still run branches with no security support. The fixes are for CVE-2026-109618 and CVE-2026-109619, two flaws php.net says can let an attacker run code on a server without logging in. Repeat the table for the next critical release, which php.net pre-announced on 18 November 2026.
Why it is still open
On shared hosting the host, not the site owner, installs PHP. TechnologyChecker, a firm that tracks web technology, found in October 2026 that 45.55% of PHP sites announcing a version ran branches with no official fixed release, and counted 876,127 PHP domains at Hostinger, 432,112 at GoDaddy, 228,741 at OVH and 150,357 at IONOS, but published no figure for how fast each host patched. W3Techs publishes PHP versions for the web as a whole, not by host. Researchers have measured hosts once: in 2017 Samaneh Tajalizadehkhoob and colleagues at TU Delft and elsewhere gathered signals from 442,684 domains at 1,259 shared hosting providers, and found that providers have real influence over their customers' patch levels and that a provider moving from the worst 10% to the best 10% on web application security would see four times fewer phishing incidents. That study was a single snapshot and did not time hosts against a particular fix. A search found no host-by-host comparison of how fast a critical PHP fix reached customers' sites. Version numbers alone can mislead: php.net notes that some distributions and long-term-support vendors backport fixes to older branches.
Built with what exists
W3Techs's hosting list to choose the hosts; the HTTP Archive crawl and the Tranco list of popular sites to draw a sample; RIPEstat, a public lookup service for internet addresses, to tell which network serves each site; a weekly Python script that requests each sampled home page once and reads only the headers any visitor receives; a test account at each host, on which the builder checks the PHP build; an AI model such as Claude Fable 5.2 (see the Note "Three working devices") to read hosts' status pages and changelogs, with a person checking each claim.
First step
Pick three large hosts, draw 1,000 PHP sites each from the latest HTTP Archive crawl, and record their PHP version headers weekly from now until the next release.
Done looks like
For 15 hosts, the share of a fixed sample of at least 1,000 PHP sites per host on a supported, fixed build at 7, 30 and 90 days after the release, beside each host's own statement and the result from the test account. Method, code and raw data are published, and each host is sent its row for comment first.
Open 02 · the brief
Restore drill, published
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A repeatable test of the backups that shared hosts advertise. On the entry plan at each of 15 hosts, set up the same WordPress test site of about 2 GB, break it in three set ways (delete the uploads folder, drop a database table, install a plugin that breaks the site), restore it with the host's own tools or by asking support, and time each step. Also record how long after an account is cancelled its data can still be recovered.
Why it is still open
HostHive, a hosting review site, says it timed restores at seven hosts in 2026 and reports ranges, such as under five minutes for a 2 GB site at SiteGround and under two at WP Engine, but it publishes no raw timings, recordings or test files that others could check. A search for a controlled comparison with published data found none.
Built with what exists
accounts on each host's cheapest plan; WordPress with a fixed set of posts, images and database rows; WP-CLI, WordPress's command-line tool, to build and check the site; a screen recorder; a Python script that compares checksums of every file and database table before and after.
First step
Build the 2 GB test site and the checksum script, then run all three cases at two hosts.
Done looks like
15 hosts, three cases each, run twice a month apart, with timings, recordings, checksums and the hosts' replies published. A second person repeats five cases and gets times within 20% of the first.