Skip to content

Standard

CA/Browser Forum

Industry group of certificate authorities and browser makers that sets technical and policy standards for publicly trusted TLS/SSL certificates.

Known aliases

  • CABF
  • CA/B Forum
  • Certification Authority/Browser Forum

Current stories

securityConfirmed4 publishers

Let's Encrypt shortens its default certificate lifetime to 64 days from February 10, 2027

Let's Encrypt will issue certificates valid for 64 days by default from February 10, 2027, down from 90, Help Net Security reported. Staging opens October 14, 2026, 119 days earlier, and 45-day defaults follow in 2028.

Publishers:helpnetsecurity.com letsencrypt.org lwn.net securityweek.com

Perspective Coverage

4 publishers
Builder
Builder 29%
Operator
Operator 60%
Investor
Investor 11%

Reality

Evidence88
Adoption
Not scored
Hype gap0
Incentives20
Confidence86
securityConfirmed7 publishers

Hijacked .gh, .sl and .as registries handed attackers HTTPS certificates for Google domains

Attackers who hijacked the operators of three country-code domains obtained HTTPS certificates for Google domains, Google disclosed. The company says the issuing CAs did nothing wrong, so its defence came after issuance, and it cannot promise it found every affected domain.

Perspective Coverage

8 publishers
Builder
Builder 24%
Operator
Operator 69%
Investor
Investor 7%

Reality

Evidence70
Adoption
Not scored
Hype gap+15
Incentives40
Confidence68
buildOne report1 publisher

Meta adds Network Time Security to its public time service, nts.meta.com

Meta's public time service now speaks NTS, so devices can verify time delivered over NTP, a protocol unauthenticated since 1985. Unattended certificate renewals and token checks all read that clock, so a forged reply on plain NTP can break them without anyone noticing.

Reality

Evidence45
Adoption
Not scored
Hype gap+5
Incentives35
Confidence55
buildOne report1 publisher

As TLS certificate lifetimes shrink toward 47 days, experts urge checking expiry from outside the renewing host

Public certificate authorities have capped TLS certificates at 200 days since 15 March 2026, falling to 47 days in March 2029. Renewal at that pace has to run unattended, and its failures show up only in the certificate a visitor's browser receives.

Publishers:dev.to

Reality

Evidence50
Adoption80
Hype gap+10
Incentives70
Confidence55
securityOne report1 publisher

Shrinking public TLS certificates to 47 days turns a 1,000-certificate estate into 21 renewals a day

DigiCert's survey of IT and security leaders puts a price on the outages that certificate expiry already causes, and it shows how unevenly enterprises are preparing for the 47-day deadline in 2029.

Reality

Evidence42
Adoption28
Hype gap+18
Incentives82
Confidence46
securityOne report1 publisher

47 days, eight renewals: the certificate calendar stops being a calendar

Thales's Imperva is shipping a connector for DigiCert's lifecycle manager. The deadline that makes it necessary belongs to the CA/Browser Forum, not to any vendor.

Publishers:imperva.com

Reality

Evidence34
Adoption14
Hype gap+32
Incentives90
Confidence33
securityOne report1 publisher

AWS gives email-validated certificates three 2027 deadlines, and the last one is a renewal cliff

ACM stops offering email validation in new Regions on Jan 1 2027, blocks new requests on March 31, and stops renewing on Sept 30. The in-place switch to DNS keeps the certificate ARN.

Reality

Evidence70
Adoption
Not scored
Hype gap+5
Incentives55
Confidence62