Journal
Not what an antidetect browser promises - what Chromium, Edge, Firefox and the Android tools actually did on a Windows machine when we asked them to, including the several occasions on which they disagreed with their own documentation.
10 postsEach one names its data, its tool and its claimStart with what fingerprinting cannot do
Branded Chrome accepts --load-extension, loads nothing, and says so only in its own log. Measured on Chrome 151, where the old escape hatch is dead.
4 min readDivyansh Singh
Google's Android package manager prints a licence, reads end of input, installs nothing and returns success. Three packages, none of them real.
4 min readDivyansh Singh
Chrome's file handles outlive its process exit on Windows. A profile holding 431 cookies journalled as having lost every one of them.
5 min readDivyansh Singh
The msedge.exe you spawn exits after sixty milliseconds. A different process publishes the debugging port later, and it is the one you wanted.
4 min readDivyansh Singh
No automation flag, no client attached, no WebDriver anywhere. One switch sets the property, measured on Chrome 151.0.7922.76 across two launches.
4 min readDivyansh Singh
Username and password in a SOCKS5 proxy URL are ignored by Chromium, silently. The fix is a local forwarding relay, and it solves a second problem too.
5 min readDivyansh Singh
Separate profile directories give separate cookies, storage, cache and extensions. Chromium's network state is keyed by site, and no flag splits it.
4 min readDivyansh Singh
The cookie file moved to Default\Network\Cookies. Code that reads only the old path reports an intact profile as empty, with no error.
3 min readDivyansh Singh
The cheapest contradiction to detect in a proxied session, and the one most tools leave to the operator. Why Ward derives the timezone from the exit probe.
5 min readDivyansh Singh
A green score is not a result and a red one is not a failure. What to check on a public fingerprint test, in the order that tells you something useful.
5 min readDivyansh Singh
By subject
Every subject here holds more than one post. A tag with a single post on it is a page that exists to be crawled rather than read, and the suite fails when one appears.
The standard
Three rules. The first is applied by the build - a post that cannot name its source, its tool and its own claim fails the deploy - and the other two are kept by the person writing.
Every post names the data it rests on and the tool that produced it, and both are printed at the bottom of the page. Where a number appears, the browser or tool version it came from appears beside it.
A browser that has not been patched at the source level is detectable through property-descriptor and prototype inspection. Nothing here will tell you otherwise, and the words this site refuses to use are listed in the documentation.
The plan runs to a hundred posts. They go out a handful at a time, each one able to stand on its own findings, because a hundred pages appearing at once is a pattern search engines have a name for and readers can feel.
Ward runs many browser profiles on one PC, each with its own proxy and its own device identity. The free plan needs a free account and no card, and there is nothing to buy today.