Web server detection
The server software that answered, as its own headers name it.
The web server is the software that accepted the connection and sent back the response: nginx, Apache HTTP Server, LiteSpeed, Microsoft IIS, Caddy, or an edge network such as Cloudflare or Amazon CloudFront standing in front of the real machine.
How SiteScan identifies it
The row reads the Server response header of the entry page and maps it to a known product name, so Apache/2.4.62 (Debian) becomes "Apache HTTP Server 2.4.62". When the header is missing or has been rewritten, headers only one family sends serve as a fallback — cf-ray for Cloudflare, x-litespeed-cache for LiteSpeed, x-aspnet-version for IIS. A version is shown only when the server published one; nothing is guessed. If a CDN answers, its name is what you see, not the origin behind it.
The row is informational: green when a name was found, grey when the server keeps quiet.
Should you hide it?
The product name does little harm, but an exact version tells an attacker which known vulnerabilities to try. Keep the name if you like and drop the version: server_tokens off; in nginx, ServerTokens Prod with ServerSignature Off in Apache, and expose_php = Off against X-Powered-By. Then keep the software patched — hiding a version is no substitute for updating it. See version banner.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Technology”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data