An email preflight checklist is the set of checks you run before a campaign sends: verify addresses, remove duplicates, confirm SPF, DKIM, and DMARC pass, and test rendering across clients. It catches bounces, spam traps, and broken layouts before they reach inboxes. Run it every send, no exceptions.
Why run a preflight routine at all?
A preflight routine protects your sender reputation. One bad send can spike bounces, hit spam traps, and drag your domain onto a blocklist. Recovery takes weeks. Ten minutes of checks before send is cheaper than a month of throttled deliverability. Every mailbox provider watches how clean your lists are.
Mailbox providers score you on complaint rate, bounce rate, and spam trap hits. Gmail and Outlook both throttle senders who cross their thresholds, and they do not tell you when it happens. A bounce rate above 2% is a red flag. A complaint rate above 0.1% is worse. Keep both under those lines and your inbox placement stays healthy. Preflight is the routine that keeps you there, send after send, instead of firefighting a reputation problem after the damage is done.
Start with list verification and deduping
Your list is the single biggest source of deliverability trouble. Old exports carry dead mailboxes, typos, and duplicates that pile up over months. Start every preflight by cleaning it. Run each address through MX-record and SMTP-level mailbox checks so you know the domain accepts mail and the specific mailbox exists. Drop anything that comes back Invalid. Flag catch-all, role, and disposable addresses as Risky, then decide per campaign whether the upside is worth the engagement hit.
Deduping matters more than people expect. The same contact imported twice means two sends, two chances to annoy, and metrics that no longer add up. Normalize case and trim whitespace before you compare, or '[email protected]' and '[email protected] ' slip through as two records. A quick pass through Free Email Verifier catches bad syntax, duplicates, and disposable domains instantly, and it does that with a local scan that never touches your daily quota. The CSV parses in your browser, so the list never leaves your machine.
How do you check email authentication before sending?
Check authentication by sending a test message to an inbox you control, then inspect the headers. Confirm SPF, DKIM, and DMARC all show pass. SPF authorizes your sending IP. DKIM signs the message. DMARC tells receivers what to do when either fails. All three should align on every campaign.
Authentication is not a one-time setup you can forget. Records drift. A new sending platform, a rotated key, or a stray DNS edit can break DKIM overnight, and you will only find out when open rates crater. Send a seed message before every campaign and read the headers. A free mail-tester service or Google Postmaster Tools will confirm SPF, DKIM, and DMARC in seconds. If your DMARC policy still reads p=none, you are monitoring only. Move to quarantine or reject once every legitimate source is signing correctly.
Test rendering, links, and content
A verified list means nothing if the email looks broken on arrival. Test rendering across the clients your audience actually uses. Gmail, Apple Mail, and Outlook cover most B2B inboxes. Dark mode is the common trap: it flips background colors and can turn dark text invisible. Check it on a real device. Load images with descriptive alt text so the message still reads when a client blocks images by default, which many still do.
Then click every link. One dead CTA or a mistyped UTM tag can waste the entire send. Confirm your unsubscribe link works and resolves in one click, because a broken opt-out is a legal problem under CAN-SPAM and GDPR, not just a courtesy. Run the copy through a spam-score checker and cut the obvious triggers: all-caps subject lines, heavy image-to-text ratios, and link shorteners that receivers distrust. Small fixes here move placement more than most people believe.
Check your list right now, free
10 checks a day with no signup. 100 a day with just your email.
The complete email preflight checklist
Here is the full sequence in order. Work top to bottom, because each check gates the next. Cleaning the list first means you only spend testing time on a send that will actually deliver.
| Preflight check | What it prevents | Pass criteria |
|---|---|---|
| Syntax and duplicate scan | Typos, dupes, obvious junk | Zero malformed addresses |
| MX and SMTP verification | Hard bounces, dead mailboxes | Bounce risk under 2% |
| Spam trap and role filtering | Blocklisting, low engagement | Role and disposable flagged |
| SPF, DKIM, DMARC alignment | Spoofing, auth failures | All three pass on a test send |
| Render and link test | Broken layout, dead CTAs | Clean across major clients |
| Seed and spam-score test | Poor inbox placement | Lands in primary, low score |
That order is deliberate. Authentication before content means a well-built email never lands in spam over a broken signature. List hygiene before everything means your bounce rate is decided before the campaign is even written. Run the sequence the same way every time and it stops feeling like overhead.
How often should you run preflight checks?
Run the full preflight before every campaign. Verify any list that is older than 30 days, since B2B email decays at roughly 2 to 3% per month as people change jobs. Authentication and render tests take minutes once set up. Skipping them is where most bounce problems start.
Build the routine once and it becomes muscle memory. Verify, dedupe, check auth, test rendering, then send. Four checks, about ten minutes, every campaign. Your bounce rate stays under 2%, your domain stays off blocklists, and your messages land where the work is supposed to pay off: the primary inbox.