tls-reputation.comTLS fingerprint reputation

unrecognised fingerprint

t13d0315h1_55b375c5d22e_b585588df545

Multiple builds

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

TLS 1.3ALPN http/1.12026-07-21 → 2026-07-22
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 · 2 JA3 — 2 JA3s over 137 connections, but most repeat: a handful of stable builds sharing one JA4 rather than per-connection randomisation.
reach
0.000effectively one destination.

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

137
observations
1
domains reached
2026-07-21
first seen
2026-07-22
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)
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(3)
  1. 00x1301TLS_AES_128_GCM_SHA256
  2. 10x1302TLS_AES_256_GCM_SHA384
  3. 20x1303TLS_CHACHA20_POLY1305_SHA256
extensions(15)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. 80x0023session_ticket
  10. 90x0029unknown (0x0029)
  11. 100x002bsupported_versions
  12. 110x002dpsk_key_exchange_modes
  13. 120x0032unknown (0x0032)
  14. 130x0033key_share
  15. 140xff01renegotiation_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(7)
  1. 00x0804rsa_pss_rsae_sha256
  2. 10x0403ecdsa_secp256r1_sha256
  3. 20x0807ed25519
  4. 30x0805rsa_pss_rsae_sha384
  5. 40x0806rsa_pss_rsae_sha512
  6. 50x0503ecdsa_secp384r1_sha384
  7. 60x0603ecdsa_secp521r1_sha512

JA3 variants

2 distinct JA3 hashes collapse into this one JA4.

#JA3JA3_rawobsshare
0771,4865-4866-4867,0-1…41,29-23,010174%
1771,4865-4866-4867,0-1…23-24-25,03626%

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