Skip to content

Domain Warmup — Building Reputation on a New Sending Domain

IP warmup is half the story. Your sending domain also accrues reputation independently — and a fresh domain takes 30-60 days to reach full standing at major ISPs. This guide is about the domain side: separate from but interlocking with IP warmup.

Domain reputation vs IP reputation

They're related but distinct.

IP reputation is per-sending-IP. New IP → no history → blocked or filtered until you've sent enough clean volume.

Domain reputation is per-sending-domain (the part after @). New domain → no history → similar filtering.

A typical scenario: you've sent from mail.example.com for years (high domain rep). You add a new sending IP (low IP rep). You need to warm the IP, but the domain rep helps — Gmail is forgiving of a high-rep domain on a new IP.

Reverse case: well-established IP (your shared SES IP), but new domain. Gmail's per-domain reputation engine sees newdomain.com as unknown. Throttles or filters.

Both must be healthy for inbox placement.

Why a fresh domain takes 30-60 days

ISPs aggregate signals over time:

  • Days 1-7: Almost no domain rep data. Most mail goes to Spam by default.
  • Days 7-21: Engagement signals build (opens, click-throughs). Reputation climbs.
  • Days 21-45: Domain rep stabilizes. Inbox placement improves.
  • Days 45-60: Mature domain rep. Normal sending volume sustainable.

Sending too much from a fresh domain on Day 5 → recipients mark as spam → spam-rate spike → reputation drops permanently → start over with a different domain.

Subdomain strategy

Best practice: send marketing from a subdomain, NOT from your main brand domain.

brand.com           → corporate/transactional (low volume)
mail.brand.com      → marketing
news.brand.com      → newsletters
notify.brand.com    → transactional (password resets, etc)

Why subdomains?

  1. Reputation isolation — bad marketing campaigns don't damage your brand's primary domain rep
  2. Different policies — easier to set distinct SPF/DKIM/DMARC per use case
  3. Cleaner recovery — if mail.brand.com gets hit, you don't lose the brand domain
  4. Customer-side targeting — recipients can whitelist mail.brand.com without whitelisting everything else

In AcelleMail, configure each subdomain as a separate sending domain. The Sending → Sending domains screen lists every domain you've registered with status chips and authentication state:

Sending domains list

Click into a domain row to see its full detail: SPF / DKIM / DMARC records to publish at your DNS host, current verification status per check, and the per-domain DKIM keypair fingerprints:

Sending domain detail — DNS records + auth status

Verify SPF/DKIM/DMARC per subdomain. The Verify-domain workflow in this view shows you exactly the DNS records to copy-paste into your DNS host's TXT/CNAME panel.

Per-domain warmup curve

Day-by-day volume on the new domain:

Day Daily volume Engagement target
1 200-500 (engaged 7d only) >30% open rate
3 1,000-2,000 >25% open rate
7 5,000-10,000 >20% open rate
14 20,000-30,000 >15% open rate
21 50,000+ >12% open rate (B2C average)
30 100,000+ Normal segment baseline
45 Full volume Normal segment baseline
60 Same Mature domain rep

If engagement target is missed, hold or step down. Engagement is the leading signal for domain rep.

Authentication is non-negotiable

A fresh domain MUST publish SPF / DKIM / DMARC from Day 0:

Open the sending-server detail

In AcelleMail's sidebar, click Sending → Sending servers. The list shows every server connected to this account with its status chip, sending limit, and last activity:

Customer sending-server list

Click into the row you want to configure. The detail page surfaces Connection settings (host / credentials), Configuration (server name, default from, sending limit, bounce + FBL handler), and the Test connection / Send test email buttons in the toolbar:

Server detail — Connection + Configuration

The auth chips on the server detail show real-time status:

Sending server auth chips

All three Green = receiving servers can trust messages from your domain. Any Red → critical block, no warmup will succeed until fixed.

SPF — TXT record at root yourdomain.com:

v=spf1 include:amazonses.com include:_spf.mailgun.org ~all

(Include the sending vendors you use.)

DKIM — CNAME records as shown in your sending-server setup wizard.

DMARC — TXT at _dmarc.yourdomain.com:

v=DMARC1; p=none; rua=mailto:[email protected]

Start with p=none (monitor mode) for first 30 days. Move to p=quarantine then p=reject as auth pass rates settle above 99%.

Cross-reference with Postmaster Tools

Once Google Postmaster Tools is set up for your domain, the domain reputation panel shows your build-up:

Day 7:  Domain Reputation: Low
Day 21: Domain Reputation: Medium
Day 45: Domain Reputation: High

If you see Domain Bad at any point, something broke:

  • Authentication failures (auth panel <95%) → re-verify
  • Spam rate >0.3% → audit content + list
  • Volume spike → step back

See Gmail Postmaster Tools walkthrough for the dashboard setup.

Common UI signals + fixes

Symptom Likely cause UI fix
Domain shows in Google Postmaster but no data Volume too low (<1000/day to Gmail) Send more Gmail-segment volume; data appears after 7-14 days
Domain Reputation Bad on Day 7 Authentication failing OR content content-trigger spam Re-verify in AcelleMail; audit recent campaign content
Domain Reputation Low even after 30 days Sending too much too fast Step back to 30-day baseline; rebuild engagement
Authentication pass <95% in Postmaster DKIM key mismatch or rotation failure Check DKIM CNAMES at DNS host; re-verify in AcelleMail
All metrics fine but inbox placement still <70% Likely content + frequency issue, not domain rep Audit subject lines + send cadence; consider engagement-only segments
Subdomain rep separate from main brand Working as designed This is good — isolated reputation is the safe pattern
Advanced: BIMI for verified brand display + DMARC enforcement progression + multi-subdomain strategy

BIMI (Brand Indicators for Message Identification) lets your verified domain show a logo next to your messages in Gmail (US), Yahoo, Apple Mail, others. Requires:

  1. DMARC at p=quarantine or p=reject
  2. SVG-formatted logo published at your domain
  3. VMC (Verified Mark Certificate) from Entrust or DigiCert (~$1500/yr per domain)

BIMI doesn't directly boost reputation, but the trust signal does. Recipients see a verified logo → click-through rates rise ~10-15%.

DMARC enforcement progression:

Day 1:      p=none, rua=mailto:[email protected]
            (Monitor mode; receivers report SPF/DKIM failures)
Day 30:     Confirm 99%+ pass rate via aggregate reports
Day 45:     p=quarantine; failing emails go to Junk
Day 60:     Confirm still 99%+ pass rate
Day 90:     p=reject; failing emails are bounced

The progression is conservative for a reason — if you jump to p=reject while your DKIM is broken, you reject your own legitimate mail. Stage carefully.

Aggregate DMARC reports (free, from receiving servers) are XML files. Parse them via:

# DMARC report XML reader
zcat aggregate.xml.gz | grep -E "<source_ip|<count|<disposition" | head -20

Tools like dmarcian.com or postmarkapp.com/dmarc parse + visualize for you.

Multi-subdomain strategy at scale:

For SaaS operators with multiple brands:

Customer A: ┌── mail.customerA.com     (their marketing)
            └── notify.customerA.com   (their transactional)

Customer B: ┌── mail.customerB.com     (their marketing)
            └── notify.customerB.com   (their transactional)

Each subdomain warmed independently. Customer A's reputation problems don't bleed to Customer B.

In AcelleMail's admin: configure per-customer Sending Plans + per-plan Sending Domains. Each customer sees only their own subdomains.

Domain rotation for reputation recovery:

If a domain gets hit irreversibly, retire it. Move to a fresh subdomain:

old-mail.brand.com (poisoned) → Disable
new-mail.brand.com (fresh)    → New warmup cycle, day 1

Update all signup forms + DNS + AcelleMail server config to point at the new subdomain.

Spam trap exposure:

Spam traps are addresses ISPs use to detect bad senders. Hitting them = severe reputation damage. Common trap categories:

  • Recycled traps — once-real addresses that haven't been used in years; ISPs repurpose them
  • Pristine traps — never-real addresses created specifically to catch bad senders
  • Honeypots — addresses posted publicly to catch scrapers

Avoid by:

  1. NEVER buy lists
  2. Use double opt-in (cleanest signal)
  3. Run email verification before importing
  4. Use AcelleMail's bounce log to identify pattern-matching traps (often 5.7.x with specific reason text)

Domain reputation in the wild — measurement tools:

  • Google Postmaster Tools (primary signal)
  • SNDS (Outlook-specific signal)
  • mxtoolbox.com → "Email Health"
  • mail-tester.com → 0-10 score for a specific message
  • DMARC aggregate reports

Use 2-3 signals; no single tool tells you everything.

Related articles

13 comments

7 comments

  1. Tomas
    This is the clearest IP warmup schedule Ive found. The volume table at the top is what I'm referencing daily
  2. Marcus
    We warmed up a dedicated IP last fall. The 2-week ramp this article describes is on the aggressive side — Gmail in particular punishes anything faster than ~3-4 weeks. We did 4 weeks and had a clean ramp.
    1. Admin
      Fair. That table assumes a shared pool where you inherit some reputation. On a dedicated IP starting from nothing, 4 weeks is the honest floor. I'll split it out.
  3. Minh
    Does engagement-based segmentation help during warmup? E.g. only sending to the most-engaged 20% during week 1?
    1. Admin
      Yes, biggest lever in week 1. Start with 30-day openers, widen to 90d, 180d, then everything. Never-engaged stays out until you're at full volume.
  4. Isabella
    the Postmaster Tools section is gold. Most senders don't even know it exists.
    1. Admin
      Two catches: it stays empty until you're sending a few hundred a day to Gmail, and you verify the DKIM d= domain, not the From domain.
  5. Brian
    We hit a Spamhaus listing once. Self-service delisting was actually fast (< 24h) but the reputation recovery took weeks. Not the listing itself that hurt — the user complaints that caused it...
    1. Admin
      Right, delisting is a form. The complaint history is still in the receivers' own models and doesn't clear with it. Treat a post-delist restart as fresh warmup and watch complaint rate, not the listing.
  6. Linh
    For very low-volume senders (< 5k/month), does warmup even matter? Or just send and let the provider's shared pool absorb the trickle?
    1. Admin
      Depends on whether you're on a shared pool or your own IP. Under 5k/month on a shared pool, the IP reputation is already established by everyone else's traffic, so ramping the IP is not your problem. Your domain reputation still is, and that builds off your own volume regardless of the pool, so a trickle just means it builds slowly. Practical version: skip the IP ramp schedule, but still start with your most engaged segment for the first few sends so the domain's early signal is opens and not spam clicks. And get SPF, DKIM, DMARC right before the first send, at that volume you don't have enough traffic to recover from a bad start quickly. The article is written for the dedicated-IP case and doesn't say that. I'll add a low-volume section.
  7. Carlos
    if you're warming a new ip after a known issue, consider seeding with transactional mail first (password resets, order confirmations). higher engagement rate per send than marketing — helps the reputation ramp
    1. Admin
      This works, with one caveat worth stating in the article: seed with transactional to get the ramp moving, then move it back off once the marketing stream is established. Long-term you want the two on separate subdomains, because a bad campaign that tanks the reputation shouldn't also take password resets down with it. The engagement gap is real though, password resets get opened at rates marketing never touches, and that's exactly what a receiver's reputation model is watching in the first two weeks. I'll add it to the warmup article as a note under the new-IP section.

More in Sending & Deliverability