Every few months, a brand reaches out after switching ESPs and seeing inbox placement fall to levels they’ve never experienced. Authentication is configured. SPF, DKIM, and DMARC all pass. On paper, everything looks correct.
The problem, almost every time, is the sending domain. On the new setup, it has no history — and to ISPs like Gmail and Outlook, a domain without a track record gets treated with the same caution as one that’s never been seen before.
A sending domain in email is the domain in your email’s From address — for example, brand.com in hello@brand.com. It’s the identifier ISPs like Gmail, Yahoo, and Outlook use to build a reputation score for your email program. That score, entirely separate from your website domain’s search authority, determines whether your campaigns reach the inbox or get filtered to spam. It’s also invisible in your ESP dashboard, which is why it damages quietly before anyone notices.
Is Your Sending Domain the Same as Your Website Domain?
Technically it can be, but for most ecommerce senders, it shouldn’t be — and the difference has real deliverability consequences.
Your website domain carries web reputation: search engine authority, backlinks, HTTPS trust signals, years of domain age. Your sending domain — whether it’s brand.com directly or a subdomain like mail.brand.com — carries a separate, parallel reputation score built entirely on your email program’s history.
ISPs track these independently. A strong SEO ranking for your root domain doesn’t carry over to your sending reputation. And critically, the reverse is also true: damage to your email reputation doesn’t automatically pull down your web presence.
Here’s the reason a sending domain needs its own reputation at all: email is roughly 45–48% spam globally (Statista, 2024). ISPs have no way to evaluate trust at the server handshake level — so they built per-domain reputation scoring as the primary filter. Your domain is the persistent identifier that trust attaches to, more stable than an IP address and more accountable than a shared ESP pool. Without a reputation score attached to your domain, every send starts from unknown.
When you send from mail.brand.com instead of brand.com, any reputation damage from a bad campaign — a complaint spike from a cold segment blast, a botched win-back to 12-month inactives — stays on the subdomain. Your root domain, the one your website, customer logins, and transactional flows run on, is insulated from it.
How Does a Sending Domain Build — or Lose — Reputation?
ISPs don’t rate sending domains on a fixed rubric. They model your expected sending behavior based on history and compare every new send against that model. The primary signals they track:
- Spam complaint rate — the most heavily weighted signal. Google’s Email Sender Guidelines require keeping this below 0.10% — the full threshold breakdown is in the Google Postmaster guide
- Engagement signals — opens, clicks, and replies tell ISPs that subscribers want your mail; sending high volumes to low-engagement lists is a negative signal
- Hard bounce rate — invalid addresses indicate poor list hygiene, which correlates with acquired or stale lists
- Volume consistency — a domain that sends 5,000 emails per week for three months and then blasts 200,000 overnight is flagged as suspicious regardless of list quality; ISPs model your expected behavior and treat deviations from it as risk signals
- Domain age — ISPs apply additional scrutiny to domains under 90 days old; new is not the same as trusted
That last point matters more than most senders expect. Zero reputation is not a neutral starting position — it’s a signal that a domain hasn’t earned trust yet. Which is exactly why the warm-up process exists: to generate consistent, low-complaint sends that teach ISPs to trust a domain before you scale.
Sending Domain — Key Numbers
Why Subdomain Senders Have Nearly Half the Spam Rate
InboxEagle is an email deliverability monitoring platform for ecommerce brands. In our Q1 2026 analysis of 3,474 ecommerce sending domains, root-domain senders landed in spam at nearly double the rate of subdomain senders — 26.0% versus 13.3%. That 12.7 percentage point gap is the infrastructure argument made in data. The brand-by-brand breakdown is in the ecommerce email deliverability gap analysis.
Part of that gap is infrastructure: subdomain senders have separate DKIM signing, cleaner DNS records, and reputation isolated from the root domain. But it also reflects a selection effect — brands disciplined enough to configure a proper subdomain setup are typically the same ones managing list hygiene and engagement segmentation deliberately. The infrastructure investment and the sending habits tend to arrive together.
The Klaviyo Setup That’s Building Reputation on Someone Else’s Domain
Across the ecommerce brands we monitor at InboxEagle, one pattern comes up consistently: a brand has been sending for two years on Klaviyo, believes it has strong sender reputation, then either changes its setup or audits its authentication — and discovers the reputation they built doesn’t belong to them.
Without a custom sending domain configured, Klaviyo uses its own shared infrastructure to sign your outgoing mail. The d= domain in those DKIM signatures is klaviyomail.com — not yours. Every send is depositing reputation credit into Klaviyo’s shared domain, not your brand’s domain.
The practical consequence: when you switch ESPs, reset your configuration, or finally enable custom domain authentication, you’re starting from zero on your own domain. The years of sending history still exist — they just exist on someone else’s infrastructure, and they don’t travel with you.
The fix is one configuration step: add your own sending domain under Settings → Email → Sending Domains in Klaviyo. Full DNS walkthrough and alignment setup →
Once it’s configured, every send starts building equity in your domain — not a shared pool. And the reputation signals you monitor in Google Postmaster Tools will reflect your program, not Klaviyo’s aggregate.
For a deeper look at what those reputation signals are and how to protect them, Email Domain Reputation: How It’s Scored and How to Protect It covers the full scoring model.
The Bottom Line
Your sending domain is the identity ISPs use to decide whether your next email reaches your subscribers. It’s not your website. It’s not your ESP. It’s the specific domain your email program lives — and earns trust — on.
- Sending domain reputation is separate from website domain authority — strong SEO doesn’t help email deliverability, and a damaged email reputation doesn’t hurt your search rankings; ISPs score them on completely different signals
- Subdomains exist specifically to isolate email reputation —
mail.brand.comdamage stays there; your root domain is insulated - If you’re on Klaviyo without a branded sending domain, you’re building reputation on someone else’s infrastructure — it won’t transfer when you switch, update, or expand your setup
The immediate action: Check which domain is signing your DKIM by sending a test email to Gmail, opening it, and selecting “Show original.” If the dkim=pass line shows header.d=klaviyomail.com instead of your brand domain, you have one configuration step to make — and the domain alignment guide walks you through it.
The complete email deliverability guide for 2026 covers where sending domain reputation fits in the broader picture — authentication, list hygiene, engagement segmentation, and monitoring all build on this foundation.
If you want to see what your sending domain’s reputation looks like right now — across Gmail, Outlook, Yahoo, and other providers — InboxEagle shows you placement data, authentication status, and reputation signals in one dashboard. No inferring from open rates.
Note: Content created with the help of AI and human-edited and fact-checked to avoid AI hallucinations.
Sources
- Google Email Sender Guidelines
- Statista — Global Spam Email Traffic Share, 2024
- Validity 2025 Email Deliverability Benchmark Report
- Klaviyo — Email Deliverability Overview
- InboxEagle native research data, Q1 2026 (3,474 sender domains)
