Improving Your Security Score
Your SpoofWard security score reflects how well your email authentication is configured. This guide provides practical steps to improve your DMARC compliance score and overall email security posture.
Understanding Your Score
Your security score (0-100) is based on:
- DMARC Pass Rate - % of email passing authentication (40% weight)
- SPF Configuration - Valid SPF record with proper senders (20% weight)
- DKIM Configuration - Active DKIM keys published correctly (20% weight)
- DMARC Policy - Enforcement level (p=none/quarantine/reject) (15% weight)
- DNS Health - Overall DNS record validation (5% weight)
A score above 85 is good; 95+ is excellent.
Step-by-Step Improvement Plan
Step 1: Assess Current State (Week 1)
Start by understanding where you are:
- Open SpoofWard Dashboard → Select your domain
- Note your current score in the overview
- Review breakdown - Which component is lowest?
- Check DNS Health - Review any warnings or failures
- List your senders - Go to Email Sources, screenshot the list
Step 2: Identify Failing Senders (Week 1)
Review your DMARC reports to find authentication failures:
- Go to DMARC → Reports
- Look at the last 7 days
- Identify senders with high failure rate
- Check their status - Authorized or unknown?
- Research each one - Is it legitimate?
Create a spreadsheet:
| Service | Volume | Pass Rate | Status | Next Action |
|---------|--------|-----------|--------|-------------|
| SendGrid | 5,000 | 95% | Authorized | Monitor |
| Unknown IP | 200 | 10% | Unknown | Investigate |
| Office 365 | 50,000 | 100% | Authorized | Monitor |
Step 3: Fix SPF Configuration (Week 1-2)
SPF (Sender Policy Framework) is the foundation:
Current situation assessment:
- DNS → Records - Look at your current SPF record
- Check validity - Does it start with
v=spf1? - Count DNS lookups - Use the SPF Flattener tool
- Identify includes - Which mail services are authorized?
To improve:
- Add discovered services - For each authorized sender, add their include:
v=spf1 include:sendgrid.net include:mailchimp.com ~all
- Remove old services - Any includes for services you no longer use?
- Use SPF Builder - Go to Tools → SPF Builder:
- Load your current record
- Add each authorized service
- Review DNS lookup count (max 10)
- Export the optimized record
- Test before publishing:
- Use SPF Checker tool
- Verify no syntax errors
- Confirm lookup count is acceptable
- Update DNS - Publish the new record in your DNS provider
- Wait for propagation - 24-48 hours
- Verify - Use SPF Checker again to confirm
SPF has a hard limit of 10 DNS lookups. If you exceed this, the record fails. Use the SPF Flattener to consolidate if needed.
Step 4: Configure DKIM Keys (Week 2-3)
DKIM (DomainKeys Identified Mail) adds cryptographic signatures:
Assessment:
- DNS → Records - Check DKIM status
- DKIM Checker - Test your keys:
- Go to Tools → DKIM Checker
- Enter each selector (default, selector1, etc.)
- Verify keys are valid
- Identify gaps - Which mail servers lack DKIM?
To improve:
- For known services (Office 365, Google Workspace, etc.):
- Follow their DKIM setup guides
- Generate or provision keys
- Add to DNS with correct selector
- Test with DKIM Checker
- For unknown senders:
- Contact them for DKIM configuration
- Request their DKIM selector and public key
- Publish in DNS
- Test
- For internal mail servers:
- Configure DKIM signing
- Generate or obtain private key
- Publish public key in DNS
- Ensure From header domain matches
- Verify configuration:
- Send test email from each sender
- Check DMARC reports 24 hours later
- Confirm DKIM now passes
Step 5: Update DMARC Record (Week 3)
Ensure your DMARC record is properly configured:
Current record:
Go to DNS → Records and verify your DMARC record exists at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
Improve it:
- Reports pointing to SpoofWard? - Ensure
rua=mailto:[email protected] - Forensic reports enabled? -
ruf=mailto:[email protected]recommended - Failure reporting -
fo=1sends forensic reports on any failure - DKIM alignment - Consider
adkim=r(relaxed, default) oradkim=s(strict) - SPF alignment - Consider
aspf=r(relaxed, default) oraspf=s(strict)
Use DMARC Generator (Tools → DMARC Generator) to validate:
- Paste your record
- Tool validates syntax
- Shows interpretation of all fields
- Highlights any issues
- Suggests improvements
Step 6: Address DNS Health Warnings (Week 3-4)
Resolve any DNS issues:
- Go to DNS → Health Report
- Review warnings - Yellow or red items
- For each issue:
- Read the description
- Follow the recommendation
- Fix in your DNS provider
- Wait for propagation
- Re-check
Common fixes:
- SPF syntax error - Copy exact SPF record from SPF Builder
- DKIM key incomplete - Ensure full public key is published
- MTA-STS missing - Use MTA-STS Wizard to set up
- BIMI record invalid - Use BIMI Wizard to configure
Step 7: Authorize and Block Senders (Week 4)
Classify your senders:
- Go to Email Sources
- For each sender:
If legitimate:
- Click → Authorize
- Removes from "investigate" list
- Add note: "Our marketing platform" or similar
If suspicious:
- Click → Block
- Flags as unauthenticated
- Add note: "Blocked due to suspicious activity"
If unsure:
- Click → Investigate
- Research the IP and organization
- Decide authorize/block based on findings
Score Improvement Timeline
Week 1: Baseline
- Assess current score
- Identify low-performing components
- Create action plan
Week 2: SPF Configuration
- Review and validate SPF
- Add discovered services
- Test and deploy
- Expected improvement: +10-15 points
Week 3: DKIM Configuration
- Set up DKIM for all senders
- Publish keys
- Test
- Expected improvement: +15-20 points
Week 4: Cleanup & Validation
- Update DMARC record if needed
- Fix DNS health issues
- Authorize/block senders
- Expected improvement: +5-10 points
Total potential improvement: 40-50 points
Targeting Score Improvements
From 60→75 (Critical)
Focus: SPF and DKIM basics
- Ensure DMARC record exists and is valid
- Add major senders to SPF
- Publish DKIM keys for main mail servers
- Fix any DNS validation errors
Estimated time: 1-2 weeks
From 75→85 (Important)
Focus: All senders configured
- Identify and configure ALL senders
- Ensure DKIM alignment for all services
- Optimize SPF lookup count
- Enable proper failure reporting
Estimated time: 2-3 weeks
From 85→95 (Excellence)
Focus: Enforcement readiness
- Verify 95%+ pass rate
- Set up monitoring and alerts
- Plan enforcement roadmap
- Implement threat intelligence
Estimated time: 3-4 weeks
From 95→100 (Perfect)
Focus: Optimization
- Set up MTA-STS and BIMI
- Implement advanced threat detection
- Regular monitoring and updates
- Maintain enforcement status
Estimated time: Ongoing
Using Improvement Tools
SPF Flattener
If you have too many SPF includes:
- Tools → SPF Flattener
- Paste your SPF record
- Tool expands all includes to IP addresses
- Shows total DNS lookups
- Can generate flattened record
When to use: Only if exceeding 10 DNS lookups
Policy Assistant
For enforcement readiness:
- Tools → Enforcement Wizard (Pro+ plans)
- Guides you to p=quarantine when ready
- Then to p=reject when appropriate
- Handles DNS updates automatically
DNS Checker
Validate all DNS records:
- Tools → DNS Checker
- Enter your domain
- Scans all email auth records
- Shows status and issues
- Provides fix recommendations
Monitoring Progress
Weekly Check
- Dashboard - Review your score (should trend upward)
- DMARC Reports - Check pass rate trend
- Email Sources - Any new senders to configure?
- DNS Health - Any new warnings?
Monthly Review
- Detailed Report - Generate full report from SpoofWard
- Stakeholder Update - Share progress with team
- Identify Blockers - What's preventing further improvement?
- Plan Next Steps - Month 2-3 goals
Before Enforcement
Before moving to p=quarantine:
- Confirm 95%+ pass rate for 2+ weeks
- No critical DNS issues (score above 85)
- All senders identified and configured
- Team approval - Get management sign-off
- Backup plan - Know how to revert if needed
Common Improvement Scenarios
Scenario: Email from Mailchimp failing
Problem: You use Mailchimp but emails fail DMARC
Solution:
- Add to SPF:
include:mailchimp.com - Set up Mailchimp DKIM (in Mailchimp settings)
- Add DKIM record to DNS
- Wait 48 hours
- Verify in DMARC reports
- Score should improve
Scenario: Internal mail server failing
Problem: Your company's mail server sends from your domain but fails authentication
Solution:
- Configure server to include DKIM signing
- Add its IP to SPF:
ip4:203.0.113.5 - Publish DKIM key
- Test with internal test email
- Verify in DMARC reports
- Score improves
Scenario: Too many SPF includes
Problem: Your SPF record hits DNS lookup limit (>10 lookups)
Solution:
- Remove unused services from SPF
- Consolidate services (use vendor aggregates if available)
- Use SPF Flattener for critical includes
- Consider moving to Hosted DNS (Pro+ plans)
Advanced Improvements (Pro+ Plans)
Threat Intelligence
- Go to DMARC → Threat Intelligence
- See flagged IPs and threats
- Block malicious senders
- Create alert rules for threats
BIMI Setup
- Go to Tools → BIMI Wizard
- Create or upload your logo
- Generate BIMI record
- Publish in DNS
- Logo displays in supported email clients
MTA-STS Configuration
- Go to Tools → MTA-STS Wizard
- Create policy file
- Configure HTTPS
- Publish record
- Require TLS for inbound email
Benchmarks
Industry Average: 72 score
- Most organizations are in p=none
- Many have incomplete SPF/DKIM
Good Performance: 85+ score
- Proper SPF/DKIM for major senders
- Planning enforcement
Excellent Performance: 95+ score
- Complete sender configuration
- Likely in enforcement (p=quarantine or p=reject)
- Advanced features enabled
Your target: 95+ to reach enforcement level
Related Documentation
- DNS Health Score - DNS record validation
- SPF Builder - Build optimized SPF
- DMARC Enforcement Roadmap - Policy progression guide
- Email Source Discovery - Identify senders