New Domain Emails Going to Spam: A 28-Day Fix

A new domain usually needs 28 days of clean authentication, low volume and gradual engagement before cold email stops landing in spam. If you send bursts before the domain has history, filters learn the wrong pattern. This guide gives you the diagnosis table, DNS records, warm-up rules, pause points and proof checks to fix it.

Start by separating the causes. A new domain can fail because it has no reputation, but it can also fail because SPF, DKIM, DMARC, content or list quality is wrong. Use the broader email spam causes guide if older domains are also affected.

What failed first?

Do not start by rewriting every email. First prove whether the problem is technical, behavioural or reputation-based.

Send three plain-text tests from the new mailbox: one to Gmail, one to Outlook or Microsoft 365, and one to another provider. Use no links, no signature images and no attachments.

Open the received message headers. Check SPF, DKIM and DMARC results. Also record where the message landed: Inbox, Promotions, Junk or Spam.

Fix in this order: authentication, identity, volume, content, recipients, then warm-up.

Why are new domain emails going to spam?

New domains have no positive sending history. Mailbox providers have not seen consistent human replies, low complaint behaviour or stable authentication from that domain.

Domain age alone does not solve this. A six-month-old unused domain can still behave like a new sender. What matters is recent, authenticated mail that recipients accept and interact with.

Burst volume is the common mistake. You register a domain on Monday, connect mailboxes on Tuesday and send hundreds of cold emails on Wednesday. That pattern looks disposable.

Secondary domains add another risk. They protect your main business domain, which is sensible for cold outreach. But a secondary domain starts with its own reputation. It does not inherit trust from your main domain.

Keep secondary domains recognisable. Use a clear variation, not a deceptive lookalike. Add a simple website or redirect, real sender names and matching company details. If recipients feel tricked, complaints rise.

Content can make a new domain fail faster. Heavy link tracking, URL shorteners, image-only signatures, attachments and overused sales phrases give filters more reasons to distrust a sender with no history.

Recipient quality matters as much as volume. Old scraped lists, role accounts and unverified addresses create bounces and complaints. New domains have little reputation buffer, so mistakes show quickly.

Are the DNS records correct?

Authentication is the first fix because it is binary. You either pass, fail or create alignment problems. Warm-up cannot compensate for broken DNS.

Use provider values from your admin console. Do not copy records from another domain. SPF, DKIM and DMARC are domain-specific, and some records include unique selectors or tokens.

SPF

SPF is a TXT record at the root domain, often shown as @ in DNS.

Common patterns look like this:

Use one SPF record per domain. Do not create two TXT records starting with v=spf1. Merge includes into one record.

Use the free SPF checker after saving. DNS may take minutes or hours to propagate, depending on your TTL and provider.

DKIM

DKIM signs each message and ties it to your domain. It is usually a TXT or CNAME record at a selector host.

Common selectors include google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu and zoho.

Do not guess the selector. Open your provider admin panel and copy the exact host and value.

For Google Workspace, go to Admin console → Apps → Google Workspace → Gmail → Authenticate email. Generate the DKIM record, add it in DNS, then return and start authentication. Google’s email sender guidelines explain its authentication expectations.

Use the free DKIM checker to confirm the selector is visible.

DMARC

DMARC tells receivers what to do when SPF or DKIM alignment fails. For a new domain, start with monitoring before enforcement.

Create this TXT record:

Replace the reporting address with a real mailbox or reporting service address. Make sure it exists.

A p=none policy does not tell receivers to quarantine or reject. It lets you collect reports while you confirm alignment. After stable authentication, you can move to stricter policies if your business needs them.

Yahoo also publishes sender requirements covering authentication, low complaints and easy unsubscribe for bulk senders. Use the free DMARC checker before campaigns.

What is the 28-day plan?

For a new domain, use 3–4 weeks. Four weeks is safer if you plan cold outreach. You are teaching filters that this domain sends normal, authenticated mail to real inboxes.

This is not permission to send unlimited messages after day 28. It is a controlled ramp to a modest daily baseline.

Those warm-up numbers match a conservative ramp: start at 3 emails per day, add 2 per day, and cap at 30 per day. Weekends should be lighter. A 30% weekend schedule is safer than seven identical sending days.

Do not jump from 20 real emails to 200. Add mailboxes instead of forcing one mailbox to carry all volume. Most cold outreach programmes work better when each mailbox stays modest.

If you use Gmail or Google Workspace, follow a provider-specific setup before ramping. The Gmail warm-up guide covers mailbox connection and authentication checks.

For more detail on timing, use the day-by-day warm-up timeline. The short version: existing domains may need about 14 days, but new domains should get 3–4 weeks.

When does warm-up help?

Warm-up helps when the domain is technically correct but has little positive history. It creates low-volume, normal-looking conversations before you ask the domain to carry campaigns.

It can also help after a pause, if the original cause is fixed. If you sent too fast in week one, stop, reduce volume and rebuild gradually.

Warm-up is not a repair tool for broken infrastructure. It will not fix duplicate SPF records, unsigned DKIM, DMARC alignment failures, bad lists, misleading content, malware, phishing-like pages or blocklisted sending infrastructure.

A useful warm-up pattern has these traits:

BobWork Email Warm-up runs a shared network by default, with a private-pool switch per account. The free pool does this step automatically: it starts at 3 emails per day, adds 2 per day, caps at 30 by default, spreads sends between 09:00 and 18:00 in each mailbox’s time zone, and replies to about 40% of warm-up mail. One mailbox is enough; a private pool needs two.

The private-pool option is useful for secondary domains because strangers do not receive your addresses. It also means you need enough of your own mailboxes to create movement.

BobWork supports Gmail and Google Workspace, Zoho Mail, Lark Mail, Yahoo Mail, iCloud Mail, Amazon SES, SendGrid, Mailgun and generic IMAP plus SMTP. Outlook and Microsoft 365 are not supported yet because Microsoft requires OAuth.

When should you pause?

Pausing is not failure. It prevents filters from learning more bad signals.

Pause the mailbox or domain when any of these happen:

Use the free blacklist checker if delivery changes suddenly. A listing is not always the cause, but it is fast to rule out.

Microsoft’s anti-spam guidance is useful when Outlook or Microsoft 365 is the main problem. Look for policy rejections, not only junk placement.

Do not resume at the old volume. Restart below the last stable point. If 30 real emails per day caused trouble, restart at 10–15 and hold for several days.

What should you do now?

Work fastest to slowest. You can complete the first five checks in under an hour if you have DNS access.

If a step fails, do not skip it. A new domain needs clean basics more than clever copy.

How do you prove recovery?

You need proof from several angles. One inbox test is not enough, and a single reply does not prove healthy deliverability.

First, inspect headers again. SPF, DKIM and DMARC should pass on mail received by Gmail, Microsoft and another provider. Alignment should match the visible sending domain or the provider-approved sending domain.

Second, monitor placement over seven days. A mailbox can look fine on Tuesday and degrade by Friday after a campaign. Use a rolling view, not one test.

Third, compare warm-up spam rate with campaign results. BobWork defines spam rate as the share of a sender’s warm-up mail found in Spam by receiving mailboxes over seven days. That direct mailbox measurement is more useful than guessing from opens.

Fourth, confirm campaign behaviour. Bounces should be low, complaints should stay below provider danger levels, and replies should not be mostly negative. Google’s published guidance says to keep spam complaint rates under 0.1% and avoid ever reaching 0.3%.

Fifth, look for stability before scaling. In BobWork, a mailbox is ready for outbound after 14 or more days warming, a 7-day spam rate at or below 3%, and at least 30 warm-up emails received. For a new domain, still use the full 3–4 week plan before meaningful cold volume.

Finally, scale sideways. If you need more sends, add properly configured mailboxes and domains. Do not turn one new mailbox into a high-volume sender.

You can run the 28-day plan manually, but it is easy to send too much too soon. BobWork Email Warm-up is free, has no credit card and no time limit, and lets you warm up to 20 mailboxes per account in a shared network or a private pool. Use it after DNS is correct, then confirm the numbers before you restart campaigns.

Frequently asked questions