How do I find an expired certificate in a packet capture?
In TLS 1.2 and older, the server sends its certificate in the clear during the handshake, so its expiry date (notAfter) is visible in the capture. TLS 1.3 encrypts the certificate, so for TLS 1.3 servers check the certificate with a browser or openssl instead.
What it looks like in the packets
- A Certificate handshake message from the server (TLS 1.2 and older).
- The leaf certificate's validity period: notBefore and notAfter.
- Clients reject an expired certificate, often with a certificate_expired or bad_certificate alert.
Common causes
- Automatic renewal failed or was never set up.
- A renewed certificate was never deployed to every server.
- The device's clock is wrong, which makes a valid certificate look expired.
What to check
- Compare notAfter with the capture date.
- Check that every server behind the name has the new certificate.
- Check the client's clock if only one device complains.
Wireshark display filters
tls.handshake.type == 11
How Blame Finder flags it
High if expired; Warning within 14 days; Low within 30 days. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.