tls-reputation.comTLS fingerprint reputation

unrecognised fingerprint

t13d1312h2_f57a46bbacb6_ab7e3b40a677

Multiple builds

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

TLS 1.3ALPN h2 · 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 5340 connections, but most repeat: a handful of stable builds sharing one JA4 rather than per-connection randomisation.
reach
0.401 roams across 55 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

5,340
observations
55
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
TLS 1.3
ALPN (wire order)
h2, http/1.1
EC point formats
0x0000
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(13)
  1. 00xc02bTLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  2. 10xc02fTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  3. 20xc02cTLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
  4. 30xc030TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  5. 40xcca9TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
  6. 50xcca8TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
  7. 60xc009TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  8. 70xc013TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  9. 80xc00aTLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  10. 90xc014TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  11. 100x1301TLS_AES_128_GCM_SHA256
  12. 110x1302TLS_AES_256_GCM_SHA384
  13. 120x1303TLS_CHACHA20_POLY1305_SHA256
extensions(12)sorted
  1. 00x0000server_name (SNI)
  2. 10x0005status_request (OCSP)
  3. 20x000asupported_groups
  4. 30x000bec_point_formats
  5. 40x000dsignature_algorithms
  6. 50x0010application_layer_protocol_negotiation (ALPN)
  7. 60x0012signed_certificate_timestamp
  8. 70x0017extended_master_secret
  9. 80x002bsupported_versions
  10. 90x0032unknown (0x0032)
  11. 100x0033key_share
  12. 110xff01renegotiation_info

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

curves / groups(5)
  1. 00x11ecX25519MLKEM768 PQ
  2. 10x001dx25519
  3. 20x0017secp256r1 (P-256)
  4. 30x0018secp384r1 (P-384)
  5. 40x0019secp521r1 (P-521)
signature algorithms(10)
  1. 00x0804rsa_pss_rsae_sha256
  2. 10x0403ecdsa_secp256r1_sha256
  3. 20x0807ed25519
  4. 30x0805rsa_pss_rsae_sha384
  5. 40x0806rsa_pss_rsae_sha512
  6. 50x0401rsa_pkcs1_sha256
  7. 60x0501rsa_pkcs1_sha384
  8. 70x0601rsa_pkcs1_sha512
  9. 80x0503ecdsa_secp384r1_sha384
  10. 90x0603ecdsa_secp521r1_sha512

JA3 variants

3 distinct JA3 hashes collapse into this one JA4.

#JA3JA3_rawobsshare
0771,49195-49199-49196-…23-24-25,04,89392%
1771,49195-49199-49196-…23-24-25,04278.0%
2771,52393-52392-49195-…23-24-25,0200.4%

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 15 of 55. Share is the fraction of this fingerprint’s observations reaching each name.