CrawlCheck

Agent view · Findings · 2026-10-14

An access rule on one path locked our customers out

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/an-access-rule-on-one-path-locked-our-customers-out-of-sign-in: 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.

status200
content-typetext/markdown; charset=utf-8
varyAccept
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/an-access-rule-on-one-path-locked-our-customers-out-of-sign-in>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes12,958
words1,846
sha-25641c4b1551654e5ec5abf82eed11da135c7adc4ea8a19cf001a4725d192543eba
repr-digestsha-256=:QcSxVRZU5exav4Lu0R2hNcetxOqKGc8AGkcl0ZJUPro=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795183084;expires=1795186684;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="s9xRDN8aqf5YJT_GBzc9vg";tag="crawlcheck-page"
signaturesig1=:KL4PnyU0Sclm2u80pb2QBazDPOZwEsgF2pf0ytMlaUCR8ItUNBbsOoEBtfc2G3cI+qGWsEik43a286PIP+/vAw==:
verifiedyes — 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-14 · By [VSNARY | Emmanuel Orta](/author)

# An access rule on one path locked our customers out

On 14 October 2026 an access rule meant for staff-only pages also covered customer sign-in, which shared the same address. For an hour, the Sign in link on 247 pages led to a login customers could not pass.

On 14 October 2026, from 10:56 to 11:56 AM MDT, CrawlCheck customers who clicked Sign in reached a login they could not pass. An access rule added to protect staff-only pages also covered customer sign-in, because both used the same address, and a path rule covers everything beneath that path. A sweep of the site's links found the 247 affected pages. Customer sign-in moved to its own address, /signin, along with its form and sign-in email. No data was exposed; the failure only refused access.

On this page

- What did a customer see?
- Why did one rule catch both?
- How was it found, and what changed?
- What should you check before gating a path?

Which addresses one path rule covers

The path itself

Covered by the rule?

Yes

A page below it that a form posts to

Covered by the rule?

Yes

A page below it that an emailed link opens

Covered by the rule?

Yes

A different path that only starts with the same letters

Covered by the rule?

No

An access gate in front of chosen paths stops a request before it reaches the site unless the visitor passes the gate's own login. On 14 October 2026 we added one to protect pages only staff should see. For an hour it also locked out the people who pay us.

## What did a customer see? #

From 10:56 AM Mountain Time, a customer who clicked Sign in in the site header was sent to the gate's login page, which asked for an email address it would never accept. Customer sign-in, the form it posts to and the address the emailed sign-in link opens all lived under the same path as the staff pages being protected.

## Why did one rule catch both? #

A path rule covers that path and everything below it, not every address that starts with the same letters. We tested its reach afterwards, signed out, from outside our network:

| Address, relative to the protected path | Covered by the rule? |
| --- | --- |
| The path itself | Yes |
| A page below it that a form posts to | Yes |
| A page below it that an emailed link opens | Yes |
| A different path that only starts with the same letters | No |

That is the right behaviour, and path gates generally work this way. [our CDN's documentation on Access application paths](https://developers.cloudflare.com/cloudflare-one/access-controls/policies/app-paths/) describes the inheritance: when no more specific rule exists, a deeper path takes the rules of its parent. It is exactly what caught the customer pages.

## How was it found, and what changed? #

| Mountain Time, 14 Oct | What happened |
| --- | --- |
| 10:56 AM | Access rule added for staff-only pages |
| Just before noon | A sweep of every page and all 4,433 internal links finds the Sign in link on 247 pages redirecting to another company's login page |
| 11:56 AM | Customer sign-in moves to /signin; every link, redirect, form and the sign-in email move with it |

Not a customer report: the sweep was run before a site rebuild, and a public link that redirects to another domain's login stands out in it ([how to run that kind of sweep](/guides/how-to-audit-internal-links-and-dead-anchors)). The fix was checked by outcome: /signin answers 200 with its forms, the translated pages link to it, and no customer page links to the old address. Anyone with an old bookmark should use [/signin](/signin). Reports, licence keys and data were never exposed; the failure refused access, it did not grant any.

## What should you check before gating a path? #

- **List every route under the path**, including the ones a form posts to and the ones an email links to. No page links to those, so they are the easiest to forget.
- **Give staff and customers different addresses.** A shared sign-in page means any wall in front of one is a wall in front of both.
- **Fetch your own site signed out after any access change**, every page and every link. A public link that redirects to another domain's login page is the signal.
- **Prefer a specific path to a short one.** The shorter the protected path, the more lives under it.

For what a crawler gets when a gate or firewall answers instead of your site, see [HTTP status codes for crawlers](/guides/http-status-codes-what-a-crawler-actually-gets).

This is one of the corrections CrawlCheck publishes when its own output was wrong. [All of them are listed together](/blog?kind=corrections).

CrawlCheck’s dataset when this page loaded: 570,959 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%2Fan-access-rule-on-one-path-locked-our-customers-out-of-sign-in%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fan-access-rule-on-one-path-locked-our-customers-out-of-sign-in%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=An%20access%20rule%20on%20one%20path%20locked%20our%20customers%20out)[Email](mailto:?subject=An%20access%20rule%20on%20one%20path%20locked%20our%20customers%20out&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fan-access-rule-on-one-path-locked-our-customers-out-of-sign-in)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### Does a path-based access rule cover subpaths?

Yes. In our test a rule on one path also gated the pages beneath it, including a form target and an emailed-link address, while a different path that only shared the first letters reached the site normally. The vendor's documentation says a deeper path inherits its parent's rules when no more specific rule exists.

### Why could CrawlCheck customers not sign in on 14 October 2026?

From 10:56 to 11:56 AM MDT, customer sign-in shared an address with staff-only pages that had just been put behind an access rule. Customer sign-in moved to its own address.

### Where do I sign in to CrawlCheck?

At crawlcheck.io/signin.

### Was any customer data exposed?

No. The failure only refused access to the sign-in page; it did not grant access to anything. Reports, licence keys and data were unaffected.

### How do I avoid gating customer pages by accident?

List every route under each path you protect, including form targets and links sent by email, keep staff and customer sign-in on different paths, and fetch your whole site signed out after any access change.

## Related findings

[2026-11-06 Most of our 'referring pages' were forged Referer headers We counted any Referer header as a link click. Most were forged: our own addresses on control-panel ports, lookalike search domains, bare hostn](/blog/most-of-our-referring-pages-were-forged-referer-headers)[2026-09-10 A newspaper’s schema coordinates put it in China A regional US newspaper's LocalBusiness schema drops the minus from its longitude and lands in China. Why range checks pass it and](/blog/the-newsroom-that-published-coordinates-in-china)[2026-10-14 Sitemap lastmod: 103 pages, one date, why engines skip it 103 pages in our sitemap shared one lastmod though most had been rebuilt. Why Google and Bing ignore dates like that, and how to d](/blog/sitemap-lastmod-103-pages-one-date-why-engines-ignore-it)

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.

**Pages:** [SDK](/sdk) · [Certificates](/certificates) · [Website audit](/website-audit) · [Conduct: ChatGPT-User](/agents/conduct/chatgpt-user) | **Registry:** [MCP: Operator](/registry/mcp/operator) · [MCP](/registry/mcp) | **Datasets:** [Technologies: Hubspot](/datasets/technologies/hubspot) · [Technologies: Powr](/datasets/technologies/powr) | **Guides:** [HTTP 3 how to check whether your site offers it](/guides/http-3-how-to-check-whether-your-site-offers-it) | **Glossary:** [change receipt](/glossary/change-receipt) · [Approximate nearest neighbor](/glossary/approximate-nearest-neighbor) · [Cache key](/glossary/cache-key)

[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/an-access-rule-on-one-path-locked-our-customers-out-of-sign-in.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.