Topic · Authentication
DMARC aspf tag
The DMARC aspf tag controls relaxed or strict matching for the SPF-authenticated domain.
How it works
aspf=r allows organizational-domain alignment; aspf=s requires exact domain equality for the envelope-based SPF identifier.
What can go wrong
Vendor-managed bounce domains can pass SPF yet fail strict alignment with the visible From address.
What to check or do
Test envelope domains from each sender and confirm whether SPF alignment is needed alongside DKIM alignment.
How to investigate DMARC aspf tag
- Signal to investigate
- SPF passes for bounce.service.example.com but does not align with the visible From domain under strict mode.
- Evidence to collect
- Check aspf=r or aspf=s in the effective DMARC record and the actual RFC5321.MailFrom used by the provider.
- Common wrong conclusion
- Changing SPF includes cannot change the envelope domain the provider actually transmits.
How to interpret the evidence
SPF alignment depends on both authentication success and a domain comparison. Some services offer custom MAIL FROM domains; others depend on aligned DKIM to satisfy DMARC.
What to change and how to verify it
Use supported custom return-path settings or aligned DKIM, then inspect a received header to confirm the outcome.
Put this into practice
Run a focused check, then explore protection if your domain needs it.