
Business IT Advice
Protect the email your customers trust.
Understand domain authentication, investigate delivery problems and keep legitimate business email working.
Separate sender identity from inbox filtering.
Domain authentication helps a receiving mail system decide whether a message is authorized to use your domain. Filtering assesses other signals, including suspicious content. Both matter, and neither guarantees that every harmful message is blocked or every legitimate message reaches the inbox.
Background: Microsoft’s email authentication overview.
Three records with different jobs
SPF: authorized sources
A DNS record identifies the mail servers authorized to send for an envelope-sender domain. Keep one SPF record per domain and account for all legitimate sending services.
DKIM: signed messages
A sending service signs parts of each message. Receivers use a published public key to check the signature. Use the selectors and DNS values supplied by your actual mail provider.
DMARC: alignment and policy
DMARC checks whether the visible From domain aligns with a passing SPF or DKIM result. Its policy requests how receivers handle failures, and reporting helps you review domain use.
When mail goes to spam or your domain is impersonated
- List every legitimate sender: Microsoft 365, invoicing, CRM, newsletters and other applications.
- Check published records, then examine real message headers to see whether authentication and alignment pass.
- Review changes in sending services, reputation, message content and recipient feedback rather than assuming DNS is the only cause.
- Use DMARC reports to distinguish legitimate configuration gaps from unauthorized use before tightening the policy.
A DMARC monitoring policy does not request rejection of failing messages. Quarantine and reject are enforcement requests; receiving systems still apply their own handling rules. Microsoft explains the policy and alignment requirements.
Check your domain
Start with a public-record check. Treat the result as a starting point for review, not proof that your whole email environment is secure.
Building records? Use the SPF generator or DMARC generator as a drafting aid and validate the result with your mail provider before publishing. DKIM keys and selectors should come from your sending platform.
Questions worth clarifying
Will SPF, DKIM and DMARC stop all phishing?
No. They help receiving systems verify domain use and identify some forged mail. They do not stop every lookalike domain, compromised account, malicious link or social-engineering attempt. Use them alongside filtering, MFA and staff awareness.
Does a passing email security check guarantee inbox delivery?
No. A public DNS check can identify published records, but it does not prove every sending service is correctly configured. Delivery also depends on message content, sender reputation and the receiving system. Review real message headers and legitimate sending sources.
Should we immediately change DMARC to reject?
First identify legitimate sending services and verify their SPF or DKIM alignment. Review reports and move toward enforcement in a controlled way. A reject policy applied before legitimate senders are ready can disrupt business email.
Review your business email security
See our Microsoft 365 management and Cybersecurity Services.
Schedule a conversationReviewed