Glossary

The words this category is searched under

Definitions for the vocabulary of anti-detect browsing — what each term means, what it costs you in practice, and where in Argus the mechanism lives.

23 entries, each written to be read on its own. Where a definition touches something Argus does, it says what is applied and what is not — the surfaces that are left alone are named rather than left out.

Anti-detect browser

A browser built to run many separate identities on one machine, each with its own storage, device characteristics and network address.

Browser fingerprint

The set of properties a page can read about your browser and machine in a few milliseconds, without permission, which together identify the device.

Canvas fingerprint

An identifier derived by asking the browser to draw a shape or a line of text and hashing the exact pixels that come back.

WebGL fingerprint

An identifier built from the graphics hardware a page can see through WebGL — the reported vendor and renderer strings, plus the pixels a 3D scene produces.

Audio fingerprint

An identifier derived from processing a synthesized tone through the browser's audio stack and hashing the numbers that come out.

WebRTC leak

A page reading your real IP address out of WebRTC's connection setup, bypassing the proxy the rest of the browser is using.

User-agent client hints

Chromium's structured replacement for the user-agent string: a set of Sec-CH-UA request headers and a JavaScript API that report the browser, platform and hardware separately.

Cookie jar

The store a browser keeps cookies in. Everything sharing one jar shares one identity, which is why isolation is a property of the jar and not of the tab.

Browser profile

A directory on disk holding everything one browsing identity owns — cookies, storage, cache, history and settings — plus, in an anti-detect browser, its fingerprint and proxy.

Residential proxy

A proxy whose exit address belongs to a consumer internet connection, which is what makes a login from it unremarkable.

Datacenter proxy

A proxy hosted in a data centre. Fast, cheap and openly identifiable as hosting, which makes it right for fetching public pages and wrong for signing in.

ISP proxy

An address registered to a consumer ISP but hosted in a data centre — datacenter speed and stability with residential registration.

Mobile proxy

A proxy exiting through a carrier network, where one address is shared by thousands of real phones — which is what makes it tolerant.

SOCKS5

A general-purpose proxy protocol that forwards TCP connections without inspecting them, optionally behind a username and password.

Proxy rotation

Changing the exit address automatically — per request or on a timer. Right for collecting public pages, wrong for a signed-in session.

Multi-accounting

Running several accounts on one platform from one machine without them being read as one operation.

Account linking

A platform deciding that two accounts belong to the same operator, from storage, device, network or behaviour.

Device entropy

How much identifying information a device's reported properties carry — measured in bits, and lowered by looking ordinary rather than by hiding.

TLS fingerprint

An identifier computed from the way a client opens a TLS connection — the cipher suites, extensions and their order in the ClientHello.

Cookie injection

Writing a saved set of cookies into a fresh browser profile so it opens already signed in, without the password being entered.

Headless browser

A real browser engine run without a visible window, usually under automation. Cheap to run at volume, and increasingly easy for a site to spot.

CAPTCHA solving

Passing a challenge to a third-party service that answers it. Useful occasionally, and a poor substitute for not triggering the challenge.

Timezone and geolocation spoofing

Making a browser report a clock — and sometimes a position — that matches where the session claims to be rather than where the machine is.