# Keep getting certificate expiration notice emails even though certificate already renewed

**URL:** <https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833>\
**Category:** Issuance Tech\
**Created:** [December 8, 2016, 8:27pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833 "2016-12-08T20:27:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kz26](https://avatars.discourse-cdn.com/v4/letter/k/b9bd4f/32.png) [@kz26](https://community.letsencrypt.org/u/kz26)\
**Post date:** [December 8, 2016, 8:27pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833/1 "2016-12-08T20:27:20Z")

</div>

I’ve been receiving certificate expiration notice/renewal reminder emails for one of my Let’s Encrypt certs, even though the certificate has been renewed and doesn’t expire until February (cert expiration date has been checked with openssl and browser). Looks like a bug with the Let’s Encrypt reminder system?

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [December 8, 2016, 8:32pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833/2 "2016-12-08T20:32:59Z")

</div>

Hi @kz26,

This is a common point of confusion that we recently added [some more documentation for](https://letsencrypt.org/docs/expiration-emails/):

> If your certificate is already renewed, we won’t send an expiry notice. We consider a certificate to be renewed if there is a newer certificate with the exact same set of names, regardless of which account created it. If you’ve issued a new certificate that adds or removes a name relative to your old certificate, you will get expiration email about your old certificate. If you check the certificate currently running on your website, and it shows the correct date, no further action is needed.

Typically folks will add additional domain names to a certificate, creating a **new** certificate from our system's perspective, not a renewal. When the old (typically unused) certificate with the smaller set of names is due to expire, the warning email about it can be confusing.

If this sounds like your circumstance then the mystery is solved 🙂 If you aren't sure the next step for us to help would be for you to provide the domain name(s) you are receiving warnings for so that we can check the certificate issuance history for them.

Thanks!

---

<div class="post-metadata">

**Author:** ![kz26](https://avatars.discourse-cdn.com/v4/letter/k/b9bd4f/32.png) [@kz26](https://community.letsencrypt.org/u/kz26)\
**Post date:** [December 8, 2016, 8:50pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833/3 "2016-12-08T20:50:49Z")

</div>

I did add some additional subdomains, so I guess that’s what happened. Thanks for the quick response.

---

<div class="post-metadata">

**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\
**Post date:** [December 8, 2016, 8:55pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833/4 "2016-12-08T20:55:06Z")

</div>

Great! Happy to help.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [January 7, 2017, 8:55pm UTC](https://community.letsencrypt.org/t/keep-getting-certificate-expiration-notice-emails-even-though-certificate-already-renewed/23833/5 "2017-01-07T20:55:18Z")

</div>

Closed on January 7, 2017, 8:55pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
