Email Deliverability Checklist for B2B Outbound: What to Check, When, and What Passes


In this post:
This email deliverability checklist covers every check that decides whether your cold email lands in the inbox. Each check tells you what passes, how often to look and where to find it.
TL;DR
Keep cold email on separate sending domains with names that describe your service, because Google counts mail from your subdomains toward your main domain's bulk sender status, and that status is permanent.
Set up SPF with one record and no more than 10 lookups, DKIM with 2048-bit keys, and DMARC starting at p=none with reports switched on.
The published rules from Gmail, Yahoo and Outlook.com mostly cover personal inboxes, so your B2B buyers' corporate filters in Microsoft 365 and Google Workspace expect more from you.
Keep bounce rates under 2% and spam complaints under 0.1%, and stop sending to any address that returns a permanent error.
Check blocklists and inbox placement every week, and when a number slips, trace it back through every layer before you change anything.
How to use our email delieverability checklist
Each section covers one layer of your sending system, and each table tells you what passes, how often to check it and where. Work through the setup items once, then put the weekly and monthly ones in someone's calendar.

In our experience, deliverability issues rarely come from one big mistake, and they usually come from small checks nobody owns. We also label every number as either a mailbox provider rule or guidance from a sending tool, so you know which is which.
The email deliverability checklist for B2B outbound in 2026
The checklist below has nine parts, and each part covers one layer of your sending setup. Work through them in order, because each layer depends on the one before it.
Layer 1: Set up your sending domains and mailboxes
Everything else depends on where you send emails from. The most important rule is to keep cold email off your main domain.
Google counts mail from a primary domain and its subdomains together toward its bulk sender threshold of around 5,000 messages a day, and once a domain is classed as a bulk sender, it stays one. So a subdomain like outreach.yourcompany.com doesn't protect the domain your invoices and customer emails come from.

Source: Google, Email sender guidelines FAQ
We make one exception to that rule. Some enterprise clients in compliance-heavy industries won't send from unbranded domains, so for one client targeting companies with more than 2,000 employees, we used subdomains of the main domain instead.
Subdomains are debated, and they only make sense when the main domain has years of good reputation behind it, because a strong reputation is much harder to damage. Before you choose them, look up your main domain in Spamhaus's domain reputation checker, and stick to separate domains if the score is low.
New domains also start at a disadvantage, because Spamhaus gives newly registered domains a "poor" reputation by default, so we use a mix of new domains and older aged domains. If you target large enterprises, plan for domains that have aged at least a year before they carry cold email.
Watch the names of your sending domains as well.
We avoid sending domains that copy the company name one to one, because security gateways look for patterns, and in our experience, when one domain in a set of near-identical brand domains gets blocked, the others tend to follow. Names that describe the service spread that risk.

We also split sending across email providers, with about half through Google, 40% through Outlook and 10% through a custom SMTP setup, so one filtering change can't stop every campaign. If most of your market uses Microsoft Outlook, send from Outlook or SMTP mailboxes too, instead of only Google Workspace.
Most B2B teams don't need a dedicated IP address. Cold outbound from Google Workspace or Microsoft 365 shares the provider's IP addresses, so your domain reputation and sender reputation do most of the work.
Sending domain checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
Separate sending domains | No cold email from your main domain or its subdomains, unless a strong main domain and a compliance need justify subdomains | Once at setup | Your sending tool and Spamhaus |
Domain names | Names that describe your service on a classic extension like .com, instead of near-copies of your brand | Once at setup | Your registrar |
Domain age | At least a year old when you target large enterprises | Once at setup | Your registrar |
Mailboxes per domain | Three to five at most, per Instantly | Quarterly | Your sending tool |
Spread across email providers | A mix of Google and Microsoft mailboxes | Quarterly | Your sending tool |
Under platform limits | Under 2,000 messages a day per Google Workspace user and 10,000 recipients a day per Exchange Online mailbox | Monthly | Google and Microsoft admin consoles |
Layer 2: Authenticate your domains with SPF, DKIM and DMARC
Authentication proves your sender identity to receiving servers and protects your sender reputation. Without it, Gmail, Yahoo and Outlook.com can reject your mail outright.
How SPF, DKIM and DMARC work together
SPF (Sender Policy Framework) lists the servers allowed to send email for your domain. Each domain needs exactly one SPF record with no more than 10 DNS lookups, because a second record or an 11th lookup breaks it.
DKIM (DomainKeys Identified Mail) adds a digital signature, so the receiving server can confirm nobody changed the message on the way. Google and Yahoo require at least 1024-bit keys and recommend 2048.
DMARC (Domain-based Message Authentication, Reporting and Conformance) checks that your From domain lines up with SPF or DKIM and tells servers what to do when a message fails. Start with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com and move toward p=reject as your reports come back clean.

The DMARC standard changed in May 2026 to RFC 9989, which drops the old pct tag, so don't be surprised when older guides still show it.

Source: RFC 9989, Domain-based Message Authentication, Reporting and Conformance
Your sending domains also need MX records so they can receive replies, plus a valid reverse DNS (PTR) record and encrypted TLS connections, which Google requires from every sender.
Authentication checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
SPF record | Exactly one, with 10 lookups or fewer and ending in ~all | Once at setup, after every new tool | MXToolbox |
DKIM | 2048-bit keys, rotated at least twice a year per M3AAWG | Twice a year | Your email provider's admin console |
DMARC | At least p=none, aligned, with reports switched on | Once at setup | Google Check MX or MXToolbox |
DMARC enforcement | Moving from none to quarantine to reject | Quarterly | Your DMARC reports |
MX, reverse DNS and TLS | All three in place | Once at setup | Your email provider's settings |
Layer 3: Compare and meet the sending rules from Gmail, Yahoo and Microsoft
The big mailbox providers have all tightened their rules since 2024. Google and Yahoo started enforcing in February 2024, Apple followed for iCloud in February 2025, and Microsoft for Outlook.com in May 2025.
Provider | Who the rules cover | What they require | If you miss them |
|---|---|---|---|
Gmail | Around 5,000 messages a day to personal Gmail accounts | SPF, DKIM and aligned DMARC, one-click unsubscribe on marketing mail honored within 48 hours, spam rate under 0.3% with 0.1% as the target | Temporary and permanent rejections since November 2025 |
Yahoo | Bulk senders | SPF, DKIM, DMARC at p=none or stricter, one-click unsubscribe honored within two days, complaints under 0.3% | Filtering and blocking |
Outlook.com | More than 5,000 emails a day to consumer Outlook addresses | Passing SPF and DKIM, DMARC at least p=none and aligned | Junk first, then rejection with "550 5.7.515" |
Apple iCloud | Bulk senders | SPF, DKIM, a DMARC record, reverse DNS and a bounce policy | Rejection |
Why the published rules are only the minimum for B2B outbound
Here's the part almost no deliverability checklist mentions. Google says its sender guidelines don't apply to messages sent to Google Workspace accounts, and Microsoft's rules cover consumer Outlook addresses and leave out Microsoft 365.

Source: Google, Email sender guidelines FAQ
Your B2B buyers mostly use Workspace and Microsoft 365, often behind corporate filters that publish no rules. Those filters judge you on your sender reputation, your authentication and how recipients react, so the published rules are the floor.
The bigger the company, the harder this gets. Companies from around 200 employees up usually use email security gateways like Proofpoint, Barracuda or Mimecast, which are much harder to get through and quick to block a sender, so the larger your targets, the more every other part of this checklist matters.

Layer 4: Check and pass the Microsoft 365 checks most deliverability guides miss
Microsoft 365 is where a lot of outbound teams lose mail without noticing. A campaign looks fine in Gmail tests, and the same message goes to Junk or quarantine at a corporate tenant.
You can't see into a prospect's tenant, but you can check your inbox placement at Microsoft by sending test emails to a Microsoft 365 mailbox you control. Paste the headers into Microsoft's Message Header Analyzer and look at three values.
SFV shows Microsoft's spam verdict, where SFV:NSPM means Microsoft didn't mark the message as spam, and SFV:SPM means it did.
BCL is the bulk complaint level from 0 to 9, and a higher number means Microsoft expects more people to complain about mail like yours.
compauth is Microsoft's combined SPF, DKIM and DMARC result for your From domain, and a fail means Microsoft doesn't trust your sender identity.

Source: Microsoft, anti-spam message headers
Test against the Strict preset
Microsoft 365 admins can switch on preset security policies called Standard and Strict, and Microsoft always applies Strict first. Mail with a BCL of 7 or higher goes to Junk under the default policy, Standard lowers that to 6, and Strict quarantines anything at 5 or above.

Source: Microsoft, recommended settings for EOP and Defender for Office 365
So the same email can reach the inbox at one company and end up in quarantine at another. We test against a Strict mailbox before scaling a campaign, because that's the hardest filter your buyers can have.
Layer 5: Warm up your mailboxes and control sending volume
New domains and mailboxes have no reputation, and when you send emails in bulk from them straight away, it looks exactly like spam. Warm up builds that sender reputation by starting with very low volume and increasing it slowly.
During the warm up phase, a warm-up tool exchanges emails with a network of mailboxes that open, reply and mark them as important. We keep warm up on after campaigns start and avoid sudden spikes, because volume that jumps from zero to full speed looks like a hacked account.

Ask which warm-up pool your tool uses as well, because warm up only helps when the mailboxes in the pool behave like real ones.
Warm up checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
Warm up before the first campaign | At least two weeks per Instantly, or three to four weeks per lemlist | Once per new mailbox | Your warm-up tool |
Daily sends per mailbox | Around 30 per Instantly, under 40 for young mailboxes per lemlist, and no more than 50 per Smartlead | Weekly | Your sending tool |
Daily sends per domain | Under about 500 cold emails, per Smartlead | Weekly | Your sending tool |
Volume drops when problems appear | Lower volume as soon as bounce rates or deferrals rise, which Google also recommends | Whenever a number slips | Your sending tool |
Those per-mailbox numbers are guidance from sending tools, and neither Google nor Microsoft sets them. Hunter's 2026 report on 31 million outreach emails points the same way, with senders at 20 to 49 emails a day getting a 5.7% reply rate against a 4.5% average.
Layer 6: Clean your list to keep bounce rates and unsubscribes low
Every invalid address, spam trap and ignored unsubscribe costs you sender reputation. This is where cold email deliverability connects most directly to your GTM system, because your lists come from your enrichment workflows and your CRM.
Email marketing teams protect list quality with double opt-in, and cold outbound can't use it, so verification does that job instead. We verify every address through a waterfall of providers before it reaches a sequence, and Hunter's 2026 report put most of its 3.6% average bounce rate down to unverified contact data.
A hard bounce is a permanent (5xx) error, and Microsoft forbids resending after one, so hard bounces should leave your lists immediately. Spam traps are harder to spot because they look like normal addresses, including old ones that once belonged to real people.
List hygiene checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
Verification before every sequence | Invalid addresses removed, catch-all addresses handled separately | Before every campaign | Your verification tool |
Hard bounce rate | Under 2% | Weekly | Your sending tool |
Hard bounces suppressed | No resending after a permanent error | Monthly | Your suppression list |
Unsubscribes honored | Within 48 hours for Gmail and two days for Yahoo | Monthly | Your sending tool and CRM |
Bounces, unsubscribes and spam complaints synced | In HubSpot or Salesforce, so no other tool emails them again | Monthly | Your CRM |
Old lists and inactive subscribers re-checked | Verified again before reuse | Every 90 days | Your verification tool |
That 2% bounce limit is industry guidance, because no mailbox provider publishes one. The clearest published policy comes from Amazon SES, which reviews accounts at 5% and may pause them at 10%.

Source: Amazon SES, enforcement FAQs
Layer 7: Review your content quality and tracking
Once the technical layers pass, content quality decides whether your emails get read or turn into spam complaints.
According to Gartner's 2025 survey of 632 buyers, 73% of B2B buyers actively avoid suppliers who send irrelevant outreach, so we segment lists on behavioral data like website visits, hiring or a new person in the role.
Subject lines, spam trigger words and tracking
Spam filters care more about your reputation than single words, but spam trigger words still add up. We keep subject lines short and plain, avoid all-caps words and exclamation points, and send plain text, which keeps the text-to-image ratio safe.
Open tracking adds a tiny image that email clients load when the message opens, and that pixel is one of the signals spam filters look at. In Hunter's 2026 report, campaigns with open tracking off got a 7.4% reply rate, against 4.4% with it on.
Content checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
Open tracking | Off for cold email | Before every campaign | Your campaign settings |
Links | None in the first email and at most one in a follow up, per lemlist | Before every campaign | The email itself |
Format | Plain text, with no attachments | Before every campaign | The email itself |
Subject lines | Honest, with no fake "Re:" or "Fwd:", which Google warns against | Before every campaign | The email itself |
Sender details | Your real identity and a clear unsubscribe link or opt-out line | Before every campaign | The email itself |
Layer 8: Follow the consent rules for B2B cold email in the Netherlands and the EU
In Europe, the rules for cold email to businesses are stricter than many teams assume. This section summarizes the official positions and can't replace legal advice, so check your situation with a lawyer.
In the Netherlands, article 11.7 of the Telecommunications Act (Telecommunicatiewet) bans unsolicited commercial email without prior consent, and the Dutch privacy regulator says this also applies to emails to other businesses. The law allows two exceptions for business recipients.
The company published the address specifically to receive messages like yours.
The recipient is a company outside the European Economic Area, and you follow its local rules.
Every message has to show who you really are and give a working way to opt out, and the regulator ACM puts the burden of proof on the sender.

GDPR's "legitimate interest" doesn't change this, because the sending rule comes from separate law based on the EU's ePrivacy Directive, which each EU country applies in its own way.
Layer 9: Monitor your domain reputation and sender reputation
Monitoring tells you when your sender reputation starts slipping. Without it, a flagged domain or a broken DNS record can go unnoticed for weeks while your team rewrites copy that was never the problem.
Google Postmaster Tools shows your spam rate and domain reputation for personal Gmail accounts, and we check it weekly, though low-volume senders often see an empty dashboard.
Microsoft SNDS only helps if you own your sending IP addresses, so most teams rely on seed tests and blacklist monitoring through Spamhaus or MXToolbox.
Monitoring checklist
Check | What passes | Cadence | Where to check |
|---|---|---|---|
Spam complaints | Under 0.1%, and never 0.3% or higher | Weekly | Google Postmaster Tools and your sending tool |
Inbox placement | Most test emails land in the inbox at Gmail and Microsoft 365 | Weekly | A seed testing tool |
Blocklists | No domain or IP listed | Weekly | Spamhaus and MXToolbox |
Microsoft 365 headers | SFV:NSPM, a low BCL and compauth=pass | Before every campaign | Message Header Analyzer |
Engagement metrics | Reply, bounce and unsubscribe rates in line with past campaigns | Weekly | Your sending tool |
DMARC reports | No unknown services sending as your domain | Monthly | Your DMARC reports |
Troubleshooting deliverability issues
When a number slips, trace it back through the layers before you change anything, because a random fix usually hides the real cause. An underperforming campaign almost always has one of three problems, infrastructure, targeting or messaging, and the reply pattern tells you which one to check first.
What you see | Check first | What to look at |
|---|---|---|
Very few replies of any kind | Infrastructure, targeting or messaging | Start with deliverability, because emails in spam get no replies at all |
Plenty of replies, few of them positive | Messaging or targeting | The angle, the proof and whether the segment really has the pain |
Few replies, but most of them positive | Infrastructure or targeting | Inbox placement, and whether the list is too narrow |
Hard bounces jump | List quality | The list source and when it was verified |
Replies drop at one provider | That provider's filtering | Inbox placement tests and message headers |
Replies drop everywhere | Domain or IP reputation | Blocklists, DNS records and recent changes |
Spam complaints rise | Targeting and content | The segment, the copy and the unsubscribe link |
New domains never reach the inbox | Warm up | Warm up length, volume and authentication |
How email deliverability fits your GTM system
We treat email deliverability as part of the whole GTM system, because your outbound, your demo follow up and your meeting bookings all depend on reaching the inbox. A deliverability failure shows up as a pipeline problem first.
So the last checks are about how the system fits together. Your domains, DNS, DMARC reports and sending accounts should belong to your company's own accounts with a named owner, bounces and replies should sync to your CRM, and LinkedIn and calls should carry outreach while you fix a domain.

That's how we build deliverability for clients at Nebor, a GTM and RevOps agency, as one part of the outbound and inbound system in their own accounts. Our email deliverability guide explains the reasoning behind each layer, and our email deliverability statistics cover the data.
If your reply rates have dropped and nobody can tell you why, book a call with us and we'll go through the checklist with you.
Frequently asked questions about email deliverability
Is it a deliverability problem or a messaging problem?
Start with the reply pattern before anything else. Plenty of replies with few positive ones points to messaging or targeting, while few replies that are mostly positive points to infrastructure or targeting, so send a seed test across Gmail and Microsoft 365 to check inbox placement before you rewrite anything.
What is a good bounce rate for cold email?
Aim for a hard bounce rate under 2%. No mailbox provider publishes a bounce threshold, but Amazon SES uses 2% as its guideline, and Hunter's 2026 report found an average of 3.6% across cold outreach.
Should you send cold email from your main domain?
We'd advise against it, because Google counts mail from your main domain and its subdomains together toward its bulk sender threshold, and bulk sender status is permanent. Use separate domains with names that describe your service, and only consider subdomains if your main domain has a strong, long reputation and a compliance reason to stay branded.
Is B2B cold email legal in the Netherlands?
The Dutch rules are stricter than most teams expect. The privacy regulator's position is that commercial email to businesses needs prior consent, unless the company published the address for that purpose or is based outside the EEA, so check your approach with a lawyer.
Related Articles

Deliverability
The Ultimate Email Deliverability Guide: How We Get a Higher Inbox Placement Rate at Nebor
Your delivery rate can look perfect while every email lands in spam. This is the deliverability system we use on our own cold campaigns, from domain sourcing to inbox rotation.
Andrew van Rossenberg

Deliverability
10 Best Email Deliverability Experts to Fix Your Outbound Pipeline
A 98% delivery rate means nothing if the messages pile up in spam. Ten experts and tools that fix inbox placement, and the one question to ask before hiring any of them.
Ibrahim Litinine

Why the Best Time to Send Cold Emails is When the Intent Data or Buying Signals Say You Should
Nobody buys enterprise software because an email landed at 10 AM on a Tuesday. Buying windows open when budget, pain, and timing line up, and you can watch for them.
Ibrahim Litinine
By clicking Sign Up you're confirming that you agree with our Terms and Conditions.








