She's being caught.

[A-UNSAL]

It is detected by the following tools.

https://iphey.com/
https://abrahamjuliot.github.io/creepjs/

[Cloak-HQ]

Thanks for the report.

We tested both sites against our latest build.

CreepJS scores 0% headless, 0% stealth, which are the detection metrics that matter. The red sections indicate that fingerprint values have been modified. This is expected.

iphey.com passes Browser and Software checks. The Hardware section flags "masking your fingerprint" for the same reason. The Location flag is from using a datacenter IP. A residential proxy with geoip=True resolves that by matching timezone and locale to your exit IP. Running in headed mode (headless=False) also improves results on these checkers.

These tools detect that we randomize fingerprint values. We do this intentionally. Without it, every session on the same machine produces identical fingerprint hashes, which means sites can track and correlate you across sessions. Removing it to pass these checkers would make the browser less private, not more stealth.

We've investigated this tradeoff extensively (#64, #31) and tested against production anti-bot systems. None of them use fingerprint hash databases to detect modification. Real-world blocking comes from automation markers, fingerprint consistency, CDP leaks, IP reputation, and behavioral signals.

If we see production anti-bot systems start using these checks on live sites, we'll address them. Until then, these diagnostic tools flagging fingerprint modification is expected and by design.