What is email deliverability? A plain-language map of the whole subject

Email deliverability is the ability of your messages to reach recipients' inboxes — not merely their mail servers, but the inbox itself, rather than the spam folder or silent rejection. That one-sentence definition contains the entire subject, because every word of it is doing work: "ability" (it's a capacity you build, not a setting you enable), "your" (it attaches to your identity and follows you), and "inbox" (the only destination that counts).

This is the map guide. Each territory below has its own detailed guide linked from it; this page exists so a newcomer can see how the pieces connect before descending into any of them.

Deliverability is not delivery

The first distinction the subject demands. Delivery rate — the number your sending platform reports — counts messages a receiving server accepted. It says nothing about where the message went after acceptance, and a message filed straight to junk counts as delivered. Deliverability, measured honestly, is about inbox placement: of the mail that was accepted, how much landed where humans look?

The gap between the two numbers is where senders get blindsided — a dashboard can read 99% while half the mail rots in spam folders. Why the gap opens and how to close it is the subject of how to improve email deliverability.

The three parties in every send

Deliverability is decided in a negotiation among three parties, and knowing which controls what saves a lot of misdirected effort.

You, the sender, control the inputs: who is on your list, what you send, how often, and whether your domain's authentication is in order. Most deliverability outcomes trace back here, which is the uncomfortable, useful truth of the field.

Your sending platform (ESP) provides the infrastructure: the servers and IP addresses your mail travels from, bounce and complaint processing, and compliance enforcement. Platforms differ in infrastructure quality and policy strictness, which is why the same list and content can perform differently across them — the differences our platform reviews and deliverability rankings exist to measure.

Mailbox providers — Gmail, Microsoft, Yahoo and the rest — make the final call. Each runs its own filtering on its own data, answering one question: do our users want this mail? Nobody can overrule that verdict, buy their way past it, or configure around it. All deliverability work is ultimately about earning a better answer to it.

The inputs: what the verdict is built from

Four categories of evidence feed the mailbox providers' decision, roughly in this order of precedence.

Authentication — can you prove who you are? Three DNS-based protocols carry the proof: SPF (which servers may send for your domain), DKIM (a cryptographic signature on each message) and DMARC (the policy tying both to the address recipients see). Since 2024, major providers require all three of bulk senders — the thresholds are collected in our Gmail sender requirements page. Authentication doesn't earn inbox placement by itself; it establishes the identity everything else attaches to. The three-protocol system is walked through in SPF, DKIM and DMARC explained.

Reputation — what's the track record of that identity? Providers keep memory per sending domain (domain reputation) and per IP address (IP reputation): complaint history, bounce patterns, engagement, consistency. Reputation moves slowly, which is why deliverability problems feel sudden but never are, and why new senders must warm up before sending at volume.

Recipient behavior — how do actual humans react? Opens, replies and rescues from the spam folder argue for you; deletions without reading argue mildly against; the spam button is the heaviest single signal in the system. Google publishes the threshold: user-reported spam under 0.3%, ideally under 0.1%.

Content — last, and less than folklore claims. Modern filters weigh identity and reaction far more than word choice; content mostly matters when it resembles deception. The evidence-ordered tour of what actually causes spam placement is in why emails go to spam.

Feeding all four: list quality. Who is on the list — consented, current, engaged, real — determines bounces, complaints and engagement at once. It's the closest thing deliverability has to a single root variable.

How deliverability is measured

Your platform's dashboard gives delivery rate, bounce rate and complaint data — necessary, but all acceptance-side. Receiver-side truth comes from three places. Google Postmaster Tools reports your reputation and measured spam rate at Gmail, from Gmail's own data; it's free, and worth registering before problems start. Message headers show each receiver's authentication verdict on real mail (readable with the email header analyzer). And placement itself, inbox versus spam folder, is measured by sending to controlled seed mailboxes across providers and looking, which is the method behind our own testing protocol.

Configuration, the part of deliverability you can audit in one minute, is checked by tools like our email deliverability score: it reads your DNS the way a receiving server does and scores the setup layer — clearly labeled as setup, because no tool can score your reputation from outside. Keep the labels honest when you read any tool's output: a setup score, a delivery rate and a placement rate are three different measurements, and vendors blur them constantly.

What it isn't: three persistent myths

A deliverability guarantee. Any service promising perfect inbox placement is describing something no sender controls. Placement is the receivers' verdict; everything else is influence.

A one-time setup. Authentication is close to one-time; reputation and list quality are ongoing operations. Treating deliverability as a launch checklist item is how it degrades quietly for a year — the standing practices are in email deliverability best practices.

A trick. Filter-evasion tactics are the patterns filters train on. The entire durable strategy fits in one line: send mail people demonstrably want, from an identity that proves itself and keeps a clean record.

Where to go from here

Three profiles, three starting points. Setting up a new sending domain: authentication first — SPF, DKIM and DMARC, then a warm-up plan. Mail currently landing in spam: the diagnostic checking order in why emails go to spam. Everything nominally fine: verify it — run the email deliverability score, register Postmaster Tools, and adopt the prevention practices before anything needs diagnosing.

Related guides

• Why emails go to spam — the diagnostic companion to this map
• How to improve email deliverability — the repair plan
• SPF, DKIM and DMARC — the authentication layer in one guide
• Email deliverability best practices — the standing operating discipline
• Email deliverability score — audit your setup layer in one pass
• Inbox placement — the metric that distinguishes deliverability from delivery
• Sender reputation — the memory your identity accumulates

About this guide

Written by InboxRatio Editorial, the team behind InboxRatio's controlled inbox placement benchmark. This pillar guide draws on the providers' own published documentation for every threshold it cites, and on the DMARC, SPF and DKIM specifications for protocol mechanics. No vendor sponsorship influences it.

Methodology

InboxRatio measures deliverability by sending real campaigns through each reviewed platform to a controlled seed list and recording where every message lands — placement measured directly, not inferred from delivery rates. The full protocol is documented in how we test, and our source rules in sources.

Last updated

6 September 2026. Definitions and provider requirements reviewed quarterly.

Frequently asked questions

What does email deliverability mean? The ability of your email to reach recipients' inboxes rather than their spam folders — or nothing at all. It's distinct from delivery, which only measures whether a receiving server accepted the message, wherever it was filed afterward.

What is a good email deliverability rate? Measured as inbox placement, strong senders see the large majority of accepted mail reach the inbox — but any specific number depends on measurement method and provider mix, so treat quoted averages skeptically unless the testing method is published, as ours is in how we test.

What affects email deliverability the most? List quality and recipient reaction, expressed through complaint rates and engagement, sitting on top of correct authentication. Content matters least of the major inputs, despite receiving most of the folklore.

How do I check my email deliverability? Three layers: run your domain through the email deliverability score for the setup side; register with Google Postmaster Tools for Gmail's view of your reputation and spam rate; and send to mailboxes you control at major providers to observe placement directly.

Is email deliverability the sender's or the ESP's responsibility? Shared, unevenly. The ESP owns infrastructure and shared-IP stewardship; you own list quality, content, cadence and domain reputation. A strong platform cannot rescue a poor list, though a poor platform can drag down a good one — the differences our rankings are built to quantify.

Can I fix deliverability quickly? Configuration faults — broken SPF, missing DKIM — fix in hours and can show results in days. Reputation damage repairs on the receivers' timetable: typically weeks of consistent, well-received sending. Anyone promising instant recovery is selling something.

Deliverability, compressed: prove your identity, keep its record clean, send what people want. Start where every audit starts — two minutes running your domain through the email deliverability score.