JA4_R missing for chrome? 0029 #178
Description
my browser ja4_r
002f,0035,009c,009d,1301,1302,1303,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0000,0005,000a,000b,000d,0012,0017,001b,0023,0029,002b,002d,0033,44cd,fe0d,ff01_0403,0804,0401,0503,0805,0501,0806,0601
with curl impersonate
002f,0035,009c,009d,1301,1302,1303,c013,c014,c02b,c02c,c02f,c030,cca8,cca9_0000,0005,000a,000b,000d,0012,0017,001b,0023,002b,002d,0033,44cd,fe0d,ff01_0403,0804,0401,0503,0805,0501,0806,0601
at first my ja4 is t13d1516h2_8daaf6152771_8802cfb92a1f on first browser page load then it changes to
after refreshing the page to
t13d1517h2_8daaf6152771_7e51fdad25f2
Can't this be easily detected? :O
full fingerprint my browser
https://pastebin.com/kAfG6KKE
and curl impersonate
https://pastebin.com/PcKjp6eb
Metadata
Metadata
Assignees
Labels
No labels
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
UnChaotic commentedon Aug 28, 2025
im on windows 11 latest version chrome 139
lexiforest commentedon Aug 28, 2025
JA4 is not very useful, because it's cryptically encoded and does not cover the entire of hello packet. I cannot offer any help for a ja4 mismatch. The likely reason is PSK extension. Feel free to reopen if you can compare the hello packet content, recommended tools are wireshark and tls.peet.ws.