How to detect Dolphin{anty} in 2026
Dolphin{anty} is an antidetect browser: a fake browser that gives every profile its own device fingerprint, cookies and proxy, so one team can run hundreds of accounts that each look like a different person. Its own site sells it for affiliate marketing, media buying, e-commerce and "bonus hunting", and tells buyers to "Farm accounts, warm up and launch" (dolphin-anty.com, September 2026). Maskbreak's answer does not name the product. It checks what every such session has to fake (the device, the network path and often the hands on the keyboard) and blocks a fake browser by default.
What Dolphin{anty} is (September 2026)
Dolphin{anty} is made by Zhitnyakov software solutions LTD of Limassol, Cyprus (site footer). The vendor's own guide says the browser "runs on the Chromium engine" (updated 8 August 2026); its plan table also lists a "Chrome or Firefox engine" option on every plan, which no release note we found confirms. Monthly prices, read on 25 September 2026: Free (5 profiles), Starter from $10, Base $89 (100 profiles), Team $159 (300) and Enterprise from $299, with discounts for paying months ahead (plans). The plan table lists no cloud phones.
The features are about running accounts as a team. Every plan has tags, statuses and notes for dividing profiles between people, and profiles can claim a desktop or a mobile operating system. The Scenario builder, a Synchronizer that repeats one person's actions across many profiles, bulk proxy assignment, the Remote and Local API, and Selenium, Puppeteer and Playwright support start at Starter. Profile sharing with permissions and Admin, Team Lead and User roles start at Base. That describes the workload: many made-up identities, each on its own proxy, worked by several people and partly by script.
How Maskbreak reads a Dolphin{anty} session
A Dolphin{anty} session makes three claims: a real device, an ordinary connection and a person at the keyboard. Maskbreak's device check and network intelligence test them separately. A fake browser, a script driving the browser or a proxy exit each blocks on its own by default; a VPN alone is flagged for review.
device.antidetect is true, the reason antidetect_browser is added and the decision is block, the same as for a proxy, Tor, automation or an emulator. It flags the class of tool; it does not say which product the visitor used.device.tampering_score is a 0–1 score from the device check, not a probability of fraud, and it can sit near zero while antidetect is true. Route on decision and reasons; do not build a threshold on the score.device.automation is true, the reason automation_detected is added and the visit is blocked. It does not name the framework; bot detection covers the signal in full.proxy_detected and blocks; a VPN alone adds vpn_detected and goes to review. A residential proxy it does not recognise passes this layer, which is why the device check matters.device.virtual_machine is true and the reason virtual_machine is listed; on its own it asks for review, never a block: plenty of developers browse from one. It raises the risk score next to other findings.device.times_seen counts how often the device appears in Maskbreak's retained history, across all customers, not only yours. Send your own accountId and device.linked_accounts counts how many of your accounts the device has been used for; more than one adds multi_account_device. Links stay inside your account, stored as one-way hashes. Profile switchers are built to defeat exactly this, so treat linking as an extra layer, not the main one.An example response: the fixture that GET /v1/evaluate/sample returns for ?scenario=bot (no key needed), a fake browser driven by a script on a clean-looking address, trimmed to the fields that matter. It is test data for your handler, not a measurement of Dolphin{anty}.
// example response, POST /v1/evaluate
{
"decision": "block",
"risk_score": 83,
"reasons": ["antidetect_browser", "automation_detected"],
"network": {
"vpn": false,
"proxy": false,
"datacenter": false,
"tor": false,
"residential": true,
"service": null
},
"device": {
"antidetect": true,
"automation": true,
"virtual_machine": false,
"tampering_score": 0.78
}
}
Either finding alone would block. residential is true only because no proxy or cloud-server flag fired; it does not prove a home connection.
Shipping it
Add the Maskbreak browser snippet to your signup, login and bonus-claim forms. Your server forwards the two tokens the snippet collects to POST /v1/evaluate with your API key and gets allow, review or block back, with the reasons; the device and network blocks carry everything above. Start in watch mode: log each decision and let every visitor through, then enforce once the Events log looks right. Field-by-field docs live in the API reference and the quickstart has the handler.
If some of your own customers run Dolphin{anty} for agency or seller work, set the Fake browser (antidetect) rule to review on the console's Rules tab. A rule changes the answer only for the signal it names, so a proxy or a script on the same visit still blocks; when a rule does change the answer, engine_decision keeps the default. The antidetect hub explains how the detection works and compares the other browsers; the bonus abuse and multi-accounting playbooks cover the two jobs Dolphin{anty}'s own use-case list points at.
Free plan: 10,000 visitor checks a month, no card. Paid plans from €29 a month.