Digital fingerprint and profile settings in Dolphin {anty}
To work in multiple accounts on the same resource, you need to swap your fingerprint, which is a set of device and browser data. 🌐 That's exactly what Dolphin{anty} 🐬 is for.
Below is a description of what data can be spoofed using Antic, what it even means and why you need it ⬇️
🖥️ What Dolphin {anty} spoofs?
Dolphin{anty} spoofs more than 20 device and browser parameters. Specifically:
🧩 Hardware compatibility
In real life, there is no such thing as, for example, a macOS computer with an Apple M1 processor and an NVIDIA graphics card. Anti-fraud systems notice such mismatches between the OS, graphics card, processor and memory and can use them to identify a profile.
That's why Dolphin{anty} makes sure the hardware in a profile looks realistic: all parameters are checked against a table of real-world configurations.
How it works ⬇️
- You choose the OS - the graphics card list (WebGL info) keeps only the options that fit it.
- You choose the graphics card - the CPU architecture is set on its own (ARM for Apple, x86 for the rest).
- Processor cores and memory are linked to each other: once you choose the number of cores, the memory list keeps only matching values, and vice versa.
Incompatible options are simply not shown in the lists, so it's impossible to build a configuration that doesn't exist. This works everywhere the fingerprint is configured: when creating and editing a profile, in bulk import and smart import, and in profile templates.
💡 Existing profiles keep working as before. If a profile has incompatible hardware, a window about incorrect browser fingerprint settings will appear when you open it for editing, and the corrected values will already be filled in. "Save" writes the new values, "Cancel" leaves the profile as it is.
When you copy such a profile, the copies are created with corrected hardware, and the original profile is updated too.
Profiles where these parameters are set to "Random" or "Off" are not affected.
🤔 Why you need spoof fingerprint ?
Fingerprint spoofing may be required for different tasks:
- Online anonymity. For example, to protect one's data from systems that collect user data in order to identify them later.
- Imitation of ordinary user data. It is important not to confuse anonymity with imitation. In the first case, the program hides your real data. In the second case, the program substitutes data so that you do not stand out among millions of ordinary users and do not attract the attention of anti-fraud systems. To do this, the fingerprint must not be unique, but similar to other fingerprints. It is the latter task that is more difficult.
- Simultaneous work with dozens of accounts of one site. For example, for betting, working with social networks, running advertising, etc.
- Visiting blocked resources.
- Testing. For example, if you need to test the site's performance with connections from different countries or with different browser settings.
ℹ️ General recommendation
- Do not make too unique a fingerprint, it is desirable not to put noises because the user becomes too unique and can be detected by the principle - "a white crow among a pack of blacks". The task of an anti-detect browser is to disguise the user so that he can be recognized as any other user, so too unique fingerprint can stand out and it will lead to blocking.
Profiles can match on all parameters with real values and real hashes - and that's fine. Each profile here is created with different Vendor and Renderer values, and if different proxies are also connected to them, there won't be any problems. The goal is to blend in with the crowd, not to make each profile unique: the more unique a profile is, the higher the chance of a block.