Cloned Boy
Professional
- Messages
- 857
- Reaction score
- 695
- Points
- 93
Hello everyone, 
I continue to share information.
Works with PC/MAC.
Let's start with setting up anti-detect. When working with anti-detect and with self-registrations in general, you need to understand the following:
There are different types of fingerprints that websites see and that we can replace in antidetect.
WebGL - video card/video driver fingerprint. Audio card fingerprint (which, by the way, antifraud almost doesn't take into account)
Canvas - a general fingerprint of the system, including OS version, languages, fonts, etc.
Clients Rects - a parameter responsible for how the site elements are arranged on the browser display and their size - is directly related to the display resolution.
There is also the so-called WebGPU, which is talked about by developers in the field; in essence, it is the same imprint of a video driver, only in the form of information about it.
When working with self-registers, the most important thing for us is the trustworthiness of the fingerprint . When we use substitutions, this is in any case detected by antifraud and can affect successful registration, so the best option is to use the native fingerprint without substitutions.
We select the language in the browser manually - EN-US, the rest we configure for our system. Also, the trust can increase the addition of browser bookmarks and extensions from chrome, such as Paypal Honey / Capital One Shopping (it is also important to log in to them), but you should not make all profiles with the same bookmarks and extensions, with mass registration this can increase the attention of antifraud to us.
Why do we need substitutions in antidetect?
1. Mass registration. When we work from one system (with the same fingerprints), sooner or later we will start to be fraudulent by these same fingerprints. It is impossible to single out some general possible number of successful registrations in a row without fingerprint substitution since AF is different everywhere, but if we take the average, then when working with Windows it is 2-3, with Mac Intel - 4-6, with Mac ARM it is 8-10. This situation is because on the Windows base, for example, there are many different devices with different fingerprints, so AF immediately adds fraud points if it sees a couple of similar sessions. Mac Intel fingerprints differ depending on the version of the processor / video card, and there are fewer Mac ARM versions and, accordingly, fraud by fingerprint is activated later.
How to solve it. The best option is to replace WebGL (enable the item in the antiquities), and along with it, replace the corresponding WebGPU - select another video device in the antiquities. I will note that in this case, the trustworthiness of the fingerprint will be somewhat lower, but with mass registration we actually have no other options. Those who work with the sphere - there is a hybrid fingerprint, where only the replacement of WebGPU with a similar one installed on your device is enabled, also a good solution.
2. Working with logs. Here the situation is different, we need to adjust to the holder, and the entire success of our work depends on a normal IP and live cookies from the log. In this case, you can enable at least all the substitutions, the main thing is the correspondence of languages and the browser itself, with what is installed at the holder. Here we also enable the substitution of Client Rects, since we need to change the display resolution. But if it matches yours, the substitution is not necessary.
We don’t touch Useragent in Antique, because even if we change the version, it will all be perfectly visible.
Regarding the substitution of Timezone and Geolocation - as a rule, all this is perfectly picked up by Antik from the IP we are sitting from. However, sometimes, due to frequent changes of geo IP in rotation, this can throw us into another state, which is not good. It is better to check geo using maxmind.
I continue to share information.Works with PC/MAC.
Let's start with setting up anti-detect. When working with anti-detect and with self-registrations in general, you need to understand the following:
There are different types of fingerprints that websites see and that we can replace in antidetect.
WebGL - video card/video driver fingerprint. Audio card fingerprint (which, by the way, antifraud almost doesn't take into account)
Canvas - a general fingerprint of the system, including OS version, languages, fonts, etc.
Clients Rects - a parameter responsible for how the site elements are arranged on the browser display and their size - is directly related to the display resolution.
There is also the so-called WebGPU, which is talked about by developers in the field; in essence, it is the same imprint of a video driver, only in the form of information about it.
When working with self-registers, the most important thing for us is the trustworthiness of the fingerprint . When we use substitutions, this is in any case detected by antifraud and can affect successful registration, so the best option is to use the native fingerprint without substitutions.
We select the language in the browser manually - EN-US, the rest we configure for our system. Also, the trust can increase the addition of browser bookmarks and extensions from chrome, such as Paypal Honey / Capital One Shopping (it is also important to log in to them), but you should not make all profiles with the same bookmarks and extensions, with mass registration this can increase the attention of antifraud to us.
Why do we need substitutions in antidetect?
1. Mass registration. When we work from one system (with the same fingerprints), sooner or later we will start to be fraudulent by these same fingerprints. It is impossible to single out some general possible number of successful registrations in a row without fingerprint substitution since AF is different everywhere, but if we take the average, then when working with Windows it is 2-3, with Mac Intel - 4-6, with Mac ARM it is 8-10. This situation is because on the Windows base, for example, there are many different devices with different fingerprints, so AF immediately adds fraud points if it sees a couple of similar sessions. Mac Intel fingerprints differ depending on the version of the processor / video card, and there are fewer Mac ARM versions and, accordingly, fraud by fingerprint is activated later.
How to solve it. The best option is to replace WebGL (enable the item in the antiquities), and along with it, replace the corresponding WebGPU - select another video device in the antiquities. I will note that in this case, the trustworthiness of the fingerprint will be somewhat lower, but with mass registration we actually have no other options. Those who work with the sphere - there is a hybrid fingerprint, where only the replacement of WebGPU with a similar one installed on your device is enabled, also a good solution.
2. Working with logs. Here the situation is different, we need to adjust to the holder, and the entire success of our work depends on a normal IP and live cookies from the log. In this case, you can enable at least all the substitutions, the main thing is the correspondence of languages and the browser itself, with what is installed at the holder. Here we also enable the substitution of Client Rects, since we need to change the display resolution. But if it matches yours, the substitution is not necessary.
We don’t touch Useragent in Antique, because even if we change the version, it will all be perfectly visible.
Regarding the substitution of Timezone and Geolocation - as a rule, all this is perfectly picked up by Antik from the IP we are sitting from. However, sometimes, due to frequent changes of geo IP in rotation, this can throw us into another state, which is not good. It is better to check geo using maxmind.
