Authentication context
Review SPF, DKIM and DMARC evidence for received messages.
Maail Protect · SecurityPlanned
Give your team a clearer view of suspicious mail.
Bring sender authentication, impersonation and content signals together before choosing a response.
What you can build
Email Security API for Phishing & Spoofing Signals
Review suspicious messages. Explore the planned capabilities below.
Impersonation signals
Inspect display-name abuse and lookalike sender domains.
Phishing indicators
Combine URL and content evidence with deterministic rules.
Explicit actions
Define when to allow, flag, quarantine or reject under your policy.
Mail-filter integration
Plan Postfix Milter or Rspamd connections with safe defaults.
Reversible rollout
Measure false positives and keep review and rollback paths.
Three steps
A workflow your team can follow.
- Inspect message evidence
- Apply your security policy
- Review and tune outcomes
In practice
Review an unusual payment request
A display name resembles a supplier, but the sender domain differs. Flag the message for review and verify the request through an established channel.
Combine security with classificationWhat is included in the wider product direction?
Evaluate filter integrations and action policies against your own false-positive requirements.
Can DMARC alone stop phishing?
DMARC evaluates authentication alignment for the visible sender domain. Lookalike domains, compromised accounts and display-name impersonation need additional controls and review.
Can I integrate this product today?
This product scope is planned. Discuss your requirements with us to confirm available components, processing terms and integration timing. The public DNS tools can be used without an account.
Start with the task you want to simplify.
Tell us which messages, systems and decisions need to connect.