Cookies on this site

We would like to use cookies to understand how the site is used and to measure our campaigns. Nothing is set until you choose, and you can change your mind at any time from “Cookie settings” at the foot of every page. Privacy policy

Contact UsContact Us

Resources / Blogs

Security & compliance

Explaining DMARC, DKIM and SPF DNS Records

Learn how SPF, DKIM, and DMARC email authentication protocols protect your domain from phishing, spoofing, and improve email deliverability with best practices.

· · 3 min read

Implementing robust email authentication protocols is essential for protecting your organization’s domain from phishing, spoofing, and other malicious activities. By configuring SPF, DKIM, and DMARC records in your DNS settings, you enhance the credibility and security of your email communications.​

Understanding SPF, DKIM, and DMARC Records

  • SPF (Sender Policy Framework): An SPF record is a DNS TXT record that specifies which IP addresses and mail servers are authorized to send emails on behalf of your domain. This helps receiving mail servers verify the legitimacy of incoming emails, reducing the risk of spam and phishing attacks.
  • DKIM (DomainKeys Identified Mail): DKIM adds a digital signature to your emails using public-key cryptography. This signature allows the recipient’s mail server to verify that the email content has not been altered and confirms the sender’s identity, thereby enhancing email integrity and authenticity.
  • DMARC (Domain-based Message Authentication, Reporting, and Conformance): DMARC builds upon SPF and DKIM by providing a mechanism for domain owners to publish policies on how to handle emails that fail authentication checks. It also offers reporting capabilities, enabling you to monitor and improve your email authentication practices.

Benefits of Implementing These Email Authentication Methods

  1. Protect Against Phishing and Spoofing: By implementing SPF, DKIM, and DMARC, you reduce the risk of attackers sending fraudulent emails from your domain, thereby protecting your brand reputation and your recipients from potential scams.​
  2. Improve Email Deliverability: Authenticated emails are more likely to be trusted by receiving mail servers, reducing the chances of your legitimate emails being marked as spam.​
  3. Gain Visibility into Email Usage: DMARC reports provide insights into who is sending emails on behalf of your domain, allowing you to identify and address unauthorized use.​

Best Practices for Configuring SPF, DKIM, and DMARC Records

  1. Simplify Your SPF Record: Ensure that your SPF record includes only the necessary IP addresses and servers authorized to send emails on behalf of your domain. Overly complex SPF records can lead to errors and impact email deliverability.
  2. Avoid the “+all” Mechanism in SPF: The “+all” mechanism in SPF records allows any IP address to send emails on behalf of your domain, defeating the purpose of SPF and potentially leading to domain abuse.
  3. Use Appropriate CIDR Notation: When specifying IP address ranges in your SPF record, use CIDR notation with ranges between /30 and /16 to maintain precision and control over authorized senders.
  4. Use 2048-bit DKIM Keys: Ensure your DKIM keys are at least 2048 bits in length to enhance security and comply with current standards.
  5. Regularly Rotate DKIM Keys: Periodically rotating your DKIM keys (at least annually) helps maintain security by limiting the exposure time of any single key.
  6. Start with a DMARC Policy of ‘None’: Begin by setting your DMARC policy to ‘none’ to monitor your email streams without affecting email delivery. This allows you to gather data on legitimate and fraudulent email activities.
  7. Gradually Enforce DMARC Policies: Once you have sufficient data, you can move to a ‘quarantine’ policy to direct suspicious emails to the spam folder, and eventually to a ‘reject’ policy to block them outright.
  8. Monitor DMARC Reports: Regularly analyze DMARC reports to identify and address any issues, ensuring that your email authentication mechanisms are functioning correctly.
  9. Educate Your Team: Ensure that your IT and security teams are knowledgeable about email authentication protocols and understand how to implement and maintain them effectively.​

Conclusion

Implementing SPF, DKIM, and DMARC records is essential for securing your organization’s email communications. These protocols work together to authenticate your emails, protect your domain from misuse, and enhance your overall email deliverability. By following best practices and regularly monitoring your email authentication status, you can maintain a robust defense against email-based threats.

For expert assistance in setting up and optimizing your email authentication protocols, consider reaching out to our team of specialists. We offer comprehensive services to ensure your organization’s emails are secure, trusted, and effectively delivered.

← All articles

Case studies

Microsoft Consulting in practice

Client names are withheld. We are happy to share details on a call.

All case studies
  • Delivered

    600k files, < 3 days

    Document management

    Microsoft

    600,000 documents moved from ImageRight to SharePoint in under three days

    A one-file-at-a-time script would have needed about 22 days of continuous running. We rebuilt the migration around a SQL work queue with parallel uploads, automatic retries and crash recovery, and it finished unattended in under three days.

    • 1,125 → 8,314 files per hour
    • Under 3 days instead of about 22
  • Product

    Every prompt screened

    Any industry on Microsoft 365

    Microsoft

    AI activity and data posture for Microsoft 365

    Sentinel watches Copilot and Copilot Studio agents in a Microsoft 365 tenant. It logs prompts and tool calls, scores each agent's risk, flags oversharing and stale access, and screens prompts for injection attempts with a classifier that runs locally at no per-call cost.

    • Every agent prompt screened
    • Runs inside the customer's own Azure tenant
  • In production

    Hours → minutes

    Food manufacturing

    AI Consulting

    Document intake agent for a national food cooperative

    A Copilot Studio agent reads certificates of analysis as they arrive in the quality team's inbox, extracts 14 fields with AI Builder, checks them, files the PDF in SharePoint and posts a summary in Teams. Fields it is unsure about go to a person instead of being guessed.

    • Hours of daily filing down to minutes
    • 14 fields per document, validated

Keep reading

All Security & compliance articles

See what Copilot and your users can reach

A 30-minute demo of Princeton Sentinel on sample data: AI activity and data posture across Microsoft 365, with the engineers who build it.