Home / Writing

Cold Email Deliverability: SPF, DKIM, DMARC, and Warmup

You wrote twenty careful emails, sent them from your main domain, and spent the next week refreshing the sent folder. Three opened, one bounced, and nothing came back. The copy was not the first problem. The inbox never had a reason to trust the sender, and no amount of rewriting fixes a message that lands in spam or gets filtered at the gateway. Most cold email deliverability is decided before the first word of copy.

The rest is infrastructure: which domain sends, what the DNS records say about it, how warm the mailbox is, and how the recipient's provider handles a message from an unknown sender. The good news is that this part is concrete. There are three records to publish, one domain decision to make, and a handful of signals to watch.

Cold Email Deliverability: The Three Records in Plain English

SPF: which servers may send for this domain

SPF is a DNS TXT record that lists the servers allowed to send mail as your domain. It answers one question for the receiving provider: did this message come from a machine the domain owner authorized? Keep it to one record, keep the lookup count under the provider limit, and end with -all unless you are still testing.

DKIM: proof the message was not changed

DKIM puts a cryptographic signature on each message, using a key pair. The public key lives in DNS at a selector you choose; the private key stays with your sending tool. If the signature checks out, the receiver knows the message was sent by someone with the key and was not altered in transit.

DMARC: what to do when the first two fail

DMARC tells the receiving provider how to treat mail that fails SPF and DKIM alignment, and where to send reports. Start with p=none to collect data, move to p=quarantine and then p=reject once your legitimate senders are aligned. Publishing DMARC does not make you deliverable by itself, but it removes one of the largest reasons providers distrust a new domain, and it lets you see who is sending as you.

RecordWhere it goesExample valueWhat it does
SPFTXT at @v=spf1 include:_spf.yourprovider.net -allAuthorizes sending servers
DKIMTXT or CNAME at selector._domainkeyv=DKIM1; k=rsa; p=MIGfMA0...Signs each message
DMARCTXT at _dmarcv=DMARC1; p=none; rua=mailto:dmarc@example.com; pct=100Sets the failure policy and reports
PTR / rDNSReverse DNS on the sending IPmail.yoursendingdomain.comConfirms the IP belongs to the sending host

The example values are placeholders. Copy the exact record your sending tool generates, including the selector, and verify with a public DNS lookup before you send a single cold email.

Send From a Domain You Can Afford to Lose

Separate domain, not your main one

Register a separate domain, or at minimum a dedicated subdomain, for cold outreach. If a mailbox or domain gets blocked, your invoice email and client replies keep working. A separate domain also keeps a bad day of cold sending from affecting your main reputation. Do not put the cold domain on the same page as your primary brand if you can help it.

Warm-up takes weeks, not days

A brand-new domain that sends 100 emails on day one looks like a spam operation, whatever the copy says. Ramp up over roughly two to three weeks: a handful of emails per day at first, then 20-50 per mailbox per day once replies and bounces look normal. Send to people who might actually reply during warm-up, because a mailbox with no replies and no engagement teaches providers nothing good.

Read the Signals, Not the Vibes

Bounce rate above 2-3 percent

A bounced address is a dead address or a typo. If bounces climb above 2-3 percent on a batch, stop, clean the list, and verify the risky addresses before continuing. Bounce rates that stay high get a domain throttled quickly.

Replies and complaints

Replies are the best signal that the sending domain has real people on both ends. Complaints are the worst: a small number of spam complaints in a short window can put a shared IP in a bad state for weeks. Treat a complaint as a stop signal for that address and that domain, not as an acceptable cost of doing business. The full list of stop rules is in when to stop a cold email sequence.

Sudden changes in opens and clicks

Open tracking is unreliable now that many providers prefetch images, so do not read too much into a single day. A drop across a week, together with a rise in bounces or a block message, is worth investigating before you send again.

The Compliance Layer That Also Affects Delivery

Deliverability and compliance overlap more than people expect. Accurate From names, a real reply-to address, and a subject line that matches the body are both legal requirements under CAN-SPAM and technical signals that keep a sender out of the spam folder. Never use a fake "Re:" or a misleading subject; providers and recipients both notice. In the EU and UK, know whether you are emailing a corporate subscriber or an individual, and include a working opt-out in every message. A clean opt-out process also reduces complaints, which is the single most useful thing you can do for a cold domain's reputation. For the sending rhythm that goes with this setup, see the 21-day cold email follow-up cadence.

Do this today

  • Look up the SPF, DKIM, and DMARC records on the domain you use for cold email and confirm all three return the values your sending tool expects.
  • Add a DMARC reporting address with p=none if you have not already, and send one test email to see the report arrive.
  • Cut next week's daily volume in half and move cold outreach to a separate domain or subdomain before the next batch.

Free tool: reply rate calculator — no signup.