Home PHP version checker
FREE WEBSITE TOOL
Use this free website PHP version checker to look for a PHP version in public response headers. If it is hidden, use the owner-run WordPress plugin or enter a version from your host to review support dates and patch guidance.
Free to use · No login needed · No website changes made
FOR WORDPRESS WEBSITE OWNERS
The free PHP Runtime Check plugin runs inside your WordPress dashboard. It reads the PHP version executing that admin request and checks its support schedule. Public headers and CDN settings do not need to change.
Download PHP Runtime Check (.zip)
Admin-only. No public diagnostic endpoint, website changes or permanent connection. The optional patch button requests release data from php.net. The online handoff passes only the PHP version to jagjeetsingh.in when you choose it. Deactivate and delete the plugin after checking if you prefer.
Do not want to install a plugin? Use WordPress → Tools → Site Health → Info → Server, or your hosting dashboard, and enter that version here. The plugin reports the admin request’s runtime; separate applications or differently routed frontends may use another version.
No login or payment needed. A version check is not a security audit. Public headers can be hidden or outdated.
PHP version hidden? Use the free WordPress runtime-check plugin in “Check inside WordPress” above. It reads the runtime locally, without changing Sucuri or CDN settings. Or find the version in your hosting panel or Site Health and use manual mode. See the owner-check instructions.
TWO WAYS TO CHECK
Enter the public homepage address. The checker looks for a clear PHP version in its response headers. A reverse proxy or cache can hide the server’s runtime.
Own the WordPress website? Use the free admin-only plugin to read its actual runtime and support dates. The optional patch button checks PHP’s upstream reference. No permanent connection or public diagnostic endpoint is created.
Already have the version? Enter it manually to check support and patch guidance. Confirm hosting package details and test compatibility before an upgrade. A branch such as 8.4 cannot establish an exact patch status.
A CLEARER ANSWER
Looks for a PHP version in the public homepage response headers. If it is hidden or conflicting, the tool says so.
Shows whether the branch receives active support, security fixes only, or has passed its upstream support date.
Compares a complete version with PHP’s official release reference. Hosting-provider backports still need confirmation.
This is a version and support check, not a vulnerability scan or a security guarantee. It cannot verify server packages, vendor-backported fixes, WordPress plugin security or your hosting configuration.
WHEN PUBLIC DETECTION IS UNAVAILABLE
Use a source you control to identify the runtime serving your website. PHP and WordPress have separate version numbers; a WordPress core update does not confirm a PHP update.
Download PHP Runtime Check, upload it under Plugins → Add Plugin → Upload Plugin and activate it. Open Tools → PHP Runtime Check to see the runtime and branch support. Select Check latest PHP patch to compare with php.net. You can remove the plugin afterwards.
No automatic PHP updates, public diagnostic endpoints, background reports or permanent connection are added. The local runtime can be read without a network request; fetching the upstream patch reference requires access to php.net. Hosting backports still need confirmation.
The WordPress Site Health documentation explains the server information panel. Do not paste the full diagnostic report or any credentials.
Open your domain’s PHP settings in the hosting dashboard. In cPanel, MultiPHP Manager lists the selected version for each domain. Copy the value; checking it does not require changing the runtime.
If you administer the server, php -v reports the command-line PHP version. The CLI version can differ from PHP-FPM or the web-server runtime, so confirm which environment serves your website. See the PHP command-line reference.
There is no need to expose a PHP banner or upload a public phpinfo() file to use this checker.
SUPPORTED PHP VERSIONS
PHP’s upstream policy provides two years of active support followed by two years of security support for each release branch. After that, the branch reaches end of life. Use the official PHP supported versions schedule to plan ahead.
| PHP branch | Active support ends | Security support ends |
|---|---|---|
| PHP 8.2 | 31 December 2024 | 31 December 2026 |
| PHP 8.3 | 31 December 2025 | 31 December 2027 |
| PHP 8.4 | 31 December 2026 | 31 December 2028 |
| PHP 8.5 | 31 December 2027 | 31 December 2029 |
PHP 8.2 reaches upstream end of life on 31 December 2026. If you use it, allow time to review your theme, plugins and custom code, choose a compatible supported branch and test the change. Older branches have their own PHP end-of-life records.
A supported branch can still be missing a newer patch. Conversely, some hosts backport fixes without changing the upstream-looking version. The checker cannot verify those packages; your hosting provider must confirm them.
BEFORE YOU UPDATE
A public URL cannot reliably reveal a hidden PHP runtime. Many servers and CDNs remove version headers, and the website may use another technology. WordPress owners can run the free local plugin or open Site Health to read their runtime. Other website owners can use their hosting panel, then enter the version here. An unknown public result does not establish that PHP is absent, outdated or vulnerable.
Yes. The public check looks for a PHP header, while the optional WordPress plugin reads PHP_VERSION inside your own dashboard. Install it from the download on this page, then open Tools → PHP Runtime Check. It reports the runtime executing WordPress admin; separate applications and differently routed frontends can use another version.
It can indicate that an update needs review, but the version number alone cannot prove vulnerability. Some Linux distributions and hosting providers backport security fixes. Ask your host to confirm the installed packages and applicable advisories.
No. The checker does not change your website. A PHP upgrade should include a backup, staging tests of your theme and plugins, a rollback plan and checks after launch.
Review both the branch support date and the patch result. An end-of-life branch needs an upgrade plan; a supported branch may need a patch. Choose a supported version compatible with your application, and ask your host about vendor fixes. A public version string cannot prove that a website is secure or fully patched.
No WordPress credentials are requested by the online checker. Install and run the optional plugin through your own administrator account; it does not give this website remote access. A patch check contacts php.net for the release reference. The optional online handoff passes only your PHP version when you select it. Do not paste passwords, access tokens or full diagnostic reports here.
Reviewed 25 October 2026. Support dates come from PHP’s official support schedule. Patch references use PHP releases and refresh at most every six hours; public header results may be cached for ten minutes. PHP version headers are optional: see the PHP expose_php setting.
FROM THE CHECK TO A PLAN
Built by Jagjeet Singh, WordPress developer. Need implementation help? Share your website, hosting provider and the result through the PHP upgrade or security service below. Access and scope are agreed before work begins.
NEED A HAND?
I can help review your WordPress site’s PHP compatibility, prepare a backup and staging checks, and plan an upgrade with a rollback route. Share your website and what your host has reported.