The infrastructure layer, in order of likelihood
| Cause | What it looks like |
|---|---|
| Authentication (SPF/DKIM/DMARC) | Missing, misconfigured, or expired DNS records for your sending domain - inbox providers can't verify the mail is legitimately yours |
| Sending domain reputation | A shared or newly warmed domain with a history of complaints, spam-trap hits, or bounce spikes |
| List hygiene | Sending to long-unengaged, hard-bounced, or purchased/imported addresses that trigger spam-filter heuristics |
| Suppression-list gaps | Previously-unsubscribed or complained addresses re-entering the send pool through a data-sync error (see our segmentation guide) |
| Sudden volume changes | A large, unwarmed send spike (e.g. a list import or a Black Friday blast without a warm-up plan) |
What a deliverability diagnostic covers
- DNS record verification for SPF, DKIM, and DMARC alignment against your actual sending domain
- Suppression-list reconciliation against unsubscribe, complaint, and hard-bounce history
- Engagement-based list segmentation review - are you still mailing addresses that haven't opened in a year?
- Sending-domain and IP reputation signals available through postmaster tools and Klaviyo's own deliverability reporting
The deliverable is a prioritized fix list with the DNS/config changes specified exactly. Implementing send-cadence or content changes based on the findings is a marketing decision.