# What Is Email Deliverability?

Email deliverability is whether accepted mail reaches the inbox. See how it differs from delivery, what Gmail, Yahoo and Outlook require, and what each signal misses.

- Email deliverability is the share of accepted email that reaches the inbox, not spam or nowhere.
- Delivery only means the server accepted it; your sending platform cannot see the folder.
- Sender reputation, authentication and complaint rates decide placement at Gmail, Yahoo and Outlook.
- Measure it with several signals together; opens and delivery rate alone mislead.

This applies to any team sending from its own domain, whether marketing email or cold email, and the bulk sender rules bite above 5,000 messages a day to one provider. No tool sees every inbox. Seed tests and provider dashboards are samples of placement, not a census.

## What Is Email Deliverability?

Email deliverability is the share of your accepted email that lands in the inbox rather than the spam folder, and in [Validity's 2026 benchmark the global inbox placement rate for 2025 was 87.2 percent](https://www.validity.com/wp-content/uploads/2026/03/2026-Benchmark-Report.pdf), so roughly one message in eight did not reach the inbox. Mailbox providers, not senders, decide that outcome.

> **Email deliverability:** The share of email accepted by receiving servers that reaches the recipient's inbox, rather than the spam folder or nowhere at all.

Gmail, Yahoo and Outlook weigh authentication, sender reputation and recipient spam reports in their sender policies. Authentication is whether SPF, DKIM and DMARC prove the mail comes from you, reputation is how your domain and IPs have behaved before, and spam reports are how often people mark your mail as spam. Senders control the inputs. The providers control the result.

Validity's figure comes from seed-list tests that Validity customers ran at hundreds of mailbox providers and spam filters. The messages that missed the inbox split between spam folders and mail that went missing entirely. Validity itself calls the data a snapshot in time, which is worth remembering whenever a benchmark is quoted as a fixed truth.

This guide to [email deliverability](https://growthtribune.com/sales/email-deliverability/) uses three layers throughout:

- **Accepted:** The receiving server took the message and it did not bounce.
- **Placed:** The message reached a folder, ideally the inbox.
- **Engaged:** The recipient replied, clicked or otherwise acted on it.

Each layer has its own signals, and each signal sees only part of the picture. Most deliverability mistakes come from reading a number from one layer as proof about another.

## Accepted Mail Versus Inbox Placement

Accepted mail and inbox placement are different numbers, because [sending platforms record only the hand-off or the rejection, not the folder](https://www.spamresource.com/2024/09/delivterms-inbox-placement-delivery.html), so a campaign with 100 percent delivery can still land mostly in spam. Al Iverson of Spam Resource puts it bluntly. Full delivery could mean none, 30 percent or all of the mail reached the inbox.

Litmus draws the same line in its own definitions. Delivery rate is emails delivered (those that did not bounce) divided by emails sent. Deliverability is where the message lands once received, such as the spam folder or the Gmail Promotions tab.

**The three layers of email deliverability**

| Layer | What it means | Who reports it | Blind spot |
| --- | --- | --- | --- |
| Accepted | Server took the message | Your sending platform | Cannot see the folder |
| Placed | Inbox, spam or tab | Seed tests, provider dashboards | Samples, not your recipients |
| Engaged | Replies and clicks | Your platform and CRM | Needs inbox placement first |

The skeptic's question for any dashboard is simple. A 99 percent delivery rate says the receiving servers did not refuse the mail. It says nothing about whether a buyer ever saw it.

Placement also differs by mailbox provider, so one blended number hides problems. In Validity's 2025 seed data, inbox placement was 89.8 percent at Gmail, 87.3 percent at Yahoo and 77.4 percent at Microsoft. A sender whose list is heavy with Microsoft addresses can sit well below the global average while the Gmail share of the list looks healthy.

For a B2B team the practical rule follows from this. Report delivery rate as a hygiene number, and report placement separately, by provider, from a source that can actually see folders.

## What Is Sender Reputation?

Sender reputation is each mailbox provider's own judgement of your domain and sending IPs, and Gmail measures one input directly, since [Google asks senders to keep the spam rate reported in Postmaster Tools below 0.10% and never reach 0.30%](https://support.google.com/mail/answer/81126?hl=en). That judgement builds from authentication, complaints, bounces and engagement over time.

There is no single universal reputation score. Gmail, Yahoo and Microsoft each keep their own view, built from what they see of your mail, and a domain can be trusted at one provider and filtered at another.

Gmail used to show more of its view. In Postmaster Tools v2, the old domain and IP reputation charts were retired and replaced by a compliance status dashboard and spam rate insights, according to a Blueshift guide to the new version. Google Postmaster Tools now tells you whether you meet each Gmail sender requirement and how often recipients report your mail, not a reputation grade.

Two details matter when you read it:

- **Rolling averages:** Compliance status uses a multi-day rolling average, so a fix takes several days to show.
- **Inbox-only spam rate:** The spam rate counts DKIM-authenticated messages that recipients mark as spam after reaching the inbox, so it cannot count mail Gmail already filtered.

Sender reputation is therefore something you infer from several provider signals together. Clean authentication, a low complaint rate and a list free of bad addresses are the inputs. Folder placement at each provider is the evidence that the inputs worked.

## What Affects Email Deliverability?

Seven inputs shape email deliverability, namely authentication, sending infrastructure, complaint rate, list quality, engagement, unsubscribe handling and daily volume, and [Yahoo requires bulk senders to honour unsubscribes within 2 days and keep the spam rate below 0.3%](https://senders.yahooinc.com/best-practices). Daily volume to each provider also decides which rules apply.

Each input maps to something the provider checks and something your team controls:

**What mailbox providers check and what you control**

| Factor | What the provider checks | Input you control |
| --- | --- | --- |
| Authentication | SPF, DKIM, DMARC, alignment | DNS records per sending domain |
| Infrastructure | Forward and reverse DNS, TLS | Mail server and DNS setup |
| Complaint rate | Share of mail reported as spam | Targeting, consent and frequency |
| List quality | Bounces, spamtraps, abuse addresses | Verification before each send |
| Engagement | Recipient reports and response | Relevant, expected messages |
| Unsubscribe handling | One-click header, prompt removal | Header plus suppression process |
| Daily volume | 5,000-a-day bulk line | Planned volume per domain |

Authentication and infrastructure are pass or fail. Google requires all senders to Gmail accounts to use SPF or DKIM, valid forward and reverse DNS, TLS and standard RFC 5322 formatting. Bulk senders need SPF, DKIM, DMARC and From-domain alignment on top.

List quality shows up as bounces and traps. ZeroBounce's status guidance tells senders to delete invalid addresses, avoid spamtrap and abuse addresses, and treat catch-all addresses as riskier. A catch-all domain accepts mail for any address, so a verifier cannot confirm the person exists.

Complaint rate and unsubscribe handling are linked. When leaving is hard, the spam button becomes the way out, and every report counts against the spam rate that Gmail and Yahoo cap.

## What Do Gmail, Yahoo And Outlook Require From Senders?

Gmail, Yahoo and Outlook now set similar authentication floors for bulk senders, and [Outlook rejects mail from domains sending over 5,000 messages a day that fail SPF, DKIM or DMARC](https://techcommunity.microsoft.com/blog/outlook/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730) rather than filing it in Junk. Gmail, by contrast, may route non-compliant mail to spam or reject it.

The authentication floor for high-volume senders looks like this:

**Bulk sender authentication rules by mailbox provider**

| Requirement | Gmail | Yahoo | Outlook |
| --- | --- | --- | --- |
| Applies to | 5,000+ a day to Gmail | Bulk senders | Over 5,000 a day |
| SPF and DKIM | Both required | Both required | Both must pass |
| DMARC | Required | At least p=none | At least p=none |
| Alignment | From domain aligned | From domain aligned | SPF or DKIM aligned |

Gmail and Yahoo add rules on unsubscribes and complaints:

**Unsubscribe and spam rate rules**

| Requirement | Gmail | Yahoo |
| --- | --- | --- |
| One-click unsubscribe | Marketing and subscribed mail | Header plus visible link |
| Spam rate | Below 0.10%, never 0.30% | Below 0.3% |

What happens to mail that misses the rules differs. Google says such mail might not be delivered as expected or might be marked as spam, and unauthenticated mail can be rejected with a 5.7.26 error. Microsoft, from May 5, 2025, rejects non-compliant messages from high-volume domains with a "550; 5.7.515 Access denied" error instead of routing them to Junk.

DMARC p=none satisfies the Yahoo and Outlook floor, but it enforces nothing. It asks receivers to report results and take no action on failing mail, so the policy blocks nothing, spoofed mail included. Use the reports from p=none to find every legitimate sender, then move toward quarantine or reject.

For cold email teams, the 5,000-a-day thresholds count all mail from the domain to that provider, not one rep's mailbox. Several reps on one domain can cross the line together. To set the records up correctly, [check SPF, DKIM and DMARC before sending](https://growthtribune.com/how-to-check-spf-dkim-and-dmarc-before-sending/) any new domain.

This summarises mailbox provider policies and is general information, not legal advice.

## How Do You Measure Email Deliverability?

No single number measures email deliverability, and open rates are an unreliable signal because [Apple Mail Privacy Protection downloads remote content in the background whether or not the email is opened](https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/). Reliable measurement combines bounce data, seed-list placement tests, provider dashboards, DMARC reports and replies, and reads each against its blind spot.

**What each deliverability signal shows and misses**

| Signal | What it tells you | Blind spot |
| --- | --- | --- |
| Bounce and delivery rate | Servers accepted the mail | No folder data |
| Seed-list placement test | Folder at test mailboxes | Not your recipients; a snapshot |
| Postmaster spam rate | Gmail users' spam reports | Ignores mail already filtered |
| Postmaster compliance status | Gmail requirements met | Gmail personal accounts only |
| DMARC aggregate reports | Authentication and policy applied | No folder data |
| Opens | Pixel loads | Inflated by Apple MPP |
| Replies and clicks | Real recipient action | Lags; depends on offer too |

Three blind spots catch most teams.

- **Postmaster spam rate:** It counts reports from mail that reached the inbox. If Gmail already sends much of your mail to spam, few people see it to report it, so the rate can look low while placement is poor.
- **Seed tests:** A tool such as GlockApps sends your message to mailboxes it manages, not to your buyers' mailboxes, and each test is a moment in time.
- **DMARC reports:** An aggregate report lists sending IPs, SPF and DKIM results and the policy the receiver applied. It records authentication, never which folder a message reached.

> **Warning:** Do not treat open rates as proof of inbox placement. Mail Privacy Protection loads tracking pixels whether or not anyone reads the email, so opens can rise while placement falls.

**Illustrative scenario (assumed figures, not a real sender):** Assume a B2B team sends 20,000 emails in a week. The sending platform shows 99 percent delivered. A seed test shows most Gmail seeds in the inbox but most Microsoft seeds in Junk. Postmaster Tools shows a Gmail spam rate of 0.04 percent.

Read the numbers by layer. The 99 percent says servers accepted the mail and nothing more. The seed test says Microsoft is filtering this message, a problem the delivery rate cannot show. The low Gmail spam rate is consistent with good Gmail placement, but on its own it could also mean Gmail is filtering quietly. The seed test is what breaks the tie for Gmail, and it points the team at Microsoft first, where the next step is checking authentication and complaint sources for that provider.

To check sender reputation at Gmail, read the Postmaster Tools compliance status and spam rate together, and confirm folder placement with a seed test before drawing a conclusion.

## Which Tools Show Each Part Of Email Deliverability?

Each email deliverability tool below is built around one main question, so Google Postmaster Tools shows how Gmail sees your domain, GlockApps seeds test mailboxes to show folder placement, MXToolbox checks blacklists and DNS, ZeroBounce screens addresses before sending and dmarcian turns DMARC reports into enforcement. None covers every layer.

**Which layer each tool covers**

| Tool | Layer it covers | Blind spot |
| --- | --- | --- |
| Google Postmaster Tools | Gmail compliance and spam rate | Gmail personal accounts only |
| GlockApps | Seed-list placement | Managed seeds, not recipients |
| MXToolbox | Blacklists, DNS, DMARC rollout | Lookups show setup, not folders |
| ZeroBounce | List validation before sending | Validation alone does not show folder placement |
| dmarcian | DMARC reporting and enforcement | No folder data |

The tools below are grouped by the question they answer, not ranked. To weigh placement testers against each other, [compare email deliverability tools](https://growthtribune.com/best-email-deliverability-tools/) in the dedicated guide.

### Google Postmaster Tools For Gmail Compliance

**What it measures:** The compliance status dashboard marks each Gmail sender requirement (SPF and DKIM, DNS, formatting, TLS, spam rate, plus DMARC and one-click unsubscribe for bulk senders) as Compliant, Needs work or No data found. Other dashboards cover authentication, encryption and delivery errors.

**What it does not show:** The spam rate counts reports only from mail that reached the inbox, so it can look low when Gmail already filters your mail. It covers personal Gmail accounts only, and low-volume days may show no data.

**Best fit:** Any team with meaningful Gmail volume. It is Google's own data on mail sent to Gmail users.

### GlockApps For Seed-List Placement

**What it measures:** GlockApps Inbox Insight sends a test email to a seed list of mailboxes GlockApps manages at Gmail, Outlook, Yahoo, Office 365, Zoho and regional providers, and reports whether each copy landed in the inbox, spam or a sub-folder. It also runs the message through filters including SpamAssassin, Barracuda and Proofpoint, and adds a DMARC analyzer and blocklist monitoring.

**What it does not show:** Seed mailboxes have no history with you, so they cannot reproduce how your engaged buyers' inboxes treat your mail. One test is one moment.

**Best fit:** Teams that need folder-level placement by provider before a large send or after a change to copy, domain or infrastructure.

**GlockApps pricing**

| Plan | Price | Billing | Notes |
| --- | --- | --- | --- |
| Free | $0 | per month |  |
| Essential | $59 | per month, billed annually |  |
| Growth | $99 | per month, billed annually |  |
| Enterprise | $129 | per month, billed annually |  |

### MXToolbox For Blacklists And DNS

**What it measures:** MXToolbox's public lookups list a domain's MX records, run mail server diagnostics (reverse DNS, open relay, response time) and check each MX IP against 105 DNS-based blacklists. Its Delivery Center product guides DMARC deployment toward a reject policy and monitors blacklists across all sending sources.

**What it does not show:** A clean blacklist check and correct DNS do not prove inbox placement. The lookups describe your setup, not where your mail lands.

**Best fit:** Admins who manage DNS and mail servers and need fast diagnostics, plus teams moving DMARC from p=none to reject.

**Real cost driver:** Paid tiers scale on inbox placement analyses per month (30 on Delivery Center, 100 on Delivery Center Plus), on domains and on email message volume (500,000 or 5,000,000 messages).

**MXToolbox pricing**

| Plan | Price | Billing | Notes |
| --- | --- | --- | --- |
| Free | $0 | per month |  |
| Basic | $129 | per month |  |
| Pro | $399 | per month |  |
| Enterprise | Custom pricing | per custom |  |

### ZeroBounce For List Validation

**What it measures:** ZeroBounce sorts addresses into valid, invalid, catch-all, unknown, spamtrap, abuse and do\_not\_mail before a campaign goes out. ZeroBounce claims 99.6 percent validation accuracy, which is the vendor's own figure. Its subscription also bundles an inbox placement test, blacklist monitoring every 8 hours, email warmup and a DMARC monitor.

**What it does not show:** A valid address can still route your mail to spam. Validation lowers bounces and trap hits. It does not decide the folder.

**Best fit:** Outbound teams sending to bought, enriched or ageing lists, where bad addresses are the first risk. To act on each result, [interpret email verification statuses](https://growthtribune.com/how-to-interpret-email-verification-statuses/) before you send.

**Real cost driver:** Validation is billed by credits. The subscription needs a minimum of 10,000 credits, and unused credits roll over, so list size and re-verification frequency drive spend.

**ZeroBounce pricing**

| Plan | Price | Billing | Notes |
| --- | --- | --- | --- |
| Freemium | $0 | per month | per credit |
| Pay-As-You-Go | $39 | per month | per credit |
| ZeroBounce ONE | $99 | per month | per credit |

### dmarcian For DMARC Reporting And Enforcement

**What it measures:** dmarcian turns DMARC aggregate reports into views of every source sending as your domain (Domain Overview, Detail Viewer, Source Viewer and Alert Central). Founded in 2012 by a primary author of DMARC, it also offers deployment and full outsourcing services.

**What it does not show:** DMARC reports record authentication results and the policy applied, never the folder a message reached.

**Best fit:** Organisations with several sending services or domains that need to reach p=reject without blocking their own mail.

**Real cost driver:** Tiers scale on DMARC-capable messages per month and active domains, from 100,000 messages and up to 2 domains on the entry tier to 5,000,000 messages and up to 15 domains on the largest published tier, with custom pricing for overages.

**dmarcian pricing**

| Plan | Price | Billing | Notes |
| --- | --- | --- | --- |
| Personal | $0 | per month |  |
| Basic | $24 | per month |  |
| Plus | $240 | per month |  |
| Enterprise | $600 | per month |  |
| Custom | Custom pricing | per custom |  |

## How To Improve Email Deliverability

Improving email deliverability starts with authentication and list quality, since Google requires senders of more than 5,000 messages a day to Gmail to set up SPF, DKIM and DMARC and support one-click unsubscribe. Work through the steps in this order.

- [ ] Publish SPF, DKIM and DMARC at p=none for every sending domain; success is a pass in DMARC aggregate reports for every legitimate source
- [ ] Move DMARC toward quarantine, then reject, once reports show no legitimate source failing; success is enforcement with no lost mail
- [ ] Verify the list before each campaign and remove invalid, spamtrap and abuse addresses; success is fewer hard bounces
- [ ] Segment catch-all and unknown addresses and send to them at low volume; success is stable bounces on those segments
- [ ] Add a one-click List-Unsubscribe header and a visible link, and honour requests within 2 days; success is no unsubscribe-driven complaints
- [ ] Keep the Postmaster Tools spam rate under 0.10%; success is a Compliant status on spam rate
- [ ] Check sending IPs and domains against blacklists; success is no listings
- [ ] Run a seed placement test before any large send; success is inbox placement at each provider your list uses
- [ ] Ramp new domains and mailboxes gradually; success is steady placement as volume grows

The first two steps come first because everything else builds on authenticated mail. DMARC at p=none gives you reports without risk, and enforcement then stops others sending as your domain. The detailed record check belongs before the first send, not after a drop.

List work is the input outbound teams control most directly. Verification will not change the folder for a valid address, but it keeps bounces and spamtraps from damaging the reputation every later message depends on.

Ramping is a judgement call that depends on your domain's history and the providers on your list. If you are setting up new sending domains, [email warmup tools](https://growthtribune.com/best-email-warmup-tools/) automate part of that ramp, though they do not replace a clean list and correct authentication.

## What Is A Good Email Deliverability Rate?

A useful reference point for an email deliverability rate is the inbox placement average at each mailbox provider, not a fixed target, and in Validity's 2025 data that average was 89.8 percent at Gmail, 87.3 percent at Yahoo and 77.4 percent at Microsoft. Those are independent benchmarks, not provider rules, and they sit beside the provider spam rate ceilings.

**Success measures and who owns each number**

| Measure | Target or benchmark | Owner |
| --- | --- | --- |
| Global inbox placement | 87.2% average in 2025 | Validity benchmark |
| Gmail inbox placement | 89.8% average | Validity benchmark |
| Yahoo inbox placement | 87.3% average | Validity benchmark |
| Microsoft inbox placement | 77.4% average | Validity benchmark |
| Gmail spam rate | Under 0.10%, never 0.30% | Google policy |
| Yahoo spam rate | Under 0.3% | Yahoo policy |
| Outlook authentication | SPF, DKIM, DMARC pass | Microsoft policy |
| Invalid addresses | Removed before send | Your team |

Keep the owners apart when you report. The Validity numbers describe what Validity's seed tests saw across many senders. They are a reference point for comparison, not a target or a pass mark. The spam rate ceilings and Outlook's authentication rule are provider policies, and missing them changes how your mail is handled.

The decision rule is to compare your seed-test placement with the provider-level averages, not the global one. For example, a sender at 85 percent overall may be beating the Microsoft average and trailing the Gmail one, which points to different fixes. Weight each provider by its share of your list, and treat any provider well below its average as the first problem to fix.

## Common Email Deliverability Mistakes

A frequent email deliverability mistake is reading a high delivery rate as success, because a sending platform cannot see which folder a delivered message reached. The others follow the same pattern of trusting one signal for a question it cannot answer.

- **Delivery rate as inbox rate:** Accepted mail can still land in spam.
- **Trusting opens:** Apple Mail Privacy Protection fires pixels without a real open.
- **A low Postmaster spam rate as proof:** The rate counts only inbox-delivered mail, so it can stay low while Gmail filters you.
- **DMARC at p=none forever:** It meets the floor but stops no spoofing.
- **Catch-all and unknown addresses at full volume:** These carry more bounce risk and belong in small segments.
- **One seed test as permanent truth:** Placement changes, and a test is a snapshot.

> **Warning:** Acting on a single number is a risky habit. Pair every delivery or open figure with a placement test and a provider signal before changing copy, volume or domains.

## Frequently Asked Questions

**Does email verification improve deliverability?**

Email verification improves deliverability only indirectly, by removing addresses that bounce or trap senders before a campaign goes out; it does not change which folder an accepted message reaches. ZeroBounce, for example, flags invalid, spamtrap and abuse addresses for removal and advises sending to catch-all addresses in small segments at low volume.

**Do the bulk sender rules apply to cold email?**

Yes, once volume crosses the threshold. Google treats roughly 5,000 or more messages to Gmail accounts in 24 hours from a domain as bulk. The count covers all mail from that domain to the provider, so several reps sending cold email on one domain can cross it together.

**Is DMARC p=none enough?**

DMARC p=none meets the Yahoo and Outlook minimum for bulk senders, so it keeps you compliant, but it enforces nothing. Receivers report results and take no action on failing mail. Treat p=none as the monitoring stage, use the aggregate reports to confirm every legitimate source passes, then move to quarantine or reject.

## Sources

- [2026 Email Deliverability Benchmark Report](https://www.validity.com/wp-content/uploads/2026/03/2026-Benchmark-Report.pdf), validity.com
- [DELIVTERMS: Inbox Placement (Delivery versus Deliverability)](https://www.spamresource.com/2024/09/delivterms-inbox-placement-delivery.html), spamresource.com
- [Email sender guidelines - Gmail Help](https://support.google.com/mail/answer/81126?hl=en), support.google.com
- [Sender Best Practices | Sender Hub](https://senders.yahooinc.com/best-practices), senders.yahooinc.com
- [Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders](https://techcommunity.microsoft.com/blog/outlook/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730), techcommunity.microsoft.com
- [Mail Privacy Protection & Privacy](https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/), apple.com

---
Source: https://growthtribune.com/what-is-email-deliverability/
