InboxRatio
Check your domain

Glossary term

Domain reputation: the record that follows your brand

What domain reputation is

Domain reputation is the standing a sending domain has earned with each mailbox provider: the accumulated verdict on every message ever sent under that name. Where IP reputation judges the machine, domain reputation judges the brand.

The identity being scored is established through authentication. When your mail passes SPF, DKIM and DMARC, the receiver knows with confidence which domain is responsible: the SPF envelope domain, the DKIM signing domain (d=), and the From domain they align with. Every open, every unread deletion, every spam complaint and unsubscribe that follows gets booked against that identity.

Each major receiver keeps its own ledger. Gmail is the most transparent about the concept — Google Postmaster Tools reports your domain reputation directly, in bands from high to bad, based on how Gmail users have received your mail. Other providers keep equivalent internal scores without the dashboard.

The property that makes domain reputation strategically different: it is portable and persistent. Change ESPs, renumber servers, move continents — the domain's record follows, because the domain is the one identity you carry into every send. That persistence is the entire design goal. IPs turned out to be too easy for bad actors to rotate; domains that recipients recognize are the identity worth scoring.

How domain reputation differs from IP reputation

The two ledgers answer different questions and move on different timescales.

IP reputation is infrastructure trust: is this machine currently emitting wanted mail? It reads instantly (the IP is known at connection time), reacts fast, and resets — imperfectly — when infrastructure changes. It can be shared with pool neighbors whose behavior you do not control.

Domain reputation is brand trust: does mail from this name have a history of being wanted? It is slower to build, slower to decay, immune to infrastructure changes, and entirely yours — no neighbors, no pool effects.

The asymmetry that matters in practice: you can escape an IP, you cannot escape your domain without abandoning the brand equity and recognition the domain carries. Filtering systems have leaned into exactly this property, and the industry consensus reflected in receiver guidance is that the domain signal now carries more long-term weight than the IP signal in placement decisions. The IP still gates the connection; the domain increasingly decides the folder.

One consequence worth spelling out: switching email platforms does not reset your deliverability. Senders who blame their ESP for placement problems and migrate find out, three weeks and one migration later, that the problem traveled with the From address.

How domain reputation works

The inputs mirror IP reputation's, booked against the authenticated domain:

  • Engagement. Mail that recipients open, reply to and move out of spam builds the record; mail deleted unread or ignored erodes it. Receivers see their own users' behavior perfectly.
  • Complaints. Spam-button clicks against your domain are the strongest negative input, and providers publish the thresholds they expect senders to stay under.
  • Hygiene signals. Unknown-recipient rates and spam-trap hits reveal list quality regardless of which IPs carry the traffic.
  • Consistency. Domains with steady volume and stable authentication build coherent history; erratic patterns read poorly.
  • Association. The domains you link to in message bodies carry reputations too, and consistently linking to poorly regarded destinations bleeds into the sender's standing.

Authentication is the bookkeeping mechanism underneath all of it. Without aligned SPF or DKIM, receivers cannot confidently attribute mail to your domain — which does not exempt you from judgment, it just makes the attribution sloppier and the default more suspicious. Verifying that your records actually align is step zero; the email authentication checker runs the full SPF, DKIM and DMARC evaluation in one pass.

Subdomains complicate the ledger productively. Receivers track subdomains somewhat separately while still noticing the organizational relationship. Senders exploit this deliberately: marketing from news.yourdomain.com, transactional from mail.yourdomain.com, corporate mail from the root. A promotional misstep then bruises the marketing subdomain's record while receipts and password resets keep flowing on the transactional one. The separation is real but not absolute — a root domain with a genuinely bad record shadows everything under it.

Domain reputation and your deliverability

For most senders, domain reputation is the single most consequential deliverability asset they own — more than their ESP choice, more than any individual campaign decision.

It compounds. Years of wanted mail buy a domain the benefit of the doubt: an occasional volume spike or an off campaign gets absorbed where the same behavior from a young domain triggers filtering. This is also why new domains face a cold start — no history is not neutral, and the first weeks of a new sending domain's life are a proving period regardless of how clean the practices are. (This is domain warm-up, the counterpart to IP warm-up.)

It gates the extras. BIMI logo display, for instance, is discretionary even with perfect records — providers decorate senders they trust.

And it is the reason list quality beats list size, arithmetically. Every disengaged address you keep mailing dilutes the engagement rates that build your record. A smaller list that wants your mail is not just cheaper to send to; it is actively building an asset a bigger, colder list would be spending down.

Gmail's Postmaster Tools gives you the domain-reputation band directly and free. If you send any meaningful volume to Gmail and have not set it up, do that before optimizing anything else — it converts the largest single receiver from a black box into a gauge. Our test methodology measures where mail lands across providers; Postmaster Tools tells you what Gmail thinks of the domain doing the sending.

Limitations and failure modes

Burning the root with cold outreach. The signature failure of the genre: a sales team runs unsolicited outreach from the corporate domain, complaint and unknown-recipient signals pile up against the name the whole company mails from, and every department's deliverability degrades together. Outbound prospecting is off-charter for us, but its collateral damage on sending domains is a pattern we cannot avoid documenting.

Expecting the ESP switch to reset it. The most common misdiagnosis in deliverability. A platform change fixes placement only when the platform (its pools, its throttling, its authentication defaults) was actually the problem — which is precisely what measured placement testing distinguishes.

Subdomain strategy done backwards. Two versions. One: everything — marketing blasts included — sends from the root domain, so there is no compartment to contain a mistake. Two: a throwaway-subdomain rotation scheme, spinning up mail7.yourdomain.com when mail6 burns, which receivers recognize as evasion and score against the organizational domain. Subdomains are for separating legitimate streams, not for laundering reputation.

The lookalike-domain trap. Sending from yourbrand-mail.com or getyourbrand.email to protect the main domain starts the cold-start clock on a name with zero recognition, splits your reputation-building across identities, and — the part senders underestimate — trains recipients to trust lookalike domains, which is exactly the phishing pattern receivers penalize and security teams war-game against.

Slow feedback. Domain reputation moves on a lag measured in weeks. A bad practice adopted today shows up gradually; a fix applied today earns its way back gradually. Senders routinely misattribute both directions to whatever they changed most recently.

No universal score. Each receiver keeps its own books. Gmail's band can read high while another provider junks you — cross-provider variance is normal, diagnosable only by testing placement per provider.

Related terms

IP reputation, sender reputation, DKIM, DMARC, SPF record, email warm-up, list hygiene, spam complaint rate, double opt-in.

Frequently asked questions

How do I check my domain reputation? Google Postmaster Tools reports it directly for Gmail, in bands, once you verify domain ownership. No equivalent public dashboard exists for most other receivers; placement testing and deferral patterns fill the gap.

How long does it take to build domain reputation? Weeks to months of consistent, wanted mail. It builds slower than IP reputation and decays slower too. A new domain should ramp volume gradually and lead with its most engaged recipients — same logic as IP warm-up.

Does switching email providers reset my domain reputation? No. The record attaches to your domain and follows it to any platform. What a migration does change is the infrastructure underneath — pools, IPs, throttling — which helps only when that was the actual problem.

Should I send marketing email from a subdomain? Generally yes — a dedicated subdomain per mail stream compartmentalizes risk while the root keeps its record for corporate mail. Use stable, honestly named subdomains; rotating through disposable ones reads as evasion.

Can I repair a damaged domain reputation? Usually, with patience: stop the damaging practice, cut the list to recipients who demonstrably want the mail, hold volume steady, and let weeks of clean signals accumulate. What rarely works is a new lookalike domain — cold start plus phishing-pattern penalties usually underperform the repair.

What ruins domain reputation fastest? High complaint rates and spam-trap hits — both symptoms of mailing people who did not ask. List quality failures outrank every technical misconfiguration in destructive power.

Treat the domain as the asset it is: verify your authentication actually attributes mail to it with the email authentication checker, then protect it with list discipline before any other optimization.

Sources