tls-reputation.comTLS fingerprint reputation

unrecognised fingerprint

t13d1011h1_61a7ad8aa9b6_3a8073edd8ef

Randomising client

Reshuffles its own ClientHello per connection — browser-shaped behaviour, but no catalogue build has reproduced this exact hello.

TLS 1.3ALPN http/1.12026-07-19 → 2026-07-23
JA4
JA4_r
JA3
permutes its ClientHello, so every connection emits a fresh JA3 — none represents it.
JA3_raw

explore in graph →

Read

catalog identity
No ground-truth build has reproduced this hello yet — absence is not a verdict.
self-randomisation
randomising · 93 JA3 — 100% of connections presented a JA3 never seen before for this client — it reshuffles its own ClientHello. Chrome has permuted extension order since version 110.
real-browser tell
Browser-shaped cipher list but no post-quantum key share — the tell that separates curl-impersonate / uTLS from a real Chrome.
reach
0.890 roams across 5 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

93
observations
5
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)
http/1.1
EC point formats
0x0000
Post-quantum key share
absent

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(10)
  1. 00x1302TLS_AES_256_GCM_SHA384
  2. 10x1301TLS_AES_128_GCM_SHA256
  3. 20x1303TLS_CHACHA20_POLY1305_SHA256
  4. 30xc02cTLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
  5. 40xc02bTLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  6. 50xcca9TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
  7. 60xc030TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  8. 70xc02fTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  9. 80xcca8TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
  10. 90x00ffTLS_EMPTY_RENEGOTIATION_INFO
extensions(11)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. 60x0017extended_master_secret
  8. 70x0023session_ticket
  9. 80x002bsupported_versions
  10. 90x002dpsk_key_exchange_modes
  11. 100x0033key_share

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

curves / groups(3)
  1. 00x001dx25519
  2. 10x0017secp256r1 (P-256)
  3. 20x0018secp384r1 (P-384)
signature algorithms(13)
  1. 00x0201rsa_pkcs1_sha1
  2. 10x0203ecdsa_sha1
  3. 20x0401rsa_pkcs1_sha256
  4. 30x0403ecdsa_secp256r1_sha256
  5. 40x0501rsa_pkcs1_sha384
  6. 50x0503ecdsa_secp384r1_sha384
  7. 60x0601rsa_pkcs1_sha512
  8. 70x0603ecdsa_secp521r1_sha512
  9. 80x0804rsa_pss_rsae_sha256
  10. 90x0805rsa_pss_rsae_sha384
  11. 100x0806rsa_pss_rsae_sha512
  12. 110x0807ed25519
  13. 120x0808ed448

JA3 variants

93 distinct JA3 hashes collapse into this one JA4.

#JA3JA3_rawobsshare
0771,4866-4865-4867-491…29-23-24,011.1%
1771,4866-4865-4867-491…29-23-24,011.1%
2771,4866-4865-4867-491…29-23-24,011.1%
3771,4866-4865-4867-491…29-23-24,011.1%
4771,4866-4865-4867-491…29-23-24,011.1%
5771,4866-4865-4867-491…29-23-24,011.1%
6771,4866-4865-4867-491…29-23-24,011.1%
7771,4866-4865-4867-491…29-23-24,011.1%
8771,4866-4865-4867-491…29-23-24,011.1%
9771,4866-4865-4867-491…29-23-24,011.1%
10771,4866-4865-4867-491…29-23-24,011.1%
11771,4866-4865-4867-491…29-23-24,011.1%
12771,4866-4865-4867-491…29-23-24,011.1%
13771,4866-4865-4867-491…29-23-24,011.1%
14771,4866-4865-4867-491…29-23-24,011.1%
15771,4866-4865-4867-491…29-23-24,011.1%
16771,4866-4865-4867-491…29-23-24,011.1%
17771,4866-4865-4867-491…29-23-24,011.1%
18771,4866-4865-4867-491…29-23-24,011.1%
19771,4866-4865-4867-491…29-23-24,011.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. Showing the busiest 20.

Reach — domains contacted

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