What it is
Before any page loads, the browser sends a ClientHello to start TLS. Its contents and order differ between browsers and versions, and hashes such as JA3 and JA4 summarise them.
Servers and CDNs can compare the TLS fingerprint with the user agent: a Chrome user agent that opens connections like a script library is a mismatch.
Why it matters
It is read on the network, before cookies or JavaScript, so page-level protections cannot hide it.
Automation tools and old engines often have distinctive TLS fingerprints.
What to do
Use a real browser engine whose TLS matches the claimed browser and version.
Keep the engine version in line with the user agent.
In Clout Browser
Clout Browser profiles run on real Chromium-based engines (SunBrowser, Chroma), pinned per profile, and the fingerprint settings include a TLS feature switch with a cipher blacklist.