Infraova
Resources›Guides›How to audit email authentication

Guide

How to audit email authentication

Review SPF, DKIM, and DMARC configuration across a domain and identify authentication gaps.

BusinessAgencyDeliverability·8 min read

The situation

Email authentication — SPF, DKIM, and DMARC — is the foundation of deliverability. Misconfigured or missing authentication causes messages to be rejected, quarantined, or flagged as suspicious.

Before you begin

The domain to audit
A list of all platforms sending email for the domain
Access to Infraova for the automated checks

The operational path

01Scan
02Review SPF
03Review DKIM
04Review DMARC
05Identify gaps
06Fix
07Verify

The goal isn't just to find the error. The goal is to move from detection to a verified infrastructure state.

What could have caused this?

Cause

What changed

Possible impact

New sender not added to SPF

Sending service not authorized

Authentication failure for that sender

DKIM not configured

No signature on outgoing messages

DMARC cannot pass via DKIM alignment

DMARC at p=none

Policy not enforced

Failures logged but not acted on

Step by step

01Run the authentication scan

Infraova checks SPF, DKIM, and DMARC as part of its standard scan. Start by reviewing the current results.

What to check

✓Open the domain in Infraova
✓Review the authentication section of the scan results
✓Note which checks pass and which are flagged
✓Identify the severity of any flagged issues

With Infraova

Infraova checks SPF syntax, lookup count, DKIM key presence and strength, DMARC policy, and alignment configuration.

02Audit SPF configuration

Review SPF to confirm every legitimate sender is authorized.

What to check

✓Pull the current SPF record
✓List every platform sending mail for the domain
✓Confirm each sender is included in the SPF record
✓Count the DNS lookups and confirm the total is under 10
✓Check the policy mechanism
03Audit DKIM configuration

For each sending platform, confirm DKIM is configured and the DNS public key record is present.

What to check

✓List each sending platform and its DKIM selector
✓Look up the DKIM record for each selector
✓Confirm the public key is present and complete
✓Confirm the key length is at least 1024 bits
04Audit DMARC configuration

Review the DMARC policy and confirm it is appropriate for the domain's current authentication maturity.

What to check

✓Pull the current DMARC record
✓Note the current policy (none, quarantine, reject)
✓Confirm a reporting address (rua) is configured
✓Review aggregate reports for failure patterns
05Address identified gaps

For each gap, determine the appropriate fix and move it through the proposal → approval → execution → verification workflow.

What to check

✓Prioritize gaps by severity and sending impact
✓Use Infraova's proposals for DNS-based fixes
✓Configure sending platform settings where DNS changes are not sufficient
✓Verify each fix after application

You decide. Infraova executes.

Infraova can propose and execute an approved infrastructure change, but it does not independently decide to modify client infrastructure. Every proposed change requires explicit authorization before execution.

Infraova detects
↓Infraova diagnoses
↓Infraova proposes
↓YOU APPROVE
↓Infraova executes
↓Infraova verifies

Key takeaway

An authentication audit should be repeated whenever a new sending platform is added or a DNS change is made. Infraova makes the ongoing check automatic.

Turn this playbook into a continuous workflow

Without Infraova

Someone discovers the issue
↓Someone investigates manually
↓Someone decides what to do
↓Someone makes the change
↓Someone checks whether it worked

With Infraova

Monitor
↓Detect
↓Prioritize
↓Propose
↓Approve
↓Remediate
↓Verify
↓Record

The guide teaches you how to solve the problem once. Infraova keeps watching for it after you're done.

Want the product-level details?

Guides answer "How do I solve this?" Documentation answers "How does Infraova work?"

Stop discovering infrastructure problems manually.

Infraova continuously monitors your client and business infrastructure, identifies meaningful problems, proposes the next action, executes approved changes, and verifies the result.