Security Scan Results

WordPress version 6.9.1 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: Content-Security-Policy -- Controls resource loading

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

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

1 of 6 security headers configured

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

HTTP correctly redirects to HTTPS

User enumeration possible via REST API -- found: ascheller, acaumont, bwormald, bsakla, bwebster

How to fix: Disable the REST API users endpoint with a plugin like Disable REST API or add a filter to block /wp/v2/users.

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.

3 trusted external script(s): challenges.cloudflare.com (Security), stats.wp.com (WordPress), www.googletagmanager.com (Google)

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.