ChatGPT-User

The wire fingerprints traffic claiming to be this fetcher presented, split by whether a channel the operator publishes for verification — its IP ranges or forward-confirmed reverse DNS — confirmed the claim.

Claims in window

Same adjudication as the stats page: a claim confirmed by either channel the operator publishes — its IP ranges or forward-confirmed reverse DNS — is legit; one confirmed by neither is spoofed. Operators differ in which channels they offer, and either alone fully identifies. Sources count distinct clients, not traffic. Fingerprint windows below are day-granular, like sources.

observationssourceslegitspoofedspoof rate
22200.0%

Fingerprints presented by confirmed traffic

The highest-volume fingerprints the operator's own traffic runs, per signal — claims confirmed via operator-published channels. A Match pill marks an exact match against a controlled capture — an association with known stacks, not an identity verdict: unrelated clients built on the same stack can legitimately share a fingerprint.

TLS ClientHello (JA4)

fingerprintobservations
t13d1712h2_5b57614c22b0_ef7df7f74e48 1
t13d1713h2_5b57614c22b0_02c8e53ee398 1

HTTP request (JA4H)

fingerprintobservations
ge20nn06enus_32386ca2063f_000000000000_000000000000 2

HTTP/2 frames (Akamai)

fingerprintobservations
2:0;1:4096;8:0;3:1024;4:1048576|25100289|0|a,p,m,s 2

TCP SYN (JA4T)

fingerprintobservations
64240_2-4-8-1-3_1418_9 2

TCP SYN (p0f)

fingerprintobservations
4:47+17:0:1418:mss*44,9:mss,sok,ts,nop,ws:df,id+:0 1
4:49+15:0:1418:mss*44,9:mss,sok,ts,nop,ws:df,id+:0 1