src_823f7b237762257237
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Aug 14, 2025 00:00 UTC
- Retrieved
- Oct 08, 2026 03:47 UTC
End of Life Plan for RFC 6962 Certificate Transparency Logs
Update, August 18, 2025 We have updated the read-only and shutdown dates to ensure that our new Static CT API logs are fully trusted by browsers before switching Oak to read-only in order to avoid any disruption. Let’s Encrypt operates two types of Certificate Transparency (“CT”) logs—some implement the original RFC 6962 API, and some that implement the newer Static CT API. Today we are announcing
Reference details
- Source category
- Research & news
- Report title
End of Life Plan for RFC 6962 Certificate Transparency Logs- First reported
- Aug 14, 2025 00:00 UTC
- Last reported
- Aug 14, 2025 00:00 UTC
- Catalog updated
- Oct 08, 2026 03:47 UTC
- Record ID
48d8d041a7e1a0b191be0c51f9a837929fa2371c96c4348de52695ee00d78f4c
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.