Security Scan Results

WordPress version 7.0 detected

WP_DEBUG is disabled (no PHP errors visible)

Missing security header: X-Frame-Options -- Prevents clickjacking attacks

How to fix: Add to .htaccess: Header always set X-Frame-Options "SAMEORIGIN" — prevents clickjacking attacks.

Missing security header: X-Content-Type-Options -- Prevents MIME-type sniffing

How to fix: Add to .htaccess: Header always set X-Content-Type-Options "nosniff" — prevents MIME-type sniffing.

Missing security header: Strict-Transport-Security -- Enforces HTTPS connections

How to fix: Add to .htaccess or nginx: Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

Missing security header: Content-Security-Policy -- Controls resource loading

Missing security header: Referrer-Policy -- Controls referrer information

Missing security header: Permissions-Policy -- Controls browser feature access

SSL certificate valid (59 days remaining) — issued by Let's Encrypt

HTTP correctly redirects to HTTPS

Debug log exposed

/wp-content/debug.log

WordPress license file exposed

/license.txt

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: accounts.google.com (Tranco rank #1)

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): accounts.google.com

How to fix: These scripts are from globally popular domains. They are very likely legitimate services but were not in our curated whitelist.