NewOne plan from €9.90, extra domains €1, every feature included

Free tool

What's My TLS
Fingerprint?

This is the fingerprint your browser sent when it connected to our edge just now, measured on the real TLS handshake. It is how DDoS protection tells a real browser from a bot pretending to be one.

Your JA4

t13d1011h2_61a7ad8aa9b6_3fcd1a44f3e3

JA3 (MD5)

f9618636c76d569cba2aa0e485815ed1

Your IP address

216.73.217.36

ProtocolTCPt
TLS versionTLS 1.313
Server name (SNI)sent (a domain name)d
Cipher suites offered1010
Extensions offered1111
First ALPN protocolHTTP/2h2
Cipher suites hashsorted list, SHA-256, first 12 hex61a7ad8aa9b6
Extensions + signature algorithms hashsorted extensions and signature algorithms, SHA-256, first 12 hex3fcd1a44f3e3

User-Agent your browser claims

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

Nothing is stored. Reload in another browser to compare.

Why it matters

A bot can lie in its headers. Its handshake is harder to fake.

01

Same browser, same fingerprint

Every copy of a browser version sends the same handshake, so the fingerprint names the software, not the person using it.

02

Mismatch is the giveaway

A request that claims to be Chrome in its User-Agent but sends a Python or Go handshake is almost certainly automated.

03

Floods share a fingerprint

A botnet can use thousands of addresses but usually one tool. Counting requests per fingerprint finds it even when no single address stands out.

04

Why JA4 beats JA3 here

In one attack on our edge, 12,664 handshakes produced 10,789 different JA3 hashes and only 11 JA4s: the tool shuffled its extension order, and JA4 sorts it away.

FAQ

About TLS
Fingerprints.

What is a TLS fingerprint?+

When your browser opens an HTTPS connection it sends a ClientHello message listing the TLS versions, cipher suites, extensions and other options it supports. Different software sends different combinations, so a summary of that message identifies the client type, for example Chrome, Firefox, curl or a Python script, without looking at cookies or the User-Agent.

What is the difference between JA3 and JA4?+

JA3 (2017) is an MD5 hash of the ClientHello fields in the order they were sent. JA4 (2023) sorts the cipher suites and extensions before hashing and adds a readable prefix with the TLS version, counts and ALPN. Because of the sorting, a client that shuffles its extension order gets a new JA3 on every connection but keeps the same JA4.

Is my TLS fingerprint unique to me?+

No. It identifies your browser and version, not you. Everyone running the same version of Chrome on the same platform sends the same fingerprint, so it is not a tracking identifier the way a cookie is.

How does DDoS protection use TLS fingerprints?+

Attack tools usually do not run a full browser, so their ClientHello looks different from the User-Agent they claim. A request that says it is Chrome but sends a Python or Go fingerprint is a strong bot signal. During an attack, the edge can also count requests per fingerprint and slow down or ban a fingerprint that floods the site, even when the requests come from thousands of addresses.

Can attackers fake their fingerprint?+

Partly. Libraries such as uTLS can imitate a browser's ClientHello or randomise it. Randomising the order defeats JA3 but not JA4, which is why we fingerprint with both; imitating a browser exactly is harder to sustain at flood rates and still has to pass the browser check.

Fingerprints Every
Request. Automatically.

Akarguard checks the handshake, the browser and the request pattern of every visitor before it reaches your server. €9.90 a month, 7 days free.