Email deliverability is your ability to get messages into the recipient’s inbox, not just onto their mail server. A message can be “delivered” according to your sending platform and still land in the spam folder, a promotions tab, or nowhere the recipient will look. Deliverability depends on three things: whether your mail is properly authenticated, whether your sending reputation is good, and whether recipients actually want what you send.

This guide explains how deliverability works, what mailbox providers like Gmail, Yahoo, and Microsoft look at, and where a beginner should start.

Email delivery vs. email deliverability

These two terms get mixed up constantly, and the difference matters.

Delivery (or “delivery rate”) means the receiving server accepted the message. In SMTP terms, it answered with a 250 reply instead of a 4xx temporary failure or a 5xx permanent failure.
Deliverability (sometimes called “inbox placement”) means the accepted message ended up somewhere useful, usually the inbox.

Your email service provider (ESP) dashboard can show a 99% delivery rate while half your mail goes to spam. The receiving server accepted it, then its filters decided where to put it. That second decision is what deliverability is about.

Metric	What it measures	Where you see it
Delivery rate	Messages accepted by the receiving server	ESP dashboard, SMTP logs
Bounce rate	Messages rejected (hard or soft)	ESP dashboard, bounce webhooks
Inbox placement	Share of accepted mail that reached the inbox	Seed tests, panel data, provider tools
Spam complaint rate	Recipients who clicked “Report spam”	Feedback loops, Google Postmaster Tools

How mailbox providers decide where your email goes

Every large mailbox provider runs its own filtering, and none publish the full recipe. But their public sender guidelines agree on the main inputs.

1. Authentication: can they prove the mail is really from you?

Authentication is the entry ticket. The three standards are:

SPF lists the servers allowed to send for your domain.
DKIM adds a cryptographic signature that proves the message wasn’t altered and ties it to a domain.
DMARC tells receivers what to do when SPF and DKIM don’t line up with the visible From: domain, and sends you reports.

Since February 1, 2024, Google’s sender guidelines require every sender to personal Gmail accounts to set up SPF or DKIM, and senders of 5,000 or more messages a day to set up SPF, DKIM, and DMARC. Yahoo’s sender requirements took effect the same month with a similar split. Microsoft’s Outlook.com postmaster policies added SPF, DKIM, and DMARC requirements for domains sending more than 5,000 emails per day starting May 5, 2025.

A minimal DNS setup looks something like this:

example.com.              TXT  "v=spf1 include:_spf.your-esp.com -all"
s1._domainkey.example.com TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
_dmarc.example.com.       TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

For the full walkthrough, see how to set up SPF, DKIM, and DMARC step by step.

2. Reputation: what has your mail been like before?

Mailbox providers track the history of your sending domain and your sending IP address. If past mail from that domain drew complaints, hit spam traps, or bounced a lot, new mail from it gets more suspicion. If past mail got opened, replied to, and rarely reported, it gets the benefit of the doubt. We cover this in depth in sender reputation explained.

3. Engagement: do recipients want it?

Providers watch what people do with your mail. Reporting spam is the strongest negative signal. Google asks senders to keep the user-reported spam rate in Postmaster Tools below 0.1% and never let it reach 0.3% or higher, according to its sender guidelines FAQ. Yahoo sets 0.3% as its complaint ceiling as well.

Other signals (opens, replies, moving a message out of spam, deleting without reading) are used too, but providers don’t publish the weights.

4. List quality: are you sending to real, consenting people?

Mail sent to addresses that don’t exist bounces. Mail sent to old abandoned addresses can hit spam traps. Mail sent to people who never signed up draws complaints. All three damage reputation, which damages inbox placement for everyone else on your list.

5. Content and formatting

Content matters less than most people think, but it isn’t irrelevant. Google’s guidelines warn against hiding content with HTML or CSS, mixing promotional content into transactional messages like receipts, and impersonating other senders. Messages should be formatted according to RFC 5322.

What hurts email deliverability most

If you’re new to this, the problems below cause the majority of trouble. Most are about who you send to, not what you write.

Sending to a bought, scraped, or very old list. These lists are full of invalid addresses and people who never agreed to hear from you.
No authentication or broken authentication. A missing DKIM signature or a DMARC failure is now enough for major providers to junk or reject bulk mail.
High bounce rates. Amazon SES, for example, places accounts under review at a 5% bounce rate and may pause sending at 10%, and recommends staying below 2%.
Hard-to-find unsubscribe links. People who can’t unsubscribe click “Report spam” instead.
Sudden volume spikes. A new domain that goes from zero to 50,000 messages in a day looks like a spammer. New sending domains need a gradual ramp.
Sending what people didn’t sign up for. Someone who wanted order updates and gets daily promotions is a future complaint.

For a longer diagnostic list, see why are my emails going to spam.

How to measure email deliverability

You can’t fix what you don’t measure, and no single number tells the whole story. Use a few together.

Bounce rate

Track hard bounces (permanent failures like 550 5.1.1 User unknown) separately from soft bounces (temporary failures like 452 4.2.2 Mailbox full). A rising hard-bounce rate almost always points to list quality.

Spam complaint rate

Sign up for feedback loops (Yahoo’s Complaint Feedback Loop, Microsoft’s JMRP) and check Google Postmaster Tools. Google calculates its spam rate as the share of DKIM-authenticated messages delivered to an engaged recipient’s inbox that the recipient then marked as spam, per the Postmaster Tools help page. More detail is in our spam complaint rate guide.

Inbox placement

Seed-list tests send your campaign to test mailboxes at different providers and report where it landed. They’re useful for catching big problems (everything going to spam at one provider) but they don’t reflect your real recipients’ engagement. See inbox placement testing.

Engagement trends

Opens are less reliable than they used to be because of Apple Mail Privacy Protection, which downloads remote content privately in the background when a message arrives, so tracking pixels can fire whether or not anyone reads the email. Clicks, replies, and conversions are better signals. A sudden drop in clicks at one provider often means your mail started landing in spam there.

A beginner’s email deliverability plan

If you’re starting from scratch, do these in order.

Authenticate your domain. Publish SPF and DKIM for every service that sends as your domain, then add a DMARC record at p=none with a reporting address.
Send from your own domain, ideally a subdomain. For example, news.example.com for marketing and mail.example.com for receipts. This keeps one stream’s problems from dragging down the other.
Clean your list before the first send. Remove malformed addresses, dead domains, typo domains, and obvious junk. Our free email verifier checks syntax, whether the domain exists and has MX records, disposable domains, role addresses like info@, free-provider addresses, and common typos like gmial.com. It doesn’t log into or ping the mailbox, so it can’t confirm a specific inbox exists, but it catches a large share of the obviously bad addresses before they bounce.
Use confirmed opt-in for new signups. A confirmation email proves the address works and that the owner asked for your mail.
Add a visible unsubscribe link and one-click unsubscribe headers. Bulk senders to Gmail and Yahoo are required to support one-click unsubscribe as defined in RFC 8058.
Ramp up volume gradually on any new domain or IP.
Process bounces and complaints automatically. Hard bounces and complainers should be suppressed on the first event.
Watch your numbers weekly, not just when something breaks.

Who should care about email deliverability?

Everyone who sends email that matters, which is nearly every business.

Marketers lose revenue when newsletters and promotions go to spam.
Founders and SaaS teams lose users when signup confirmations and password resets don’t arrive.
Sales teams doing outbound lose pipeline when cold email gets filtered. Cold outreach carries extra risk because recipients never opted in.
Developers own the DNS records, bounce handling, and sending infrastructure that everything else depends on.

Deliverability is shared: a marketing team that buys a list can damage the domain that sends your password resets. That’s one reason to separate streams by subdomain.

FAQ

What is a good email deliverability rate?

There’s no single industry-standard number, because inbox placement varies by provider, list, and type of mail. Focus on the measurable inputs instead: keep hard bounces low (Amazon SES recommends staying under 2%), keep Gmail’s reported spam rate under 0.1%, and make sure authentication passes. If those are healthy, inbox placement usually follows.

Is email deliverability the same as delivery rate?

No. Delivery rate counts messages the receiving server accepted. Deliverability is about whether accepted messages reached the inbox. You can have a high delivery rate and poor deliverability if most of your accepted mail is filtered to spam.

Does verifying my email list improve deliverability?

It helps with one specific input: bounces. Removing malformed, nonexistent-domain, disposable, and typo addresses lowers your bounce rate and reduces the chance of hitting abandoned addresses. It won’t fix authentication or complaint problems, and no verifier can guarantee a mailbox exists without the receiving server’s cooperation.

How long does it take to fix bad email deliverability?

It depends on what caused it. Fixing a broken DNS record can help within days. Recovering from a reputation problem caused by complaints or spam traps takes longer, because providers need to see a consistent run of good sending. Google, for example, restores mitigation eligibility only after a sender’s spam rate has stayed below 0.3% for seven consecutive days.

Do I need a dedicated IP for good deliverability?

Usually not. Most small and mid-sized senders do better on a well-managed shared IP pool, because a dedicated IP needs steady volume to build and keep a reputation. See shared vs dedicated IP for email for how to decide.

What Is Email Deliverability? A Beginner's Guide for Senders