Which TLS versions does this server still accept?

example-company.com accepted TLS 1.3 and chose TLS_AES_256_GCM_SHA384. That is the suite a normal client actually gets, because this handshake ran on Node's default cipher list rather than a weakened one. 1.3 is the current version — it drops the older key exchanges outright and completes in fewer round trips, so it is both the safest and the fastest option a visitor can be given.

example-company.com accepted TLS 1.2 and chose ECDHE-ECDSA-AES128-GCM-SHA256. That is the suite a normal client actually gets, because this handshake ran on Node's default cipher list rather than a weakened one. 1.2 is not deprecated and remains entirely acceptable; a large share of the web runs on it, and some clients still cannot do better.

example-company.com accepted a connection using TLS 1.1, a version deprecated by RFC 8996. Nothing is broken and no visitor is affected — current browsers refuse these versions themselves, so this costs you no traffic. It is a hardening gap rather than an outage: it widens the set of clients that can negotiate a weak connection, and it is the finding an auditor writes up, since RFC 8996 deprecates both and PCI DSS has required TLS 1.0 be disabled since 2018. Where the site sits behind a CDN this is usually one setting rather than server work — Cloudflare, for instance, defaults to a Minimum TLS Version of 1.0, and raising that to 1.2 is the whole change. No cipher is reported for this handshake: offering TLS 1.1 at all requires deliberately weakening the client here, which changes what gets negotiated, so the suite would say more about this tool than about your server. What is reported is the thing that matters — the version was accepted.

example-company.com accepted a connection using TLS 1.0, a version deprecated by RFC 8996. Nothing is broken and no visitor is affected — current browsers refuse these versions themselves, so this costs you no traffic. It is a hardening gap rather than an outage: it widens the set of clients that can negotiate a weak connection, and it is the finding an auditor writes up, since RFC 8996 deprecates both and PCI DSS has required TLS 1.0 be disabled since 2018. Where the site sits behind a CDN this is usually one setting rather than server work — Cloudflare, for instance, defaults to a Minimum TLS Version of 1.0, and raising that to 1.2 is the whole change. No cipher is reported for this handshake: offering TLS 1.0 at all requires deliberately weakening the client here, which changes what gets negotiated, so the suite would say more about this tool than about your server. What is reported is the thing that matters — the version was accepted.