# Revoking certain certificates on March 4

**URL:** <https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864>\
**Category:** Help\
**Created:** [March 3, 2020, 8:38am UTC](https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864 "2020-03-03T08:38:36Z")\
**Posts on this page:** 1\
**Showing post:** 182

<div class="post-metadata">

**Author:** ![jillian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jillian/32/11635_2.png) [@jillian](https://community.letsencrypt.org/u/jillian)\
**Post date:** [March 5, 2020, 10:00pm UTC](https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864/182 "2020-03-05T22:00:13Z")

</div>

We updated our FAQ this morning to reflect yesterday's work.

> [@JamesLE](#):
>
> Updated 2020-03-05: The following certificates were revoked prior to the compliance deadline at 2020-03-05 03:00 UTC (9pm U.S. ET 2020-03-04):
> 
> - 1,706,505 certificates that we are confident were replaced during the incident period
> - 445 certificates that we treated as highest priority for revocation because, at the time we found the bug, they had CAA records that forbid issuance by Let’s Encrypt.
> 
> We plan to revoke more certificates as we become confident that doing so will not be needlessly disruptive to Web users. Please continue to renew and replace affected certificates. If there are any changes to revocation plans, updates will be provided in this thread. Thank you all very much for your patience, understanding, and help as we work through this issue.

I hope this clarifies the current state of revocations.

---

_[View the full topic](https://community.letsencrypt.org/t/revoking-certain-certificates-on-march-4/114864)._
