Launch prices end 31 Dec. Subscribe before then and keep yours · Lock my price

What is a TLS fingerprint (JA3/JA4)?

A TLS fingerprint identifies the software making a connection from how it opens a secure connection: its TLS version, cipher suites, extensions and their order.

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.

FAQ

Questions, answered.

Something else? Ask us on Telegram. We answer fast and we don’t bite.

Can a proxy change my TLS fingerprint?
An ordinary HTTP or SOCKS proxy passes TLS through unchanged; the fingerprint comes from the browser.
Why does the engine version matter?
TLS behaviour changes between browser versions, so it should match the version the user agent claims.

Run every account in its own browser.

Download free, import your profiles in minutes and pay $9 a month for 100 of them. Every plan is free for 3 days.

  • 100 profiles for $9 a month
  • Imports AdsPower, Multilogin, Dolphin, GoLogin, Kameleo
  • Mac, Windows and Linux
Get my fleet planDownload freeOne profile free forever. No credit card for the download.

Your accounts deserve a better browser.

One profile free for as long as you like. Every plan free for 3 days. Cancel any time.