Report Details Deep Dive

Detailed explanation of individual DMARC report components and what they mean for your email security

DMARC Report Structure Breakdown

When you click "View" on any report in your reports list, you'll see a detailed breakdown of that specific DMARC aggregate report. Understanding each section helps you make informed security decisions.

Report Header Information

Field Description Example Significance
Report ID Unique identifier for this report 15714726821611789 Reference for tracking and support
Organization Entity that generated the report google.com, outlook.com Shows which email providers process your domain
Date Range Time period covered by report 2024-01-15 to 2024-01-16 Usually 24-hour periods, helps with timing analysis
Domain Your domain being reported on example.com Confirms which of your domains this report covers
Policy Applied DMARC policy that was in effect p=none, p=quarantine, p=reject Shows what action was taken on failed emails

Authentication Results Explained

SPF (Sender Policy Framework) Results

SPF Pass

Meaning: The sending IP address is authorized in your SPF record.

What it shows:

  • Legitimate email source
  • Proper SPF configuration
  • Email sent from authorized server
SPF Fail

Meaning: The sending IP address is not authorized in your SPF record.

Possible causes:

  • Spoofing attempt
  • Missing IP in SPF record
  • New email service not configured
SPF SoftFail

Meaning: SPF record uses "~all" (soft fail) mechanism.

Action:

  • Investigate sending source
  • Consider strengthening to "-all"
  • Update SPF if legitimate
SPF Neutral

Meaning: SPF record doesn't specify authorization for this IP.

Action:

  • Review SPF record completeness
  • Add missing authorized IPs
  • Consider policy strictness

DKIM (DomainKeys Identified Mail) Results

DKIM Pass

Meaning: Email signature was verified using your DKIM public key.

Indicates:

  • Message integrity preserved
  • Authorized sending source
  • Proper DKIM configuration
DKIM Fail

Meaning: DKIM signature verification failed.

Possible causes:

  • Message tampering
  • Incorrect DKIM selector
  • Missing/invalid DKIM record
DKIM Selector Information

In the detailed report, you'll see DKIM selector information like "selector1._domainkey.yourdomain.com". This tells you which DKIM key was used for signing. Multiple selectors allow for key rotation and different sending sources.

DMARC Alignment

DMARC requires either SPF or DKIM (or both) to be in "alignment" - meaning the authenticated domain matches the "From" header domain.

Alignment Type Relaxed Mode Strict Mode Example
SPF Alignment Organizational domain match Exact domain match required mail.example.com → example.com (relaxed OK)
DKIM Alignment Organizational domain match Exact domain match required newsletter.example.com → example.com (relaxed OK)

Disposition and Policy Actions

Understanding Disposition

Disposition shows what action the receiving email server took based on your DMARC policy and authentication results.

None

Action: No special action taken

Result: Email delivered normally

Policy: Usually p=none or authentication passed

Quarantine

Action: Email marked as suspicious

Result: Likely sent to spam folder

Policy: p=quarantine for failed emails

Reject

Action: Email completely blocked

Result: Email not delivered

Policy: p=reject for failed emails

Policy vs. Disposition

The disposition may not always match your DMARC policy. Email providers can override your policy based on their own rules, reputation systems, or other factors. A p=none policy doesn't guarantee all emails will show "none" disposition.

Source Identification and Analysis

IP Address Information

Each report record includes detailed information about the sending source:

Data Point What It Shows How to Use It
Source IP The IP address that sent the email Identify sending servers, trace origins
Message Count Number of emails from this source Understand volume patterns
PTR Record Reverse DNS lookup of the IP Verify legitimate sending domains
Country/Location Geographic location of the IP Identify unexpected sending locations

Categorizing Email Sources

Legitimate Sources
  • Your organization's mail servers
  • Authorized third-party services (marketing, CRM)
  • Business partner systems
  • Cloud email services you use
Investigate Further
  • Unknown IP addresses
  • Unexpected geographic locations
  • High-volume sources with authentication failures
  • Consumer ISP ranges with business email

Interpreting Report Patterns

Normal vs. Suspicious Patterns

What it means:

Most of your email is properly authenticated and coming from legitimate sources.

Action:
  • Continue monitoring
  • Investigate the remaining failures
  • Consider strengthening DMARC policy

What it means:

Potential spoofing attack or new legitimate service not yet configured.

Action:
  • Investigate the source IP and PTR record
  • Check if it's a new service your organization started using
  • If illegitimate, document as a security incident
  • If legitimate, update SPF/DKIM records

What it means:

Email appearing to come from countries where you don't have operations.

Action:
  • Verify if any legitimate services operate from those locations
  • Check cloud service provider data center locations
  • Investigate authentication failure patterns
  • Consider geographic restrictions if appropriate

Action Items Based on Report Analysis

Immediate Actions

High Priority
  • Investigate unknown high-volume sources
  • Fix authentication for legitimate failing sources
  • Document and report potential security incidents
Medium Priority
  • Update SPF records for new legitimate sources
  • Configure DKIM for third-party services
  • Review and strengthen DMARC policies

Long-term Monitoring

  • Track trends: Monitor authentication success rates over time
  • Baseline establishment: Document normal traffic patterns
  • Policy evolution: Gradually move from p=none to p=quarantine to p=reject
  • Regular reviews: Schedule monthly deep-dive analysis sessions
Expert Analysis Tips
  1. Always correlate report data with your email sending calendar
  2. Keep a whitelist of known legitimate IP ranges for quick reference
  3. Document investigation results for pattern recognition
  4. Set up automated alerts for unusual patterns
  5. Regular coordination with IT and security teams
  6. Use report details to fine-tune DNS record configurations