Deliverability is the combined result of authentication, reputation, audience quality and sending behaviour. Use this checklist before increasing volume or launching an important campaign.
1. Authenticate the sending domain
Publish one valid SPF policy for the envelope-from domain, sign outgoing mail with DKIM and deploy DMARC so receiving providers can align and evaluate those identities. Start DMARC reporting before moving to an enforcement policy.
Check the exact domain and selector used by the sending provider. A record on the root domain does not automatically cover every subdomain or third-party stream.
- SPF resolves without multiple records or excessive lookups
- DKIM signing is active and the public selector resolves
- DMARC alignment matches the domains users see
- DMARC aggregate reports reach a monitored mailbox
- Return-path and tracking domains are intentionally configured
2. Protect domain and transport quality
Confirm MX and TLS readiness, review blocklist evidence in context and separate marketing traffic from business-critical transactional mail. New domains should not jump from zero activity to large daily volume.
A clean technical check is a starting point, not a reputation guarantee. Monitor provider feedback, hard bounces and complaints continuously.
- TLS is available for normal mail transport
- The sending domain has a working website and consistent identity
- Marketing and transactional streams use intentional subdomains
- Daily volume increases gradually and predictably
- Postmaster and provider feedback is reviewed where available
3. Prepare a high-quality audience
Verify addresses, remove duplicates and apply global suppression before scheduling. Segment by source, recency and relevance instead of sending the same message to every record.
Do not re-add an opted-out or complaining recipient because the address later verifies successfully. Deliverability status and messaging permission are separate controls.
- Hard bounces, complaints and unsubscribes are suppressed
- Unknown or stale contacts are reviewed separately
- The audience source and business purpose are documented
- Role accounts and catch-all results follow a defined policy
4. Review content and operational safeguards
Use an accurate sender identity, a clear purpose and a working unsubscribe process. Test the plain-text alternative, links, mobile layout and reply routing before sending.
Set per-mailbox daily limits, local send windows and stop rules for replies, bounces and complaints. A campaign should pause automatically when its quality signals move outside agreed thresholds.
- From name, reply address and company identity are accurate
- Unsubscribe is visible, functional and honoured immediately
- Links use trusted HTTPS domains
- Mobile and dark-mode previews remain readable
- Automatic stop and alert thresholds are configured
Frequently asked questions
Do SPF, DKIM and DMARC guarantee inbox placement?
No. They establish authenticated identity and policy signals. Reputation, audience quality, content and recipient engagement still influence placement.
Should marketing and transactional email use the same domain?
Using intentional subdomains or streams can reduce operational coupling, but each domain still needs correct authentication, monitoring and alignment.
What should stop a campaign automatically?
At minimum, hard bounces, complaints, opt-outs and direct replies should trigger suppression or stop rules. Teams should also define thresholds for unusual failure rates.
Apply this workflow in WorldsContact.
Start with 500 opening credits and keep every action visible in one workspace.