Detected automatically by js_execution · 2026-08-03 18:40:49 UTC
A client executed JavaScript on this site
A client declaring Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.7871.186 Mobile Safari/537.36 (compatible; GoogleOther) reached the beacon on the script-rendered probe 1 time, which requires having executed the page's script.
What was observed
Between 2026-07-31 13:24:03 and 2026-07-31 13:24:03 UTC, a client reached the beacon URL 1 time.
Declared identity: Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.7871.186 Mobile Safari/537.36 (compatible; GoogleOther)
What it means
The beacon is requested only by the script embedded in the probe page. Reaching it therefore requires having executed that script — this is observed capability rather than capability inferred from a user agent string.
Limits
- The declared user agent is unverified. Any client can send any string, so this describes a claim rather than a confirmed identity.
- This establishes execution on these visits. It does not establish that the client executes scripts generally, nor that it does so when crawling other sites.
- One domain, observed continuously. Nothing here generalises to how this client behaves elsewhere.
Evidence chain
This finding was not written from memory. Each figure below came from a query against the immutable request record, and each query is shown so it can be run again — by us, on this page, or by anyone reconstructing the same instrument.
| Stage | What it produced |
|---|---|
| 1. Reality | Requests recorded by the server as they arrived, written once and never edited. |
| 2. Evidence | The rule js_execution selected the observations that bear on this question and emitted each figure with the means of reproducing it. |
| 3. Statement | A fixed template turned that evidence into the prose above. No language model was involved and no figure was altered. |
| 4. Verification | Every figure was recomputed against the record. A single mismatch would have discarded the draft. |
| 5. Publication | 2026-08-03 18:40:49 UTC, after review by a person. |
What was measured
Each figure is stated first as what it means, which does not depend on how this system happens to store anything today. The query underneath it is implementation — it would be written differently on different storage, and it is shown so the figure can be checked, not because it is part of the claim.
Evidence
beacon requests from this client
At publication: 1 · recomputed now: 1 unchanged
Implementation — how this is computed on today's storage
SELECT COUNT(*) FROM JsExecution j JOIN RequestReality r ON r.id = j.requestId
WHERE j.siteId = ? AND r.cfRay IS NOT NULL AND r.userAgent IS ?
AND r.cfConnectingIp NOT LIKE '2a00:1d34:4896:b600:%'
AND r.cfConnectingIp NOT IN (
SELECT cfConnectingIp FROM RequestReality
WHERE cfConnectingIp IS NOT NULL AND (userAgent LIKE 'curl%' OR userAgent LIKE 'Wget%' OR userAgent LIKE 'Python-urllib%' OR userAgent LIKE '%python-requests%' OR userAgent LIKE 'Go-http-client%' OR userAgent LIKE 'node-fetch%'))Every figure still returns what it returned at publication.
Governed by
- I. Reality is not interpretation — Reality ≠ Interpretation
- III. No layer validates itself — No layer validates itself with its own output
- VI. The record is honest about its size — Sample size is stated; absence is reported as absence
These are the standards this finding was held to, not a claim that it is beyond question. The constitution states them in full.