How to use Email Authentication Configuration Audit
- Paste one SPF record, one public DKIM key record or DKIM-Signature header, and one DMARC record. The domain field labels this review; nothing is fetched.
- Enter the actual MAIL FROM, header From and DKIM d= signing domains for the scenario. Do not substitute the s= selector or its DNS lookup name for d=.
- For relaxed alignment, supply the organizational-domain boundary determined independently. This simplified model does not discover or verify it.
- Run Review mail records. Separate structural problems, unresolved DNS-dependent terms and the supplied alignment scenario from a real authentication result.
Example: Email Authentication Configuration Audit
Inspect three example records and compare a relaxed SPF domain with a strict DKIM domain.
Options
- Domain the records are published for
- The domain itself. The audit does not fetch it; it only labels the findings.
- SPF record (TXT)
- One record only. include, a, mx, ptr, exists and redirect are counted but never looked up: this page makes no DNS queries.
- DKIM key record or signature header
- A public DNS key record (v=DKIM1) or a DKIM-Signature header (v=1). Public values only; the audit never accepts or stores secrets.
- DMARC record (TXT)
- The record published at _dmarc. The p tag is required for a policy record and v must come first.
- Bounce (MAIL FROM) domain
- The RFC5321.MailFrom domain used by the SPF check in this scenario.
- Header From domain
- The RFC5322.From domain. DMARC compares SPF and DKIM against this domain.
- DKIM d= domain
- Enter the signing domain from d= in the DKIM signature. The selector is s= and is used with that domain to locate a public key; it is not the signing domain.
- Organizational domain for relaxed alignment
- Supply the organizational-domain boundary for this simplified relaxed-alignment comparison. The page performs no DNS policy discovery or public-suffix lookup and does not verify the boundary.
Supported inputs and limits
- A bounded offline subset of record text and a supplied alignment scenario.
- No DNS resolution, recursive SPF evaluation, DKIM message/key-strength validation or deliverability check.
- Direct DNS-dependent SPF terms are counted, but recursive lookup totals remain unresolved.
- DMARC parsing retains legacy tags, including pct, rf and ri; it is not full RFC 9989 validation and does not perform its DNS tree-walk policy discovery.
- No message is authenticated.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Keep a text review separate from mail authentication
SPF include and redirect targets need DNS evidence not available here. A DKIM tag list can describe a key or signature without proving a message passed. Alignment also requires the correct domains: d= is the signing domain, while s= names its selector. Use the structural and unresolved findings to decide which real DNS and message checks remain.
The DMARC standard has changed
RFC 9989 replaced RFC 7489 in May 2026. It uses DNS tree-walk policy discovery and removes legacy pct, rf and ri tags. This page keeps its smaller text parser and manually supplied alignment boundary; it does not implement that discovery or certify a policy against the complete new standard.
Questions about Email Authentication Configuration Audit
Does it check my DNS?
No. Only supplied record text is reviewed.
Does a DKIM record mean a message passed?
No. Message-signature verification is a separate operation.
Can the page infer organizational domains?
No. Supply the supported domain information for relaxed-alignment scenarios.