No automation extension has written its marker into the page
No comment containing UIPATH_EXTENSION_ID, and no webdriver, selenium or driver attribute on <html> (severity: warn).
What a detector infers
Some automation tools announce themselves in the pages they control. UiPath's browser extension leaves a comment carrying UIPATH_EXTENSION_ID in the document, and a widely deployed CAPTCHA's challenge script looks for exactly that comment. Older Selenium drivers set a webdriver attribute on the <html> element, and public bot-detection libraries also test for selenium and driver attributes there.
A page can read every comment node and the root element's attributes, so these markers are visible to any script on it. The row reports only these specific markers, never ordinary comments or attributes, so a site's own markup cannot trip it. Only the absent side has been measured: no marker in Google Chrome 154–156, Chromium 153 or Clearcote r52 without extensions; the markers themselves come from that challenge script and those libraries, not from a capture of each tool.
How to resolve it
Use a profile without the UiPath extension for anything that should look like a person browsing, and a driver that does not mark the document.
Nearby checks in Automation surface
- The user agent names no headless product
headless-ua-tokenBoth of Chrome's headless modes name themselves in the user agent. - A fresh frame has none of Node's, Deno's, Bun's or Pyodide's globals
runtime-globals-absent-in-fresh-frameA new about:blank frame starts with the browser's own globals and nothing else, because no page script has run in it. process, module… - history.replaceState to another origin throws SecurityError
history-replacestate-cross-origin-throwshistory.replaceState may change the URL shown for a document only within its own origin; the HTML standard requires a SecurityError for any… - No interface stable Chrome keeps behind a developer switch is exposed
flag-only-surfaces-absentStable Chrome keeps unfinished web platform features behind developer switches, and some of them add global interfaces as soon as the switch… - No debugger client attached to this tab after it loaded
console-replay-trapV8 keeps the console messages a page logs, which is why DevTools can show messages logged before it was opened. - navigator.webdriver does not assert WebDriver control
webdriver-offThis check is intentionally one-way. The WebDriver specification defines navigator.webdriver as the browser's assertion that it is under… - navigator.webdriver is a native prototype getter returning false
webdriver-descriptor-integrityRather than reading the value, this check inspects the property's shape: it requires a getter on Navigator.prototype whose… - No Selenium / Puppeteer / Playwright globals
automation-globalsThis check tests a fixed list of roughly two dozen known names against both window and document (Selenium's __webdriver_evaluate /…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Automation surface checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Automation surface — the family automation-extension-markup belongs to.