Author
anonymous
Independent anti-detect and anti-fraud researcher. Sole reviewer and editor of UndetectableBrowsers.
Last updated
I write under the nickname anonymous. Every review on this site is authored and maintained by me, and every one of them follows our published methodology.
What I work on
I have spent years on both sides of the browser-fingerprinting problem — developing and defeating the techniques that anti-detect tools rely on. My areas of focus:
- Browser fingerprinting
Canvas, WebGL/GPU, WebRTC, audio, fonts, and timezone vectors, and how detectors correlate them.
- Multi-accounting
Profile isolation, identity consistency, and the failure modes that get accounts flagged.
- Automation
Selenium, Puppeteer, Playwright, CDP, and the practical limits of headless and RPA workflows.
- Proxies and networking
Residential vs. datacenter vs. mobile, proxy hygiene, and IP/fingerprint mismatch.
- Anti-fraud
How platforms detect and cluster suspicious sessions — so I can judge what actually evades detection rather than what merely claims to.
How I test
Reviews are hands-on, not copied from spec sheets. For each browser I:
- Create real profiles and run them through established anti-detect test suites — Pixelscan, CreepJS, and BrowserLeaks among them — and check both the scores and whether the reported fingerprint stays consistent.
- Exercise the automation surface (API, CDP, drivers) rather than assuming the docs are accurate.
- Set up proxies, test profile isolation, and look for leaks the marketing doesn't mention.
- Verify pricing against the vendor's own pages and re-check it periodically.
When a tool is weak — JS-injection masking that detectors catch, automation locked behind the top tier, opaque pricing — I say so.
Editorial independence
The site earns affiliate commissions on some sign-ups. That funding never influences a score or a ranking. I grade against the fixed rubric before any commercial relationship enters the picture, and products with no affiliate program are scored exactly like those with one. The full disclosure is on the methodology page.
Why anonymous
This is a privacy-focused niche. The people who use these tools value discretion, and the people who build detection systems would prefer researchers in this space to be easy to identify. Staying anonymous lets me write candidly about both vendors and detectors, without the work being shaped by who I am or who I'm expected to please. The credibility here comes from the testing and the transparent method — not from a name.
Contact
Have a correction, a tip, or a product I should cover? The best route is the submit an update page. Corrections are checked against the methodology, verified, and then published.