What is JA3 / JA4 fingerprint?
Also: ja3 · ja4 · tls fingerprint
A JA3 (or newer JA4) fingerprint is a hash of the fields in a TLS ClientHello — the parameters a client offers when starting an encrypted connection. Because VPN clients, proxies, and automation tools assemble these fields differently from mainstream browsers, the fingerprint helps identify what software is really connecting.
Last updated
Two clients claiming to be the same browser will share a JA3/JA4 hash if they truly are; a mismatch between the claimed user-agent and the TLS fingerprint exposes spoofing, VPN wrappers, or scripted clients.
TLS fingerprinting is one signal among many — it complements IP reputation and active probing rather than replacing them.
How does a TLS fingerprint reveal what software connects?
A JA3 or JA4 fingerprint is a hash of the fields a client offers in its TLS ClientHello when it opens an encrypted connection. Different software assembles those fields differently. Two clients that really are the same browser share a hash. A script, a proxy or a VPN wrapper that claims to be that browser usually does not. That mismatch between the claimed user-agent and the fingerprint exposes spoofing and scripted clients. The fingerprint says nothing about the address itself, so it is one signal among many. It complements address-based checks and live handshake checks and does not replace them. A single odd fingerprint should not decide a verdict alone. On a self-check at iplogs.com, the server reads the browser's TLS fingerprint and compares it with the browser its user-agent claims. It returns a verdict of clean, suspicious, vpn_likely or vpn_detected, a score from 0 to 100 and the evidence behind it. Checks are free and need no API key.
How IPLogs handles it
IPLogs hashes the TLS ClientHello (JA3/JA4) and compares it against known VPN-client and automation fingerprints.