Tandoor Recipes: 170 title matches and a small sample to read carefully

A count of 170 is small enough that each entry matters, and small enough that indexing gaps change the result. Tandoor is a self-hosted recipe manager, and the index identifies it by page title while returning nothing for an application signature.

What the queries measured

Two queries were run against the ZoomEye index on 5 October 2026, scoped to all asset types.
Search query: app="Tandoor". Result: 0 matching assets.
Comparison query: title="Tandoor". Result: 170 matching assets.

Why a small count is read differently

A population of 170 sits inside the range where crawl coverage, crawl timing and naming choices each move the number by a visible amount. A service that is reachable only on a non-default port, or that is fronted by a proxy which rewrites the page title, may be absent from the figure even though it is reachable.
The count is therefore a lower bound on reachable instances in a way that a figure of tens of thousands is not. The smaller the number, the larger the share of it that the measurement can miss.
A population this size supports a different use than a large one. It is not a headline count and it is not a measure of a problem at scale. It is a short enough list that an operator can work through it, and the same property applies to the defensive reading: a deployment that should not be public is worth fixing whether the population around it is 170 or 17,000.

What an instance holds

A recipe manager stores a collection, the accounts that reach it and, in a common configuration, a link to a database that holds the same data. Personal recipe collections are not sensitive in the way that records or credentials are, and the interfaces that manage them may still hold session tokens, user records and the connection string for the backing store.
The exposure question is the same as for other self-hosted household services. Whether the instance should answer from the internet, and whether the database behind it is reachable separately from the application.

What an operator can do next

Compare the figure against the organisation's own records, and note that a small count is not evidence of a small problem. Then check the two paths separately: the application interface and the database behind it.
Where the service is internal, removing the public route is the smaller change. Where it must stay reachable, the account list and the database port are the two items to confirm.

Limitations

The count describes indexed assets on one day. It cannot separate a running instance from a page that mentions the product, it does not identify version or authentication state, and at this size crawl coverage is a material factor rather than a rounding error.

References

[1] Tandoor Recipes. https://tandoor.dev/
[2] Tandoor Recipes source repository. https://github.com/TandoorRecipes/recipes
[3] ZoomEye. https://www.zoomeye.ai/