See the WordPress version, plugins, and theme a site shows, checked against known vulnerabilities, plus the files that give too much away.
Sample
example.com
1 problem to fix
Sample result | 2 good | 0 to improve | 1 to fix
WordPress
6.8.3
Plugins seen
9
Known vulnerabilities
2
Fix: Contact Form 7 5.9.2: 2 known vulnerabilities
High severity at worst. Fixed in 6.0.6.
How to fix: Update Contact Form 7 to 6.0.6 or newer (Plugins, after a backup).
Good: 8 plugins and themes with no known vulnerabilities
Elementor 3.31.2, Yoast SEO 26.1, and 6 more.
What This Checks
The WordPress version, plugins, and theme the site shows publicly
Each version against our daily copy of Wordfence Intelligence's vulnerability feed
A public debug log, listed user names, browsable folders, and XML-RPC
Every check reads only what the site and its public DNS show. Nothing is signed in to, submitted, or attacked.
Questions
Is it safe to scan a site I do not own?
The scan only reads public pages and files any visitor could open. It never signs in, guesses passwords, or tries an exploit, so it is safe to run on any site.
Where does the vulnerability data come from?
From Wordfence Intelligence, a free vulnerability database. We copy its feed once a day into our own systems and check against that copy, so your scan is never sent to anyone else.
Why are some plugins listed without a version?
A site only shows what its pages load. Some plugins hide their version, and some load nothing on the home page. A scan from inside WordPress, which MountDev Maintenance runs daily, sees every plugin and version.
What should I do if a plugin has a vulnerability?
Update it to the fixed version shown, after a backup. If no fix exists yet, deactivate it or replace it with another plugin until its developer releases one.