Free end-of-life software checker
See whether your home page advertises a version of PHP, Apache, IIS, nginx or OpenSSL that potentially no longer gets security fixes.
Example report
example.com- 1 Medium
- 1 passed
Also 3 informational.
Potentially end-of-life softwareexample.comMediumPotential
The X-Powered-By header advertises PHP 8.0.30. PHP releases before 8.2 no longer receive security fixes from the PHP project, so this is potentially end-of-life software.
Next step
Confirm the installed version on the server.
- End-of-life software
What the home page discloses
| Host | Technology | Version | Seen in |
|---|---|---|---|
| example.com | nginxWeb server | 1.24.0 | Server header: nginx/1.24.0 |
| example.com | PHPProgramming language | 8.0.30 | X-Powered-By header: PHP/8.0.30 |
| www.example.com | cloudflareHosting or CDN | Not disclosed | Server header: cloudflare |
What the end-of-life check looks at
Advertised versions
Version numbers in headers such as Server and X-Powered-By, and in the markup.
Five products
PHP, Apache httpd, IIS, nginx and OpenSSL, against a list checked in October 2026.
Support status
Whether each advertised version still receives security fixes.
Potential, not proof
An advertised version is a lead to confirm on the server.
Vendors and Linux distributions often backport fixes without changing the version they advertise, so confirm what is installed before acting.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
Potentially end-of-life softwareMedium
A version string suggests software that no longer receives security updates.
X-Powered-By: PHP/8.0.30Software past its end of life gets no fixes for newly found vulnerabilities. The version was inferred from what the server advertises: vendors sometimes backport fixes without changing it, so this needs checking.
Confirm the installed version on the server. If it is genuinely end-of-life, upgrade to a supported release.
Common end-of-life issues you can put right
Potentially end-of-life softwareMedium
An advertised version past its end of life potentially gets no more security fixes. Confirm what is installed, then upgrade to a supported release and stop advertising versions.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- One request for the home page of the domain and, for a registrable domain, its
www.name: HTTPS first, plain HTTP if HTTPS does not answer, following up to 2 redirects. - Every version number disclosed in headers such as
ServerandX-Powered-By, or in the page's markup. - Each version against a curated list, checked in October 2026: PHP before 8.2, Apache httpd before 2.4, IIS before 10, nginx before 1.18 and OpenSSL before 3.0.
- Severity by product: High for Apache httpd and IIS, Medium for PHP and OpenSSL, Low for nginx. Confidence is always low.
Reading a result
Software past its end of life gets no fixes for vulnerabilities found after that date. A server running it stays exposed to each new one, and an advertised version tells anyone scanning the internet which ones to try.
A pass means no advertised version matched the list. Often that is because the site advertises no versions at all, which is good practice, but it says nothing about software that stays quiet. Only the five products listed are judged; other software is shown by the technology detector but not compared with any end-of-life date.
A finding is always marked potential. The version was inferred from what the server sends, and vendors and Linux distributions often backport security fixes without changing it. Someone who knows the server should confirm the installed version and its support status before acting.
What it does not do
- Only versions the home page advertises are seen. Many servers advertise none, and a CDN in front of the site usually hides them.
- Only PHP, Apache httpd, IIS, nginx and OpenSSL are compared, against a list checked in October 2026. Other software is not judged.
- An advertised version can be wrong for the software actually running: vendors backport fixes, and a proxy can send its own headers. Every finding needs confirming on the server.
- It does not log in, read package lists or test for any vulnerability.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- Why is an end-of-life finding only potential?
- Because the version was read from what the server advertises, not from the software itself. Vendors and Linux distributions often backport security fixes to an old version number, so confirm what is installed and whether it is still supported before acting.
- Which PHP versions are end of life?
- As of October 2026, PHP releases before 8.2 no longer receive security fixes from the PHP project. Some Linux distributions support older versions for longer in their own packages.
- Is hiding the version number enough?
- No. It removes an easy clue for attackers, but the software is just as unsupported. Upgrade to a supported release, then stop advertising versions.

