Email deliverability is the share of your emails that land in the inbox, rather than in the spam folder or nowhere at all. It is decided in a fraction of a second by your recipient's mail provider, most often Google or Microsoft, which asks three questions: can this address receive mail, can this message prove who sent it, and does this sender deserve trust?
Most deliverability guides repeat the same advice without showing why it matters. This one is built on two datasets we run ourselves. The first is a DNS scan of the 50,000 most-linked domains on the web, which shows who filters the world's business email and how strictly. The second is the result of more than half a billion email address checks run through MailTester Ninja in the last 30 days, which shows what unverified data really looks like. Both are described in the methodology at the end.
Quick answer: how do you improve email deliverability? Authenticate your domain with SPF, DKIM and DMARC. Send only to addresses verified as real: in our data, half of the addresses people check cannot receive email at all. Keep hard bounces under 2% and spam complaints under 0.1%. Build volume gradually from a domain with a clean history. And measure inbox placement, not just delivery. Since 2024 Gmail and Yahoo, and since 2025 Microsoft, refuse bulk mail that skips the first step.
Contents
- What Email Deliverability Means
- Who Decides: The Mailbox Providers
- Gate 1: Can the Address Receive Mail?
- Gate 2: Can You Prove Who You Are?
- Gate 3: Do They Trust You?
- Content and Engagement
- How to Measure Deliverability
- Diagnosing Common Problems
- The Deliverability Checklist
- Methodology
- Frequently Asked Questions
What Email Deliverability Means
Two numbers are constantly confused, and the difference between them is where most senders lose results without noticing.
Delivery rate is the share of your emails that the receiving server accepted, in other words that did not bounce. Deliverability, or inbox placement, is the share that actually reached the inbox. An email that Gmail accepts and files in spam counts as delivered in your sending tool. You get no error and no bounce: the message simply never gets read.
| Metric | What it measures | Where you see it | Healthy level |
|---|---|---|---|
| Delivery rate | Messages accepted by the receiving server | Your sending platform | Above 98% |
| Hard bounce rate | Messages permanently refused (address or domain does not exist) | Your sending platform | Below 2%, ideally below 0.5% |
| Spam complaint rate | Recipients who clicked "Report spam" | Google Postmaster Tools, your platform | Below 0.1%, never 0.3% |
| Inbox placement rate | Messages that reached the inbox rather than spam | Seed tests, inbox placement tools | Stable across providers |
Deliverability is not a single score you can look up. It differs by provider, by domain, even by recipient, because filters weigh each person's own behavior. What you can do is control the inputs those filters use, which is what the rest of this guide covers. For published industry benchmarks and where they come from, see our email deliverability statistics.
Who Decides: The Mailbox Providers
Your email is judged by your recipient's mail provider, not by your sending tool. Knowing who those providers are tells you whose rules matter. Our scan of the 50,000 most-linked domains found 40,366 that accept email. This is who handles their mail:
| Mail provider | Share of mail-enabled domains | Publish DMARC p=reject | MX reachable over IPv6 |
|---|---|---|---|
| Google Workspace / Gmail | 28.2% | 27.3% | 99.9% |
| Microsoft 365 / Outlook | 22.7% | 31.7% | 91.3% |
| Proofpoint (security gateway) | 5.6% | 62.0% | 0.8% |
| Mimecast (security gateway) | 3.1% | 36.3% | 0% |
| Tencent QQ | 1.9% | 2.4% | 4.2% |
| Namecheap | 1.2% | 1.0% | 0.2% |
| Self-hosted and other providers | 32.5% | 18.7% | 18.5% |
"Publish DMARC p=reject": share of these domains that tell the world to reject unauthenticated mail claiming to come from them. Source: MailTester Ninja Deliverability Radar, September 2026.
Three things stand out.
Two companies set the rules for half the inboxes. Google and Microsoft together filter 50.9% of the mail-enabled domains in the sample, before counting personal Gmail and Outlook.com accounts. Both publish formal requirements for senders, and both enforce them. If you follow only two sets of rules, follow theirs.
One business domain in ten sits behind a security gateway. Proofpoint, Mimecast, Cisco IronPort and Barracuda together protect 10.2% of mail-enabled domains, mostly larger organizations. A gateway filters your message before the recipient's mailbox ever sees it, and it can quarantine mail that Google or Microsoft would have accepted. The organizations that pay for one are also the strictest about authentication: 62% of Proofpoint-protected domains publish p=reject for their own mail. If you sell to companies, a meaningful part of your list is behind one of these filters.
A third of domains run their own servers or use smaller providers, each with its own filtering. That is why testing your inbox placement at Gmail alone tells you only part of the story.
Gate 1: Can the Address Receive Mail?
Before any filter reads your message, the receiving server decides whether the recipient exists. Every "no" is a hard bounce. Bounces are the fastest way to damage a sender's reputation, because mailbox providers read a high bounce rate as the signature of someone mailing a list they did not build.
What unverified data looks like
In the 30 days to October 30, 2026, MailTester Ninja ran more than half a billion address checks. Here is how the ones that returned a definitive answer break down:
| Result | Share | What it means if you send |
|---|---|---|
| Valid mailbox exists | 35.0% | Safe to send. |
| Invalid mailbox does not exist | 39.3% | Hard bounce. |
| No mail server domain has no MX record | 10.4% | Hard bounce: typo, expired domain or invented address. |
| Catch-all domain accepts every address | 15.1% | Cannot be confirmed: may reach a person, bounce later or vanish. |
| Disposable temporary inbox | 0.2% | Delivered, but nobody will read it. |
Half of the addresses, 49.7%, could not receive email at all. This is not what a healthy opt-in newsletter list looks like: people verify the data they doubt, such as purchased or scraped lead lists, addresses guessed by email-finding tools, or old CRM exports. But that is exactly the data that gets sent when nobody checks it. Mail a list like this unverified and about half the messages bounce. That is enough to get an account suspended by most sending platforms, and to burn a sending domain in a single campaign. Amazon SES, for example, puts an account under review once its bounce rate reaches 5%.
Check an address before you send to it
Real-time SMTP verification, with catch-all and disposable detection. Free for single checks, nothing stored.
Catch-all domains: the 15% nobody can confirm
A catch-all domain accepts mail for any address, real or not, so no verifier can confirm the mailbox from the outside. Some of these messages reach a real person, others are silently discarded or bounce hours later. Treat catch-all addresses as a separate segment: send to them after your verified addresses, in smaller batches, and drop the ones that never engage. Our guide to catch-all email addresses explains how to handle them.
Lists decay, so verification is not a one-time job
People change jobs, companies change domains, and free mailboxes get closed. A list verified a year ago is not verified today (see email list decay). Two habits keep bounces low: verify addresses at the point of capture, with an API call on your signup and lead forms, and re-verify any list older than three months before you mail it. Our step-by-step guide shows how to verify a mailing list. For cold outreach, also think twice about role-based addresses such as info@ or sales@, which reach several people and draw more complaints.
Gate 2: Can You Prove Who You Are?
Authentication lets the receiving server check that a message really comes from the domain shown in the From line. Three DNS records do the work:
1SPF: who may send for your domain
A list of the servers and services allowed to send email with your domain in the return path. Every tool that sends for you (your email platform, CRM, helpdesk, invoicing tool) must be in it, within the limit of 10 DNS lookups.
2DKIM: a signature on every message
Your sending service signs each message with a private key, and publishes the matching public key in your DNS. The receiver can then prove the message was not forged or altered on the way. Use 2048-bit keys.
3DMARC: what to do when the checks fail
A policy that requires SPF or DKIM to pass for the domain in the From line (this is called alignment), tells receivers what to do with mail that fails (nothing, quarantine or reject), and sends you daily reports on who is sending in your name.
Where the web stands
Among the 40,366 mail-enabled domains in our sample:
Publish SPF91.7%
Publish DMARC77.6%
Enforce DMARC (quarantine or reject)49.0%
Reject (p=reject)26.7%
SPF is close to universal among established domains, and DMARC has gone mainstream. A sending domain without DMARC now belongs to a shrinking minority, and the large providers treat it that way.
What Gmail, Yahoo and Microsoft require
| Provider | Who it applies to | Requirements | Since |
|---|---|---|---|
| Gmail, Yahoo | Anyone sending to their users | SPF or DKIM, valid forward and reverse DNS for the sending IP, TLS, spam rate kept under 0.3% | February 2024 |
| Gmail, Yahoo | Senders of more than 5,000 messages a day | SPF and DKIM, DMARC (p=none accepted) aligned with the From domain, one-click unsubscribe on marketing mail | February 2024, enforcement tightened since |
| Microsoft (Outlook.com, Hotmail, Live) | Senders of more than 5,000 messages a day | SPF, DKIM and DMARC (at least p=none) aligned with SPF or DKIM; failing mail goes to Junk or is refused with error 550 5.7.515 |
May 2025 |
Our guide to Gmail and Yahoo bulk sender requirements covers each rule and how to set up SPF, DKIM and DMARC. Three practical points from the data:
- Do not agonize over ~all versus -all. Of the domains that publish SPF, 50.2% end their record with ~all (softfail) and 44.9% with -all (hardfail). Receivers treat both as a failure signal. DMARC is what turns a failure into an action.
- Start DMARC at p=none, but do not stay there. 36.3% of DMARC records are still at p=none. It is the right first step, because the reports show you every service sending in your name before you enforce. As a destination, it protects nothing: anyone can still spoof your domain, and the spam they send damages your name.
- Check your IPv6 setup. 99.9% of Google-hosted domains and 91.3% of Microsoft-hosted ones accept mail over IPv6. If your own server has IPv6, it will often deliver to them over IPv6. Gmail refuses such mail when the IPv6 address has no reverse DNS, with the error "this message does not meet IPv6 sending guidelines regarding PTR records and authentication". Many senders set up reverse DNS for IPv4 and forget IPv6.
You can check any domain's SPF, DKIM and DMARC for free with our email authentication checker, which explains the exact fix for each gap.
Gate 3: Do They Trust You?
Once a message passes the first two gates, filters rely mostly on reputation: what they have already seen from your domain and your sending IP addresses. Reputation is built from a handful of signals:
- Bounces, which is why gate 1 matters so much.
- Spam complaints. Google asks senders to stay below 0.1% and never reach 0.3%. Amazon SES reviews accounts at 0.1%. One complaint per thousand messages is already a lot.
- Engagement. Replies, clicks, messages moved out of spam help; messages deleted unread, or never opened, hurt.
- Spam traps, addresses that belong to no real person and exist to catch senders who mail lists they did not build. Verification removes dead addresses, but recycled traps can look valid, so permission and engagement remain the real protection.
- Blocklists. A listing on a major list such as Spamhaus has an immediate effect; many minor lists have almost none. Our guide to email blacklists explains which ones count.
- History and consistency. A new domain that sends 10,000 messages on its first day looks exactly like a spammer. Volume that grows gradually and stays steady looks like a real business.
Reputation is slow to build and quick to lose. A new domain or IP needs a warm-up: start with small daily volumes, send first to your most engaged recipients, and increase step by step over several weeks. Our email warm-up guide gives a schedule, and our guide to sender reputation covers how to repair a damaged one. For cold outreach, send from a separate domain, so that a reputation problem on prospecting never reaches your invoices and password resets.
Content and Engagement
Content matters less than most senders think, and in different ways. Lists of forbidden "spam words" are largely a myth today: modern filters judge a message mostly by who sent it and how recipients react to it. What still causes trouble:
- A mismatch between the From name, the sending domain and the domains of the links.
- Link shorteners and links to domains with a poor reputation.
- Messages that are a single image, or have no plain-text version.
- No easy way to unsubscribe, which turns "not interested" into "report spam". Bulk senders must offer one-click unsubscribe.
Measure engagement with clicks and replies rather than opens. Since Apple Mail Privacy Protection loads images automatically, open rates are inflated and say little about the inbox (see which email metrics to trust). To see how a message scores against spam filters before sending it, run an email spam test.
How to Measure Deliverability
1Read bounces and complaints after every send
Your sending platform reports both. A hard bounce rate above 2% means a list problem; a complaint rate above 0.1% means a targeting or permission problem.
2Register with the providers' own tools
Google Postmaster Tools shows the spam rate Gmail users report for your domain and whether you meet Gmail's sender requirements. Microsoft SNDS shows how your sending IPs perform at Outlook.com. Both are free.
3Read your DMARC reports
The aggregate reports (rua) list every server sending in your name and whether it passes authentication. They reveal forgotten tools and spoofing.
4Test a real message
Send one email to our free email deliverability test and get a score out of 100 covering SPF, DKIM, DMARC, SpamAssassin, blocklists and reverse DNS. To audit a whole domain or sending IP, run a Deliverability Radar report.
5Check inbox placement before large sends
A seed test sends your message to test mailboxes at several providers and shows where it lands: inbox, promotions or spam. Our guide to the email deliverability test compares the options.
Diagnosing Common Problems
| Symptom | Likely cause | First check |
|---|---|---|
| Hard bounce rate above 2% | Unverified or outdated list | Verify the list, remove invalid and no-MX addresses |
550 5.7.515 from Outlook or Hotmail |
SPF, DKIM or DMARC missing or failing | Authentication checker |
| Gmail error mentioning "IPv6 sending guidelines" | No reverse DNS on your IPv6 address | Add a PTR record for the IPv6 address, or send over IPv4 |
554 5.7.1 "blocked using zen.spamhaus.org" |
Sending IP or domain on a blocklist | Blocklist checker, fix the cause, then request delisting |
| Accepted, but clicks collapse at one provider | Spam folder placement at that provider | Seed test, then the provider's spam rate in Postmaster Tools or SNDS |
| Many "try again later" (4xx) deferrals | Greylisting or rate limiting | Slow down and let your server retry: normal for new senders (see greylisting) |
| B2B prospects never reply, yet nothing bounces | Security gateway quarantine, or catch-all domains | Check authentication, segment catch-all addresses, test with a Microsoft 365 seed |
The Deliverability Checklist
Authentication
- SPF lists every service that sends for you, within 10 DNS lookups.
- DKIM signs all your mail, with 2048-bit keys.
- DMARC is published with reports (rua), aligned, and on a path from p=none to enforcement.
- Reverse DNS is set for every sending IP, IPv6 included.
List quality
- Verify at capture with an API call on every form.
- Re-verify any list older than three months before sending.
- Segment catch-all addresses and send to them last, in small batches.
- Remove contacts who have not engaged in six months.
Reputation and sending
- Warm up every new domain and IP.
- Keep volume steady, without spikes.
- Separate cold outreach from your main domain.
- Offer one-click unsubscribe on all marketing mail.
Measurement
- Hard bounces below 2%, complaints below 0.1%.
- Google Postmaster Tools and Microsoft SNDS set up.
- Test a real message before every large send.
Methodology
Domain scan. The 50,000 highest-ranked domains of the Majestic Million list, scanned by the MailTester Ninja Deliverability Radar on September 2, 2026. We read public DNS only (MX, SPF, DMARC, and whether the MX hosts have IPv6 addresses); no email was sent. 40,366 domains had MX records. The aggregate dataset is free to reuse under CC BY 4.0 on the Email Infrastructure Index.
Verification results. Aggregate counts of the results MailTester Ninja returned between September 30 and October 30, 2026: more than half a billion checks, about four in five of which gave a definitive result. The others met temporary conditions (greylisting, timeouts, servers limiting checks) or our own abuse protections, and are left out of the percentages. These are counters only: MailTester Ninja does not store the addresses it checks, so nothing on this page can be traced to a person or a customer.
Limits. The domain panel comes from the top of a popularity ranking, so it over-represents large, well-run organizations: adoption of SPF and DMARC across all domains is lower. The verification results reflect what our users chose to check, which leans toward doubtful data.
Frequently Asked Questions
What is a good email deliverability rate?
Aim for a delivery rate above 98%, hard bounces below 2% (below 0.5% on an opt-in list) and spam complaints below 0.1%. Inbox placement varies too much by provider and industry for a universal target; what matters is the trend. A drop of a few points at one provider is a warning sign worth investigating.
What is the difference between email delivery and email deliverability?
Delivery means the receiving server accepted your email. Deliverability means it reached the inbox. A message filed in spam counts as delivered, so a 99% delivery rate can hide a serious inbox placement problem.
Does email verification improve deliverability?
Yes, because it removes the addresses that would bounce, and bounces damage your sender reputation. In our data, 49.7% of the addresses checked with a definitive result could not receive email. Verification does not fix authentication or content, which are separate gates.
Do I need DMARC?
If you send more than 5,000 messages a day to Gmail, Yahoo or Outlook.com users, yes: it is required. Below that volume it is still strongly recommended. 77.6% of mail-enabled domains in our sample publish one, and it is the only record that stops others from sending spam in your name.
How long does it take to fix a bad sender reputation?
Authentication errors can be fixed in a day. Reputation recovers more slowly: usually several weeks of lower, steady volume sent only to verified and engaged recipients. Delisting from a blocklist takes hours to days once the cause is fixed.
Why do my emails reach the inbox at Gmail but not at Outlook?
Each provider runs its own filters and weighs signals differently, and Microsoft gives a lot of weight to the reputation of the sending IP. Check your authentication first, then your IP's data in Microsoft SNDS, and run a seed test to confirm where messages land.
Is cold email deliverability different?
Yes. Cold email has no prior consent and lower engagement, so the margin for error is smaller: verify every address, send from a separate domain, keep the daily volume per mailbox low and warm up each mailbox. See our guides on cold email setup and how many cold emails to send per day.
How can I test my email deliverability for free?
Send a message to our free email deliverability test for a score out of 100, check your domain with the Deliverability Radar, and verify your list with MailTester Ninja. None of these tools stores your data.
Continue reading
DataEmail Deliverability Statistics
Industry benchmarks, each traced to its source.
Read the guide →
AuthenticationGmail and Yahoo Sender Requirements
SPF, DKIM, DMARC and one-click unsubscribe, set up step by step.
Read the guide →
How to build sending volume without hurting your reputation.
Read the guide →

About the author
Danila Kozlov
COO at MailTester.Ninja
Danila has spent the last few years deep in email deliverability, helping SaaS companies and growth teams fix the infrastructure problems that silently kill their outbound results. As COO of MailTester.Ninja, he oversees product and operations with a single obsession: making email verification fast, accurate, and genuinely useful for the people who need it most.
Deliverability starts with addresses that exist
Half of the addresses people check cannot receive email. Find out which ones are in your list before your next campaign does it for you.
Real-time SMTP verification · Catch-all detection · Bulk lists and API · Zero data storage




