Neither TLS 1.2 nor TLS 1.3 is supported

HighConfirmedtls.protocols.no-tls12

What this check looks for

The server offers only versions of TLS that browsers have already removed. Most visitors cannot connect at all.

Why it matters

Every current browser refuses TLS 1.0 and 1.1. If neither modern version is available, the site is effectively offline for anyone not running a years-old client.

When the check passes, your report says: “The server supports TLS 1.2 or better”.

What it costs your score

When this check fails it removes 40 points from your TLS score, before the status, confidence and repeat multipliers are applied. TLS carries a weight of 15 in the overall score.

It shares the tls.protocols family ceiling of 40 points: however many findings that family produces, together they cannot remove more than that from TLS. One underlying problem showing up in several places is still one problem.

Severity: high
Default confidence: confirmed
Status when triggered: fail
Deduction: 40 points
Family cap: tls.protocols · 40
Category: TLS
Module: Tls protocols
Fix owned by: user
In the ruleset since: 2026.09

How the whole score is calculated

How to fix it

Enable TLS 1.2 and TLS 1.3.

Without one of them the site does not load in any current browser.

Update the TLS library if it predates OpenSSL 1.0.1.
Set the protocol list to TLS 1.2 and 1.3 and reload.

How to confirm it worked

openssl s_client -connect ‹host›:443 -servername ‹host› -tls1_2 </dev/null 2>&1 | grep Protocol

A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.

Remediation by platform

nginx

ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers off;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;

Apache

SSLProtocol             -all +TLSv1.2 +TLSv1.3
SSLHonorCipherOrder     off
SSLCipherSuite          ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305

Caddy

‹host› {
	tls {
		protocols tls1.2 tls1.3
	}
}

Cloudflare

SSL/TLS → Edge Certificates → Minimum TLS Version → TLS 1.2.

Put this in the http block so it applies to every server block; a per-server ssl_protocols directive silently overrides it for that server only.
Set it in the main configuration, not in .htaccess — SSLProtocol is a server-context directive and .htaccess cannot change it.
Caddy already defaults to TLS 1.2 and 1.3; an explicit block is only needed to pin them.
This setting governs the connection between visitors and Cloudflare's edge only. It does not change what the origin server negotiates, and an origin that is reachable directly — by IP, or through any DNS record that is not proxied — still accepts what it accepted before. This scan measured the origin, so apply the server-side configuration as well.

Technical detail

No handshake succeeded at TLS 1.2 or TLS 1.3 against ‹host›. Chrome, Firefox, Safari and Edge all removed TLS 1.0/1.1 in 2020. The usual cause is an OpenSSL version predating 1.0.1, or a configuration that pins an obsolete protocol list.