Guide · Deliverability

Why your cold emails are going to spam: a 12-point check.

By Nouman, founder · 26 September 2026

Cold emails usually land in spam for one of three reasons: the sending domain isn't properly authenticated, the domain or inbox has a poor sending reputation, or the people receiving them mark them as spam. Check them in that order. Authentication is the quickest to fix, reputation takes weeks to rebuild, and complaints are fixed only by sending to fewer, better-chosen people.

Authentication: prove the email is really from you

  1. SPF. A DNS record listing the servers allowed to send for your domain. If you send through Google Workspace or Microsoft 365, their record must be in it, and there can only be one SPF record per domain.
  2. DKIM. A signature your email provider adds to each message, checked against a key in your DNS. Turn it on in your provider's admin console; it's often off by default on new domains.
  3. DMARC. A DNS record telling receivers what to do when SPF or DKIM fails, and where to send reports. Start with a monitoring policy (p=none) and read the reports before tightening it.
  4. Alignment. The domain in your From address must match the domain SPF or DKIM authenticates. Sending as name@company.com through a tool that signs with its own domain fails this.

Why this is no longer optional: Gmail requires every sender to set up SPF or DKIM, and senders of more than 5,000 messages a day to also set up DMARC, with the sending domain aligned to SPF or DKIM (Google). Outlook has applied the same SPF, DKIM and DMARC requirements to domains sending more than 5,000 messages a day since 5 May 2025, and rejects mail that fails them (Microsoft).

Checked 26 September 2026.

How to check: send yourself a message, open it in Gmail, choose "Show original", and look for PASS next to SPF, DKIM and DMARC.

Domain and inbox: protect your reputation

  1. Never send cold email from your primary domain. Use separate secondary domains, so a reputation problem can't reach the domain your customers and invoices depend on. We run all sending this way, in the client's own accounts.
  2. Warm up new domains and inboxes. A brand-new domain that starts sending in volume looks like a spammer. Start small, send to people who reply, and raise volume gradually over weeks.
  3. Cap volume per inbox, and write the cap down. Spread sending across several inboxes rather than pushing one hard, and send in the recipient's business hours. We set sending volume and warm-up practice in writing for each engagement. How many per day?
  4. Check the basics your provider should already handle. Valid forward and reverse DNS, and TLS for sending. Google Workspace and Microsoft 365 handle both; self-hosted or cheap sending services may not.

Your list: send to fewer, better-chosen people

  1. Verify every address before sending. Bounces tell mailbox providers you don't know who you're writing to. Remove anything unverifiable rather than risking it.
  2. Only write to people with a plausible reason to care. Every spam complaint counts against your domain, and the surest way to collect them is a list built for size rather than fit.

Gmail asks senders to keep the spam rate reported in its Postmaster Tools below 0.10%, and never to reach 0.30% (Google).

Checked 26 September 2026.

The message: look like a person writing to a person

  1. Drop open and click tracking. Tracking pixels and redirected links add machinery a personal email wouldn't have. We don't use them in our own outreach. Plain text, one link at most, no attachments.
  2. Make opting out easy, and keep your headers honest. Say who you are, give a real way to stop hearing from you, and act on it.

In the US, CAN-SPAM makes no exception for business-to-business email. It requires accurate From and Reply-To details, a subject line that reflects the content, a valid physical postal address, a clear way to opt out, and opt-outs honoured within 10 business days. Each email in violation can cost up to $53,088, and hiring someone else to send doesn't transfer the responsibility (FTC).

Checked 26 September 2026. This is a summary, not legal advice.

How to test where your email lands

  • Send to a few inboxes you control on Gmail and Outlook, and check spam as well as the inbox.
  • Read the authentication results in "Show original" (Gmail) or the message headers (Outlook).
  • Once you send enough mail to Gmail, register your domain in Google Postmaster Tools to see its spam rate and reputation.
  • Check your sending domains and IPs against the public blocklists.
  • Then judge replies against a benchmark that counts the same way you do: reply rate benchmarks.

If it lands in the inbox and still gets no replies

Then the problem isn't deliverability, it's the email: who it's aimed at, why they'd answer, and how big the ask is. That's what a teardown fixes. See a cold email marked up and rebuilt, or send us yours.