Defaults.Exposed › October 2026 census › v10 registry › HTTPS available
HTTPS available
Methodology v10 · canonical ID https-available · TLS (Transport Layer Security) & Certificates · scored
Without it, browsers warn visitors "Not secure" and they leave.
HTTPS available: definition
| Canonical ID | https-available |
|---|---|
| Category | TLS & Certificates |
| Grade impact | Scored, counts toward the grade |
| Pass | The site serves content over HTTPS (Hypertext Transfer Protocol Secure, TLS handshake completes and a response is returned). |
| Fail | The site is reachable over plain HTTP (Hypertext Transfer Protocol) only, or HTTPS connections fail. |
| Example (passing) | https://example.com/ → HTTP 200 over TLS |
HTTPS available across the census
66.2% of graded domains serve over HTTPS (220,264,382 of 332,492,319, as of October 12, 2026).
Aggregates only: never an individual domain's result.
How this check is scored
HTTPS available is one of the 24 scored checks in methodology v10. It carries points toward the grade, and a pass earns them. When the result cannot be determined for a domain (a timeout, a SERVFAIL, a redacted source), the check returns N/A and drops out of that domain's scoring denominator. A result that could not be determined is never counted as a fail; a determined absence is.
In the October 2026 census, every graded domain had a determinable result for this check.
Every outcome in the census
| Outcome | Domains | Share of graded domains | In the headline figure |
|---|---|---|---|
| Serves content over HTTPS | 220,264,382 | 66.2% | Yes |
| No completed HTTPS connection | 112,227,937 | 33.8% | No |
Source: the October 2026 census rollup, deduplicated per domain, as of October 12, 2026.
By top-level domain
This splits the share of graded domains that serve over HTTPS by TLD, with generic and country-code TLDs kept apart. A TLD is named below only when at least 100,000 of its domains are in this check's base.
| Kind | Combined share | Highest | Lowest |
|---|---|---|---|
| Generic TLDs (gTLDs): 353 TLDs, 234,547,634 domains | 63.0% | .cam 82.5%, .bet 78.9%, .blog 78.3% | .bond 9.82%, .skin 14.4%, .garden 19.4% |
| Country-code TLDs (ccTLDs): 167 TLDs, 97,233,639 domains | 74.1% | .ke 95.2%, .rs 94.7%, .ro 94.4% | .gq 0.17%, .cf 0.17%, .tk 0.30% |
The largest TLD in this base, .com, stands at 66.0% (101,602,779 of 153,849,480).
Kind follows the IANA (Internet Assigned Numbers Authority) delegation type: every two-letter TLD is a ccTLD. The per-TLD rollup covers 331,781,273 of the 332,492,319 domains in this base. Grade shares for every TLD are on TLDs compared: the census section.
Against the other checks
Among the 6 TLS & Certificates checks with a published figure, HTTPS available has the 6th highest pass share. Next above it is Certificate valid: 89.2% of HTTPS-serving domains. Across every check with a published figure it ranks 9th of 24 .
Each share is measured on the check's own base, named on its page, so the ranking compares rates across different sets of domains.
Fix it
Plain-English impact, cost of ignoring it, and step-by-step remediation: How to fix HTTPS & forced-secure redirect
Cite this check
Defaults.Exposed, "HTTPS available (https-available)", Grading Methodology v10 (census as of October 12, 2026). https://defaults.exposed/methodology/https-available
Permalink: https://defaults.exposed/methodology/https-available ·
All 33 checks: v10 registry ·
Machine-readable: /methodology/checks.json ·
Licence: open data