SFTPGo title and body counts describe different discovery layers
SFTPGo combines file transfer protocols with browser administration and a REST API. A team that uses a single broad search result to inventory it can mix an exposed SFTP listener with a public WebAdmin page, a read-only WebClient, and a documentation mention. The ZoomEye fields are more useful when they are treated as separate observations.
On 2026-11-17, a bounded SDK query used sub_type=all, page 1, and pagesize=1. title="SFTPGo" returned 2,160 total matches at 07:46:49 +08:00. http.body="SFTPGo" returned 10,455 at 07:46:50 +08:00. The title value is the narrower branded signal in this sample. The body value can include login pages, help pages, API documentation, asset directories, and text that merely mentions the product.
Separate the protocols from the control plane
SFTPGo documentation describes SFTP, SCP, FTP/S, WebDAV, a web client, a WebAdmin interface, and a REST API. Those surfaces can share a data provider while using different authentication paths and bindings. A valid SFTP account does not prove that the same account can use the API. An API key must be enabled for a user or administrator and on the relevant HTTP binding.
The inventory should record each binding, enabled protocol, identity provider, user role, home directory, sharing policy, and storage backend. The WebAdmin is a control plane. The WebClient is an end-user file interface. A deployment may expose the former on a management network and the latter on a public application host. A title count cannot tell those apart.
Review delegated administration
The product documentation describes restricted administrators and scoped roles. Those roles are only useful if the provider assignments are reviewed. A delegated administrator who can create users across an entire storage backend has more authority than a role label may suggest. API keys and OIDC mappings need the same owner review.
Check whether a public binding has both WebAdmin and WebClient enabled when only one is needed. Confirm that the API key feature is disabled where no integration requires it. Look at shares, quotas, writable directories, and the storage backend's own credentials. The same file may be reachable through SFTP, WebDAV, and the HTTP API, so removing one path does not remove the data.
Turn counts into a bounded lead list
Use the title matches as candidates for confirmation. Check the certificate, HTTP title, WebAdmin route, response headers, and the owner's deployment records. For body-only matches, inspect the page type before treating the host as an SFTPGo service. Do not describe 10,455 body matches as 10,455 files or file servers.
The 2,160 title observations give a bounded population for a product-specific review. The next decision is which of those hosts expose a control plane and which identity path governs it. Those questions belong to the asset owner, not to the count.
References
[1] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9IlNGVFBHbyI%3D
[2] ZoomEye body query. https://www.zoomeye.ai/searchResult?q=aHR0cC5ib2R5PSJTRlRQR28i
[3] SFTPGo Web user interfaces. https://docs.sftpgo.com/enterprise/web-interfaces/
[4] SFTPGo REST API. https://docs.sftpgo.com/enterprise/rest-api/
Top comments (0)