Agent view · Findings · 2026-10-22
Our receipt checker would have rejected our own receipts
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/our-receipt-checker-would-have-rejected-our-own-receipts: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/our-receipt-checker-would-have-rejected-our-own-receipts>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 11,556 |
| words | 1,578 |
| sha-256 | 6fd2c3c1abae3e785cd710e341378bf44c300df3486185e550d3023369d8acfe |
| repr-digest | sha-256=:b9LDwauuPnhc1xDjQTeL9EwwDfNIYYXlUNMCM2nYrP4=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795363678;expires=1795367278;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="lvAUkr-oBlM_-rdGFvglpg";tag="crawlcheck-page" |
| signature | sig1=:qrbuK4ivaA1QMgEKPVie2naqrK7Dno7sGON2iJxkrD3id0HM1B/O86WvJvMHbqczhwit0D0czfsm0uqUXvlNDQ==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Findings · 2026-10-22 · By [VSNARY | Emmanuel Orta](/author) · 13 views # Our receipt checker would have rejected our own receipts A flaw in our published offline verifiers would have called genuine CrawlCheck receipts forged after our first routine key change. Our tests caught it before any receipt was affected. CrawlCheck's offline verifiers for JavaScript, Python and the command line would have rejected genuine receipts signed by a key that had since been replaced, and in one case would have accepted a receipt signed by the wrong key. No real receipt was ever affected: the keys involved start signing on 9 November 2026, and our own tests caught the gap first. The fix shipped in SDK 1.9.1 on 22 October 2026. Anyone who verifies CrawlCheck receipts should upgrade before 9 November. On this page - What would users have seen? - What was wrong? - What changed? - What should you do? - The lesson for anyone who checks signatures The flaw at a glance Real receipts affected Status None Fixed in Status SDK 1.9.1, released 22 October 2026 Keys involved start signing Status 9 November 2026 Verifiers fixed Status npm package, Python package, command-line tool How it was found Status a missing case in our own published key-rotation tests The answers CrawlCheck gives AI agents come back signed, so an agent, or anyone auditing it later, can check them offline with the verifier we publish, without having to trust us. Ours was right about today and wrong about the day after our first routine key change. ## What would users have seen? # After that key change, a genuine receipt signed before it would have failed verification, reported as signed by the wrong kind of key. The gap ran the other way too: a receipt signed by a key that should not have signed it would have passed. The first people to notice would have been the ones relying on the receipts. ## What was wrong? # When a signing key is replaced, the receipts it signed while it was in service are still genuine and must still verify. Our verifiers forgot about replaced keys when deciding which key should have signed a receipt, so they would have judged old receipts by the wrong rule. | Item | Status | | --- | --- | | Real receipts affected | None | | Fixed in | SDK 1.9.1, released 22 October 2026 | | Keys involved start signing | 9 November 2026 | | Verifiers fixed | npm package, Python package, command-line tool | | How it was found | a missing case in our own published key-rotation tests | ## What changed? # A replaced key now counts only for the period it was in service. Receipts it signed in that period verify; anything it signs afterwards is rejected. A decision can now only pass if it was signed by the kind of key that was meant to sign it at that moment. The published key-rotation tests now include the case that caught this. ## What should you do? # If you verify CrawlCheck receipts, upgrade to 1.9.1 before 9 November: `npm install @crawlcheck/sdk@1.9.1` or `pip install crawlcheck==1.9.1`. If you wrote your own verifier, run the published conformance tests against it; the key-rotation cases are the ones this flaw would have failed. If you only read CrawlCheck reports, nothing changes for you. ## The lesson for anyone who checks signatures # A signature check is only as good as its rule about time. When you rotate a key, test the documents it signed before the rotation, not only the ones signed today. The same kind of gap left [our timestamp proofs stuck at pending](/blog/our-proofs-said-pending-for-26-days); for how signed requests are checked in general, see [Web Bot Auth explained](/guides/web-bot-auth-how-signed-crawler-requests-work). CrawlCheck’s dataset when this page loaded: 584,504 sites measured. Written by [Emmanuel Orta](/author) · VSNARY I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post. [Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta) Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-receipt-checker-would-have-rejected-our-own-receipts%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-receipt-checker-would-have-rejected-our-own-receipts%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Our%20receipt%20checker%20would%20have%20rejected%20our%20own%20receipts)[Email](mailto:?subject=Our%20receipt%20checker%20would%20have%20rejected%20our%20own%20receipts&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-receipt-checker-would-have-rejected-our-own-receipts)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Questions this post answers ### Were any CrawlCheck receipts rejected because of this? No. The keys involved had not signed anything and no key had been replaced, so the flaw never judged a real receipt. ### Do I need to upgrade? If you verify CrawlCheck receipts with the npm package, the Python package or the command-line verifier, upgrade to 1.9.1 before 9 November 2026. Readers of reports need to do nothing. ### Does a receipt stay valid after its signing key is replaced? Yes, as long as it was signed while that key was in service. Anything the key signs after it was retired is rejected. ### Does a valid receipt mean an agent may act? No. A valid signature proves the receipt is genuine and unchanged. What the agent may do is the decision written inside it. ## Related findings [2026-11-13 Claude-User uses two published address lists. We checked one CrawlCheck checked Claude-User against one of two Anthropic address lists and counted real fetches as failed. Fixed 13 November 20](/blog/claude-user-comes-from-two-published-address-lists-we-checked-one)[2026-10-22 Three sections said “not scored”. Our grade counted them. On 22 October 2026, three CrawlCheck report sections labelled not scored still counted in the grade. Who was affected, what we fix](/blog/three-report-sections-said-not-scored-the-grade-counted-them)[2026-11-13 Both our SDKs cut a tool list at 300 with no warning CrawlCheck's lockfile and both SDKs fingerprinted only the first 300 tools of an MCP server, unmarked. Fixed 11 November 2026.](/blog/our-sdks-cut-a-tool-list-at-300-with-no-warning) The main product Found this on your own site? **We fix it for $100.** Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after. [Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v) [What it covers](/pricing#fix) · [scan first, it is free](/) Free browser extension Check this on any site you open, **without leaving the page.** CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account. [Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post) [What it does](/extension) Write for the library Measured something yourself? **Submit an article.** Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published. [Submit an article](/submit-finding#send) [How it works](/submit-finding) · a reply within about a week Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections). ## Comments Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*. Send for review Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan. [All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy) We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io) #### How we measure, and our own machine files CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io). **Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing. **Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours. **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) · [Agentapi](/registry/agentapi) · [coconutcreekchevrolet.com](/registry/coconutcreekchevrolet.com) · [example-shop.com](/registry/example-shop.com) · [lakewoodplumbingpros.com](/registry/lakewoodplumbingpros.com) | **Pages:** [IP ranges](/data/ip-ranges) | **Glossary:** [Redirect chain](/glossary/redirect-chain) · [Link equity](/glossary/link-equity) · [decision receipt](/glossary/decision-receipt) · [Retry-After](/glossary/retry-after) [Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /blog/our-receipt-checker-would-have-rejected-our-own-receipts.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.