---
title: "Discussion on \"TLS certificates now expire every 200 days. Here's a small Python check before it drops to 47\" | Hashnode"
description: "Discussion on \"TLS certificates now expire every 200 days. Here's a small Python check before it drops to 47\". On March 15, 2026, the maximum lifetime of a public TLS certificate dropped from 398 days to 200. In March 2027 it drops to 100, and in March 2029 to 47. The CA/Browser Forum approved this schedule in"
url: "https://hashnode.com/posts/tls-certificates-now-expire-every-200-days-here-s-a-small-python-check-before-it-drops-to-47/6af2a4df80d52f3ac61dfdb8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [TLS certificates now expire every 200 days. Here's a small Python check before it drops to 47](https://matiasisnard.hashnode.dev/tls-certificates-now-expire-every-200-days-here-s-a-small-python-check-before-it-drops-to-47?utm_source=hashnode&utm_medium=feed)

On March 15, 2026, the maximum lifetime of a public TLS certificate dropped from 398 days to 200. In March 2027 it drops to 100, and in March 2029 to 47. The CA/Browser Forum approved this schedule in

6d ago · 7 min read · matiasisnard.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#python](https://hashnode.com/tag/python)
-   [#ssl](https://hashnode.com/tag/ssl)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Matias Isnard](https://hashnode.com/@misnard)

@misnard · Buenos Aires, Argentina

  
[View profile](https://hashnode.com/@misnard)

Security engineer (IAM & GRC). Practical guides on certificates, access and automation with Python.

Security engineer working on identity and access management (IAM), GRC and ISO 27001. I write practical, tested guides on TLS certificates, access reviews and automating security checks with Python.

## Responses 2

Markdown supported · ⌘↵ to post

[AI Developer](https://hashnode.com/@lycore)

[6d ago](https://hashnode.com/posts/tls-certificates-now-expire-every-200-days-here-s-a-small-python-check-before-it-drops-to-47/6af2a4df80d52f3ac61dfdb8/comment/6af2ec883e19241a9e34a749)

The distinction between an expiry warning and a failed TLS validation is useful for alert routing. For services behind a load balancer, consider checking every served address from more than one network vantage point: a single DNS result can miss a stale certificate on one backend. A separate alert for inventory coverage would also help distinguish “all checked hosts are healthy” from “all hosts are accounted for.”

[Matias Isnard](https://hashnode.com/@misnard)

[6d ago](https://hashnode.com/posts/tls-certificates-now-expire-every-200-days-here-s-a-small-python-check-before-it-drops-to-47/6af2a4df80d52f3ac61dfdb8/comment/6af2ec883e19241a9e34a749#reply-6af2ff7961f6cdda08fd6e48)

Good point on load balancers. The script resolves the hostname once and connects to whatever address comes back, so a stale certificate on one backend can hide behind the others. Resolving all A/AAAA records and checking each IP with the hostname as SNI would close that gap. I'll add it as an option in the repo.
