Skip to content
ScanAnt

WordPress security scanner for live sites

Most WordPress compromises come from the same few places: an outdated plugin, a forgotten backup in the web root, a user list anyone can read. ScanAnt recognises a WordPress site, then runs the checks that matter for it. Header and script checks work for anyone; the WordPress-specific probes run after you prove the site is yours.

Free, no signup. We only read what your site already shows every visitor.

What we check

Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.

  • WordPress detection

    Quick scan

    We identify WordPress from the page, so the right checks run instead of a generic list.

  • Theme and plugin front-end

    Quick scan

    Outdated JavaScript libraries (an old jQuery is common), scripts without an integrity check and keys pasted into theme code.

  • Headers, HTTPS and cookies

    Quick scan

    HSTS, CSP, clickjacking protection, mixed content and the flags on login cookies.

  • User enumeration

    Verified scan

    Whether the REST users list works for anonymous visitors, including through the ?rest_route= form that bypasses a blocked /wp-json.

  • Config backups and the readme

    Verified scan

    Editor swap copies of wp-config.php, which hold database passwords and keys, and readme.html, which announces your version.

  • XML-RPC

    Deep scan

    Whether xmlrpc.php is enabled. It is a common target for credential guessing and request amplification.

  • Plugin folder listing

    Deep scan

    Whether the plugins directory lists its files, and whether installed plugin versions match a built-in list of known vulnerable releases. It is not a full vulnerability database.

  • Debug logs and old backups

    Deep scan

    A public debug.log, SQL dumps and zip backups in the web root, plus debug mode left on.

  • Quick scan: No signup. Reads only what every visitor receives.
  • Verified scan: After you prove you own the site. Read-only.
  • Deep scan: After you prove ownership and tick the deep option.

No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.

Common mistakes

  • Plugins you no longer use but did not delete

    Inactive plugins still ship vulnerable files that can be requested directly.

  • Backups and wp-config copies in the web root

    A file like wp-config.php.bak is served as plain text and contains your database password.

  • Leaving the author and user lists open

    It gives attackers real usernames, so only the password is left to guess.

  • Keeping xmlrpc.php open without needing it

    It lets scripts try many passwords in one request.

  • Using the default admin username and no rate limit

    The most common login attacks assume exactly that.

How to fix it

  1. Update core, themes and plugins, and delete the ones you do not use rather than just deactivating them.

  2. Remove backups, swap files, readme.html and debug.log from the web root, and block them at the web server.

  3. Restrict the /wp/v2/users endpoint for anonymous visitors and disable XML-RPC unless an app needs it.

  4. Turn WP_DEBUG off in production and add a login rate limit or two-factor sign-in through a security plugin.

  5. Add HSTS and a basic CSP at the web server or CDN.

Questions

Does it test my plugins for vulnerabilities?

Partly. When plugin versions are visible, we compare them with a built-in list of known vulnerable releases. That list is not exhaustive, so keep using your normal update routine and a dedicated WordPress vulnerability feed.

Do I need to install a plugin?

No. ScanAnt scans from outside by URL. Nothing is installed on your site and no admin access is needed.

Will it try to log in or guess passwords?

No. We do not guess passwords from a list and never use credentials we find. The optional login rate-limit probe sends up to 10 attempts with random non-existent credentials, only with your separate opt-in.

Why can the scan not see my wp-admin?

It only notes whether admin-looking pages open without a login screen. Anything behind a login is out of scope unless you provide a test account in a deep scan.

Is a hosted wordpress.com site covered?

The public-page checks work on any URL. Server-level probes only make sense on a site where you control the files, and they need ownership proof.

Run the scan now

Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.

Choose a scan level →