As the Chrome 126 has officially arrived, I started comparing the fingerprints of it and the current default chrome profile. I've got two colleagues with windows machines to send me the output of the tls.peet.ws/api/all request (results bellow). I notice that the ciphers were out of order. I have not gotten deeper into the rest of it but I'll be looking at it one of these days.
fingerprints
Output of tls.browserleaks.com/json of the real browser:
Info
As the Chrome 126 has officially arrived, I started comparing the fingerprints of it and the current default chrome profile. I've got two colleagues with windows machines to send me the output of the tls.peet.ws/api/all request (results bellow). I notice that the ciphers were out of order. I have not gotten deeper into the rest of it but I'll be looking at it one of these days.
fingerprints
Output of tls.browserleaks.com/json of the real browser:
With this proposed fix, now the normalised ja3 (ja3n) matches;
tls peet api results