How we identify the platform
We fetch the homepage like a regular visitor and read the HTML and response headers, such as the generator tag, X-Powered-By and recognizable paths like /wp-content/. Versions come only from explicit product information, never from file names or cache parameters like ?ver=. No password or installation is needed.
The sources we compare against
WordPress is checked against WordPress.org's list of versions. Drupal, PrestaShop, TYPO3, Ghost, Next.js and other code-based platforms are checked against OSV, an open database of vulnerabilities in software packages. These need a full version, such as 10.2.3. WooCommerce, Elementor and other WordPress plugins are checked against WPVulnerability. The sources receive at most a product name and version, never your domain or email address.
Insecure or just outdated
WordPress.org marks every version that is not the latest in its release branch as insecure. The latest version in an older branch counts as outdated, meaning a newer major version exists. The report separates known security issues from ordinary updates and shows severity and fixed versions when the source provides them. A notice is not evidence of a breach.
Plugins, themes and JavaScript
Plugins and themes often show up in the paths of the page's files, but rarely with a version. Without a version we cannot match vulnerabilities, and the report then says the version is not shown. For JavaScript we read up to five referenced scripts, up to 1 MB per file and 3 MB in total. Retire.js recognizes the library and version from the file contents, so even a renamed script can often be identified.
Notices when the version is hidden
Many websites hide their version. We then retrieve the platform's recent notices from GitHub Advisory Database, WordPress.org security news, Joomla Security Centre or WPVulnerability. For Magento and Adobe Commerce we always show Adobe's latest security bulletins, because the patch level cannot be determined from outside. These notices are shown separately, do not lower the score and do not trigger email.
Platforms we recognize
Identification includes WordPress, WooCommerce, Elementor, Drupal, Joomla, Magento/Adobe Commerce, PrestaShop, TYPO3, Ghost, Next.js, Nuxt and Astro. SvelteKit, Shopware, Craft CMS, Umbraco, Statamic, Strapi, Directus, Payload, Laravel and Symfony can be identified when they expose explicit product metadata. Visible WordPress plugins and themes can be linked to WPVulnerability, up to twelve additional components per check.
Provider-managed platforms
Shopify, Wix, Squarespace, Webflow, Framer, BigCommerce and HubSpot CMS handle core platform updates themselves. We recognize them and say so in the report. Identification is not a security approval.
Monitoring and email
With monitoring the check runs on activation and then every day. New findings, both known vulnerabilities and newer versions, are grouped into one email. The same ongoing finding does not trigger a new email every day, but if it disappears and comes back, we email again. Source results may be reused for up to six hours.
When a finding counts as fixed
A finding is marked as fixed only when a new check sees a version that no longer matches. If the version information disappears, the page is blocked or a source does not respond, earlier findings remain as not verified as fixed. Missing or conflicting version details give no match, and finding nothing does not mean the website is secure.