Server version disclosure in headers
Response headers that publish exact software versions. They tell whoever is looking which known vulnerabilities to try first, and cost nothing to switch off.
Many servers announce themselves in their response headers: Server: Apache/2.4.41 (Ubuntu), X-Powered-By: PHP/7.4.3. The exact version number helps nobody visiting your site, but it is the first thing automated attack tools read: a version maps directly to a list of known vulnerabilities, and a site running an old one is picked for exactly those exploits. Hiding the version does not fix anything, but it removes a free hint and makes you a less obvious target.
How SiteScan checks it
The scanner reads four headers of the home page — Server, X-Powered-By, X-AspNet-Version and X-Generator — and flags those that contain a version number. Product names alone, such as Server: nginx, are fine. If any version is found, the row lists the values and is amber; otherwise it says “None”.
How to switch them off
- nginx:
server_tokens off; - Apache:
ServerTokens ProdandServerSignature Off - PHP:
expose_php = Offin php.ini - ASP.NET:
<httpRuntime enableVersionHeader="false" />in web.config, and removeX-Powered-Byin IIS - CMS generator tags: a plugin or a theme setting usually removes them.
The most important step, though, is still to keep the software updated. See also the Exposure group.
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 “Delivery & reputation”
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