This is the first reason why most proxies get detected (with or without a browser) all details included

• headers
• UserAgent
• cipher suite

• https://en.wikipedia.org/wiki/Cipher_suite

so this is what happened

lets say you send a request claiming that you are Chrome 122 and have proper headers that's great but when it comes to the cipher suite the proxy won't adjust the cipher suite according to your headers and UserAgent
most proxies send requests via nodejs or python and simply those clients don't have low-level access to change the cipher suite


you will look like the following example to the end server

send a request claiming that you are chrome 122 but when I verify your cipher suite I found that you have nodejs cipher suite so this will look to the server 99% using proxy

The solution
well there is no solution for this as it is related to the proxy provider and not you if the server is checking for JA3 then it knows that you are using a proxy

Except you are using your proxy farm then you can make a logic that will adjust the cipher suite according to every userAgent and this is a pain to do

another bypass for this is to use only 1 well-known user agent with the exact same header and adjust the cypher suite to this using C/C++ or Golang, this is the solution I am using I adjusted the cipher suite using C but other languages listed above can do the job as well

feel free to ask anything regarding this

Cathrine D'Amore said:

Very interesting. A question that may be a bit silly: Can websites see the IMEI/MAC of the device? I understand that apps can, but not through the browser. Is this correct? Thank you

Click to expand...