Review and update your PHP
Check the PHP version and vendor patches actually serving your website. Update, restart the service, and verify the running version.
Enter your website to check its public PHP version. Understand the version risk and what to do next.
We read public response headers and compare the PHP version with official security fixes.
SourcePHP security advisory
ScopeTwo PHP2Shell vulnerabilities
Rules reviewed2026.10.22
Read the advisory ↗Find large files and folders on Mac with DiskTreeSize. Sort a folder tree by size, compare allocated and logical size, and explore visual disk usage maps locally.
Explore appEdit local files in tabs, use regular-expression find and replace, edit columns, and run restricted local scripts with timeout and rollback.
Explore appKeep Codex usage, remaining 5-hour and weekly quota, reset times, and daily token totals visible in the Mac menu bar while you work.
Explore appUpload files over SFTP and run commands or scripts on multiple Linux servers from one Mac app. View live output, retry failed tasks, and store credentials in Keychain.
Explore appPHP Check is our free tool. If it helped, take a look at our Mac apps too.
Check the PHP version and vendor patches actually serving your website. Update, restart the service, and verify the running version.
The reported version reaches the official fix for its branch. Other vulnerabilities, configuration, and application security need separate checks.
The website may hide its version or not use PHP. Check the web-serving PHP-FPM or hosting panel, then compare the version manually.
Use the complete version serving your website. The command-line PHP version may differ from your website's runtime.
Headers may be hidden or changed. Vendors may backport security patches without changing the upstream version. This check provides a lead, not proof of exploitability or compromise.
No. We send HEAD, falling back to GET only if unsupported, and read response headers. We follow up to three public redirects. No uploads, login attempts, or exploit requests.
We don't store check URLs or history. We query Cloudflare's public DNS using the domain only, then request your website. Paths and query strings aren't sent to the DNS service. Don't enter URLs containing private tokens.