Homepage: 45 App Matches Are Useful, 617,479 Title Matches Are Not a Product Count

Homepage is a self-hosted dashboard that gathers links, service widgets, and status data into one page. The product name is also an ordinary word. That combination makes query design part of the security method.

A ZoomEye SDK probe on 22 November 2026 used sub_type=all, page 1, and pagesize=1. app="Homepage" returned 45 matches. title="Homepage" returned 617,479. The probes completed between 06:46 and 06:47 Asia/Shanghai.

The title query is almost useless as a product census. It matches generic landing pages, web-server defaults, and unrelated applications. The application query is narrower, but it still requires ownership and route verification. A value that resembles a product name is a candidate, not proof.

Why a dashboard can be sensitive

Homepage documentation notes that widgets can access personal information, such as data from a home-automation system. The project added a simple authentication gate with a password or OIDC in version 2.0, but the deployment guide still recommends protecting an untrusted-network deployment with a reverse proxy or VPN that enforces authentication and TLS.

The dashboard often holds API keys for the widgets it displays. A widget that can query a media server, automation hub, or monitoring API turns the dashboard into a central place for service credentials. The page may also disclose internal hostnames, service URLs, topology, and availability.

Use the application field as a filter

Start with the 45 app matches, then confirm each candidate using certificate names, page assets, paths, and ownership records. Do not import all 617,479 title matches into an asset inventory. If the ordinary title must be used for discovery, combine it with a product-specific body clue or a known dashboard path and document the limitation.

For owned instances, record the base URL, authentication gate, OIDC provider, reverse-proxy policy, widget credentials, Docker discovery, and Host header handling. Place the dashboard behind a trusted access gateway when it is reachable from an untrusted network.

Use per-widget credentials with the smallest useful scope. Keep dashboard configuration in a protected repository, because API keys, service URLs, and labels can reveal the estate even when the rendered page is private. Test that forwarding an arbitrary Host header does not reach a privileged virtual host.

Measurement method

The useful result is not the largest number. It is the combination of a product-specific field, a bounded comparison query, and an ownership check. Here, the app field is narrow enough to start a review; the title field is a striking example of why search counts need context.

References