How to fix: X-Backend-Server header reveals backend hostname
The X-Backend-Server header discloses the internal hostname or IP of the backend server that handled the request.
Why it matters
Internal hostnames and IPs reveal your infrastructure topology, making it easier to target specific backend servers, bypass load balancers, or enumerate internal services.
Remove all headers that expose backend server identity.
How to fix it
- 1Configure your load balancer or CDN to strip X-Backend-Server
- 2Audit all custom headers set by backend services for internal information
Code examples
Nginx: strip backend headers
proxy_hide_header X-Backend-Server;
proxy_hide_header X-Real-Server;
proxy_hide_header X-Node-Id;References
Detected automatically by VulnRadar. The check id is x-backend-server-exposed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-Backend-Server header reveals backend hostname?
- VulnRadar rates this low severity in the headers 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 x-backend-server-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Backend-Server header reveals backend hostname 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.