What this tool does
It reviews WordPress signals, XML-RPC exposure, public readme/license files, uploads directory listing, REST user exposure, HTTPS, and quick header signals.
Run passive checks for common WordPress exposure and hardening issues.
No login, no exploit attempts, no invasive scans.
Find public files and endpoints that often leak information.
Get concise recommendations for server and WordPress cleanup.
This passive scanner checks common public WordPress exposures without logging in, exploiting, or changing the site.
It reviews WordPress signals, XML-RPC exposure, public readme/license files, uploads directory listing, REST user exposure, HTTPS, and quick header signals.
Enter the site URL and review the exposure list. Confirm any warning inside WordPress, the web server, or the control panel before changing production settings.
Warnings mean an endpoint or file is publicly reachable. Some are acceptable for specific workflows, but they should be intentional and protected where possible.
WordPress is a major hosting workload. Regular passive checks help reduce brute-force, information leakage, and misconfiguration risk.









































