# SSL/TLS certificate news: policy, browsers, CAs, Let's Encrypt

> Dated, source-checked news on TLS certificates: CA/Browser Forum ballots, browser root program decisions, CA incidents and Let's Encrypt changes.

Source: https://ssl.sh/news/
Last updated: 2026-11-10

Certificate news on ssl.sh covers four kinds of change to publicly trusted TLS certificates: CA/Browser Forum ballots that amend the [Baseline Requirements](https://ssl.sh/glossary/baseline-requirements/), browser [root program](https://ssl.sh/glossary/root-program/) decisions such as distrusting a CA, incidents at individual [certificate authorities](https://ssl.sh/glossary/certificate-authority/), and changes at Let's Encrypt, the most widely used [ACME](https://ssl.sh/glossary/acme/) CA.

Each article answers three questions: what happened, who is affected and what you should do, with commands you can run against your own servers. Every date is checked against the official source listed at the end of the article, and dates that have not arrived yet are marked as upcoming. As of November 2026, newly issued public TLS certificates are limited to 200 days.

For the full sequence of lifetime changes see the [certificate validity timeline](https://ssl.sh/timeline/certificate-validity/). Let's Encrypt changes are collected in the [Let's Encrypt timeline](https://ssl.sh/timeline/lets-encrypt/), and browser trust decisions in the [root program timeline](https://ssl.sh/timeline/root-program-changes/). To check what your own site serves right now, use the [SSL checker](https://ssl.sh/tools/ssl-checker/).