Let's Encrypt is launching is own Certificate Transparency service!
I think this could be a great new addition to the source list for subdomain enumeration.
Today we are announcing a new Certificate Transparency log called Oak. The Oak log will be operated by Let’s Encrypt and all publicly trusted certificate authorities will be welcome to submit certificates.
We decided to create and operate a CT log for a few reasons. First, operating a log is consistent with our mission to create a more secure and privacy-respecting Web. We believe transparency increases security and empowers people to make well-informed decisions. Second, operating a log helps us take control of our destiny. Google Chrome requires all new certificates to be submitted to two separate logs, so multiple log options are imperative to our operation. Finally, Let’s Encrypt often issues more than 1M certificates each day, so we wanted to design a CT log that is optimized for high volume. We’ve designed our log to be able to handle submissions from all other publicly trusted Certificate Authorities so they can use Oak to fulfill their logging requirements as well.
Hi there,
Let's Encrypt is launching is own Certificate Transparency service! I think this could be a great new addition to the source list for subdomain enumeration.
Introducing Oak, a Free and Open Certificate Transparency Log
Announcement from Let's Encrypt:
Link to the CT-Logs docs with public keys
Cheers!