HTTPS Adoption and TLS Deployment Report 2026

Websites using HTTPS by default (%)
source: W3Techs site elements survey, historical yearly trend (W3Techs, 2026-11-02)
HTTPS-by-default share by site popularity (%)
source: W3Techs, default protocol https by ranking (2026-10)
TLS version share of encrypted requests (%)
source: Cloudflare Radar (2026-08)
HTTPS is now the web's default state: as of October 2026, 90.0% of all websites use HTTPS by default (W3Techs, 2026-11-02), and 95-99% of pages loaded in Chrome travel over HTTPS (Google Transparency Report, 2026-10). TLS (still commonly called SSL) 1.3 carries roughly 73% of encrypted requests (Cloudflare Radar, 2026-08), while TLS 1.0 and 1.1 have dropped to effectively zero. Unencrypted sites are no longer the norm — they are the exception. This report consolidates the authoritative public data, maps the remaining gap, and lists what site owners should do now.
Data sources and methodology
This report uses only publicly verifiable sources: W3Techs' site-element sampling (counted by website), Google Transparency Report's Chrome page-load telemetry (counted by traffic), and Cloudflare Radar's TLS-version request distribution (counted by request). The three metrics answer different questions — how many sites enable HTTPS, how much traffic is encrypted, which protocol version carries each request — so the numbers are not directly comparable; every figure in this report cites its source and measurement date. Throughout, TLS refers to the transport-layer encryption protocol.
HTTPS adoption: 90.0% overall, higher at the top
Counted by website, 90.0% of all sites worldwide used HTTPS by default in October 2026 (W3Techs, 2026-11-02). Counted by traffic, 95-99% of Chrome page loads on Windows, Mac and Android are HTTPS, with Linux at roughly 88% (Google Transparency Report, 2026-10). Adoption stratifies with site popularity: the top 1,000 sites reach 96.4%, and the top 1 million reach 93.7% (W3Techs, 2026-11-02). The tipping point came between 2018 and 2021 — default-HTTPS share jumped from 26.9% in 2018 to 68.8% in 2021, hit 84.9% in 2024, and has been climbing slowly ever since (W3Techs historical data).
TLS version migration: 1.3 leads, 1.0/1.1 gone
Among encrypted requests on the Cloudflare network, TLS 1.3 accounts for about 73%, QUIC (the transport under HTTP/3) for about 20.5%, and most of the rest is TLS 1.2 (Cloudflare Radar, 2026-08). TLS 1.0 and 1.1 were disabled by all major browsers at the end of 2020; public traffic on them is effectively zero, limited to legacy embedded devices. TLS 1.2 remains the compatibility floor: a 1.3-only server will refuse some enterprise and older clients.
HSTS: 35.9% of websites
HSTS (HTTP Strict Transport Security) forces browsers to use HTTPS on every subsequent visit, preventing downgrade attacks. As of October 2026, 35.9% of websites deploy HSTS (W3Techs, 2026-11-02) — up from 0.4% in 2015 — though uptake among small sites is still uneven. HSTS preload-list membership remains the most reliable hardening signal.
Where the remaining gap lives
The roughly 10% of sites that still do not default to HTTPS skew heavily toward low-traffic personal sites, legacy government and education portals, and some embedded devices. For site owners the gap is not only a security issue — browsers label plain HTTP as "Not secure," which deters visitors, and HTTP resources referenced from HTTPS pages trigger mixed-content blocking.
Step 1: Audit your current HTTPS configuration
Run your domain through the SSL Checker to confirm the certificate is valid, TLS 1.2/1.3 are enabled, and no mixed-content warnings appear. If the certificate has already expired, follow the emergency renewal playbook first.
Step 2: Verify protocol versions and the certificate chain
Use the SSL Tracer to inspect the negotiated TLS version and the full certificate chain, confirming that 1.0/1.1 are disabled, 1.3 is on, and no intermediate certificate is missing.
Step 3: Serve HTTPS-only and enable HSTS
First 301-redirect all HTTP traffic to HTTPS, then add the header Strict-Transport-Security: max-age=31536000; includeSubDomains and consider HSTS preloading once stable. Afterwards, re-check the certificate subject and SANs with the Certificate Decoder to make sure every subdomain is covered.
Troubleshooting checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| Browser shows "Not secure" | Site still answers over HTTP, or certificate expired | Locate with the SSL Checker; renew immediately if expired |
| Some legacy clients cannot connect | Server enables TLS 1.3 only | Enable both TLS 1.2 and 1.3; disable anything older |
| Mixed-content blocking | HTTPS page references HTTP resources | Switch resources to HTTPS or protocol-relative URLs, then re-test |
| Cannot fall back to HTTP after enabling HSTS | Browser enforcing HTTPS — expected | Fix HTTPS properly, then clear the browser's HSTS cache |
| Certificate warning on a subdomain | Wildcard does not cover it, or SAN is missing | Inspect SANs with the Certificate Decoder and reissue if needed |
| Some users see an untrusted-certificate error | Incomplete chain, missing intermediate | Verify chain completeness with the SSL Tracer and add the missing intermediate |
Take Action
Run a 30-second HTTPS health check with the SSL Checker, or learn TLS deployment from the ground up in the SSL certificate guide.
Related reading: Let's Encrypt Market Share and Chain of Trust Report 2026, HTTP/3 and QUIC Adoption Report 2026, TLS 1.2 Deprecation 2026: Status and Upgrade Path.
FAQ
Is HTTPS adoption measured by domains or traffic?
Both metrics exist: W3Techs counts by website (90.0%, 2026-10), while Google Transparency Report and Cloudflare Radar count by traffic or requests (above 95%). Traffic-weighted numbers give more weight to large sites, but both datasets agree that HTTPS is the overwhelming mainstream.
Do I still need to support TLS 1.2?
Yes. TLS 1.2 remains the compatibility floor — a 1.3-only server breaks some enterprise and embedded clients. Enable both 1.2 and 1.3, and disable 1.0/1.1.
Should a small site enable HSTS?
Yes. HSTS costs one response header and removes downgrade and hijacking risks. Start with a short max-age (such as 300 seconds), confirm every page is served over HTTPS, then extend the duration and consider preloading.
Is anyone still using TLS 1.0 or 1.1?
Major browsers and operating systems disabled both versions at the end of 2020. Public usage is effectively zero, limited to legacy embedded systems. Unless you must serve specific old devices, there is no reason to keep them.
Free SSL/TLS tools
Verify and inspect your certificates in seconds.
Related Certificate Info
Learn more about choosing and buying certificates.