Identity and sender checks
Protected-name mismatch and supported own-domain DMARC failures can contribute identity signals. SPF, DKIM and DMARC results remain distinct checks.
EMAIL SECURITY · PACKAGE 2
Business Email Compromise (BEC) protection
A fraudulent payment request may contain no malicious file. BEC and impersonation checks help your IT team review supported identity, similar-domain and payment-pressure signals before incoming email reaches your server.
An everyday example
A message asks finance to change bank details urgently and sends replies to an unrelated address. The supported combination of payment language, pressure and an identity or Reply-To signal can select the configured payment-risk action.
Illustrative scenario; this is not a live message or a detection-rate claim.
How it works
- Define trusted identitiesConfigure protected display names and their approved sender addresses for the domain. Protected-name matching requires these entries.
- Evaluate supported signalsChecks compare sender and Reply-To domain lookalikes with the recipient domain and evaluate supported identity and payment-risk combinations.
- Apply the saved policySeparate actions cover identity, similar domains, payment risk and incomplete analysis. The final message decision can also include other security policies.
What your IT team can control
Lookalike domains
Supported Sender and Reply-To similarity checks can flag a domain resembling the recipient domain. A similar-domain rule has its own action.
Payment-risk combinations
Bounded English/Turkish text heuristics combine payment or bank-change language with pressure and supported identity/Reply-To evidence. A different Reply-To alone does not select a blocking action.
Coverage and responsibilities
- These checks do not verify a bank account, authorize a transaction or identify every compromised sender. Legitimate messages can match.
- No eligible body text or no configured protected names limits the observations available. Completed checks do not certify that the sender is trustworthy.
- For a change to payment instructions, verify through a trusted independent channel even when an email has passed its configured checks.
Choose the incoming security gateway
Email Security requires SecuraWall as the only published MX and a separate real receiving destination. Your mailboxes remain with your provider. Backup MX does not include these inspection or personal quarantine controls; the SMTP Relay add-on does not enable incoming protection.
Explore Email Security Compare pricing