Crawlers that ignore the rules, scrapers and vulnerability scanners rarely look like attacks any more. They send plausible browser identifiers, rotate through cloud addresses and spread their requests over many sites. FFS answers with a layered classifier in its front-end — it runs before a request reaches any site, and it costs no disk or network access per request.
Seven independent signals
| Signal | What it notices |
|---|---|
| Network hygiene | source addresses that cannot belong to a real client |
| Datacenter origin | requests from hosting and cloud ranges rather than homes and offices |
| User-agent sanity | browser identifiers that no real browser has ever sent |
| Identifier fan-out | one and the same browser identifier arriving from many datacenter addresses |
| Session coherence | one address that changes operating system or browser engine mid-visit |
| Cross-site fan-out | one address — or its neighbours — sweeping across many sites of the server |
| Cadence | requests spaced with a machine's regularity |
Signals have different weights. Some are proof on their own; some only add to a score; the weakest can only ever mark a visitor for closer attention, never block it. Coming from a cloud address alone is never enough to be refused — and addresses shared by many people, such as an office behind one gateway, are not counted against them.
The answer is nothing
When the classifier is sure, the connection is closed without a single byte — no status code, no error page, no headers. An error page would confirm that a filter exists and give the operator of the bot something to tune against. Silence gives them nothing.
Safe to introduce
- Shadow mode first: every filter runs and logs what it would have dropped, while every request is still served. Switch to enforcement when the log shows only what you expect.
- Each filter can be switched off on its own, and a site can opt out entirely.
- Search engines and partners you name are exempt from the behavioural filters, and a whitelisted address skips the classifier altogether.
- All state lives in memory and is rebuilt on restart: nothing to clean up, nothing to leak.
