Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Statistics · Statistics

SSL Certificate Usage Statistics (2026)

Short answer

About 90% of websites use HTTPS by default as of November 2026, according to W3Techs. Let's Encrypt is the largest certificate authority, used by 64.4% of all websites. Most encrypted traffic now uses TLS 1.3, while only about 36% of mobile pages send an HSTS header.

Key takeaways

  • About 90% of websites use HTTPS by default as of November 2026, per W3Techs.
  • Let's Encrypt is used by 64.4% of all websites, a 67.4% share of the certificate authority market.
  • Google Trust Services is the main challenger in the HTTP Archive crawl, with its WE1 intermediate on 17.24% of mobile pages.
  • TLS 1.3 carried 72.7% of requests in Cloudflare Radar data for the third quarter of 2026.
  • Only 36% of mobile pages sent an HSTS header in the Web Almanac 2025, despite HTTPS reaching 97.3% of mobile home pages.
  • Let's Encrypt certificates last 90 days as of November 2026, with a 64-day default planned from 10 February 2027.

What percentage of websites use SSL certificates in 2026?

About 90% of websites use HTTPS by default as of November 2026, so an SSL certificate is now the normal state for a public site.

W3Techs puts the share of websites that use HTTPS as their default protocol at 90.0% as of November 2026. That figure counts websites, not visits, so it answers how many sites have made the switch.

The remaining share is about 10% of sites. Those sites are often old, local, or internal systems that never moved to HTTPS.

An SSL certificate is the file that makes HTTPS possible. It proves the site owns its domain name and lets the browser encrypt the connection.

How is HTTPS use measured, and why do the figures differ?

The figures differ because W3Techs counts websites, the HTTP Archive counts home pages and requests, and Google counts pages loaded in Chrome.

Each measure answers a different question. A site count shows how many sites offer HTTPS, while a request count shows how much traffic travels over HTTPS.

The Web Almanac 2025 found 97.3% of mobile home pages served over HTTPS. It also found 98.8% of mobile requests sent over HTTPS, up 0.74% on the 2024 edition.

Google Transparency Report data for the week of 1 November 2026 shows a similar split by device. Pages loaded over HTTPS in Chrome were 99% on Android, 99% on ChromeOS, 98% on Mac, 95% on Windows, and 88% on Linux.

MeasureFigureSourceYear
Websites using HTTPS by default90.0%W3Techs2026
Mobile home pages served over HTTPS97.3%HTTP Archive Web Almanac2025
Mobile requests sent over HTTPS98.8%HTTP Archive Web Almanac2025
Chrome page loads over HTTPS, Android99%Google Transparency Report2026
Chrome page loads over HTTPS, Windows95%Google Transparency Report2026

Do not compare these numbers as if they were the same test. The higher traffic figures show that popular sites moved first, while the 90.0% site figure includes many small and old sites.

Which certificate authority issues the most SSL certificates?

Let's Encrypt issues the most SSL certificates, with 64.4% of all websites and a 67.4% share of the certificate authority market as of November 2026.

W3Techs gives Let's Encrypt that lead in its November 2026 survey. GlobalSign is next, used by 21.1% of all websites for a 22.1% market share.

The rest of the market is much smaller. Sectigo reaches 4.4% of all websites, GoDaddy Group reaches 3.4%, Starfield reaches 2.2%, and DigiCert reaches 1.6%.

Certificate authorityShare of all websitesCA market share
Let's Encrypt64.4%67.4%
GlobalSign21.1%22.1%
Sectigo4.4%4.6%
GoDaddy Group3.4%3.6%
Starfield2.2%2.3%
DigiCert1.6%1.6%

Market share here means the share among sites whose certificate authority W3Techs knows. The “all websites” column is the share of every site in its survey.

The HTTP Archive counts by page instead of by site, and its top issuers look different. Its 2025 chapter lists Let's Encrypt intermediates R11 at 21.86% and R10 at 21.73% of mobile pages, with Google Trust Services intermediate WE1 at 17.24%.

That WE1 figure matters because it shows a second large issuer behind the site-level ranking. Let's Encrypt vs paid SSL explains how the free authority differs from paid options.

How many active certificates does Let's Encrypt have?

Let's Encrypt had about 700 million active certificates in October 2026, covering more than 720 million fully qualified domain names.

Let's Encrypt stats report that active total, which counts live certificates rather than websites. One website can hold several certificates, so this total is far larger than the count of sites.

The authority issues free certificates that last 90 days as of November 2026. Site owners renew them often, usually by an automatic process, instead of buying a new certificate each year.

That short lifetime is set to shrink further. The default drops to 64 days from 10 February 2027, and to 45 days from 16 February 2028, so automatic renewal will matter even more.

If you pay for a certificate, the price and lifetime differ by vendor. How much an SSL certificate costs sets out the paid options beside the free route.

Which TLS version do most websites use?

TLS 1.3 is the leading version, with 72.7% of requests in Cloudflare Radar data for the third quarter of 2026.

Cloudflare Radar puts TLS 1.3 at 72.7% of requests in that quarter. TLS over QUIC, the transport under HTTP/3, accounted for 21.1% in the same data.

The Web Almanac 2025 points the same way. It says TLS 1.2 decreased by another 4.5% this year, while the share of sites using QUIC rose by only 0.8%.

TLS is the current name for the protocol still commonly called SSL. TLS 1.3 is the newest widely used version, and it removed some older methods that had flaws in TLS 1.2.

Your host and CDN settings decide which version a visitor can use. Cloudflare SSL settings for WordPress show the settings that control this on a WordPress site.

How many websites send HSTS headers?

About 36% of mobile pages sent an HSTS header in the Web Almanac 2025, up 6 percentage points from the 2024 edition.

The Web Almanac 2025 reports that 36% figure for mobile pages. HSTS is a response header that tells a browser to visit a domain only over HTTPS, instead of trying plain HTTP first.

That gap is the clearest lag in the data. HTTPS reaches 97.3% of mobile home pages, yet only about a third of mobile pages add the header that locks HTTPS in.

The header settings themselves look sound where they exist. The Almanac says 96% of HSTS responses had a valid max-age, and the median max-age was 1 year, or 365 days.

The 10th percentile max-age rose from 30 days to 91 days. That rise means fewer sites now set very short values that expire too soon to help.

How to add security headers to WordPress covers HSTS beside the other headers a site can send.

What do the numbers mean for a WordPress site?

For a WordPress site, the numbers mean HTTPS is expected, while HSTS and current TLS settings are where most sites still lag.

Browsers now try HTTPS first before falling back to plain HTTP, according to the Web Almanac 2025. They often show a security warning on a site without HTTPS, so a missing certificate stands out to visitors.

A certificate alone does not make a site safe. It encrypts data in transit, but it does not patch plugins, fix weak passwords, or block login attacks.

Is WordPress secure looks at what the vulnerability data shows beyond HTTPS.

WordPress security statistics give the wider numbers for the same question.

Check three things on your own site: the padlock shows on every page, the certificate renews before it expires, and no page loads mixed content over plain HTTP.

How have SSL certificate numbers changed over time?

SSL use has moved from a minority practice to the default, with mobile HTTPS requests rising from 98% in 2024 to 98.8% in 2025 in the Web Almanac.

The Web Almanac 2025 records that rise, up 0.74% on the 2024 edition. Mobile home pages over HTTPS rose from 89% in the earlier comparison to 95.6% in 2024, then to 97.3% in 2025.

Growth is now slow because the ceiling is near. Each extra point is harder to win, since the sites left are often old or rarely maintained.

The issuer mix is still moving, even as total HTTPS growth slows. The Almanac says the share of mobile pages using a Let's Encrypt certificate fell from 56% to 52.6%, while Google Trust Services grew behind its WE1 intermediate.

Shorter certificate lifetimes are the next change to plan for. With defaults falling to 64 days in February 2027, manual renewal will fail more often than it did with year-long certificates.

What mistakes should you avoid?

Most SSL mistakes come from treating the certificate as the whole job, instead of checking renewal, headers, and the rest of the site.

  • Treat a certificate as full security, when it only encrypts data in transit and does not patch code or block attacks.
  • Compare a site share with a traffic share as if they were the same number, when each source counts a different thing.
  • Let a certificate expire because renewal was manual, when the default lifetime is 90 days and will fall to 64 days in February 2027.
  • Skip HSTS because HTTPS already works, when only 36% of mobile pages send the header that locks HTTPS in.
  • Assume a free certificate is weak because it costs nothing, when the issue is the validation level and renewal process, not the price alone.

Frequently asked questions

How many websites have an SSL certificate in 2026?

About 90% of websites use HTTPS by default as of November 2026, according to W3Techs. That is the closest site-level answer to how many sites hold a certificate. Traffic-based counts are higher, at 97.3% of mobile home pages and 98.8% of mobile requests in the Web Almanac 2025.

Is Let's Encrypt the most used certificate authority?

Yes. W3Techs gives Let's Encrypt 64.4% of all websites and a 67.4% share of the certificate authority market as of November 2026. GlobalSign is second at 21.1% of all websites. The HTTP Archive counts by page and puts Let's Encrypt at 52.6% of mobile pages in its 2025 edition.

How long does a Let's Encrypt certificate last?

A Let's Encrypt certificate lasts 90 days as of November 2026. Most sites renew it automatically before it expires. The default lifetime drops to 64 days from 10 February 2027 and to 45 days from 16 February 2028, so automatic renewal becomes more important with each change.

What is the difference between HTTPS share by website and by traffic?

A website share counts sites, while a traffic share counts visits or requests. W3Techs counts websites and reports 90.0% using HTTPS by default. The HTTP Archive counts home pages and requests, at 97.3% and 98.8% on mobile. Popular sites moved to HTTPS first, so traffic figures run higher than site figures.

Does an SSL certificate make a WordPress site fully secure?

No. A certificate encrypts the connection between a visitor and your site, but it does not fix vulnerable plugins, weak passwords, or outdated code. You still need updates, strong login protection, backups, and security headers. HTTPS is a base layer, not a complete security plan.

Sources

  1. Usage statistics of SSL certificate authorities W3Techs
  2. Let's Encrypt usage statistics W3Techs
  3. Security | 2025 | The Web Almanac HTTP Archive
  4. Let's Encrypt Stats Let's Encrypt
  5. HTTPS encryption on the web Google Transparency Report
  6. Adoption and Usage Cloudflare Radar

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test