Survey Data Mining:   Home | FAQ | Archive | Glossary
Free Reports

You are viewing an outdated report. The latest version of this report was published on July 1st, 2024

Weighed Web Server Share
June 1st, 2002

Report Description
How popular is a web server? Is it based on installed base, web pages served out, or other means? This weighed web server share report provides a market share analysis of web servers by weighing a web server based on how many sites link to it (see methodology).

As a result, some web servers that may not rank very high on our regular survey, may rank highly here, if they are used by very well known, highly referenced web sites. As the number of websites change (top 50, top 250 and top 1000 websites from our survey), the results are also very interesting and different.

Weighed Web Server Share - Top 50 Sites
Weighed Web Server Share - Top 50 Sites Web Server Historical Share - Top 50 Sites

Web ServerShare
Not Known11.54%
Netscape-Enterprise 5.66%
Stronghold 3.61%
GWS 2.98%
NaviServer 2.82%
Roxen 1.41%
AV 1.34%
AOLserver 1.32%

Weighed Web Server Share - Top 250 Sites
Weighed Web Server Share - Top 250 Sites Web Server Historical Share - Top 250 Sites

Web ServerShare
Not Known 8.29%
Stronghold 2.80%
Zeus 1.62%
GWS 1.51%
NaviServer 1.42%
AOLserver 1.39%
AV 0.91%
AkamaiGHost 0.89%
0W 0.80%
Roxen 0.71%
IBM_HTTP_Server 0.67%
Resin 0.42%
DCLK-HttpSvr 0.42%
Spry-SafetyWEB-Serve 0.36%
Y.G.Apache-SSLv3 0.24%
ConcentricHost-Naram 0.20%
Netscape-Commerce 0.20%

Weighed Web Server Share - Top 1000 Sites
Weighed Web Server Share - Top 1000 Sites
Web Server Historical Share - Top 1000 Sites

Web ServerShare
Not Known 6.80%
Stronghold 2.06%
Zeus 1.91%
GWS 1.09%
AkamaiGHost 0.98%
AOLserver 0.96%
NaviServer 0.86%
AV 0.72%
IBM_HTTP_Server 0.59%
0W 0.58%
Roxen 0.51%
thttpd 0.27%
Resin 0.26%
DCLK-HttpSvr 0.25%
Spry-SafetyWEB-Serve 0.22%
Y.G.Apache-SSLv3 0.14%
swcd 0.14%


Our goal with this report is to get closer to answering the question of how much traffic is served up on the internet by various servers than a typical web server count would reveal. We want to distinguish between a highly trafficed portal and a site that has only a couple visitors per month.

Since we don't have access to the actual traffic logs from all the different web servers in question, we focused on a different technique to determine the popularity of servers. The technique measures how authoritative a web server appears to be on the internet by how often it is referenced by other sites. The idea is that a server that is referenced by hundreds or thousands of sites wil in general have much more traffic than a web server that is referenced only a hand full of times, or not at all.

Our survey each month reports on the most popularly referred sites, which we call the popular referral report. This gives us a measure of how authoritative a site is. By combining this information with our existing knowledge of what server is running at the site in the report, we build a ranking of web servers based on referral popularity.

The scoring algorithm goes as follows:

  • Look up the next host in the referral report
  • Determine how many hosts referred to this web site
  • Determine the server signature (e.g. Apache, Netscape)
  • Add to this server type the number of hosts referring to the site
  • Go back to step 1 and look up the next host.

This is process is done 3 times, once for the top 50 sites, once for the top 250 sites, and once for the top 1000 sites. The percentages shown assume that the sites examined - 50, 250 or 1000 respectively - carried all internet traffic. While this is clearly not the case, the percentages are at least accurate relative to each other.

Finally, remember that the referral report (and thus how authoritative a site is) is based on a sample of the web. There is an inherent limitation in this report, which causes some site's referral count to be higher than warranted. Usually, this is a result of a suite of portals, all operated by the same group, each that refers to all the others. The effect of this is to lend a higher than justified weight to some sites. This results in a spiky historical trend line in the weighed graphs.

This problem is exasperated by the fact that our general crawler, up to and including the August 2000 survey, crawled our known list of sites alphabetically. This caused several of these portal "suites" to be clustered together due to their names. As of September 2000, the crawler has been randomized to limit the impact of this problem.

Because of the above problems, we recommend that the graphs be interpreted by paying limited attention to spikes in the graph, and more attention to general trends, such as server X appears to have more share than server "Y" when examined over the course of an 3-4 months.

© 1998-2024 E-Soft Inc. All rights reserved.