How to fix: Server header truncated
The Server response header ends with the literal string '(truncated)', which indicates the upstream version was actively hidden but the truncation marker is itself a fingerprint.
Why it matters
Even a truncated Server header confirms that a real version string is present upstream and that the masking is incomplete. The marker reveals which middleware layer is involved and may help an attacker identify the proxy or load balancer in use.
Some reverse proxies append '(truncated)' after the version string when server_tokens is configured to mask but not fully strip the value. The marker still confirms a real version is present upstream.
How to fix it
- 1Set `server_tokens off;` in nginx.conf and remove the Server header entirely with `proxy_hide_header Server;`.
- 2In Apache, set `ServerTokens Prod` and `ServerSignature Off`.
- 3At Cloudflare, use a Transform Rule to strip Server before the response leaves the edge.
Code examples
Nginx (nginx.conf)
http {
server_tokens off;
server {
# Strip the Server header entirely at the proxy layer
proxy_hide_header Server;
add_header Server "" always;
}
}Apache (httpd.conf)
# Reveal only the product name, no version
ServerTokens Prod
# Remove the version footer from error pages
ServerSignature OffReferences
Detected automatically by VulnRadar. The check id is server-header-truncated, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
- InforeCAPTCHA site key exposure
Questions
- How severe is Server header truncated?
- VulnRadar rates this info severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id server-header-truncated, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server header truncated map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.