Free, instant, no sign-up

Website version checker: is your PHP, WordPress or jQuery out of date?

Enter your website. We load its home page once, read the software versions it shows to anyone who visits, and check each one against the latest releases and published security advisories.

We load your home page once, the way a browser would, and read what it shows. No sign-up needed.

What we check and where the data comes from

Release data is read live from php.net, wordpress.org, httpd.apache.org and nginx.org and refreshed every six hours. If one cannot be reached, we still show the versions we found and say we could not check them. Support dates for the frameworks and Magento come from their projects' own pages, read on 16 November 2026.

  • PHP, from the X-Powered-By header your server sends. We compare it with php.net's list of the latest release in each supported branch. A branch that is not on the list is end of life; an older release in a supported branch is missing security fixes. Security support ends on 31 December 2026 for PHP 8.2, 2027 for 8.3, 2028 for 8.4 and 2029 for 8.5 (php.net supported versions).
  • WordPress, from the generator tag, or else from the version number on WordPress's own stylesheet and script addresses. We look it up in the release list that api.wordpress.org publishes, which marks every release as latest, outdated or insecure.
  • jQuery, from the script addresses on the page (jQuery Migrate is a separate file and is not counted). Versions before 3.5.0 are affected by the cross-site scripting advisories CVE-2020-11022 and CVE-2020-11023, both fixed in 3.5.0. The current release is jQuery 4.0.0, published in January 2026 (jQuery blog).
  • Drupal, from the generator tag or the X-Generator header. Drupal 7 reached end of life on 5 January 2025, Drupal 9 on 1 November 2023 and Drupal 8 on 2 November 2021. Drupal 10 and 11 are supported, and Drupal 10's support ends on 9 December 2026 (Drupal release schedule).
  • AngularJS and Angular, from AngularJS script addresses or its ng-app and ng-controller attributes, and from the ng-version attribute that a server-rendered Angular page carries. AngularJS (version 1.x) has had no support since 31 December 2021 (Angular blog). For Angular we use the release table on angular.dev: versions 2 to 19 are no longer supported, Angular 20 is supported until 28 November 2026, 21 until June 2027 and 22 until June 2028.
  • Vue, from script addresses. Vue 2 reached end of life on 31 December 2023 (Vue 2 end of life notice); Vue 3 is the current version.
  • Bootstrap, from stylesheet and script addresses. The Bootstrap team's release policy lists Bootstrap 3 as end of life since 24 July 2019 and Bootstrap 4 since 1 January 2023; Bootstrap 5 is supported.
  • Magento, from the file paths and scripts each version uses. Adobe ended support for Magento 1 in June 2020 and released its final security patches then (Adobe bulletin APSB20-41). Magento 2 does not show its version, so we only say that we found it and point you to Adobe's security bulletins.
  • Server software, from the Server header, when it names a version. Apache httpd is compared with the latest 2.4 release on httpd.apache.org (2.2 and older are end of life), and nginx with the current stable and mainline releases on nginx.org. Linux distributions often patch these packages without changing the number, so confirm an "out of date" result with your host. Other server software is reported without a verdict. Either way, a visible version helps attackers pick known weaknesses, and OWASP recommends hiding it.

What the checker cannot tell you

It reads what your home page shows the public, nothing more.

  • A hidden version is not a safe version. Hiding versions is good practice, but it says nothing about whether the software is up to date.
  • It reads the home page only. Other pages, plugins, themes, the admin area and the server itself are not checked.
  • Some hosts use a Linux distribution's PHP, Apache or nginx, which can carry security fixes without a new version number. Confirm an "out of date" result for these with your host.
  • A CDN or cache in front of your site can hide or change the headers your server sends.
  • Frameworks bundled into your own JavaScript files usually show no version, and a page built only in the browser does not show Angular's version. Not finding a framework does not mean it is not there.

What to do if something is out of date

Back up first, and test updates on a copy of the site before the live one.

  • PHP end of life or missing security releases: ask your host to move the site to the latest release of a supported branch. Our guide to PHP versions and support dates explains what changes between versions, and our PHP security audit checks the server, the code and the upgrade path.
  • WordPress outdated or insecure: update WordPress from Dashboard > Updates, then plugins and themes. If updates break the site or have been put off for years, our WordPress team can do it with you.
  • jQuery older than 3.5.0: it is usually loaded by your theme or a plugin, so updating those often fixes it. Read do you still need jQuery? before you decide whether to update it or remove it.
  • Drupal 7, 8 or 9: the Drupal project no longer publishes security fixes for these versions, so plan a move to a supported version or another platform; our redesign and migration team can help.
  • AngularJS, an old Angular, Vue 2 or Bootstrap 3 or 4: these no longer get fixes, and moving off them usually means rewriting parts of the front end. Our Angular and Vue.js teams do these upgrades; for an old Bootstrap theme, a redesign is often the simpler route.
  • Magento 1: plan the move to Magento 2 (Adobe Commerce) or another platform with our Magento team.
  • Apache or nginx older than the current release: first ask your host whether the package carries backported fixes; if it does not, update it. Our PHP security audit covers the server as well as the code.
  • To stop it happening again: a website maintenance plan keeps the software up to date as releases come out.

Frequently asked questions

Is the website version checker free?

Yes. There is no sign-up. It loads your public home page once and shows the result on the page. If you want a copy, you can ask for the report by email; that is optional.

My result says "not visible". Does that mean my site is safe?

Not necessarily. Hiding versions is good practice and gives attackers less to go on, but it does not show whether the software is up to date. Ask your host or developer which versions you run, or check your admin area (in WordPress: Tools > Site Health > Info).

Why does it say my PHP or server software is out of date when my host says it is up to date?

Some hosts install PHP, Apache or nginx from a Linux distribution's packages (Ubuntu, Debian and others), which can include security fixes without changing the version number. Ask your host whether that applies to you. If it does not, update to the release the checker names.

Which frameworks does it recognise?

AngularJS and Angular, Vue and Bootstrap, when their version shows in a script or stylesheet address or, for Angular, in the ng-version attribute of a page rendered on the server. It also spots Magento 1 and Magento 2. A framework bundled into your own JavaScript files usually shows no version, so the checker cannot see it.

What happens if I ask for the report by email?

We email you the same list, with the source for each verdict, and our team may follow up about it. We keep your email address, the address you checked and the result like an inquiry. The newsletter box is separate and never ticked for you. See our privacy policy.

Does the checker scan my website for vulnerabilities?

No. It reads one page and compares the versions it shows with published release data. It does not test plugins, themes, the admin area or the server. A security audit does that.

How do I stop my site showing its versions?

For PHP, set expose_php = Off in php.ini. On nginx, use server_tokens off; on Apache, ServerTokens Prod and ServerSignature Off. WordPress prints its version in a generator tag, which many security plugins remove. Hiding versions does not replace updating them.

Need help updating PHP, WordPress or Drupal?

Tell us what the checker found and what your site runs on. We come back with questions, a suggested approach and an estimate.