end-of-life.org

Quick Verdict

End-of-life.org is a public tracker for software and hardware end-of-life dates and support status, covering 478 products and 8,773 versions or release branches. It may help teams identify versions that have already stopped receiving security patches or are approaching that point, especially when older systems remain in production.

The site reports that 78% of tracked products are already end of life and that 190 are expected to reach end of life within 90 days. It says the data is updated daily, which makes it useful for periodic lifecycle checks. However, the website does not clearly state its data sources, detailed update process, pricing, or the full scope of product coverage, so those points should be verified before relying on it for formal compliance or procurement decisions.

Key Features

• Tracks end-of-life dates and support status for software and hardware.
• Covers 478 products and 8,773 versions or release branches, according to the site.
• Lists CVEs missed by end-of-life software versions, helping readers connect lifecycle status with potential security exposure.
• Shows the proportion of tracked products that are already end of life and those reaching end of life within 90 days.
• Presents itself as updated daily, supporting recurring checks rather than a one-time lookup.
• Requires no account, form, or comments. The privacy page says the site does not record what visitors type or collect identifying information; one analytics tool counts visits in aggregate.

Who this is for

This appears best suited to developers, infrastructure teams, security practitioners, and technology managers who need a quick reference for checking whether a software or hardware version is still supported. It may also help organizations build an initial upgrade or replacement list, though the website does not clearly state whether it supports exports, alerts, integrations, or organization-specific tracking.

The main limitation is verification depth. Product coverage, source reliability, update methodology, and the meaning of individual support statuses are not described in detail in the available information. Treat the site as a useful reference point, then confirm critical dates with the relevant vendor before scheduling a migration, assessing risk, or making a compliance claim.