Browser Check: request header signals

Verdict: Strong automation signals (score 45)
Several signals point to an automated or headless session. A real anti-bot system would likely score this browser the same way.

Signals:
  [CLEAN] User-Agent sent
      Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
  [CLEAN] Known automation client
      The User-Agent does not name a known scripted client.
  [DETECTED] Accept-Language sent
      No Accept-Language was sent. Browsers always send one; scripted clients usually do not.
  [DETECTED] Accept is browser-shaped
      Accept is "*/*", the catch-all a scripted client sends.
  [DETECTED] Sec-Fetch metadata complete
      Missing: sec-fetch-site, sec-fetch-mode, sec-fetch-dest. Current browsers send all three; scripted clients send none.
  [N/A] Client Hints sent
      This check applies to requests that claim a Chromium browser.
  [N/A] Client Hints version agrees
      This check applies to requests that claim a Chromium browser.
  [N/A] Client Hints platform agrees
      This check applies to requests that claim a Chromium browser.
  [N/A] Client Hints form factor agrees
      This check applies to requests that claim a Chromium browser.
  [CLEAN] Brotli offered
      gzip, br, zstd, deflate
  [NOTABLE] Upgrade-Insecure-Requests sent
      Not sent. Browsers send this on page navigations; scripted clients and background fetches do not.

Note: this covers request headers only. The full check, including the
client-side browser probes, runs at https://checknet.uk/browser-check