Call · 30 min
MarketingMattia Esposito10 November 202614 min read

Email deliverability in 2026. Three lines in the DNS decide whether Gmail, Yahoo and Outlook let you in.

A well-written email ends up in spam because of a DNS record nobody checked. Here is what Gmail, Yahoo and Outlook require, with the checklist and three example records in Word and PDF.

In brief

Deliverability is an email’s ability to reach the inbox, and in 2026 it depends first of all on three DNS records: SPF, DKIM and DMARC. Without them, Gmail can reject the message or send it to spam.

Google has required it of everyone since 1 February 2024. Senders sending more than 5,000 messages a day to Gmail must have all three records, one-click unsubscribe and a spam rate below 0.30%; since November 2025 non-compliant messages are also rejected. Yahoo asks the same, Microsoft since 5 May 2025.

DMARC has a new standard. Since May 2026 it is RFC 9989, which replaces RFC 7489 and makes the pct tag historic.

The checklist with the three example records can be downloaded below, in Word and PDF, without leaving your email.

Written by: Mattia Esposito, AI and marketing consultant, founder of Itria AI. From Puglia, based in Turin since 2023, he works remotely in Italy and abroad. LinkedIn profile.

The checklist with the three example records, to download

A sheet with the three records written for an example domain, the Gmail, Yahoo and Outlook requirements and ten checks with where to look, in Word to fill in and PDF to print. You need access to the domain’s DNS panel and to that of the service sending the emails. It takes an afternoon.

The deliverability checklist with example SPF, DKIM and DMARC records and the Gmail, Yahoo and Outlook requirements
FileContentsLink
Wordto fill in, in Italian

The three example records, the requirements by provider, the ten checks.

deliverability-email-spf-dkim-dmarc-checklist.docx

PDFto print, in Italian

The same checklist, to tick off with a pen.

deliverability-email-spf-dkim-dmarc-checklist.pdf

The three records for the example domain azienda.example

SPF, TXT record on azienda.example
v=spf1 include:_spf.provider.example -all

DKIM, TXT record on s1._domainkey.azienda.example
v=DKIM1; k=rsa; p=(the public key your sending service provides)

DMARC, TXT record on _dmarc.azienda.example
v=DMARC1; p=none; rua=mailto:[email protected]

The .example domain is reserved for examples by RFC 2606: put yours in its place, and in place of provider.example the name your sending service gives you. If you send from two services, for example the company mailbox and a newsletter tool, SPF needs two includes.

N.What to checkWhere to look
1

A single SPF record, with every service sending email in the domain’s name, within 10 DNS lookups.

nslookup -type=TXT yourdomain.com

2

DKIM active on every sending service, with the key published in the DNS.

Service panel, DNS

3

DMARC published, even at p=none, with the rua address for reports.

nslookup -type=TXT _dmarc.yourdomain.com

4

The From domain matches the one passing SPF or DKIM.

Gmail, «Show original»

5

Sending IPs have valid reverse DNS (PTR).

Sending service provider

6

The connection uses TLS and the message follows the RFC 5322 format.

Gmail, «Show original»

7

Marketing emails have List-Unsubscribe and List-Unsubscribe-Post, DKIM-signed, and a visible link in the body.

Message headers

8

Unsubscribers leave the list within 2 days.

Sending tool

9

The spam rate stays below 0.10% and never touches 0.30%.

Google Postmaster Tools

10

DMARC reports get read, and the policy rises from none to quarantine to reject.

The rua report mailbox

On 10 November 2026 I queried itria.io’s DNS with the same commands as the checklist: SPF, DKIM and DMARC are all three there. It’s the check I run before any change to the domain, and it takes two minutes.

What deliverability is: meaning and the difference from delivery

Deliverability is the share of emails that reach the inbox, while delivery counts only those accepted by the recipient’s server. A delivered email can end up in spam and still show as «delivered» in the sending tool. The deliverability rate vendors show should therefore be read together with bounces and complaints.

In Italian it’s called recapitabilità, or people keep the English word. The mailbox providers decide: Google for Gmail, Yahoo, and Microsoft for Outlook.com, Hotmail and Live. Their rules are public and the same worldwide, and they are the basis of every test.

Gmail, Yahoo and Outlook requirements in 2026

The three providers ask for the same things, with different thresholds and dates: domain authentication, DMARC for high-volume senders, easy unsubscribe and few spam complaints. The table brings together the official pages of Google, Yahoo and Microsoft, read on 10 November 2026.

ProviderRequirementFrom when
Gmail, all senders

SPF or DKIM, valid forward and reverse DNS, TLS, RFC 5322 format.

1 February 2024

Gmail, all senders

Spam rate in Postmaster Tools below 0.30%, ideally below 0.10%.

1 February 2024

Gmail, over 5,000 a day

SPF and DKIM and DMARC (even p=none), aligned From.

1 February 2024

Gmail, over 5,000 a day

One-click unsubscribe on marketing emails, visible link in the body.

1 February 2024

Gmail, bulk senders

Above 0.3% spam, no mitigation procedure.

June 2024

Gmail, stricter enforcement

Non-compliant messages get temporary and permanent rejections.

November 2025

Yahoo, all senders

SPF or DKIM, spam below 0.3%, valid reverse DNS.

February 2024

Yahoo, bulk senders

SPF and DKIM, DMARC at least p=none with rua, unsubscribes honoured within 2 days.

February 2024

Outlook.com, over 5,000 a day

Passing SPF and DKIM, DMARC at least p=none and aligned; non-compliant mail goes to Junk.

5 May 2025

One sentence in Google’s FAQ changes the maths for anyone who thinks they’re under the threshold: «Senders who meet the above criteria at least once are permanently considered bulk senders.» A single day of 5,000 messages to Gmail, counted on the same primary domain, and bulk sender status stays for good.

Microsoft sends non-compliant messages to Junk and has announced rejection, with error 550 5.7.515, at a date not yet set. Yahoo calculates the spam rate on mail delivered to the inbox, so its figure and Google’s can’t be compared.

SPF, DKIM and DMARC: what each record does

SPF says which servers can send for the domain, DKIM signs the message and DMARC ties the two checks to the domain the recipient sees in the From. They are three TXT records in the DNS, and the receiving server reads them in this order, as in the diagram. Without DMARC, SPF and DKIM can pass on a domain different from the one shown.

An email’s path: the recipient’s server checks SPF, then DKIM, then DMARC, and decides between inbox, spam and rejection The email leavessigned with DKIM SPFis the IP listed? DKIMdoes the signature match? DMARCaligned with the From? The decisioninbox, spam, rejection sender’s serverTXT on azienda.examples1._domainkey _dmarcp=none, quarantine, reject
The receiving server reads three records in the sender’s DNS. DMARC passes if SPF or DKIM pass with the same domain as the From, and its policy says what to do when it fails.
ElementWhat it doesRecord
v=spf1

Opens the SPF record; a domain can have only one.

SPF

include:

Authorises an external service’s servers; every include costs a lookup.

SPF

-all and ~all

Anything not listed fails (-all) or is only suspicious (~all).

SPF

selector._domainkey

The DNS name where the key sits; each service has its own selector.

DKIM

k=rsa; p=

Algorithm and public key: at least 1024 bits, 2048 recommended (RFC 8301).

DKIM

p=

The policy: none observes, quarantine sends to spam, reject refuses.

DMARC

rua=

The address receiving aggregate reports (RFC 9990).

DMARC

adkim= and aspf=

Relaxed alignment (r, subdomain too) or strict (s, identical domain).

DMARC

sp= and np=

The policy for subdomains and, new in RFC 9989, for non-existent ones.

DMARC

t=y

Test mode introduced by RFC 9989; pct has become historic.

DMARC

SPF and the 10-lookup limit

An SPF record can make the receiving server run at most 10 DNS queries, and beyond that number verification returns a permanent error. RFC 7208 of 2014 sets it: «SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation». Include, a, mx, ptr, exists and redirect all count, including those nested inside includes.

The limit gets exceeded without anyone noticing: every service added over the years brings its include, and some includes contain others. The result is called permerror and, for DMARC, equals an SPF that fails. The fix is to remove services that no longer send anything and leave the signing to DKIM.

DKIM: the signature and key length

DKIM adds to every message a signature made with a private key, and the receiving server checks it with the public key written in the sender’s DNS. RFC 6376 of 2011 describes it as the way the domain owner takes responsibility for the message. Unlike SPF, the signature stays valid when the email is forwarded unchanged.

RFC 8301 of 2018 sets the length: signers must use RSA keys of at least 1024 bits and should use 2048. To move to 2048 you generate the new key with a different selector, publish it in the DNS and remove the old one once the service signs with the new one.

DMARC in 2026: RFC 9989 replaces RFC 7489

In May 2026 the IETF published RFC 9989, which brings DMARC onto the IETF standards track and replaces RFC 7489 of March 2015, an informational document for eleven years. RFC 9990 for aggregate reports and RFC 9991 for individual failure reports came out alongside it. The syntax of existing records keeps working.

Three things change. The pct tag, used to apply the policy to a share of messages, is historic, because values between 0 and 100 were applied inconsistently; t=y for testing takes its place. There’s np, the policy for subdomains that don’t exist. And the organisational domain is found by walking up the DNS tree, without the Public Suffix List.

The path stays in three steps: p=none with rua, which doesn’t touch delivery and brings in reports on who sends in the domain’s name; then quarantine, when the reports show only known services; then reject.

One-click unsubscribe (RFC 8058)

Gmail and Yahoo require bulk senders to offer one-click unsubscribe, done with two headers defined by RFC 8058 of 2017. List-Unsubscribe contains an HTTPS address; List-Unsubscribe-Post contains the pair List-Unsubscribe=One-Click. Pressing the mailbox’s button unsubscribes without opening any page.

The two headers, for the example domain

List-Unsubscribe: <https://azienda.example/disiscrizione?id=abc123>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The RFC asks for both headers to be covered by the DKIM signature. Google specifies that one-click unsubscribe is needed only for marketing and promotional emails, not transactional ones like an order confirmation. Yahoo asks for the request to be honoured within 2 days and also accepts the mailto method, but recommends the RFC 8058 POST.

Why my emails go to spam

In the most common cases the cause lies in one of the technical checks, and Google writes it in the error code it returns. The sender FAQ lists the codes: 5.7.26 for unauthenticated messages, 4.7.23 for an IP without valid PTR, 4.7.29 for a connection without TLS.

The bounce message carries the code. If instead SPF and DKIM pass and the email still goes to spam, they often pass on a domain different from the From, and DMARC fails.

When the technical checks are in order, the list remains. Addresses collected without a reason to receive the email generate complaints, and complaints affect the domain’s reputation for every later email, including those to customers. That’s why good B2B lead generation starts from the right recipient before the copy.

How to run a deliverability test (free check)

The basic check costs nothing and needs three tools: the terminal, a Gmail account and Google Postmaster Tools. With nslookup -type=TXT and the domain name you read the SPF; with the same command on _dmarc followed by the domain you read the DMARC. For DKIM you need the selector, found in the sending service’s panel.

Then you send yourself an email at a Gmail address, open the message and choose «Show original» from the menu: at the top SPF, DKIM and DMARC appear with PASS or FAIL and the domain that passed them. If the domain differs from the From, alignment is missing.

Postmaster Tools, free, shows the spam rate Google measures. Online tools’ deliverability scores read the same records, but don’t match any provider threshold.

Email open rate: why in 2026 it’s an inflated number

The open rate is measured with an invisible image in the message, and Apple’s Mail Privacy Protection, which users can turn on on iPhone, stops senders knowing whether the email was opened. Apple says so in the iPhone user guide. For those mailboxes the open figure the sender sees doesn’t say whether anyone read it.

That’s why the open rate is useful for comparing one send with another on the same list, never as an absolute measure. For a B2B campaign what counts is clicks, replies and contact requests, read in the site’s analytics and the inbox. The rate formulas are in the KPI glossary.

Two cases measured on itria.io

The domain’s three records. On 10 November 2026, read with nslookup on itria.io’s domain: SPF, DKIM and DMARC published.

The email that wasn’t there. The site side counts as much as the DNS side. On 25 September 2026 itria.io’s contact page, in the code served, contained no address: Cloudflare’s obfuscation hid it from anything not running JavaScript. Of 121 food producers’ sites, 7 obfuscated it and 7 didn’t write it at all. The case is in the piece on the email AI assistants can’t see.

Cold email and deliverability: the technology is the same everywhere, the law isn’t

The Gmail, Yahoo and Microsoft requirements apply worldwide, while whether you can write cold changes from one country to another. An email with perfect SPF, DKIM and DMARC is still unlawful in Italy without a legal basis. The table lines up the legal texts read on 10 November 2026.

WhereSending ruleSource
Everywhere

Mailbox providers’ authentication, unsubscribe and spam thresholds.

Google, Yahoo, Microsoft

Italy

Promotional emails only with the consent of the contracting party, which includes legal persons.

Privacy Code, Arts 130 and 121

Italy

A recognisable sender and a contact for objecting free of charge.

Art. 130(5)

European Union

Prior consent for natural persons; for companies member states decide.

Directive 2002/58/EC, Art. 13

United Kingdom

Consent or soft opt-in for individual recipients, sole traders included.

PECR 2003, reg. 22

United Kingdom

For everyone: sender identity and an opt-out address.

PECR 2003, reg. 23

United States

No prior consent; opt-out honoured within 10 business days.

15 U.S.C. § 7704

United States

A valid physical postal address in every commercial message.

15 U.S.C. § 7704

The legal side, with the Garante’s decisions, is on the page on lawful B2B cold email. Building a list with consent starts from good content to offer: the lead magnet examples show which work. For writing copy with AI there are the email marketing prompts.

How contact source, sending, reply and follow-up fit together is told on the page on B2B acquisition engines. And if you want to be found even when you’re not writing, in assistants’ answers, the steps are in how to show up in ChatGPT. Tailored work is on the page on contact research and qualification.

Questions and answers

What is email deliverability?

The ability of a message to reach the recipient’s inbox. The server that accepts the email can still put it in spam: that’s what sets it apart from delivery. It depends on domain authentication with SPF, DKIM and DMARC, on sender reputation and on spam complaints.

Are SPF, DKIM and DMARC mandatory?

To send to Gmail, since 1 February 2024 every sender must have at least SPF or DKIM. Senders sending more than 5,000 messages a day to Gmail accounts must have all three, with DMARC even at p=none and the From domain aligned. Yahoo asks the same of bulk senders; Microsoft asks it above 5,000 messages a day to Outlook.com.

Which DMARC policy should you start with?

p=none with an rua address to receive aggregate reports: it doesn’t change delivery and shows who is sending in the domain’s name. When the reports hold no more surprises you move to quarantine and then reject. The pct tag, used for gradual steps, is historic in the new RFC 9989 standard.

Why do my emails go to spam even with SPF and DKIM?

Because passing the checks isn’t enough: the From domain must be aligned with the SPF or DKIM domain, the sending server must have valid reverse DNS and the complaint rate must stay low. Google asks you to keep it below 0.10% and never reach 0.30%.

How do I run a free deliverability test?

In three steps: query the domain’s DNS with nslookup to see SPF and DMARC, send yourself an email at Gmail and open «Show original» to read the SPF, DKIM and DMARC results, and register the domain with Google Postmaster Tools to follow the spam rate.

Notes on sources

  1. Google, Email sender guidelines and Email sender guidelines FAQ: requirements from 1 February 2024, the 0.10% and 0.30% thresholds, mitigation from June 2024, rejections from November 2025, error codes; source of the quotation. Read on 10 November 2026.
  2. Yahoo, Sender Best Practices: requirements from February 2024, unsubscribes within 2 days, spam below 0.3%. Read on 10 November 2026.
  3. Microsoft Defender for Office 365 Blog, Outlook’s New Requirements for High-Volume Senders, 2 April 2025, updated on 30 April 2025.
  4. IETF, RFC 9989 (DMARC, May 2026, obsoletes RFC 7489 and RFC 9091, appendix A.6 on the pct tag), RFC 9990 (aggregate reports) and, as a historic text, RFC 7489 (March 2015).
  5. IETF, RFC 7208 (SPF, April 2014, section 4.6.4, source of the quotation), RFC 6376 (DKIM, September 2011), RFC 8301 (key length, January 2018), RFC 8058 (one-click unsubscribe, January 2017), RFC 2606 (domains reserved for examples).
  6. Apple, Use Mail Privacy Protection on iPhone, iPhone User Guide. Read on 10 November 2026.
  7. Normattiva, Legislative Decree 196/2003, Art. 130; EUR-Lex, Directive 2002/58/EC, Art. 13; legislation.gov.uk, PECR 2003, reg. 22; Cornell LII, 15 U.S.C. § 7704.
  8. itria.io’s records were read with nslookup on 10 November 2026; the case of the obfuscated email dates from 25 September 2026.
·Who does it for you

Reaching the inbox is the prerequisite. Writing to the right companies is the work. Positioning is built starting from the market.

Mattia Esposito, who wrote this guide, also works with Itria on positioning: in-depth market analysis to find where competitors are exposed and take that ground. He did it on his own site first. In August, asked who had founded itria.io, ChatGPT couldn’t find him. From 11 October to 7 November 2026 itria.io pages appeared 13,803 times in Google and Bing results and 3,818 times in AI answers: Google’s AI Overviews and AI Mode, and Microsoft Copilot.