Sovra Recon·Glossary · TLS Certificate

SSL/TLS Certificates: Definition, How They Work, and Common Errors

By Solan Barlet, co-founder of Sovra Recon
Updated October 29, 2026

In short

An SSL/TLS certificate is an electronic file, signed by a certificate authority, that associates a domain name with a public key. It allows the browser to verify that it is communicating with the correct website and to encrypt data exchanges: this is the padlock symbol in HTTPS. The term “SSL” is historical, as these protocols have been superseded by TLS 1.2 and 1.3. As of March 15, 2026, a public certificate cannot be valid for more than 200 days, a period that is set to decrease to 47 days in 2029.

Types of Certificates

TypeWhat is verified
DV (Domain Validation)Domain name validation only; issued automatically, for example by Let’s Encrypt
OV (Organization Validation)The domain and the organization’s existence
EV (Extended Validation)A thorough verification of the organization

All three offer the same encryption; the difference lies in the verified identity, not in technical robustness.

A shorter validity period

Issued CertificatesMaximum duration
Before March 15, 2026398 days
From March 15, 2026, to March 14, 2027200 days
From March 15, 2027, to March 14, 2029100 days
Starting March 15, 202947 days

This timeline, adopted in April 2025 by the CA/Browser Forum—which sets the rules for certificate authorities—makes automatic renewal (ACME protocol) virtually indispensable.

The Most Common Errors

  • Expired certificate: The browser displays a blocking warning, and the site effectively becomes inaccessible.
  • Mismatched name: The certificate does not cover the subdomain being used.
  • Incomplete certificate chain: some browsers or applications will refuse the connection.
  • Obsolete protocols still accepted: SSL 3.0, TLS 1.0, and TLS 1.1 are officially deprecated.
  • HTTPS is not enforced: without a redirect or an HSTS header, an initial connection may occur in plain text.

Also note: public certificates are recorded in logs that are accessible to everyone (Certificate Transparency). Your subdomains appear there, including those in test environments.

Frequently asked questions

Is an HTTPS site necessarily secure?

No. The certificate guarantees that the connection is encrypted and that the domain is indeed the one displayed, not that the site is trustworthy or free of vulnerabilities: phishing sites also have valid certificates.

Sources

Find out where an attacker would get in.

Our AI agents actually attack your scope, fully automated, and hand you the proof of every vulnerability.