Web Servers templates

Templates available in Web Servers category

Web Server category templates covers popular pieces of Web server software. How to use application templates?

Templates list

Templates description

The below templates belong to Web Servers category:

Apache 1.3 Web Server, a legacy Apache Web server software, still in use by many a site.

Apache 2.X Web Server, modern version of Apache Web server software, including full sources redesign, native IPv6 support, custom protocols support and various other features.

Apache Web Server used by IPHost, allows monitoring Apache Web server bundled with IPHost itself – to make sure its configuration is appropriate and secure.

Generic Web Server – use this template in case none of the others in this category matches the exact title and version of Web server software to be monitored.

Microsoft IIS 6 Web Server (Internet Information Services), Microsoft Windows native Web services software; IIS 6 was supplied with Windows Server 2003 and Windows XP 64-bit version; legacy software, currently unsupported.

Microsoft IIS 7 Web Server has been introduced with Windows Vista and Windows Server 2008; legacy software, currently unsupported.

Microsoft IIS 8 Web Server is available in Windows Server 2012 and Windows 8; among other features, introduced SNI (binding HTTPS hosts to host names rather than IP address).

Microsoft IIS 10 Web Server is available with Windows Server 2016 and Windows 10; among other enhancements, introduces HTTP/2

Web Servers monitoring use cases

  • when monitoring sites powered by WHM/CPanel, use Apache 2.X Web Server, the default for latest CPanel versions
  • to monitor IPHost’s Web interface health, you can use Apache Web Server used by IPHost template (self-checking)
  • if Web server software provides no clue on server type/version, or if there’s no specific software mentioned in the list above, it is safe to use Generic Web Server template

Web Servers monitoring tips

  • when in doubt, which Web server template to choose, use telnet to get server response headers; server software is often reported in Server: header; you can also inquire Web server software using services like Built with
  • when exposing IPHost Web interface to public access, make sure you use HTTPS only and the latest security recommendations as well, such as those from Cipher List
  • when checking for Web server response, try choosing URL generating as little Web server load as possible; it is advised to use Web Transaction Monitor for anything requiring complex analysis
  • make sure caching is turned off for URL to monitor, otherwise you might get data different from those actually expected (such as stale, out-of-date responses).
  • when monitoring legacy servers, use Remote Network Agents, avoid exposing (even with port forwarding) legacy services to the common public – minimize security risks