Download websites that use AOLserver

About AOLserver

A web server outlives its sponsor more easily than almost any other piece of software, because the job it does has no natural end date. AOLserver came out of America Online in the era when a large portal had to write its own infrastructure, was released to the public under the Mozilla Public License, and then stopped being a corporate priority. Meanwhile the machines running it carried on answering requests.

What made the server distinctive was building it around Tcl rather than bolting a scripting layer on afterwards. Pages, database access and connection pooling lived inside the same embedded interpreter, which gave application code direct access to persistent state between requests at a time when the common alternative was to fork a process per hit. Anyone who has kept a long-running application server alive will recognise both the advantage and the maintenance bill attached to it.

Presence today is a statement about the age of a deployment. As of October 2026 we detect AOLserver on 34 sites, with our records reaching back to 1999, and a count at that level describes survivors rather than a market. Servers of this generation persist where the application on top is too specialised, too custom or too well understood to be worth rewriting: university systems, government registries, research infrastructure and internal tools that were exposed to the public once and never revisited.

The version picture is where the data earns its place. We can distinguish 5 version strings across the installations that identify themselves, and 4.5.1 is the release that keeps recurring among them. A spread that narrow, on software no longer receiving regular releases, means the installations are frozen rather than maintained. Nobody is tracking upstream, because for practical purposes there is no upstream left to track.

Caveats belong with that reading. The server announces itself in a response header, which is trivially disabled or rewritten, so hosts that suppress the banner are missing from our count entirely. The lineage also forked, and maintained descendants inherit enough behaviour that a banner alone does not always separate the original from its successors. Where a version string is present we report what was sent, and where it is absent we would rather record nothing than guess.

For a reader the question is never whether one host runs an ageing server. Confirming that takes a single request. The question is where the whole population sits, which country suffixes it clusters in, what runs alongside it and how the version spread looks laid out as a table. Security researchers want the list because unmaintained servers are where old vulnerabilities keep working. Migration and hosting vendors want it because every entry is a system whose owner will eventually have to make a decision. Anyone writing about early web infrastructure wants it because arguments about that period are usually settled from memory, and a dated list of live hosts settles them with evidence instead.