src_823f7b237762257237
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Apr 04, 2018 16:00 UTC
- Retrieved
- Oct 08, 2026 03:55 UTC
Engineering deep dive: Encoding of SCTs in certificates
Let’s Encrypt recently launched SCT embedding in certificates. This feature allows browsers to check that a certificate was submitted to a Certificate Transparency log. As part of the launch, we did a thorough review that the encoding of Signed Certificate Timestamps (SCTs) in our certificates matches the relevant specifications. In this post, I’ll dive into the details. You’ll learn more about X.
Reference details
- Source category
- Research & news
- Report title
Engineering deep dive: Encoding of SCTs in certificates- First reported
- Apr 04, 2018 16:00 UTC
- Last reported
- Apr 04, 2018 16:00 UTC
- Catalog updated
- Oct 08, 2026 03:55 UTC
- Record ID
58e0508b725107d918bd31b0b3e5ff17aa7b4157e8fe78502f4af76eceac29fd
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.
Review source update dates and status
- src_823f7b237762257237Collection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.