NewsletterDeliverabilityKit / report
NewsletterDeliverabilityKit report: demo-letter.example
Demo report on a fictional sample site.
67 / 100
6 of 14 checks need attention (1 high priority).
- ✓ Gmail/Yahoo bulk-sender DNS basics (SPF + DKIM + DMARC) (high): SPF yes, DKIM yes, DMARC yes.
- ✓ Email provider authorized in SPF (high): Mailgun (used by Substack and Ghost), SendGrid, Google Workspace, Microsoft 365
- ✓ Exactly one SPF record (high): 1 SPF record(s).
- ✗ SPF under the 10 DNS-lookup limit (recursive) (high): 12 lookups counting nested includes.
- ✗ SPF ends with ~all or -all (medium): Ends with ?all
- ✓ DKIM published for your sender (high): google
- ✓ DMARC record (high): v=DMARC1; p=none; pct=50
- ✗ DMARC enforcing (quarantine or reject) (medium): p=none
- ✗ DMARC applies to 100% of mail (low): pct=50
- ✗ DMARC aggregate reports (rua) (low): Missing.
- ✗ BIMI logo record (optional) (low): Not published (needs DMARC enforcement).
- ✓ MX records (replies and bounces have a home) (medium): mx.demo-letter.example
- ✓ Reverse DNS on the domain's mail servers (low): 198.51.100.9 → mx.demo-letter.example
- ✓ Mail server IPs not on SpamCop or PSBL (medium): 1 IPs clean.
Read-only public DNS lookups only; nothing is sent. Bulk-sender rules also require one-click unsubscribe and a low spam-complaint rate, which DNS cannot show. Provider DKIM selectors vary; copy exact values from your email provider. Blocklists checked: SpamCop and PSBL. Not a guarantee of inbox placement.