WildDuck shows why an application fingerprint beats a body keyword
WildDuck is the IMAP and POP3 server component of the Zone Mail Suite. It also exposes an HTTP management API and has an authentication model with account passwords, application-specific passwords, role-based API tokens, and audit logs. A search for the product name can therefore encounter mail content, API documentation, marketing pages, and actual service surfaces.
The 2026-11-16 observations used sub_type=all, page 1, and pagesize 1. app="WildDuck" returned 155, title="WildDuck" returned 13, and http.body="WildDuck" returned 107,060. The body result is much larger than the application fingerprint and should not be treated as an installation count.
| Query role | Exact dork | Observed total |
|---|---|---|
| Application fingerprint | app="WildDuck" |
155 |
| Page title | title="WildDuck" |
13 |
| HTTP body | http.body="WildDuck" |
107,060 |
The body field is not a census
An HTTP body match can come from a documentation page, a hostname in a directory, a mail message rendered as HTML, or a product comparison. The selected 107,060 result is useful because it shows how broad the phrase is in the index. It is not useful as a claim that 107,060 mail servers are reachable.
The application fingerprint is still only a starting point. It identifies a product signature, but the owner, version, and exposed protocol remain unknown. A hostname may be a dashboard, an API gateway, a demo, or a honeypot. The next step is authorized verification, not exploitation.
Authentication is split across protocols
WildDuck's documentation separates the IMAP and POP3 service from the HTTP API. The API can use a root token or role-based access tokens, with an authentication role intended for public authenticate calls. That separation matters during inventory because a web endpoint and a mail endpoint can expose different authentication paths.
Mail clients may use account credentials or application-specific passwords when two-factor authentication is enabled. API clients may use long-lived tokens. The control question is not only whether a WildDuck page is reachable. It is which token type can perform account, mailbox, or administrative actions and where that token is stored.
Build a two-plane inventory
One plane is the mail service: IMAP, POP3, SMTP integration, TLS, account status, and authentication logs. The other is the HTTP management API: token roles, access control, management hostnames, and reverse-proxy exposure. Record the owner and network path for each.
The official installation guide explicitly advises setting up API access control before allowing other hosts to reach the management API. That guidance is more actionable than the raw body count. Review which hosts can reach the API, which token roles exist, whether root tokens are still active, and whether role tokens are scoped to the endpoints they need.
Use the selected observation honestly
The body query is the largest observation, so it is the one linked below under the specified query-display rules. It should be presented as a broad phrase-search result, not as a product census. The application fingerprint is the better candidate set for follow-up, and the title count is a secondary signal.
Operators can correlate the 155 application matches with their own DNS and certificate inventory, then validate only authorized endpoints. A good finding might be a management API reachable outside its approved network segment or an old root token that no one owns. Those are concrete control problems, not inferred from the number of index hits.
Top comments (0)