Web Server Fingerprinting
What is Web Server Fingerprinting?
Identifies web server software (nginx, Apache, IIS), version numbers, and server-side technologies from headers and responses.
This vulnerability class falls under the Information Gathering phase of the OWASP Testing Guide (WSTG-INFO). Security engineers prioritise information gathering checks early in an assessment because weaknesses here provide a foothold that amplifies the severity of vulnerabilities found in later phases.
Security Impact
Server version information helps attackers find known CVEs. This module detects version disclosure and recommends header hardening.
Left undetected, web server fingerprinting issues can persist unnoticed for months. Continuous automated scanning ensures your team receives an alert the moment a regression or new exposure is introduced — long before an attacker discovers it through manual enumeration or automated offensive tooling.
How DygDog Detects It
DygDog passively fingerprints the target by inspecting publicly reachable assets, response headers, DNS records, and indexed content — no active probing that could alert IDS/WAF systems.
The Web Server Fingerprinting check is implemented as a passive scan module, meaning it never sends dangerous payloads or modifies application state. Scans complete in approximately 800 ms and run continuously in the background so your security posture reflects the current state of your site — not a point-in-time snapshot.
Sample Finding
The following illustrates what a positive Web Server Fingerprinting detection looks like in practice.
Observed
Response header `Server: Apache/2.4.51 (Ubuntu)` present on all responses. Version 2.4.51 is affected by CVE-2021-41773 (path traversal / RCE) and CVE-2021-42013.
Risk
Knowing the exact server version and OS reduces attacker reconnaissance time from hours to seconds. Publicly-known CVEs can be directly weaponised.
Fix
Set `ServerTokens Prod` and `ServerSignature Off` in httpd.conf to suppress version disclosure. For nginx, use `server_tokens off;`.
Remediation Approach
Limit what search engines and passive observers can reach by tightening robots.txt directives, removing unnecessary meta-data from responses, and disabling directory listing on all web server configurations.
DygDog does not stop at detection. When a Web Server Fingerprinting finding is confirmed, the platform generates infrastructure-aware, copy-paste-ready remediation snippets using frontier AI models. Instead of generic advice you need to adapt, you receive code that targets your exact server, framework, and configuration.
OWASP References
This check maps to the following OWASP Testing Guide test cases:
- WSTG-INFO-02View OWASP WSTG →
Related Information Gathering Checks
These checks belong to the same testing phase and are often assessed together:
Search Engine Reconnaissance
Checks for sensitive content indexed by search engines via robots.txt, sitemap.xml, and meta robots directives.
Metadata & Information Leakage
Scans HTML comments, meta tags, and source code for developer notes, internal paths, and sensitive information.
Subdomain Enumeration
Discovers subdomains via DNS enumeration of common prefixes (api, admin, staging, dev, internal).
Subdomain Takeover Detection
Detects dangling DNS CNAMEs pointing to unclaimed cloud resources that could be hijacked by an attacker.
Detect Web Server Fingerprinting on Your Site
DygDog runs continuous passive scans across 74 vulnerability checks — including Web Server Fingerprinting — and notifies you the moment an issue is detected. Start a free scan in under 60 seconds, no installation required.
Start Free Scan