Security Experts:

Connect with us

Hi, what are you looking for?


Security Infrastructure

Let’s Encrypt Begins Retirement of TLS-SNI-01 Validation

Free and open Certificate Authority (CA) Let’s Encrypt today started the process of completely retiring TLS-SNI-01 validation support. 

Free and open Certificate Authority (CA) Let’s Encrypt today started the process of completely retiring TLS-SNI-01 validation support. 

Let’s Encrypt decided last year that it would disable support for the TLS-SNI-01 validation after learning that users could abuse it to obtain certificates for domains they do not own. The problem, the CA revealed at the time, was the use of the ACME TLS-SNI-01 challenge type for domains on a shared hosting infrastructure.

Although the issue wasn’t related to the certificate authority itself, but instead the result of a combination of factors, Let’s Encrypt decided that disabling support for the validation method was the best way to handle the situation at the time. 

In October last year, however, the CA announced that it was ready to take its mitigation efforts to the next step by completely removing support for TLS-SNI-01 validation on February 13, 2019.

Starting today, the CA is disabling the TLS-SNI-01 method in staging, allowing users to test the change and check whether the TLS-SNI-01 retirement will affect them in any way. 

“To help people test their clients ahead of the deprecation date, we’re going to disable the TLS-SNI-01 method in staging on 2019-01-22 (this Tuesday). Once that’s live we’ll post an update here, and you’ll be able to run certbot renew –dry-run, which will do a test against staging. If the dry run succeeds, you’ll know that you’re ready for the deprecation date,” Let’s Encrypt’s Jacob Hoffman-Andrews notes

Certbot users have already received emails informing them on the planned retirement of the TLS-SNI-01 validation. Details on how to stop using the domain validation method have been published on Let’s Encrypt’s community page. 

Let’s Encrypt users currently have three other validation methods at their disposal, namely “DNS-01”, “HTTP-01” (which has been available alongside TLS-SNI-01 right from the start), and “TLS-ALPN-01” (which was introduced last year).

Related: Let’s Encrypt Now Trusted by All Major Root Programs

Related: Let’s Encrypt Disables TLS-SNI-01 Validation

Written By

Ionut Arghire is an international correspondent for SecurityWeek.

Click to comment

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Join this webinar to learn best practices that organizations can use to improve both their resilience to new threats and their response times to incidents.


Join this live webinar as we explore the potential security threats that can arise when third parties are granted access to a sensitive data or systems.


Expert Insights

Related Content

Security Infrastructure

Comcast jumps into the enterprise cybersecurity business, betting that its internal security tools and inventions can find traction in an expanding marketplace.


Identity and access governance vendor Saviynt has closed a $205 million financing round.

Security Infrastructure

XDR's fully loaded value to threat detection, investigation and response will only be realized when it is viewed as an architecture


Security orchestration, automation and response (SOAR) provider Swimlane on Monday announced the launch of a security automation solution ecosystem for operational technology (OT) environments.

Incident Response

Created and maintained by MITRE, MITRE D3FEND is a framework that provides a library of defensive cybersecurity countermeasures and technical components to help organizations...

Cloud Security

The term ‘zero trust’ is now used so much and so widely that it has almost lost its meaning.