Deliverability, explained.

Videos, written guides, and a jargon-free glossary covering everything we’ve learned about reaching the inbox: authentication, sender reputation, placement testing, and the mistakes that send mail to spam.

Run your first deliverability check

Teaches the fast pre-send routine and how to use the Unspam spam checker, so you can spot inbox risks before you hit send.

A 5 Minute Email Deliverability Check Before Hitting Send | Unspam Academy 5:04
// Deliverability check

A 5 Minute Email Deliverability Check Before Hitting Send

Walk through a complete deliverability check in five minutes using two free tools: spam score, inbox placement, and the fixes that move the needle fastest.

Best Email Spam Checker: Test Deliverability with Unspam | Unspam Academy 2:45
// Product tour

Best Email Spam Checker: Test Deliverability with Unspam

A walkthrough of the Unspam spam checker and deliverability test: what each score signal means and how to act on it before you hit send.

Read the signals, not just the score

Teaches how a full deliverability audit differs from a one-off spam test, so you know which diagnostic to reach for and how to read what it finds.

Email Deliverability Audit vs Spam Test: What is the Difference? | Unspam Academy 5:21
// Diagnostics

Email Deliverability Audit vs Spam Test: What is the Difference?

Why revenue keeps dropping even when your emails “send”: the difference between a spam test and a deliverability audit, and when each one is the right call.

2025 Email Deliverability Report: Signals Shaping Inbox in 2026 | Unspam Academy 5:05
// Industry report

2025 Email Deliverability Report: Signals Shaping Inbox in 2026

The signals reshaping inbox placement going into 2026: engagement weighting, authentication enforcement, and what the year’s data tells us about where mail actually lands.

Master deliverability at scale

Two long-form webinars that connect the fundamentals to the current state of the inbox and proven tactics for high-stakes sending seasons.

The Actual State of Email Deliverability | Unspam Academy 1:06:03
// Webinar

The Actual State of Email Deliverability

A full webinar with Email Industries on the real state of email deliverability: what’s working in 2025, what’s broken, and the diagnostic playbook senders should run.

Inbox for the Holidays: Proven Email Deliverability Tips | Unspam Academy 1:06:04
// Webinar

Inbox for the Holidays: Proven Email Deliverability Tips

A full webinar on holiday-season deliverability: authentication, branded links, volume strategy, list hygiene, engagement signals, and the privacy laws that affect your sends.

Email deliverability, from the ground up.

The concepts behind every test. Read these once and the rest of the Academy makes more sense.

How mailbox providers decide where your mail lands

There is no single rulebook. Gmail, Yahoo, Outlook, and Apple Mail each run their own filtering, and they weigh dozens of signals on every message: who is sending, whether the message is authenticated, how recipients have treated your past mail, and what the content looks like. The decision is per message and per recipient, not a fixed verdict on your domain.

Think of it as a running score rather than a gate. Strong authentication and a clean reputation earn you the benefit of the doubt; a spike in complaints or a cold, unengaged list erodes it fast. The same email can reach one subscriber's inbox and another's spam folder because their individual history with you differs.

Because the logic is hidden and changes often, you cannot reverse-engineer a guaranteed inbox. What you can do is control the inputs the filters reward, then measure placement directly with an inbox placement test instead of guessing from open rates.

Email authentication, explained simply

Authentication proves a message genuinely came from you and was not forged in transit. SPF lists which servers are allowed to send for your domain. DKIM signs each message with a private key so the receiver can verify it against a public key published in your DNS. DMARC ties these together: it passes when SPF or DKIM passes and the result aligns with the visible From domain, and it tells receivers what to do when checks fail.

Your DMARC policy escalates through three levels: p=none watches without acting, p=quarantine sends failures to spam, and p=reject blocks them outright. Since the Google and Yahoo bulk-sender rules took effect in February 2024, any sender of roughly 5,000 or more messages a day to Gmail must have SPF, DKIM, and at least a p=none DMARC policy in place. One detail trips people up: SPF evaluation is capped at 10 DNS lookups, and exceeding it returns a permerror that quietly breaks the record.

BIMI is the optional layer on top. With DMARC at enforcement (p=quarantine or p=reject), BIMI can display your verified logo next to the message in supporting clients. You can confirm all four records resolve correctly with the free SPF, DKIM, DMARC, and BIMI checkers.

Domain and IP reputation

Reputation is the trust score mailbox providers attach to the sources you send from. It splits across two layers: your sending domain, which travels with you wherever you send, and the IP address that actually transmits the mail. Domain reputation is the more durable of the two, which is why protecting it matters more than chasing a clean IP.

Reputation is earned over time and through consistency. Providers watch your volume patterns, complaint rates, bounce rates, and how recipients engage. A sudden jump in volume from a cold domain reads as suspicious, which is why new domains and IPs need a gradual ramp before they carry full volume. Shared IPs mean you also inherit the behavior of every other sender on that address.

Damage is asymmetric: reputation drops quickly after a bad send and recovers slowly through sustained good behavior. The practical takeaway is to keep volume steady, fix complaint sources fast, and avoid sending to addresses you have not built a relationship with.

Why engagement increasingly dominates

Mailbox providers want to deliver mail people actually want, so they lean hard on how recipients behave. Opens, replies, forwards, and moving a message out of spam are positive signals. Deleting without reading, ignoring mail for weeks, or hitting the spam button are negative ones. Over time these signals shape where your future mail lands for each recipient.

This is why authentication and a clean list get you to the door but engagement decides whether you stay in the inbox. A domain with perfect SPF, DKIM, and DMARC will still slide toward spam if subscribers consistently ignore it. Conversely, a segment that opens and clicks reliably builds inbox placement that protects your whole program.

The actionable response is to send to people who want your mail and to suppress the ones who do not. Segment by recent activity, slow down or stop mailing dormant contacts, and treat a falling engagement rate as an early warning long before it shows up as a deliverability problem.

Bounces, complaints, and spam traps

A clean list is one of the strongest deliverability levers you control. Hard bounces are permanent failures from invalid addresses, and continuing to mail them tells providers you are not maintaining your list. Complaints happen when recipients mark you as spam; the Google and Yahoo rules require keeping that rate below 0.3% and ideally under 0.1%, because a high complaint rate is one of the fastest ways to land in spam.

Spam traps are the most dangerous entries. These are addresses that should never receive mail: recycled traps were once real but abandoned, and pristine traps were created solely to catch senders who harvested or bought lists. Hitting them signals poor list acquisition and can trigger blacklisting.

Hygiene is ongoing, not one-time. Remove hard bounces immediately, honor unsubscribes promptly with one-click List-Unsubscribe, and suppress long-dormant contacts before they decay into traps. Validating addresses before you send is the cleanest prevention, which is what email verification is for.

Content, rendering, and the pre-send test

Content is both a filtering signal and a rendering risk. Filters read your subject, body, links, and image-to-text balance, and patterns common to spam, such as misleading subjects, link shorteners, or broken authentication on tracking domains, can pull your score down. Branded, consistent sending domains for your links help more than borrowed or unfamiliar ones.

Rendering is the other half. An email that scores clean can still fail if it breaks across clients. Gmail, Outlook, Apple Mail, and mobile apps each interpret HTML differently, so a layout that looks right in one can collapse in another, and dark mode, image blocking, and clipped messages all change what recipients actually see.

A pre-send test catches both before your list does. Running a spam-score test surfaces content and authentication problems while previews show how the message renders across real clients, so you fix issues once instead of learning about them from a drop in results.

We see this across millions of checks.

The pre-send deliverability checklist.

Run this before any campaign. Most steps take minutes with a free tool.

Authenticate the domain

  • Publish a valid SPF record and confirm it stays under the 10 DNS lookup limit, since exceeding it returns a permerror that fails SPF. Check SPF →
  • Confirm DKIM is signing every message and the public key resolves in DNS for the selector you send with. Check DKIM →
  • Publish a DMARC policy and move it past p=none toward p=quarantine or p=reject once your reports show legitimate mail aligns. Check DMARC →
  • Verify SPF or DKIM aligns with your visible From domain, because DMARC only passes when an authenticated result is aligned. Run health check →
  • If you display a brand logo in the inbox, confirm your BIMI record is valid and references a reachable SVG and certificate. Check BIMI →

Keep the list clean

  • Validate the address list and drop invalid, role-based, and risky mailboxes before sending to protect your bounce rate. Verify emails →
  • Check your sending domain against blocklists so a listing does not silently sink the whole campaign. Check domain →
  • Check your sending IP against the major DNSBL zones, especially if you send from a dedicated or recently changed IP. Check IP →
  • Include a working one-click List-Unsubscribe header and keep complaint rates below 0.3%, ideally under 0.1%, to satisfy Gmail and Yahoo bulk-sender rules.
  • Suppress unengaged and previously bounced addresses so you send to people who actually open, which keeps complaints low.

Test before sending

  • Run the full message through a spam-score test and resolve anything that pushes you out of the safe SpamAssassin range of 0 to 3.0. Run spam test →
  • Send a seed test to confirm the campaign lands in the inbox rather than spam across the providers your audience uses. Test placement →
  • Check where attention actually lands with an eye-tracking heatmap so the call to action sits where readers look first. View heatmap →
  • Preview the email across major clients to catch broken rendering, missing alt text, and a subject or preheader that truncates. Preview email →
  • Send to yourself on mobile and desktop, then click every link to confirm tracking, redirects, and the unsubscribe path all work.

Deliverability terms, made simple.

Every acronym a sender runs into, defined without the jargon.

Delivery vs. deliverability
Delivery means the receiving server accepted the message (no bounce). Deliverability is whether that accepted message actually reaches the inbox rather than the spam folder, which is a separate and harder problem.
Inbox placement rate
The share of delivered messages that land in the inbox instead of the spam folder. It is the truest measure of deliverability, since a message can be delivered yet still be filtered out of sight.
Sender reputation
The trust score that mailbox providers assign to your sending domain and IP address, based on signals like complaints, bounces, spam-trap hits, and engagement. A strong reputation raises inbox placement; a damaged one pushes mail to spam.
SPF (Sender Policy Framework)
A DNS record listing which servers are allowed to send mail for your domain. The receiving server checks the sending IP against that list, and evaluation is capped at 10 DNS lookups before it returns a permerror.
DKIM (DomainKeys Identified Mail)
A signature added to each message using a private key, which the receiver verifies against a matching public key published in your DNS. It proves the message was authorized by the domain and was not altered in transit.
DMARC (Domain-based Message Authentication, Reporting and Conformance)
A DNS policy that tells receivers what to do when a message fails authentication, with policies of p=none (monitor), p=quarantine, or p=reject. It also requests aggregate reports so you can see who is sending as your domain.
DMARC alignment
The requirement that the domain validated by SPF or DKIM matches the visible From address. DMARC passes only when SPF or DKIM passes and is aligned with that From domain, which is what stops spoofing.
BIMI (Brand Indicators for Message Identification)
A standard that lets you publish a verified brand logo in DNS so supporting mailbox providers can display it next to your messages. It requires an enforced DMARC policy (p=quarantine or p=reject) as a prerequisite.
One-click List-Unsubscribe
A header (RFC 8058) that lets recipients unsubscribe with a single action directly from the inbox, without visiting a landing page. Google and Yahoo require it for bulk senders as of February 2024.
Complaint rate
The percentage of recipients who mark your mail as spam. Google and Yahoo require bulk senders to keep this below 0.3% and ideally under 0.1%, because a high rate quickly destroys sender reputation.
Feedback loop (FBL)
A service from a mailbox provider that notifies you when a recipient marks your message as spam, so you can suppress that address. It is how senders see and act on complaints before reputation suffers.
Spam trap
An email address that never opts in and exists only to catch senders with poor list hygiene. Hitting one, especially a recycled address that was once real, signals to providers that you are mailing stale or purchased lists.
Double opt-in
A signup flow where a new subscriber must confirm their address by clicking a link before receiving mail. It costs a few signups but blocks typos, bots, and spam traps at the source, which protects bounce and complaint rates.
Hard bounce
A permanent delivery failure, such as a non-existent mailbox or invalid domain. The address should be suppressed immediately, since repeated hard bounces signal poor list quality and harm reputation.
Soft bounce
A temporary delivery failure, such as a full mailbox or a server that is down or rate-limiting. Senders typically retry for a while, then treat a persistently soft-bouncing address as undeliverable.
Seed list
A controlled set of test addresses across major mailbox providers that you send to alongside a real campaign. Checking where those seeds land lets you estimate inbox placement before and during a send.
IP warmup
The practice of gradually increasing send volume from a new or cold IP address so mailbox providers can build trust at a controlled pace. Sending too much too fast from an unestablished IP triggers throttling or spam filtering.
Dedicated vs. shared IP
A dedicated IP sends only your mail, so its reputation is entirely yours to build and protect. A shared IP pools many senders, which smooths low volumes but means you inherit their behavior. Dedicated suits high, steady volume; shared suits low or irregular sending.
Sending subdomain
A subdomain used for one class of mail, such as mail.yourdomain.com for marketing, so its reputation stays separate from your main domain. Isolating streams this way keeps a problem in one from dragging down transactional mail on the root domain.
Reverse DNS (PTR)
A DNS record that maps a sending IP back to a hostname, the reverse of a normal lookup. Providers expect a sending IP to have valid forward and reverse DNS that match, and missing or mismatched rDNS is a common reason mail is throttled or refused.
Greylisting
An anti-spam tactic where a receiving server temporarily rejects mail from an unknown sender with a soft failure, expecting a legitimate server to retry. Real mail servers retry and get through; many spam sources do not.
MTA (Mail Transfer Agent)
The server software that routes email between domains using SMTP, handing messages from one MTA to the next until delivery. Your sending MTA's behavior, retries, and IP reputation directly shape deliverability.

Deliverability questions, answered.

What counts as a good inbox placement rate?
Inbox placement rate is the share of delivered mail that reaches the inbox rather than the spam folder, and higher is always the goal. The catch is that a single blended number hides where the problem is. Gmail, Outlook, and Yahoo each filter differently, so a healthy-looking average can mask a much weaker result at one provider. The only reliable read is a per-provider measurement: seed a test list across the mailbox providers your audience actually uses and see where each one lands, rather than assuming that delivered means inboxed. Track that figure over time and treat any sustained drop at a specific provider as the signal to investigate authentication, list quality, and engagement for that audience. You can measure it directly with an inbox placement test.
What is the difference between a spam test and an inbox placement test?
A spam test scores one message against the filters and rules that decide whether it looks like spam: authentication results, SpamAssassin-style content scoring, broken links, image-to-text ratio, and header issues. It tells you why a message might be flagged and what to fix before you send. An inbox placement test answers a different question: for a given send, where does the message actually land at each provider, inbox, spam, or a tab. Placement reflects sender reputation and engagement, not just the content of one email. Use the spam test to clean up the message itself, then use a placement test to confirm real-world delivery. Unspam offers both: a free spam-score test and a separate inbox placement test.
Do I really need all three of SPF, DKIM, and DMARC?
Yes, for any serious sending program. SPF authorizes which servers may send for your domain. DKIM signs the message with a key whose public half lives in your DNS, so the receiver can confirm it was not altered. DMARC ties those results to the visible From domain through alignment and tells receivers what to do when a message fails. DMARC passes when SPF or DKIM passes and is aligned, so you technically need only one aligned mechanism to pass, but publishing both makes you far more resilient because either can break on forwards or relays. Since the February 2024 Google and Yahoo rules, bulk senders must have SPF, DKIM, and at least a p=none DMARC policy, so all three are effectively mandatory at scale. You can check each record with the free DMARC checker and its companion tools.
What are the Google and Yahoo sender requirements?
They took effect in February 2024 and apply to bulk senders, meaning roughly 5,000 or more messages a day to Gmail addresses. You must authenticate with both SPF and DKIM, publish a DMARC policy of at least p=none on your sending domain, keep your spam complaint rate below 0.3% and ideally under 0.1%, and offer one-click List-Unsubscribe per RFC 8058 with the request honored within two days. Messages also need valid forward and reverse DNS on the sending IP and must use a From domain that aligns with your authentication. Miss these and Gmail or Yahoo can rate-limit or reject your mail outright. Across the senders Unspam measures, only 14% currently pass the one-click List-Unsubscribe requirement, so this is the most commonly missed item.
What is email warmup, and does Unspam do it?
Warmup is the practice of gradually increasing send volume from a new IP or domain so mailbox providers build a reputation for you instead of treating a sudden spike as suspicious. You start with small batches to your most engaged recipients, grow the volume over days or weeks, and keep complaints near zero so providers learn to trust the sender. It matters most when you move to a new domain, a new dedicated IP, or restart after a long pause. Unspam does not offer automated warmup as a product. We can explain the process and point you to the metrics that show whether reputation is building, but the actual ramp happens through your own sending platform. If you want hands-on help planning a ramp, the team at Email Deliverability Consultants can guide it.
Why does my mail land in the Promotions tab instead of the inbox?
The Promotions tab is not the spam folder. Gmail sorts commercial and marketing-style mail there based on signals like bulk sending patterns, promotional language, heavy images and buttons, multiple links, and marketing footers. It is a category, not a penalty, and many recipients read Promotions normally. You usually land there because the message looks like a campaign rather than a personal one-to-one note. To improve the odds of the primary inbox, write in a plainer personal style, cut excessive images and tracking links, send from a consistent recognized From name, and build engagement so recipients open and reply. There is no header that forces the primary tab; placement follows content and behavior over time.
What is a spam trap?
A spam trap is an email address used by mailbox providers and blocklist operators to catch senders with poor list hygiene. There are two main kinds. A pristine trap is an address that was never a real user and was published only to catch scrapers, so hitting one signals you harvested or bought addresses. A recycled trap is an old abandoned address a provider reactivated as a trap, so hitting one signals you keep mailing contacts who stopped engaging long ago. Both damage sender reputation and can get your domain or IP listed on blocklists. Avoid them by collecting addresses with consent, never buying lists, verifying new sign-ups, and removing addresses that have not engaged in months. You can confirm whether your domain or IP is already listed with the free blocklist checkers.
How long does fixing deliverability take?
It depends entirely on the cause. A misconfigured SPF, DKIM, or DMARC record is often a same-day fix once DNS propagates, typically within a few hours to a day. Reputation problems take longer because providers respond to sustained behavior, not single changes. Recovering from elevated complaints, a recent blocklisting, or a burned domain usually takes several weeks of disciplined sending to rebuild trust, and a heavily damaged domain can take a couple of months or warrant a fresh start. List-hygiene problems sit in between: you can suppress unengaged contacts immediately, but the reputation benefit shows up over subsequent sends. The honest answer is that authentication is fast and reputation is slow, so fix the technical setup first, then give engagement time to recover.
How is sender health trending across real-world senders?
Unspam tracks this across the senders it tests, and the trailing twelve-month picture gives a useful baseline. About 82% of messages pass a full deliverability check, with 14% warning and 4% failing, and 89% score in the safe SpamAssassin range of 0 to 3.0. Authentication is uneven: 90% of domains publish a valid SPF record, but 42% still have no DMARC policy at all and 99% publish no BIMI record. Only 14% pass the one-click List-Unsubscribe requirement. The current global deliverability health score is 87 out of 100. The takeaway for most senders is that content scoring is in decent shape, while DMARC adoption and List-Unsubscribe are the common gaps worth closing. You can explore the live figures on the benchmark data hub.

Watch a video. Then test your own send.

Free spam check, deliverability score, and an AI action plan, all in under 30 seconds.