Skip to content
Skip to content
API Pricing RU Sign In
← All HTTP Headers
Response

Server

Identifies the web server software. Should be minimized for security reasons.

Syntax

Server: <product>

Example

Server: nginx

Description

Server identifies the software used by the origin server. Common values: nginx, Apache, cloudflare.

Can expose details that help attackers find known vulnerabilities. Best practice: remove or set to a generic value.

In nginx: server_tokens off;. In Apache: ServerTokens Prod.

Check if your website sends this header correctly

Check your headers →

Related Articles

Graceful Degradation vs Progressive Enhancement: Strategies and Real-World Examples
Compare graceful degradation and progressive enhancement approaches to web development. Learn practical strategies, code examples, and when to use each approach for resilient web applications.
HSTS and Preload List: Complete Implementation Guide
Complete guide to HTTP Strict Transport Security (HSTS) header and preload list. Implementation steps, risks, rollback strategy, and best practices.
Anycast DNS Explained: How It Works, Benefits, and Implementation
Learn how anycast routing works for DNS. Understand the benefits for resilience, speed, and DDoS mitigation. Practical implementation guide.

Related Headers

Connection
Controls whether the network connection stays open after the current transaction finishes.
Content-Disposition
Indicates whether the response should be displayed inline or downloaded as a file attachment.
Content-Encoding
Specifies the compression algorithm applied to the response body, such as gzip or brotli.
Content-Length
Specifies the size of the response body in bytes.
Content-Type
Indicates the media type of the response body, telling the browser how to interpret and display the content.
Date
Indicates the date and time at which the response was generated by the server.

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation