Squidex has 751 title matches and no application match in this query

Squidex is a headless content platform with an authoring interface, content APIs, OAuth and OpenID Connect authentication, app-scoped roles, and client credentials. A public title query can find deployments that show the product name. A missing application match can still leave a useful population, but it changes the review method: confirm the app and its authentication configuration before treating a title as an asset.

On 2026-11-17, a bounded ZoomEye SDK query used sub_type=all, page 1, and pagesize=1. app="Squidex" returned 0 total matches at 2026-11-17T06:55:19.580374+08:00. title="Squidex" returned 751 total matches at 2026-11-17T06:55:21.002715+08:00. The observed total is shown by the application query and the title query. The page size limited returned records, not the matched total.

The app query returned zero and the title query returned 751. The title population may include public content sites, login pages, documentation, and pages that mention Squidex without running it. The zero app result is not proof that no Squidex deployment exists. It means the exact application fingerprint did not match in this successful, bounded query.

Roles are app-scoped, tokens are not interchangeable

Squidex documentation describes OpenID Connect and OAuth 2.0 authentication. Each client has a role, and permissions are scoped to an app. The documentation notes that app permissions are automatically prefixed with the app identifier, which helps prevent a role in one app from granting authority in another.

That design still needs operational discipline. A client credential created for one content application should not be reused across a staging app, a production app, and a website. A developer role that can edit schemas and settings should not be handed to a read-only delivery integration. Review the client list, the role attached to each client, the app scope, and the expiry or revocation path. A client with no identifiable owner is an inventory problem even when the credential is encrypted at rest.

A headless API is the review surface

The public website may be only a consumer of the content API. The authoring interface and the API can share a domain or live on different hosts. An owner should identify the content host, the identity provider, the API consumers, and the app roles used by each consumer. Use the title list to find candidate domains, then confirm the app and environment with the owner.

The API may expose content that is not intended for the public site. A preview token, a workflow endpoint, or an asset URL can reveal unpublished material. Review the publication state of each item, the token scope, and the CDN or proxy cache rules. A cache that keys by URL but ignores the authorization state can serve a protected response to another user.

Compare the two fields

With zero application matches and 751 title matches, the title query is the only external signal in this sample. That makes false positives more likely. Group the candidates by certificate, domain, hosting pattern, and response title, then prioritise domains that are already in the organisation's ownership records. Do not call every title a Squidex deployment.

Record both observations with their exact dorks and timestamps. If a later alias query or a different product fingerprint produces a positive result, preserve the earlier zero and describe the scope change. A new query is new evidence, not a correction of the old query.

Use the app count as a control

The application query serves as a useful control for interpreting the title population. It does not mean the title result is worthless. It tells the reviewer to treat the 751 titles as leads and to confirm the product before assigning risk. A team that automatically labels every title match as a vulnerable application has skipped the most important part of the measurement.

Squidex's 751 titles can point to a meaningful set of content platforms. The security decision rests on the app roles, client credentials, API consumers, and cache behavior behind each confirmed host.

References

[1] ZoomEye application query. https://www.zoomeye.ai/searchResult?q=YXBwPSJTcXVpZGV4Ig%3D%3D

[2] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9IlNxdWlkZXgi

[3] Squidex authentication. https://docs.squidex.io/id-02-documentation/developer-guides/api-overview/authentication

[4] Squidex roles and permissions. https://docs.squidex.io/id-02-documentation/concepts/permissions