tls-reputation.comTLS fingerprint reputation

unrecognised fingerprint

t00d0310h2_55b375c5d22e_50cc996d9024

Multiple builds

A few stable builds share this JA4 — not per-connection randomisation, and not yet a named client.

unknownALPN h2 · h2-fb · http/1.12026-07-19 → 2026-07-23
JA4
JA4_r
JA3
several builds share this JA4 under different JA3s — no single value is canonical.
JA3_raw
—

explore in graph →

Read

catalog identity
No ground-truth build has reproduced this hello yet — absence is not a verdict.
self-randomisation
multi-build · 3 JA3 — 3 JA3s over 33 connections, but most repeat: a handful of stable builds sharing one JA4 rather than per-connection randomisation.
reach
0.776 roams across 7 domains — spread is how evenly, not how many.

Spread measures reach, not intent: it can’t tell one scraper visiting 500 domains from 500 people visiting one each. Stability is a claim about software — whether the stack is deterministic — nothing about who runs it.

Footprint

33
observations
7
domains reached
2026-07-19
first seen
2026-07-23
last seen

ClientHello anatomy

The underscore groups of JA4_r are the raw cipher suites · extensions · signature algorithms behind the hash.

TLS version
unknown
ALPN (wire order)
h2, h2-fb, http/1.1
EC point formats
—
Post-quantum key share
present (X25519MLKEM768)

The post-quantum key share is a structural fact about the hello, not a verdict — GREASE values are flagged the same neutral way.

cipher suites(3)
  1. 00x1301TLS_AES_128_GCM_SHA256
  2. 10x1302TLS_AES_256_GCM_SHA384
  3. 20x1303TLS_CHACHA20_POLY1305_SHA256
extensions(10)sorted
  1. 00x0000server_name (SNI)
  2. 10x000asupported_groups
  3. 20x000dsignature_algorithms
  4. 30x0010application_layer_protocol_negotiation (ALPN)
  5. 40x001bcompress_certificate
  6. 50x0029unknown (0x0029)
  7. 60x002bsupported_versions
  8. 70x002dpsk_key_exchange_modes
  9. 80x0033key_share
  10. 90xff04unknown (0xff04)

Stored sorted — under one JA4 the wire order varies by construction, so no single order is “the” order.

curves / groups(3)
  1. 00x11ecX25519MLKEM768 PQ
  2. 10x001dx25519
  3. 20x0017secp256r1 (P-256)
signature algorithms(4)
  1. 00x0403ecdsa_secp256r1_sha256
  2. 10x0503ecdsa_secp384r1_sha384
  3. 20x0603ecdsa_secp521r1_sha512
  4. 30x0804rsa_pss_rsae_sha256

JA3 variants

3 distinct JA3 hashes collapse into this one JA4.

#JA3JA3_rawobsshare
0771,4865-4866-4867,0-4…588-29-23,2370%
1771,4865-4866-4867,43-…-41,29-23,721%
2771,4865-4866-4867,0-4…-41,29-23,39.1%

JA3 hashes preserve wire order, so a permuting client mints a new one per connection; JA4 sorts the same set, which is why they share one JA4. Every hash here belongs to this fingerprint — there is no per-JA3 page.

Reach — domains contacted

Top 7 of 7. Share is the fraction of this fingerprint’s observations reaching each name.