Server header HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

Security scan: Server / X-Powered-By header discloses software version

Response headers reveal the exact web server or framework version, helping attackers pick known exploits.

Exact message you may see Server header version disclosureWeb Server HTTP Header Internal IP DisclosureX-Powered-By header information leakServer: nginx/1.18.0 information disclosureServerTokens Full
Seen on: HTTP Nginx Apache PHP

Meaning

Hide version details: nginx server_tokens off;, Apache ServerTokens Prod and ServerSignature Off, PHP expose_php = Off, remove X-Powered-By in Express (app.disable("x-powered-by")) and ASP.NET. This is hardening, not a substitute for patching.

Common causes

  • Default server_tokens on in nginx
  • Apache ServerTokens Full
  • PHP expose_php enabled
  • X-Powered-By: Express/PHP/ASP.NET
  • Error pages showing version banners

⚡ Quick fix

  1. nginx: server_tokens off;
  2. Apache: ServerTokens Prod + ServerSignature Off
  3. Remove X-Powered-By and keep software patched

Detailed fix by platform

Nginx

  1. nginx
    server_tokens off;
    more_clear_headers Server;   # needs headers-more module

How to diagnose

  1. Server header — Shows version?
  2. X-Powered-By — Present?
  3. Patching — Current?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

400 — 400 Bad Request: Request Header Or Cookie Too Large (HTTP)400400 — 400 Bad Request: invalid character in header (HTTP)400401 — 401 Unauthorized without WWW-Authenticate header (HTTP)401CL.TE — HTTP request smuggling: Content-Length vs Transfer-Encoding mismatch (HTTP)CL.TECORS on errors — CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses (HTTP)CORS on errorsinsufficient security — tlsv1 alert insufficient security — server rejects the offered protocol/cipher/key strength (SSL / TLS)insufficient securityStrict-Transport-Security — Security scan: Strict-Transport-Security (HSTS) header missing (HTTP)Strict-Transport-Secu…the "listen ... http2" directive is deprecated — Nginx: nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead (Nginx / Apache)the "listen ... http2…Server he…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.