Incogniton Detection

How to detect Incogniton in 2026

Incogniton is a Chromium-based antidetect browser: every profile gets its own fingerprint, cookies and proxy, so one person can run many accounts that each look like a different computer. It is cheap to try, with 10 free profiles for the first two months, then 3. Maskbreak does not look for the product's name. It checks whether a profile holds together, and a fake browser is blocked by default.

What Incogniton is in September 2026

Incogniton is made by WorkingGreen B.V., which its site places in Amsterdam, and runs on Windows and Mac. In the vendor's own list, a profile can set the device model, operating system, browser version, time zone, language, plugins, screen resolution and audio and video capabilities. New profiles have used a Chrome 152 core since 10 September 2026, two days after Chrome 153 went stable (changelog). The site pitches it at social media management, affiliate marketing and online marketplaces.

The tooling around the browser has grown. Proxies can be bought inside the app, which has had a proxy shop since July 2024. A built-in AI assistant arrived in March 2026, and since 16 July the assistant, Cas, can start, stop and delete profiles and manage tabs from chat. Version 5, on 8 June 2026, was a full redesign with a public REST automation API, an MCP token system for AI agents, team permissions and CSV import and export of profiles. Every paid plan includes a "Paste as human typing" tool. Paid plans start with Starter Plus (10 profiles); Selenium, Puppeteer and API access start one tier up, at Entrepreneur (pricing). Unlike Multilogin or Gologin, Incogniton's site does not advertise cloud phones or cloud-hosted browsers. Facts checked on the vendor's site and changelog in September 2026.

How Maskbreak flags an Incogniton session

The browser snippet on your form collects two tokens, and your server sends them to /v1/evaluate. Nothing in the answer names Incogniton. It reports the class of tool and the evidence around it. These are the fields a visit through an Incogniton profile runs into.

Fake-browser flag

When Maskbreak's device check sees a fake or tampered browser, it sets device.antidetect, adds the reason antidetect_browser and returns block by default, the same as a proxy, Tor, automation or an emulator. The console labels it "Fake browser (antidetect)". It flags the class of tool, not the product.

Claims the engine cannot back

Every value an Incogniton profile sets is a claim, while the Chromium underneath and the machine's graphics hardware stay what they are. A user agent the engine cannot back, or a graphics card the machine does not have, is the kind of contradiction the device check looks for. On our test bench, canvas or audio noise on its own did not trip the flag, because it contradicts nothing inside the browser.

Tampering score

device.tampering_score is a 0–1 value from the device check, not a probability of fraud. On our bench it stayed near zero while the fake-browser flag changed, so route on the decision and the reasons, not on a threshold of the score.

Automation

Incogniton sells Selenium, Puppeteer and REST API control from its Entrepreneur plan, and Cas can drive profiles from chat. When the device check sees signs that a script is driving the browser, it adds automation_detected and blocks by default. It does not name the framework. A virtual machine is reported as device.virtual_machine; on its own it asks for review, never a block.

The proxy each profile carries

Each profile has its own exit address, and Incogniton sells proxies in the app. On a live visit, Maskbreak's network intelligence adds proxy_detected for proxy exits it recognises, which blocks by default, and names the service in network.service when known. A VPN on its own adds vpn_detected and is flagged for review. A residential exit it does not recognise passes the network check, which is why the device layer matters.

One machine, many accounts

Send your own accountId and device.linked_accounts counts how many of your accounts this device has been used for; more than one adds multi_account_device. Links stay inside your account as one-way hashes. device.times_seen is different: it is history across all Maskbreak customers, not a count of visits to your site. Profile switchers are built to break the link, and in our lab tests a switcher produced new visitor IDs, so treat linking as an extra layer.

Keeping it honest: no check catches every Incogniton session. A carefully built profile on a proxy exit nobody has flagged can pass all of them, ours included, and Maskbreak has not published a detection rate for Incogniton or any other browser. No field in the response measures typing, so "Paste as human typing" is neither a tell nor a cover here. What you get is one decision per visit (allow, review or block) with the reasons behind it.

From signup to verdict

Add the browser snippet to the form you want to protect: signup, login or a bonus claim. Your server forwards the two tokens to /v1/evaluate with your API key and branches on decision; device.antidetect and the reasons array say why. Start in watch mode, which logs each decision and lets the visitor through, and switch to enforce once the Events log looks right. The quickstart has the handler and the API reference has every field.

If some of your own customers run Incogniton for legitimate multi-account work, such as agencies or marketplace sellers, set the Fake browser (antidetect) rule to review on the console's Rules tab (block or review?). A rule changes the answer only for the signal it names, so a proxy or automation flag on the same visit still blocks. The lab notes show how the device check was tested, the proxy mismatch guide covers where a profile and its network disagree, and the antidetect hub sets Incogniton beside the other browsers.

See which signups arrive in a fake browser.
Free plan: 10,000 visitor checks a month, no card. Paid plans from €29 a month.

Start free — no card Try the live scanner