Security Scan Results
https://whitehouse.gov
Scan complete
whitehouse.gov
Excellent Security
10 issues detected
Scanned 4 months ago
10
Total
0
Critical
0
High
0
Medium
WP_DEBUG is disabled (no PHP errors visible)
Missing security header: Permissions-Policy -- Controls browser feature access
5 of 6 security headers configured
SSL certificate valid (49 days remaining) — issued by Let's Encrypt
HTTP correctly redirects to HTTPS
REST API user enumeration blocked
wp-cron.php is publicly accessible (potential DDoS vector)
/wp-cron.php
How to fix: Disable WP-Cron in wp-config.php with define("DISABLE_WP_CRON", true) and use a real server cron job instead.
External JS from popular domain: cdn.parsely.com (Tranco rank #3,428)
How to fix: This script is from a well-known domain (ranked in the top 100K globally). Likely legitimate, but verify it matches a service you intentionally added.
1 external script(s) from popular domains (Tranco top 100K): cdn.parsely.com
How to fix: These scripts are from globally popular domains. They are very likely legitimate services but were not in our curated whitelist.
Checked against 11 blacklist services
Looking good!
Your site passed the surface scan. For complete peace of mind, a deep scan checks file integrity, database injections, and hidden backdoors at the server level.
Run Deep Scan — $1