SSL Certificate Guide 2026: Types, Validation & Selection

SSL Certificate Guide 2026
A TLS (still commonly called SSL) certificate binds a public key to a domain and is the foundation of HTTPS. Certificates come in validation levels DV, OV, and EV, and in coverage types single-domain, wildcard, and multi-domain (SAN). SC-081v3 (passed 2025) is phasing the maximum public-certificate validity from 398 days down to 200 days (from 2026-03-15), 100 days (from 2027-03-15), and finally 47 days (from 2029-03-15) — making automated renewal essential.
How certificates work
A TLS certificate is a signed statement binding a public key to a domain. When a client connects, the server presents the certificate, the client verifies the signature against a trusted root, and the two sides negotiate a session key. A certificate never travels with the private key — the key stays on the server.
Validation levels: DV, OV, EV
Domain Validation proves only that you control the domain; issuance takes minutes and is free through Let's Encrypt. Organization Validation additionally verifies the legal entity and shows its name in the certificate. Extended Validation performs the deepest checks and used to show a green address bar; browsers have since standardized the UI, so EV now mainly signals organizational trust.
Coverage: single, wildcard, multi-domain
A single-domain certificate covers one name. A wildcard like *.example.com covers the domain and all its subdomains. A multi-domain (SAN) certificate lists several distinct domains, good for consolidating example.com, example.org and a mobile API under one cert.
Validity is shrinking fast
SC-081v3 is now in force: new certs max out at 200 days from 2026-03-15, 100 days from 2027-03-15, and 47 days from 2029-03-15 (CA/B Forum SC-081v3, 2025). Let's Encrypt has defaulted to 90 days since 2015 and plans to shorten further by 2028. Shorter lifetimes shrink the damage window of a key leak and make automated renewal the norm.
Step 1: Pick a validation level
Start with free DV for personal sites or automation; upgrade to a commercial CA's OV or EV when payments, business, or compliance require verified identity.
Step 2: Choose coverage
Use a single-domain cert for one site; a wildcard *.example.com for many subdomains; a multi-domain (SAN) cert for several distinct domains.
Step 3: Request and automate renewal
Generate a CSR with the CSR Generator, submit it to your CA, complete validation, then install the certificate with its intermediate chain. Use an ACME client such as certbot or caddy to automate renewal against the ever-shorter 200→100→47-day validity.
Step 4: Verify after install
After installation, confirm the chain, hostname coverage, and expiry with the SSL Checker, and run a full chain audit with the Certificate Decoder.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Browser says certificate not trusted | Missing intermediate or wrong chain order | Install the full chain (leaf + intermediates) in the correct order |
| Certificate name mismatch | Domain not in CN/SAN | Issue for the exact hostname or add it as a SAN; use a wildcard for many subdomains |
| Certificate expired unexpectedly | Forgotten manual renewal | Automate renewal with an ACME client |
| EV shows no green bar | Browsers unified the UI | Expected behavior; EV now signals organizational identity |
| Frequent renewals strain ops | SC-081v3 shorter validity | Automate end-to-end and monitor renewal success |
| Missing domain in multi-domain cert | Incomplete SAN list | Regenerate a CSR with all names and re-issue |
Next steps
- Generate the CSR you need with the CSR Generator.
- Verify the installation with the SSL Checker.
- Audit the full chain with the Certificate Decoder.
- Browse the SSL certificate guide for types, brands and comparisons.
- Related: How to Generate a CSR, RSA vs ECDSA, SSL Security Best Practices.
FAQ
Are free certificates as secure as paid ones?
Yes. DV, OV and EV certificates use the same TLS encryption. The difference is identity verification, not cryptographic strength.
What happens when a certificate expires?
Browsers refuse the connection and visitors see a security warning. Automate renewals with an ACME client to avoid the risk entirely.
Do I need a certificate for each subdomain?
No. Use a wildcard certificate (`*.example.com`) or a multi-domain certificate listing each name.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.