# SCT feature support **URL:** \ **Category:** Issuance Tech\ **Created:** [March 29, 2018, 6:51pm UTC](https://community.letsencrypt.org/t/sct-feature-support/58101 "2018-03-29T18:51:09Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [March 29, 2018, 10:26pm UTC](https://community.letsencrypt.org/t/sct-feature-support/58101/8 "2018-03-29T22:26:08Z")
> [@tialaramex](#): > > I don’t think there’s any particular reason for Let’s Encrypt to log the finished certificate, certainly not in 3rd party logs, but nothing stops other people sending them in, and if your log partners are OK with you doubling their input volume you could harmlessly do this. One reason that's recently been endorsed on ct-policy or somewhere is that it allows people to survey the ecosystem and see what logs are actively in use to help see, for example, how disruptive it is to distrust a particular log. (I don't think Chrome will block a certificate using embedded SCTs from a later-distrusted log, though?) --- _[View the full topic](https://community.letsencrypt.org/t/sct-feature-support/58101)._