Email foundations
Read an email authentication header
Find the receiver’s SPF, DKIM, and DMARC observations and keep the three identities separate.
Language
Open the Academy in your preferred language.
The Deliverlens academy
Less guesswork. More useful evidence. Learn how email authentication, reputation and receiving systems fit together—one practical question at a time.
Explore the lessonsFollow a track, or find a specific answer below.
100 published lessons found.
Email foundations
Find the receiver’s SPF, DKIM, and DMARC observations and keep the three identities separate.
Email foundations
Separate server acceptance, inbox observation, and audience engagement in a diagnostic report.
Email foundations
Trace application, sending service, DNS, receiving server, and mailbox filtering boundaries.
Email foundations
Choose one sender and one message, capture a baseline, and record repeatable evidence.
Email foundations
Extract the responding server, enhanced status, and recommended next investigation.
Email foundations
Identify trusted receiver evidence and avoid confusing a relay with the original source.
Email foundations
Document which address serves which purpose before changing authentication settings.
Email foundations
Query the exact record name and compare authoritative and recursive answers.
Email foundations
Prioritize reproducible authentication failures before speculative content edits.
Email foundations
Record every legitimate service, owner, domain, selector, and business use.
SPF, without the guesswork
Inspect the exact sender identity and review one policy without overwriting legitimate senders.
SPF, without the guesswork
Consolidate authorized sources into one reviewed policy and preserve unrelated TXT records.
SPF, without the guesswork
Trace lookup-causing terms and dependencies rather than counting all DNS queries equally.
SPF, without the guesswork
Compare authorization composition with policy delegation using a worked DNS example.
SPF, without the guesswork
Review the meaning and operational tradeoffs of the final all mechanism.
SPF, without the guesswork
Plan a provider change with an inventory, DNS review, and fresh message tests.
SPF, without the guesswork
Follow the connecting-IP change and distinguish it from DKIM and DMARC outcomes.
SPF, without the guesswork
Verify that a retired sender is unused and measure the effect before deleting authorization.
SPF, without the guesswork
Check provider support and the relationship between envelope identity and alignment.
SPF, without the guesswork
Assign ownership and a review checklist for future sending-service changes.