Relaxed vs strict alignment
Relaxed alignment, the default, accepts an SPF or DKIM domain that shares the same organizational domain as your From domain: mail.example.com, bounces.example.com, and example.com all align with each other. Strict alignment accepts only an identical domain. You set the mode separately for DKIM (adkim) and SPF (aspf). Most domains are better off staying relaxed. Strict is for specific cases, and switching to it without checking your reports is a quick way to break mail that used to pass.
What alignment is, and why DMARC needs it, is in Identifier alignment for SPF and DKIM.
What adkim and aspf do
Both tags are optional in your DMARC record, and both default to r:
| Tag | Applies to | r (relaxed, default) |
s (strict) |
|---|---|---|---|
adkim |
The DKIM d= domain |
Same organizational domain as From | Identical to the From domain |
aspf |
The SPF (MAIL FROM) domain | Same organizational domain as From | Identical to the From domain |
Relaxed alignment means the From domain has the same organizational domain as the authenticated domain. Strict alignment means they are identical. Comparisons ignore case.
The two tags are independent. This record keeps DKIM relaxed and makes SPF strict:
_dmarc.example.com. TXT "v=DMARC1; p=none; aspf=s; adkim=r; rua=mailto:dmarc-reports@example.com"
If you leave both out, you get relaxed for both. That's what most records do. The full tag list is in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.
Does a subdomain align with my main domain?
Under relaxed alignment, yes, in any direction. The authenticated domain can be a subdomain of the From domain, the parent of it, or a sibling. Under strict, none of these align.
| From domain | Authenticated domain | Relaxed | Strict |
|---|---|---|---|
example.com |
bounces.example.com (MAIL FROM) |
Aligned | Not aligned |
marketing.example.com |
example.com (DKIM d=) |
Aligned | Not aligned |
news.example.com |
foo.example.com |
Aligned | Not aligned |
news.example.com |
news.example.com |
Aligned | Aligned |
news.example.com |
foo.example.net |
Not aligned | Not aligned |
These rows follow the usual alignment rules.
Two vendor wordings are looser than the standard. Google describes relaxed mode as the From domain having to "match or be a subdomain of" the other domain, which reads as one direction only. Microsoft describes it as "root domains" having to match, which gets fuzzy for domains like example.co.uk. The rule to go by is "same organizational domain."
How the organizational domain is found now
The older standard found the organizational domain with a Public Suffix List. The current standard dropped that. Receivers now do a DNS tree walk: they look for DMARC records from the domain upward, with a cap of eight queries, and pick the organizational domain from what they find.
For a typical setup, one DMARC record at example.com and none on its subdomains, the answer is still example.com. Setups with records on several levels, or with the newer psd tag, can get more involved, and a receiver still using the old list-based method might arrive at a different answer in edge cases. Subdomain records and inheritance are covered in Subdomain policy (sp).
Why most domains stay relaxed
In practice, nearly all domain owners have found relaxed alignment sufficient to meet their needs. Relaxed alignment typically provides sufficient spoofing protection. Strict alignment can result in messages from associated subdomains being rejected or sent to spam.
Relaxed alignment is what lets everyday setups pass:
- Microsoft 365, an ESP, or your own servers using a bounce subdomain such as
bounces.example.comfor MAIL FROM. - A vendor signing DKIM with
d=mail.example.comwhile the From address is@example.com. - A marketing platform sending from
news.example.comwith DKIM forexample.com.
Under strict, each of those stops aligning.
When strict alignment makes sense
Google suggests considering strict alignment when:
- mail is sent for your domain from a subdomain outside your control, or
- you have subdomains that are managed by another entity.
Here's why that matters. Under relaxed alignment, if someone gains control of the SPF record or DKIM keys for any subdomain of your organizational domain, they can send mail that passes DMARC for the parent domain. Think of an agency, a former vendor, or a team you don't manage that still holds DNS for promo.example.com. Strict alignment, with explicit DMARC records on every From domain you use, closes that gap. Strict alignment, with a DMARC record on every From domain you use, also avoids the cases where receivers arrive at different organizational domains.
So strict is a trade-off: tighter, at the cost of having to align every sender to the exact domain it sends as.
Before you switch to strict
- Pull your aggregate reports. For each source, the reports show the MAIL FROM and DKIM
d=domains evaluated and whether they aligned. Walk-through in A field-by-field walk-through of a DMARC aggregate report. - List every domain that would stop aligning. Bounce subdomains and vendor
d=subdomains are the usual ones. - Remember only one needs to align. A message still passes DMARC if the other mechanism aligns. Microsoft points this out: a strict SPF failure doesn't matter if DKIM aligns. Making
aspf=swhile every source has exactly aligned DKIM is far less risky than making both strict. - Change one tag at a time and watch the next few days of reports.
Mistakes worth avoiding
- Setting
aspf=swhile a service bounces from a subdomain. Microsoft lists this as a common failure:bounces.example.comdoesn't strictly align withexample.com. - Setting
adkim=son the parent domain while a vendor signs withd=mail.example.com. - Copying Google's example record as a template. It includes
adkim=s; aspf=s, while relaxed is typically enough. - Treating strict as "more secure, so better." It only helps if you can align every sender exactly.
When a vendor's mail stops aligning, see Third-party mail fails alignment. Subdomain setups with several services are in Shared domains and multi-service setups, and subdomain policy surprises in Subdomain policy is not doing what we expected.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
What's the default alignment mode?
Relaxed, for both SPF and DKIM, if your record doesn't set aspf or adkim.
Does bounces.example.com align with example.com?
Yes under relaxed alignment. No under strict.
Should I switch to strict alignment?
Only after you've checked every sender in your reports and have a reason, such as subdomains managed by someone else.
Can I make SPF strict and DKIM relaxed?
Yes. aspf and adkim are independent.