-
**Which version are you referring to**
3.2rc2 (default 3.1dev branch)
**Describe your feature request (if it's a technical feature)**
In the **Running client simulations via sockets** section rep…
-
I am opening this issue because https://github.com/dgtlmoon/changedetection.io/discussions/1979 was deleted apparently without a final state (rejected/accepted).
Obersvation: Pure changedetection (…
-
This proxy used to work for me, now the fingerprint hashes are becoming randomised on each request because the TLS extensions are being randomised on each request, just like a browser. This results in…
-
This kind of thing doesn't work as I get errors along the lines of `"ClientHello missing from cache for " `. How can I compute the JA3 from an incoming request and then `header_up` it to a reverse_pro…
-
**Actual behavior**
It looks like that there are a few websites (I mean services, but not naming them for obvious reasons) that can detect, that the TLS/JA3 fingerprint is spoofed and return with a 4…
-
In https://github.com/komuw/ong/issues/95 (https://github.com/komuw/ong/pull/244) we implemented a TLS fingerprint inspired by ja3.
`ja4+` has been released[1]. `ja4+` has a number of different fi…
-
I have tested multiple version of chrome, but i see same fingerprint.
using the following website: https://tls.browserleaks.com/json
test chrome_108: "ja3_hash":"53ff64ddf993ca882b70e1c82af5da4…
-
[JA3 is a technique for fingerprinting and describing TLS handshakes.](https://github.com/salesforce/ja3)
It would be great if for outgoing TLS sessions this fingerprint could be calculated and sto…
ghost updated
6 years ago
-
Chrome ver.127 has the ja3 fingerprint of "772,4865-4866-4867-49195-49199-49196-49200-52393-52392-49171-49172-156-157-47-53,65281-35-27-51-43-23-17513-13-18-45-16-5-65037-11-0-10,25497-29-23-24,0".
…
-
Was this site completely turned off or is it a temporary outage?