Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Checklists

Email Sending Domain Setup Checklist

A setup checklist for a new email sending domain or platform: SPF, DKIM and DMARC, alignment, unsubscribe headers, warm-up, suppression and verification.
Checklistintermediate6 min readUpdated

When to run this checklist

Run it when a business starts sending marketing or transactional mail from a domain or subdomain it has not sent from before, when it moves from one email platform to another, and when it adds another service that sends as the brand: a CRM, a helpdesk, an invoicing tool, an events platform. Each new sender needs its own place in the SPF record and its own DKIM signing, and each one can quietly break DMARC alignment for the rest.

The list is run by whoever manages the email platform, with the person who controls the domain's DNS records for the authentication group, since most of those lines are DNS changes that marketing cannot make alone. It is a one-off setup gate. Checking each campaign before it goes out is the email campaign QA checklist, which assumes this setup is already done, and assessing the whole programme's health over time is the email programme audit.

Before you start

  • DNS access, or the person who has it, booked for the time needed to publish and check records.
  • A list of every service that sends mail as the domain, including the ones marketing does not own, such as the finance team's invoicing tool.
  • The new platform's authentication settings, with the SPF include and DKIM records it asks for.
  • The contact export from the old platform, with consent records and the suppression lists (unsubscribes, hard bounces, complaints) as separate files.
  • Seed addresses at the major mailbox providers, and a way to read the full message headers.
  • A warm-up plan: which segments are mailed first and how sending grows, agreed before the first send.

The checklist

The groups follow the order a domain is set up: prove identity, configure sending, build reputation, load the list, then verify. Authentication comes first because mailbox providers check it on every message; nothing in the reputation group helps a domain whose mail fails authentication.

0/14

Authentication

Sending setup

Reputation

Verification

Where each check is explained

The widget keeps each line short enough to tick; the reasoning sits in the guides. Each check links to the page that explains it.

CheckExplained in
Publish an SPF record that lists every service sending for the domainEmail deliverability
Turn on DKIM signing with the platform's keysEmail deliverability
Publish a DMARC record starting with a monitoring policyDMARC failing
Align the visible from domain with the authenticated domainDMARC failing
Use a dedicated subdomain for marketing mail where volume justifies itEmail deliverability
Set up one-click unsubscribe headers for bulk mailEmail deliverability
Use a monitored reply-to addressNewsletter design and copy
Warm up the new domain or IP with the most engaged contacts firstEmails going to spam
Register the domain with mailbox provider postmaster toolsEmails going to spam
Set bounces and complaints to suppress automaticallyEmail bounce rate too high
Import only contacts with a consent recordList building and consent
Carry suppression lists across from the old platformEmail list hygiene SOP
Send tests to the major mailbox providers and check the headers passDMARC failing
Read DMARC reports before tightening the policyDMARC failing

If an item fails

An authentication failure stops the first send. Mail that fails SPF or DKIM, or passes both without aligning with the visible from domain, fails DMARC, and the major mailbox providers' sender requirements treat that as a reason to filter or reject bulk mail. Fix the record, wait for DNS to update, and send a fresh test to every seed address; a record that looks right in the DNS tool can still fail in a real header because of a typo in an include or a second, conflicting SPF record. The DMARC failing guide walks through reading the headers. If customers then report missing receipts or password resets from a shop, booking or account system, the diagnosis for order and account emails not arriving traces which system failed.

List and consent failures also stop the send. Importing contacts without a consent record, or leaving unsubscribes and complaints behind on the old platform, means mailing people who said no, which is a compliance problem first and a Deliverability problem second: those are exactly the people most likely to report the mail as spam, and the Spam Complaint Rate on a domain with no history moves fast. Where consent records are thin, a re-permission email or a Double Opt-In step for the doubtful segment is safer than importing everyone.

Reputation and sending setup lines can sometimes ship with a plan. Postmaster tool registration can be completed in the first days of sending, and a dedicated subdomain may not be worth it for a small sender. The warm-up line is not one to skip: a new domain that sends to its whole list on its first day gives mailbox providers no reason to trust it.

Illustrative example — not a real result

A rug retailer changes email platform

Wraybarrow Rugs, an online rug retailer, moves from one email platform to another and plans to send its autumn catalogue from the new platform the following week. The authentication group fails on alignment: SPF and DKIM both pass, but for the platform's own shared domain rather than the shop's, so DMARC fails. The DKIM records for the shop's domain are published and the test is resent. The list group fails too: the export carried the active contacts but not the old platform's suppression list of some three thousand unsubscribes and hard bounces, which is imported before anything else. The catalogue goes first to customers who opened in the past quarter, and to the wider list over the following fortnight once complaint and bounce figures in the postmaster tools look settled.

Common mistakes

  • Two SPF records. The new platform's record is added beside the old one instead of merged into it, and both fail.
  • Passing without aligning. SPF and DKIM pass for the platform's domain, the from address uses the brand's, and DMARC fails anyway.
  • Forgetting the other senders. The invoicing tool and the helpdesk are left out of SPF, and moving DMARC to a stricter policy sends their mail to spam.
  • Tightening the DMARC policy at the start. The policy is set to reject before anyone has read a single report, and legitimate mail from an unlisted service disappears.
  • Leaving suppressions behind. The migration carries the contacts and drops the list of people who asked not to be mailed.
  • Sending to everyone at once. The new domain's first send goes to the full list, including contacts who have not opened in years.

The email campaign QA checklist takes over for every send once the domain is set up, and the checklists library holds the rest.

Terms used on this page

Where this page is used

Also related

Sources

  1. Email sender guidelines — Google Workspace Admin Help
  2. RFC 8058: Signaling One-Click Functionality for List Email Headers — IETF
  3. DMARC overview — DMARC.org
  4. Messaging, Malware and Mobile Anti-Abuse Working Group — M3AAWG

Related