Compare the Software Details in Two Server Headers
Admin ·
Review the Server field as evidence from the response path. Its product tokens and optional comments show what an origin or intermediary chose to expose at capture time.
Check the product, version and platform in two captures
Load Two Apache response blocks and select Analyze Server header. Response 1 is HTTP 200. Its field at line 2 has two product tokens, Apache/2.4.62 and OpenSSL/3.0.15. The comment names Debian. The report labels the exposure Version and platform.
Select Response 2. The HTTP 304 block has only Apache at line 6, so the report shows Product identifier. Download the JSON and compare the two response statuses and original line numbers.
Verify the same public route after changing its configuration
For an Apache service you administer, review ServerTokens Prod and follow your deployment's normal validation steps. Record the public response from the same route after the change. Compare the Server product, version token and comment with the earlier response.
On NGINX, review server_tokens off for the relevant configuration block. Use a separate edge capture when a proxy or CDN can add its own Server value. Confirm installed packages and updates through the system you administer.
Review every recorded Server field when lines repeat
Paste two named Server lines back to back. The report flags the repeated field and keeps both parsed values. Check the original headers, keeping the request path and status nearby so you can find where each field entered the response.
Common questions
How are parentheses in a Server value interpreted?
They form comments. The analyzer reports recognized platform names within balanced comments and withholds the rest of the comment text.
Does the report verify the real web server or operating system?
It records advertised tokens and comments. Compare that evidence with the service inventory and any intermediary that can edit the header.