Run Your First Deliverability Test ↗
Create a disposable inbox, send one message, and understand the first report without guessing what each state means.
2 min readLanguage
Open the Academy in your preferred language.
Deliverlens help centre
Concise troubleshooting for authentication, DNS, reputation and inbox placement—grounded in the evidence you can actually verify.
Published guidance
29 guides found.
2 guides
First-run setup, report basics, and where to begin.
Create a disposable inbox, send one message, and understand the first report without guessing what each state means.
2 min readLearn how to read pass, warning, and fail signals so you can prioritize the changes that matter before you send at scale.
1 min read5 guides
SPF, DKIM, DMARC, BIMI setup and alignment.
Understand why “SPF record not found” appears and fix it with a clean, valid TXT record that passes lookups and aligns with your From domain.
5 min readUse a practical order of operations when authentication checks fail so you fix the sender identity first instead of chasing symptoms.
2 min readResolve missing selectors, wrong public keys, and provider-side signing mismatches that cause `dkim=fail` or `dkim=none`.
1 min readPublish DMARC with the right alignment and reporting tags so you can move from monitoring to enforcement without breaking legitimate mail.
1 min readBIMI depends on stronger prerequisites than a single DNS record. Use this checklist when logos do not appear in inboxes.
1 min read3 guides
Records, routing, MX, and delivery plumbing.
A compact checklist for the DNS and transport records that most affect mailbox trust and delivery consistency.
2 min readReverse DNS and HELO mismatches are classic trust issues for dedicated IPs and self-managed SMTP hosts.
1 min readUnderstand what MX warnings mean during provider migrations, domain onboarding, and routing cutovers.
1 min read2 guides
API keys, account access, and basic customer setup.
Create, rotate, and revoke customer API keys without breaking existing automations or exposing the plaintext token twice.
2 min readUse API keys, test creation, and polling to build pre-send checks into CI, staging, or release workflows.
1 min read2 guides
MTA-STS, TLS-RPT, DANE, and secure transport.
Add transport-policy and reporting records so you can enforce TLS expectations and observe failures in the wild.
1 min readKnow when TLS warnings are informational, when they reflect real delivery risk, and when DANE is worth the operational cost.
1 min read3 guides
IP/domain reputation, blocklists, warming.
A blocklist alert is a symptom, not the whole problem. Use this sequence to confirm the listing, fix the cause, and request removal.
1 min readReputation improves when volume, engagement, and authentication move together. Do not ramp blindly after a setup is technically valid.
1 min readVery new domains can trigger extra scrutiny even when DNS is technically correct. Use this guide when a sender domain is freshly registered or newly repurposed.
1 min read3 guides
Content, SpamAssassin, wording, formatting.
Use this when the message itself is creating risk even after SPF, DKIM, and DMARC are already in good shape.
1 min readSpamAssassin is only one signal, but repeated warnings there often mirror the same issues mailbox providers dislike.
1 min readLarge messages, too many attachments, and image-heavy layouts make deliverability and user experience worse at the same time.
1 min read4 guides
Headers, MIME structure, message layout.
Many “small” email-structure warnings come from missing opt-out headers or weak multipart formatting.
1 min readHeader warnings are easier to fix once you know which system creates them and which ones should remain stable across sends.
1 min readARC warnings matter most when mail passes through forwarders or mailing lists. Use this guide to decide whether the chain is optional, incomplete, or actively broken.
1 min readBulk mail increasingly needs one-click unsubscribe support, not just a footer link. Use this when Gmail or Yahoo flag missing one-click behavior.
1 min read2 guides
Link counts, redirects, safety, external assets.
Too many links or opaque redirect chains make your message look harder to trust, even when the content is legitimate.
1 min readInbox trust improves when the domains inside your message feel consistent with the identity in the From address.
1 min read3 guides
Ongoing monitoring, alerts, and diagnostics.
A single clean test is useful, but a stable pre-send baseline is what protects releases and provider changes over time.
1 min readNot every template tweak needs a full recheck, but DNS, routing, and sender changes definitely do.
1 min readAn analyzer error usually means the message could not be fully processed, not that your mail setup is automatically bad. Use this checklist before retrying or contacting support.
1 min read