An email-security detector should say exactly which evidence supports its label, and where the public internet stops revealing the true deployment.
Start with the mail path
MX records publish the addresses to which other mail servers should route incoming messages. They are usually the first useful public source for detecting secure email gateways. A direct Microsoft MX suggests Microsoft mail routing, while a validated Mimecast, Proofpoint, Hornetsecurity or other gateway fingerprint indicates an upstream delivery layer.
dig +short MX example.com
Use provider fingerprints, not broad brand keywords
Recognize controlled routing hostnames and validate new patterns against vendor documentation or audited examples. Matching a company name anywhere in DNS is prone to false positives. Preserve the exact exchanger, preference and observed time so the claim can be checked.
| Public record | Evidence role |
|---|---|
| Recognized gateway MX | Inbound mail-routing vendor |
| SPF include | Outbound authorization context |
| Autodiscover CNAME | Mail-platform support clue |
| DKIM CNAME | Signing-provider support clue |
SPF answers a different question
SPF includes show which sending services a domain authorizes. They do not prove who filters inbound messages. A provider might appear in SPF because it sends transactional or outbound mail while an entirely different gateway receives inbound mail.
Gateways can hide the Workspace
Proofpoint, Mimecast, Hornetsecurity and other gateways may conceal whether Microsoft 365 or Google Workspace hosts the eventual mailboxes. Secondary Entra ID, Autodiscover or DKIM signals can support an inference. Entra alone must not become a blanket Microsoft 365 mail classification.
API-based security is different
Some email security products integrate through Microsoft 365 or Google Workspace APIs rather than modifying public MX records. Their absence from the MX record is not evidence that they are not deployed. Externally, the result is often simply not observable.
A useful confidence hierarchy
Prefer directly observed routing over supporting signals, keep unknown as a legitimate state and record conflicts. A classification should retain the underlying DNS evidence and detection-rule version for future audits.
Why MSPs care
An incumbent gateway can inform a discussion about migration, managed administration or integration. It cannot prove operational shortcomings, renewal dates or buyer intent. Use Scan Prospects for known accounts and Find Leads to explore vendor-specific prospect discovery.
Designing a reliable classifier
A provider detector should return structured evidence: MX hostnames, matched signature, SPF clues, inferred workspace signals, timestamp and confidence. Maintain the signature mapping in a versioned table and test it against known examples, including Cisco Email Security, Proofpoint, Hornetsecurity and alternative Google MX configurations. If two rules conflict, return an explicit ambiguous state until the evidence is examined.
For MSP outreach, a correctly detected vendor supports segmentation and preparation. It does not answer whether the account owns, rents or outsources that product, or whether any API security product is deployed. Keeping those boundaries explicit makes the prospect data more credible to both technical buyers and sales teams.
Turn infrastructure signals into a qualified prospect list.
Analyze domains you already know, or find new companies that match the technologies you target. Public DNS observations support discovery, not proof of an internal security weakness.