When a domain is actually ready for its first cold email campaign

Warm-up alone doesn't mean ready

A gradual volume ramp fixes one problem: a mailbox provider's distrust of a sudden, high-volume sender. It does not fix misconfigured authentication, a domain with no MX record pointed anywhere sensible, or a brand-new domain with zero history of any kind. Before starting a ramp schedule, confirm the items below — a ramp on top of a misconfiguration just produces a slower-building problem.

Authentication, verified, not just configured

Having an SPF record is not the same as having a correct one. Check that SPF includes all services that will send on your behalf and stays under the 10-DNS-lookup limit (exceeding it causes a permerror and SPF to fail silently for everyone). Check DKIM is signing outgoing mail and that the public key in DNS matches. Check DMARC is published, even at p=none initially for monitoring, and that SPF or DKIM aligns with your From domain.

Domain age and history

A domain registered yesterday carries no history for a mailbox provider to evaluate, and that absence reads as risk by default. There's no way to manufacture history, but there is a way to not make it worse: don't register a domain and start high-volume cold sending from it the same week. Give it time with light, real traffic — even internal mail — before outreach volume starts.

MX and basic DNS sanity

Confirm the domain actually resolves correctly for mail delivery and that there's no conflicting or stale MX record left from a previous setup. A domain bought for cold outreach that still has leftover DNS from a previous owner or a parking page configuration is a common, easy-to-miss failure mode.

A mailbox that has sent and received real mail

A brand-new mailbox with zero sent or received mail history looks exactly like what it is to a mailbox provider: untested. Before outreach starts, the mailbox should have gone through genuine send/receive activity — this is what warm-up accomplishes, but check it's actually happened, not just that a tool reports "warm-up complete."

The readiness checklist

[ ] SPF record present, under 10 lookups, includes all senders
[ ] DKIM signing active, public key matches DNS
[ ] DMARC published (p=none minimum), aligned with From domain
[ ] MX record correct, no stale leftover DNS
[ ] Domain has some real send/receive history, not same-week-registered
[ ] Mailbox warm-up shows genuine engagement, not just volume
[ ] Seed-inbox placement check shows inbox, not spam, across major providers

What not to do

Do not treat "DNS record exists" as equivalent to "DNS record correct" — test it. Do not start outreach volume the same week a domain is registered. Do not trust a warm-up tool's internal "ready" status without an independent placement check across the providers you actually care about.

Readiness, scored

A domain that's "not ready" on even one row is worth fixing before outreach volume starts — a ramp schedule compounds whatever state the domain was already in, good or bad.

The failure mode this checklist catches

The most common version of this mistake isn't skipping warm-up entirely — it's running a warm-up tool, seeing a "complete" status, and treating that as equivalent to a verified placement check. A warm-up tool's internal completion metric measures its own process (sent/received volume, engagement simulation), not whether Gmail and Outlook have actually started placing your mail in the inbox. Those two things usually move together, but not always, and the only way to know for certain is an independent placement check against real seed inboxes across the providers you'll actually be sending to.

Re-run the checklist after any DNS or mailbox-provider change

A domain that passed every item on this checklist can regress — a DNS migration, a new email service added to the SPF record pushing it over the lookup limit, or a DKIM key rotation that wasn't fully propagated are all common causes. Re-run the readiness checklist after any change to DNS, sending infrastructure, or mailbox provider, not just once at initial setup.

Where MailPilot fits

MailPilot checks SPF, DKIM, and DMARC configuration directly, warms mailboxes over OAuth or SMTP/IMAP with a gradual ramp, and measures real per-provider inbox placement through a seed-inbox network — so "ready" means a verified placement result, not just a completed checklist step.