0800 433 7990 Tell us about your system

End-of-support badges

A badge for any product we track, showing whether it is still supported and until when. Put it in a README, a wiki page, an internal status board or a handover document. It is rebuilt whenever the dates change, so it never goes stale.

Windows Server 2016: security fixes end 12 Jan 2027

Pick a product

Choose the product, then copy the badge in whichever form you need. The badge is free to use with or without a link; if you link it, link to the page for that product, which explains the dates and the options.

Windows Server 2016: security fixes end 12 Jan 2027

Every badge

Status as of 3 October 2026. The address of each badge is /badge/<id>.svg; the id is the one in the feed below.

SQL Server

.NET and .NET Framework

Windows Server

Microsoft Access and Office

PHP

Older web and desktop technologies

Web servers, frameworks and content management systems

The data behind the badges

Everything the badges show is in one JSON file, free to read from a script or a dashboard.

https://www.codefirst.co.uk/end-of-life/feed.json lists every product with its release date, the end of mainstream support, the end of security fixes, the last date of any paid extension, its status on the day the file was generated, and the page and badge for it. One entry looks like this:

{
  "id": "ws-2016",
  "family": "windows-server",
  "name": "Windows Server 2016",
  "released": "2016-10-15",
  "mainstreamEnd": "2022-01-11",
  "end": "2027-01-12",
  "paidEnd": "2030-01-12",
  "status": "ending",
  "note": null,
  "page": "https://www.codefirst.co.uk/end-of-life/windows-server-2016/",
  "badge": "https://www.codefirst.co.uk/badge/ws-2016.svg"
}

The dates are taken from each vendor's lifecycle pages. Every time the site is published they are compared with endoflife.date, and the site will not publish while a date disagrees. The same dates feed the end-of-support pages, the calendar file, the free server check script and the website check.

Use the feed freely. If you publish something built on it, a link to the product page you quote lets readers see the dates in context, but it is not a condition.

How a badge keeps up to date

It is a live image
Your page embeds the badge from this site, so whatever it shows is current. Nothing needs changing on your side when a date passes.
Status is worked out on publish
Supported, ending within a year or ended is calculated on the day the site is built. The site is rebuilt at least weekly, and a badge is cached for one day.
Dates only change on evidence
A date changes only when the vendor changes it. We note the source of every date on the product pages.
Nothing is tracked
The badge is a plain SVG file. Loading it sets no cookie and sends us nothing about the page it is on or who is looking at it.

Showing a red badge somewhere that matters?

Tell us which version, what depends on it and how it is hosted. We will set out the upgrade route and what it is likely to involve.

Tell us about your system 0800 433 7990 Monday to Friday, 9am to 5pm. A first 20-minute call is free, and we reply to every enquiry within one working day. What happens after you get in touch

We would like to use analytics (Google Analytics and PostHog) to see which pages are useful and where visitors get stuck. They set cookies, so they stay off unless you agree. Cookie policy