Check guide ยท In the browser

Worker consistency

Ask the same question in four rooms of the browser. Do the answers match?

What this check is

A page is not one context. Code also runs in Web Workers, iframes and a service worker, and each context can describe the browser independently. This check asks several of them the same questions (platform, user agent data) and compares the answers with the main window's.

What Tells reads

How to read your result

Why it matters

This is the check spoofers fear most, because it attacks the method rather than any single value. Patching a property in the visible window is easy; patching it identically in every execution context, including ones created later, is a different order of work. Automation and anti-detection tools alike are routinely caught by a worker that still tells the truth.

Where this matters most

On the platforms Blowhorn works with, this tell rates Low everywhere: none of LinkedIn, X, Reddit, GitHub, Slack, Bluesky or Hacker News has public evidence of using it as an anti-bot input. It stays in the tool because it matters on the wider web (it is a standard input to commercial fingerprinting and bot-management products) and because Low is a snapshot, not a law: a platform that buys such a product changes this row without announcing it. The full reasoning is in the platform guide.

In your report

Find it in the checks table on the tool page, with the detail in the Consistency section. The same findings appear in the report JSON under verdict.reasons, and the agent guide explains how to read them programmatically.

Related checks