Bu sayfa henüz sizin dilinizde yok. İngilizce metni okuyorsunuz.
Guides
How to choose an antidetect browser: nine checks in an hour
ARMANOS ekibi7 minUpdated

In short
Nine checks. Fonts, WebGL pixels, zone and language, devices, voices, connection, memory, WebGPU, phone fields.
You need little. A trial profile, your ordinary browser and the developer console.
One conclusion. A profile's answer either matches your machine and gives it away, or differs and holds.
What you can actually test before paying
A promise on a landing page is beyond your reach, and a browser answer is not: a platform reads it with the same lines you do.
Those answers get changed along one of two roads: inside the build itself, or by a script laid over a stock Chrome.
The second road shows from the outside, and that is what the nine checks below catch.
The checks need no account on a platform and no purchase: a trial profile, your ordinary browser and the developer console are enough.
- 1
Two profiles
Create profiles that declare two different systems.
- 2
Your own window
Open your everyday browser as a third window.
- 3
One comparison
Whatever matches across all three came from your machine.
Nine checks and what each one catches
Each line below asks the browser for one value and sets it beside a second value that you already know.
| What you ask for | What gives a fake away |
|---|---|
| The six generic font families | serif, cursive, fantasy and math come back one width |
| WebGL pixels read whole and in windows | two reading routes over one drawing give different bytes |
| Timezone, language, calendar, separators | the zone comes from the proxy, the separators from your system |
| The number of microphones, cameras, speakers | in every profile it is your own |
| Speech synthesis voices | your system voices under a foreign declared system |
| Speed, latency and connection type | the same numbers your everyday browser reports |
| The heap limit given to page scripts | a number off the steps, or off the declared memory |
| WebGPU beside a named video card | the card is named and navigator.gpu is missing |
| Three connection fields on a phone profile | the fields are absent, or type answers wifi |
Fonts: six families, one measurement
A page may ask not for a font name but for a family: serif, sans-serif, monospace, cursive, fantasy and math.
A live machine resolves all six into different fonts and returns a different line width for each.
A profile of the native system answers with four different widths, while a profile of a foreign system gives all four as one number, equal to the width of serif.
| Family | macOS profile on a Mac | Windows profile on a Mac |
|---|---|---|
| serif | Its own width | Its own width |
| cursive | Its own width | Same as serif |
| fantasy | Its own width | Same as serif |
| math | Its own width | Same as serif |
Memory answers in steps, not bytes
Chromium never tells a platform's scripts the exact heap limit: the answer lands on one of a hundred steps, from 10 million to 3.76 billion bytes.
Read that number in the trial profile and in your everyday browser.
A number between the steps, or one exactly equal to your real memory, means nobody was substituting anything here.
The same number also has to agree with the memory the profile declares beside it.
A profile that names a modest memory and hands out a generous heap ceiling is two answers from two different machines.
A named card with no WebGPU
The name of the video card is declared by the profile, while the state of the card is reported by your machine, and those two answers arrive from different places.
On a rented Windows server with no card, the browser reports webgl and webgpu as disabled_off, and navigator.gpu does not appear.
The name of an expensive card beside that answer is a pair that does not occur.
A phone profile and three connection fields
Android hands a page three connection fields: type, downlinkMax and ontypechange. Desktop Chrome hands over none of them, which makes this the fastest test of a phone profile.
If the fields are there, ask for their values.
Your own machine shows through at once: type reads wifi and downlinkMax reads infinity, while the profile declares a cellular connection.
A green extension badge proves nothing
A blocker's card shows “enabled” and “files found”, and its rule may still do nothing at all.
One and the same extension with one blocking rule can behave differently: on one build the forbidden request reaches the server, on another it does not.
Load a blocker into the trial profile and watch whether the block ever reaches the network.
The same goes for any other extension you were promised. Load it, use it once, and judge by the result rather than by the green badge on the card.
A tenth check: frame and worker
A page asks for the number of cores and the platform name not only from its own window: it asks the same question inside an invisible frame and in a separate worker.
A script laid over stock Chrome reaches the window and often fails to reach those two.
Open the developer window in the trial profile and ask the window for its core count, then create a worker and ask it the same.
Two different numbers out of one profile are an answer about the vendor, not about your machine.
In return it separates substitution inside the build from substitution on top of it better than any other.
The same profile answers the same tomorrow
An eleventh question is not about substitution but about constancy: close the trial profile, open it tomorrow and read the same rows.
A real machine answers the same way day after day, and a profile has to behave the same.
In ARMANOS a profile's answers belong to it, so yesterday's canvas, fonts and memory match today's to the byte, while a second profile differs.
A browser whose fingerprint changes from launch to launch hands out a new machine at every sign-in.
Fitting nine checks into one hour
The long part is not reading the answers, it is creating the profiles and wiring the proxies. The nine lines themselves run down the table in a few minutes.
A sensible order: fonts and memory first, then the video card, then the connection. The first two disagree more often than the rest and cost you one line each.
What to do with the answers
Nine answers split sellers into two halves: some change the values inside the build, others lay a script over a stock Chrome.
The difference shows in whether a profile answer matches your machine answer. The choice is yours, and you now make it before paying rather than after the first ban.
How to run these checks in ARMANOS
The free check on the site reads 12 values in your window and sends nothing out.
In the app, "Test fingerprint" in the profile menu reads up to 37 readings and matches them against the profile's promise.
Two profiles with different systems show whether their answers differ, as they should.
Common questions
- Do I need to know how to code for this?
- No. Each check is one line in a developer console and an answer you read with your eyes.
- Is a trial period enough?
- It is enough if it lets you create two profiles with different systems. One profile will not do: half of the checks are a comparison of windows.
- And if there is no trial at all?
- Look for a product with a free start: a trial profile lets you check the nine answers with your own hands.
- Can I just use a ready fingerprint check site?
- Partly. Such a site shows the values but does not set them beside your machine, and the comparison is what catches a substitution.
- Which of the nine matters most?
- Fonts and the heap limit. They read cheaper than the rest and disagree more often than the rest.
Start with your own browser's answers
The free check reads 12 values in the window and sends nothing out.