Web security
CMS version not public
Security headers, HTTPS enforcement, cookies and cross-origin rules of the website.
Why it matters
Attackers match the exact CMS version against published vulnerabilities and target sites running affected versions automatically.
How to fix it
Quick fix · under 1 hour- Update the CMS core to the latest release.
- Remove version hints: the generator tag, readme files and changelogs in the web root.
WordPress (functions.php)
remove_action('wp_head', 'wp_generator');
add_filter('the_generator', '__return_empty_string');nginx (block readme/changelog files)
location ~* /(readme\.html|license\.txt|changelog\.txt)$ { deny all; }How we test it
The check runs from the public internet as part of every scan, read-only and without touching your data. If it fails, your report shows the evidence that proves it - the record, header, file or banner we observed - together with the fix above, tailored to the issue we found.
Does your domain pass this check?
Run all 97 checks in about a minute. Your first scan is free, with the complete fix for your most urgent finding.
Scan your domain free