Availability, receipts, observers, coverage and adoption, each with the denominator under it.
What an agent depends on when it asks before acting: the service answering in time, a receipt it can check without trusting us, observers it can tell apart from us, coverage counted honestly, and evidence of who actually uses it. Every number here is read from the running system when the page loads; the same document is /api/v1/assurance.
Definition
- Attempted
- A domain CrawlCheck tried to read, from the census, the registry, a lookup or a scan.
- Measured
- A domain with a stored, signed record of what was served.
- Full scan
- The on-demand deep read: every section, every finding with its evidence.
- Registry-listed
- A domain with a record in the public registry, claimed or not.
What this does not prove
- Measured means read and recorded, not right: every finding carries its evidence so it can be checked.
- Coverage counts what CrawlCheck was asked about or seeded with, not a sample of the web.
- A full scan is a moment; the record says when it was taken.
- The keys, observers and eligibility checks further down are listed as configured; the status page says whether they are answering now.
Check it yourself
The numbers on this page come from the signed JSON at /api/v1/instruments/assurance/now.json, rebuilt every few minutes; each copy carries its own sha256 and an Ed25519 signature by key 1hHmE3fo1rg5…. For a copy that never changes, cite a weekly edition. Verify either with no call to us:
node crawlcheck-verify.mjs --online assurance.json
The verifier: /crawlcheck-verify.mjs, zero dependencies.
How a decision receipt maps to EU AI Act Article 12 and NIST AI RMF, as a mapping and not legal advice: decision receipts as compliance evidence. A frozen public suite of 27 cases, run alone and with a signed answer: the agent safety benchmark.
degraded
service now (status)
2
signing keys, by purpose
1 of 15
observers not run by us
0
decisions to verified AI agents, 30 days
Targets and what was measured
Last 30 days. /api/slo
| Objective | Target | Measured | Samples | p50 / p95 | Result |
|---|---|---|---|---|---|
| Resolve answers without a server error | 99.9% | 100% | 16,080 | 206 / 625 ms | met met at 95% confidence |
| Resolve answers for a measured domain within 300 ms in the Worker | 95% | 87.4% | 16,080 | 206 / 625 ms | missed missed at 95% confidence |
| Preflight decisions without a server error | 99.9% | 100% | 3,384 | 220 / 668 ms | met met at 95% confidence |
| Preflight decisions within 300 ms in the Worker | 95% | 69.9% | 3,384 | 220 / 668 ms | missed missed at 95% confidence |
| A first answer for a never-measured domain within 2 seconds in the Worker | 95% | 87.6% | 784 | 1139 / 2761 ms | missed missed at 95% confidence |
A missed objective stays published until the window rolls past it. Open incidents: 0; the signed incident log is at /api/status/log.
A valid signature is not permission
Six separate answers; act only when all hold.
| Check | Fails when |
|---|---|
| integrity_valid | a byte of the receipt changed after signing |
| signature_valid | the Ed25519 signature does not verify over the digest |
| issuer_trusted | the key is not in CrawlCheck’s published directory: a perfect signature from anyone else’s key is refused |
| fresh | the receipt is past expires_at (each action has its own validity; transact is the shortest) |
| scope_valid | the receipt names a different domain or action from the one you are about to take |
| decision_permits | the decision is block or unsupported; warn without your policy accepting it; require_confirmation without a human’s yes |
curl -s -X POST https://crawlcheck.io/api/v1/preflight -H 'content-type: application/json' \
-d '{"domain":"example.com","action":"read"}' -o receipt.json
curl -sO https://crawlcheck.io/crawlcheck-verify.mjs
node crawlcheck-verify.mjs receipt.json --act example.com:read # exit 0 only when eligible_to_actThe SDK’s guard() makes the same checks in your code; the quickstart puts it inside the function that performs the action, so the model cannot route around it. Keys: requests and documents are signed with separate keys.
Who runs each observer and witness
14 of 15 are run by CrawlCheck.
Different networks are not different operators. An observer we run from another cloud shows whether a result depends on where it was measured from; only an operator outside CrawlCheck can show it does not depend on us. Each row says which it is.
| Observer | Operator | Network | Verifies | Code · credentials · deploy | Last reading | Limitation |
|---|---|---|---|---|---|---|
| crawlcheck-worker active | CrawlCheck (VSNARY) (us) | CrawlCheck primary network | every primary measurement | ours · ours (Worker secret) · ours | — | this is CrawlCheck itself: it corroborates nothing |
| gha-azure-1 active | CrawlCheck (VSNARY) (us) | GitHub-hosted runners on Microsoft Azure; not any crawler operator's network, so it corroborates a vantage question, never an operator's own crawl | the homepage under each identity, from a second network | ours · a new key per run, bound to our workflow by a GitHub token · ours (repository workflow) | 2026-11-07 15:49 | a different network and a third party (GitHub) attesting which workflow ran; not a different operator |
| aws-us-east-2 active | CrawlCheck (VSNARY) (us) | Amazon Web Services, US East (Ohio); not any crawler operator's network, so it answers whether a site treats this network or country differently, never what an | the homepage under each identity, from a second network | ours · a new key per run, bound to our workflow by a GitHub token · ours (repository workflow) | 2026-11-07 15:49 | a different network and a third party (GitHub) attesting which workflow ran; not a different operator |
| tor-exit active | CrawlCheck (VSNARY) (us) | the Tor network: an exit relay Tor chooses (address, network and country recorded per reading); it answers whether a site treats anonymising networks differentl | what a crawler is served from a visitor's own connection | ours (the extension) · one key per install, made on the device · installed by each person | 2026-11-07 15:48 | the vantage is the visitor's; the code is ours; an install key proves one install, not one person |
| ext:* active | people running the CrawlCheck extension (version 1.0.4 and later) with sharing switched on | the visitor's own connection (home, office or mobile), recorded as country and network name only; the address is never stored | what a crawler is served from a visitor's own connection | ours (the extension) · one key per install, made on the device · installed by each person | — | the vantage is the visitor's; the code is ours; an install key proves one install, not one person |
| gha:* active | any GitHub repository whose workflow runs the crawlcheck-core Action with observe: true (or posts the same envelope); id gha:<owner>/<repo> (us) | the runner the workflow ran on: GitHub-hosted (Microsoft Azure) or the repository's own self-hosted runner, measured from the connection each reading arrives on | what a crawler is served from a visitor's own connection | ours (the extension) · one key per install, made on the device · installed by each person | — | the vantage is the visitor's; the code is ours; an install key proves one install, not one person |
| ind:cc-cosig1-test revoked | CrawlCheck (VSNARY) cosig1 end-to-end test; retired after the test (us) | test container, one-off | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | — | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:cli-2ns-x7r1zy unknown | CrawlCheck (VSNARY), PHP client test from a Google Cloud container (us) | this machine's network | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | — | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:gcp-session-1 unknown | CrawlCheck (VSNARY), run from a Claude cloud session (us) | Google Cloud egress (AS396982), not Cloudflare, not Azure | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | — | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:gcp-tv-1 unknown | CrawlCheck (VSNARY), test vantage run from a Google Cloud container (us) | Google Cloud (AS396982), Columbus US | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | — | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:google-llc-iowa-e94e42 quarantined | CrawlCheck (VSNARY) - installer test from a Google Cloud container (us) | AS396982 Google LLC, Council Bluffs, Iowa, US | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | — | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:installtest-gcp quarantined | CrawlCheck (VSNARY) installer test (us) | AS396982 Google LLC, Columbus US | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | 2026-10-08 20:40 | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:refcheck-gcp- quarantined | CrawlCheck (VSNARY) reference check (us) | Google Cloud container | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | 2026-10-08 21:13 | run by CrawlCheck from another network: network diversity, not an independent operator |
| ind:vsnary-wp-1 active | VSNARY (operator of crawlcheck.io) (us) | managed WordPress hosting: the WordPress server of tree-d.example | readings of queued URLs under the open observer protocol | the open protocol client · an Ed25519 key made on the observer's machine · whoever runs it | 2026-11-08 13:27 | run by CrawlCheck from another network: network diversity, not an independent operator |
| log-witness active | GitHub (identity token) running CrawlCheck's workflow (us) | GitHub-hosted runners | each signed head of the Resolve log, co-signed with a GitHub-issued token naming the workflow that saw it | ours · GitHub's OIDC token for that run · ours (repository workflow) | — | GitHub attests which workflow ran and when; it does not recompute the log. A split view is caught by clients comparing heads (gossip) |
Anyone can run an observer under the open observer protocol; an observer run by someone else is the one thing that turns network diversity into independence.
What each number counts
| Domains | Count |
|---|---|
| attempted by the census | 700,325 |
| with at least one reading (“sites measured”) | 496,554 |
| full scans, graded | 6,268 |
| in the public registry (full scan, publishable, not opted out) | 1,101 |
attempted = every domain the census tried; measured = domains with at least one reading (most are the census's lighter reading); full scans = graded reports; registry = full scans that can be published and have not opted out. Resolve answers for any domain; a never-measured one gets a first, partial answer marked as such.
| MCP servers | Count |
|---|---|
| records in the official MCP Registry, imported | 300 |
| with a remote endpoint | 262 |
| probed this cycle (handshake only, never tools/call) | 45,656 |
| completed the handshake and listed tools | 22,936 |
| completed the handshake with no tools | 1,239 |
| asked for credentials | 15,236 |
| errored, unreachable or not MCP | 6,168 |
| tool lists scanned for poisoning | 866 |
| flagged by the scan | 0 |
| tool lists changed since first seen | 3,749 |
indexed is not connected, and connected is not safe: a clean tool scan means no known poisoning pattern was found, not that none exists. Cycle started 2026-11-01.
Who actually asks
Our own traffic is counted apart, never as adoption.
| Last 30 days | Count |
|---|---|
| signed decisions to verified AI agents (operator ranges) | 0 |
| signed decisions to other callers | 1,523 |
| signed decisions to us (tests, probes, our sites) | 844 |
| receipt checks by sites we do not run | 221 |
| receipt checks by our own sites | 4 |
Calls to the agent surfaces (MCP, Resolve, preflight, Visitor Resolve, outcome) 2026-11-01 to 2026-11-07: 18,701 from outside, 3,821 ours. Outside, by caller: other 6,337 · mcp-client 4,675 · node 1,939 · browser 1,374 · bot:other 1,315 · python 630 · http-client 474 · bot:BrickBlueBot 316 · no-ua 315 · openai 240 · sdk-python 232 · claude 202 · bot:MJ12bot 175 · bot:Amazonbot 152 · bot:SealKeeperBot 81 · bot:WellknownBot 40 · bot:InvokeRankBot 37 · bot:Maps-bot 28 · bot:agent-tools.cloud-crawle 28 · browser-app 22 · bot:PluginboardBot 19 · bot:GolemreachTrustBot 16 · bot:YandexBot 14 · bot:ElectraIndexBot 9 · bot:Faceabot 8 · bot:CapabilityIndexBot 4 · bot:KakaoBot 3 · bot:Bytespider 2 · bot:brickroad-bot 2 · bot:SemrushBot 2 · bot:Baiduspider 2 · bot:AhrefsBot 2 · bot:ExtOpsBot 1 · bot:RiverBot 1 · perplexity 1 · bot:APIEvangelistBot 1 · bot:DotBot 1 · bot:DataForSeoBot 1.
ours = our key, owner session, own sites, probes or self-tagged tests; other = everyone else and may still include an untagged test of ours; verified_agent = a caller naming an AI agent from inside that operator's published ranges, which we cannot pad. Caller classes are read from the user agent and recorded from 2026-10-10. The day-by-day series is /api/v1/adoption.
Funnel, last 30 days
| Stage | Count | Of | Share |
|---|---|---|---|
| decisions asked for by callers that are not us verified agents plus other callers; other may still include an untagged test of ours | 1,533 | — | — |
| of those, from an AI agent verified by its operator's ranges | 0 | 1,533 | 0% |
| distinct agent names asking (self-declared) counted from 10 Oct 2026; an agent that names itself the same way is one | 15 | — | — |
| receipts checked by a site we do not run a presented receipt is only visible when the site checks it, so presented and checked are one stage | 221 | 1,533 | 14.4% |
| distinct sites checking receipts | 2 | — | — |
| agent names asking on 2 or more days | 5 | 15 | 33.3% |
| sites checking on 2 or more days | 2 | 2 | 100% |
Our own traffic (our key, owner session, own sites, self-tagged tests) is never counted. Receipt checks recorded before 10 Oct 2026 were classed by host alone, so they are listed apart as host_only_receipts and excluded from every stage and from the goal.
Witness, seals, drills and succession
Read from the running system; each row links to its source.
| What | Last | Measured | Source |
|---|---|---|---|
| Outside witness co-signs the log | 7 h ago | batch 1,955 of 1,966 (11 behind) · hourly at :51 UTC on GitHub Actions, which can run late | witness |
| Daily seal after the day closes | 2026-11-07 | 7 of 7 days sealed · median 77 min after close, worst 78 · 7 in a Bitcoin block | proof |
| Revocation drill | 20 h ago | passed in 1,008 ms · 14 of 14 recent runs passed | self-test |
| Restore test (rebuild from archive) | 6 days ago | green · 20 of 20 identical, 0 mismatched · weekly, Mondays 03:17 MDT (09:17 UTC), and on demand; GitHub Actions, proven by GitHub's OIDC token | test |
daily: the incident switch on selftest.crawlcheck.io is flipped, Resolve must report the incident, a transact preflight must return block, and the domain must appear on the signed revocation list, then it is cleared. the oldest archived records rebuilt from the archive alone (the 90-day projections ignored) and compared byte for byte with what was served. delay = when the seal was written after the day closed; a seal reaches Bitcoin when a calendar's attestation is mined, usually within hours.
Succession
If the operator stops, this continues:
- every signed answer, receipt and evidence bundle verifies offline with crawlcheck-verify.mjs and the published keys, with no call to CrawlCheck
- each sealed day stays provable through its OpenTimestamps proof and Bitcoin block, which no one at CrawlCheck can alter
- the daily signed snapshot and the census are public (CC BY 4.0) and can be mirrored by anyone
- the transparency log's witnessed heads are held by every client that kept them
This stops:
- new measurements and new signed answers
- revocations and incident switches
- the observer network's scheduling
no successor operator has been named yet; until one is, the guarantees above are the ones that survive the operator.
Generated 2026-11-08 13:35 UTC.