DEV Community

Ioneyrezende
Ioneyrezende

Posted on

Maddy Mail Server's small web signature is a visibility warning

Maddy Mail Server's small web signature is a visibility warning

Maddy Mail Server is an all-in-one mail server that can handle SMTP, submission, IMAP, message storage, filters, and authentication. Its operational footprint is mostly in mail protocols and TLS configuration. A search that depends on a web application fingerprint or page title may therefore miss a working mail server entirely.

On 2026-11-16, ZoomEye was queried with sub_type=all, page 1, and pagesize 1. app="Maddy Mail Server" returned 0, title="Maddy Mail Server" returned 0, and http.body="Maddy Mail Server" returned 14. All three results are count observations from the same index. They are not an assertion that only 14 deployments exist.

Query role Exact dork Observed total
Application fingerprint app="Maddy Mail Server" 0
Page title title="Maddy Mail Server" 0
HTTP body http.body="Maddy Mail Server" 14

Mail services do not announce themselves in HTML

A server can accept SMTP on port 25, submission on 587, IMAPS on 993, or a custom local socket without serving the product name as a web title. Even when an HTTP management surface exists, it may be a reverse proxy or a separate application. The absence of a product title is not a negative inventory result.

The 14 body hits may be documentation, setup pages, or a handful of visible interfaces. They should be reviewed individually before they become assets. The count does not say whether a host is a mail gateway, a mailbox server, an administration proxy, or a static installation guide.

Identify the service first

An evidence-driven process begins with DNS, MX records, certificate names, and the ports that are authorized for assessment. Then it asks which protocol responds and which TLS identity is presented. Product classification comes after service classification.

For a mail system, the same host may advertise a public MX path while restricting submission and IMAP to a VPN. Inventory should record each service separately. A public SMTP listener does not imply a public administration interface, and a body keyword does not imply an open mailbox.

Review authentication and delivery policy

Maddy's documentation includes TLS configuration, PAM authentication, and delivery security levels. Those settings define whether a connection is encrypted, whether a certificate and DANE check succeeded, and which authentication provider receives a client credential. The useful assessment is a configuration and ownership review, not a count of pages that mention the product.

Test SMTP AUTH only with authorized test accounts. Check whether submission requires authentication, whether TLS is enforced, and whether proxy paths preserve the client connection properties the server expects. For IMAP, review account provisioning and token or password lifecycle. Record failures without attempting credential guessing.

Treat 14 as a lead, not a population

The body result is the only nonzero selected observation, so its link is shown below. It is a narrow phrase search, not a broad web search for every mail server. The zero application and title results show that the selected product-name fingerprints are weak in this index view.

The right conclusion is that Maddy inventory needs protocol and infrastructure evidence. A team should compare its owned MX records and certificates against service reachability, then verify which hosts run Maddy. If the only evidence is a documentation page, the asset remains unconfirmed until an authorized endpoint provides stronger evidence.

References

Top comments (0)