SiteDolphin

SiteDolphin / What we watch

Platform checks and security updates

A website that works can still run a version with known security issues. This check reads what your website publicly reveals about its software and compares the versions with open security sources, so you know what to ask your web agency or developer to look at.

Free, no account needed. Nothing to install on your site.

yourcompany.com

Free check · done 9:41 am

2 things to fix
  • UptimeResponds in 240 ms
  • CertificateValid for 74 days
  • DomainExpires in 211 days
  • EmailMissing DMARC
  • Links and images2 broken links
  • Search accessHomepage can be indexed
Example result from the free check

Works with any public website, for example

WordPressWixSquarespaceJoomlaDrupaland more

What we check

Everything is checked from the outside, the way a visitor or a search engine sees your website.

  • Platform and version

    We recognize close to 30 platforms, including WordPress, Drupal, Joomla and Shopify. Versions come only from explicit product information, never guessed from file names.

  • Known vulnerabilities

    A visible version is checked against WordPress.org, OSV or WPVulnerability. If it matches a known issue, or a newer version exists, you see it with the source and fixed version.

  • Plugins and themes

    WordPress plugins and themes visible in the page's files are looked up in WPVulnerability, up to twelve per check. Versions are compared when they are shown.

  • JavaScript libraries

    We read up to five of the homepage's scripts. Retire.js recognizes libraries such as jQuery and their versions from the file contents, without running the code.

  • Notices when the version is hidden

    If the website shows no version, we list the platform's recent security notices so your developer can see whether they apply. They are not counted as findings.

  • Every day

    With monitoring the check runs daily. New matches are grouped into one email, and the same finding is not emailed again every day.

Example result

This is what it can look like when you run the free check. Each row says what we found.

yourcompany.com

Free check · done 9:41 am

6 known security issues in this version
  • jquery 1.12.4 · JavaScript librarySecurity notices match this version
  • bootstrap 5.3.3 · JavaScript libraryNo matching notices in the checked source
  • WordPressVersion could not be determined
  • contact-form-7 · WordPress pluginVersion not shown publicly (common, not an error)
A made-up example of a WordPress website. The free check shows this row and the number of findings. Which notices apply, their sources and the fixed versions are shown with monitoring.

What the email looks like

With monitoring you hear from us by email, written so you understand it without being technical.

SiteDolphin
to me
9:41 am

Updates to review: yourcompany.com

Public version information on yourcompany.com matches these update or security notices:

jquery 1.12.4: Regex in its jQuery.htmlPrefilter sometimes may introduce XSS. Retire.js. Fixed versions listed by the source: 3.5.0. Check the applicable release branch in the source.

Ask whoever maintains your website to confirm the installed version and review the vendor advice. Back up and test updates before publishing.

This is not evidence of a breach and public metadata can be outdated.

View all findings and sources

You are getting this email because the website is monitored by SiteDolphin.

How to fix it

You can do this yourself, or pass it on to whoever looks after your website.

  1. Confirm the version

    Ask whoever maintains your website to check which version is actually installed, in the admin panel or on the server. Public information can be out of date, for example when a cache still serves an older page.

  2. Read the source

    Open the link in the report and check which versions are affected, which version fixes the issue and whether it only applies to a certain feature or setting. Pick the fix in the release branch you run, if there is one.

  3. Back up and test

    Back up files and the database, and ideally test the update on a copy of the website first. Plugins and themes can break after a major update.

  4. Update the right component

    An old JavaScript library often comes from a theme, a plugin or a custom snippet that loads its own copy. Updating the platform is then not enough; whatever loads the file needs to be updated or replaced.

  5. Don't just hide the version

    Removing the version information does not make the website safer. We can then no longer see that the issue was fixed, so the finding stays in the report as not verified as fixed.

  6. Check the result

    The next daily check shows whether the finding is gone. We never install patches automatically and we change nothing on your website.

How the check works

How we check, and how to read the result.

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.

Frequently asked questions

Why does it say the version is hidden?

Many platforms and plugins do not show their version, and security plugins often remove it. That is common and not an error. Without a version we cannot tell whether a known issue applies to you, so we show the platform's recent notices instead.

Does a finding mean my site was hacked?

No. A finding means the version your website shows matches a known issue in a public source. It is not evidence of a breach, but it is a reason to update soon.

I updated. Why is the finding still there?

The check runs once a day, and a cache can keep showing the old version for a while. If the page no longer shows any version, we cannot confirm the fix, so the finding stays as not verified as fixed.

Why is jQuery flagged?

Older versions of jQuery have known issues that are fixed in newer versions, and Retire.js lists them. The library is often loaded by a theme or plugin, so ask your developer which component loads it.

Does this cover Shopify and Wix?

We recognize them and show that the provider handles platform updates. Apps, themes and account security are your responsibility and are not part of the matching.

Do you send my website address to the security sources?

No. The sources receive at most a product name and version. Results are shared between checks and may be reused for up to six hours.

One price, everything included

The same monitoring for every website. Pay monthly or yearly.

First month free

$9per month

Per website, including tax

$0 for the first month, then the regular price. New customers, monthly plans. Card required; the code START is added for you.

  • No lock-in
  • Cancel anytime
  • 14-day right of withdrawal

What's included

  • Uptime and error pages checked every minute, around the clock
  • Certificate, domain and security notices daily
  • Links, images, email settings and cookies weekly
  • Plain-English emails with a suggested next step
  • History in your account and a monthly report
Try it free for a month

You see the full order before you pay. Or run a free check first

First billing month $0. Then $9 per website per month, including applicable taxes. Renews automatically monthly until canceled. Cancel before renewal in Manage billing in your account or via info@sitedolphin.com. Businesses can add a VAT ID at checkout.

VisaMastercardAmerican ExpressSecure checkout via Stripe

Check your website for free

No account and nothing to install.

First month free Then $9/month · cancel anytime