Email deliverability by audience

Email deliverability problems look different depending on who you are and what you send. An agency managing 20 client domains has different needs than a developer sending transactional email from a SaaS product. This page organizes our guides by audience so you can find the one that matches your use case.

Choose your audience

• Agencies and developers : the complete playbook for keeping every client domain in the inbox. The 7-check audit, the agency and developer workflows, and the 5 mistakes that burn you.
• Agencies : managing multiple client domains, daily monitoring, and the DNS records that break when a client changes their email provider.
• Developers : sending transactional email from a SaaS product, the SPF/DKIM/DMARC records you need, and how to test without sending real email.
• E-commerce : cart abandonment emails, order confirmations, and the DNS records that decide whether your marketing campaigns land in the inbox.
• SaaS : welcome sequences, usage notifications, and the DNS records that keep your product email out of spam.

Or browse by platform

If you use a specific email platform, our email deliverability by platform guide covers the platform-specific gotchas for Shopify, WordPress, WooCommerce, Squarespace, Wix, HubSpot, Salesforce, Mailchimp, Klaviyo, ActiveCampaign, ConvertKit, and GetResponse.

Quick checklist

• MX record exists and points to a valid mail server
• SPF record includes all sending services
• DKIM record is present and the selector matches your setup
• DMARC record exists with p=quarantine or p=reject
• TLS/STARTTLS is enabled on your mail server
• PTR record matches your sending IP

If any of these are missing, run a free audit and get the exact record values to add. Takes 30 seconds. No account needed.

Related guides

• Email deliverability checklist
• Why email goes to spam
• DMARC: what it is and why you need it
• SPF record guide
• Why your DKIM signature is failing

Audited by Inboxproof · live DNS checks · privacy