Web security
WordPress XML-RPC disabled
Security headers, HTTPS enforcement, cookies and cross-origin rules of the website.
Why it matters
XML-RPC lets attackers test hundreds of passwords in one request and is used to amplify attacks against other sites.
How to fix it
Quick fix · under 1 hour- Disable XML-RPC unless an integration needs it.
- Reload the web server and re-run the scan to confirm.
WordPress (functions.php)
add_filter('xmlrpc_enabled', '__return_false');nginx
location = /xmlrpc.php { 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