Reading a Tiki Title Match Without Overstating the Product Population

Title searches are convenient and easy to overread. A page title containing "Tiki" may belong to a Tiki Wiki CMS Groupware deployment, but it may also be a restaurant, a theme, a plugin page, or an unrelated service. The query is useful for discovery when the analyst states that the result is a title-keyword population rather than a precise product census.

For Tiki Wiki CMS Groupware, the application fingerprint query returned zero in this measurement, while the title query returned matches. On 2026-11-03, the selected query title="Tiki" used scope all, page 1, and one result and returned 1,828 assets. This is the narrower, evidence-bounded statement: ZoomEye observed 1,828 pages whose titles matched the keyword at that time under that scope.

Preserve the uncertainty in the label

The article should not call all 1,828 assets Tiki installations. The title field is a substring-style match, and the word "Tiki" is not unique to the CMS. A better review process uses the result to find candidate domains and then confirms the product through a page path, response content, headers, or an approved owner check. An application fingerprint is preferable when it is available and accurate for the version in use.

This is an important difference between data collection and editorial interpretation. The query evidence is the exact dork, scope, time, and count. The interpretation is that the result is a broad candidate pool. It can inform monitoring and ownership questions, but it cannot support a vulnerability count or a claim that every title match has the same configuration.

Filter the queue with local evidence

Prioritize domains that look like organizational collaboration sites or match known hosting and certificate patterns. Check for recognizable Tiki paths and administrative interfaces only within authorized boundaries. Confirm version and configuration from the application, not from the title alone. If the site is public and intended for anonymous use, review edit, upload, account, and plugin permissions.

Keep a second query candidate in the evidence record. The zero-result application query is still useful because it shows why the title query was selected. It also prevents a later analyst from seeing only the larger count and assuming that the product fingerprint automatically matched.

Make the count reproducible

Record the exact timestamp because title-based populations move as pages are rewritten. A change from one run to another can reflect new pages, removed pages, or changes in the search index rather than a change in Tiki adoption. Do not sum title and application results. They overlap and represent different matching methods.

The action that follows is simple. Build a short candidate list, confirm the product with a second source, and assign an owner. ZoomEye helps the team ask where to look. A careful analyst keeps the word "candidate" attached until the product and configuration are verified.