What's actually changed in email deliverability in 2026

Google Postmaster Tools' reporting overhaul

Google retired the original Postmaster Tools domain reputation chart at the end of 2025. The replacement, Postmaster Tools v2, reports spam rate, authentication results, delivery errors, and bulk-sender compliance status, and added a dedicated Deliverability analysis view in June 2026 that breaks placement issues down by likely cause rather than just showing a raw spam-rate trend line. For senders used to the old reputation chart as a quick health check, the practical change is that spam rate - with its documented 0.30% ceiling and sub-0.10% target for reliable placement - is now the clearest single number to watch, alongside the new cause-level breakdown when something needs investigating further.

DMARCbis formally replaces the original DMARC specification

DMARCbis - formalised as RFC 9989, RFC 9990, and RFC 9991 - became the current DMARC standard in May 2026, replacing RFC 7489, which had been the governing specification since 2015. DMARCbis clarifies and tightens several areas that the original specification left ambiguous, including alignment handling and reporting format details, without requiring senders to change a correctly configured existing DMARC record immediately - but new deployments and any DMARC tooling built against the spec should reference the current RFCs rather than the retired one.

Validity's Heatwave blocklist

Validity launched the Heatwave domain-level blocklist on 3 September 2026, evaluated at lookup.validity.tools with a /delist review path for removal requests. The notable shift here is the domain-level evaluation, distinct from the IP-based blocklists most senders are used to checking - a domain can appear on Heatwave independent of which IP or platform is currently sending on its behalf, which means the usual "switch sending IP" recovery tactic doesn't address a Heatwave listing.

A reference table of what changed

What hasn't changed

The fundamentals remain the same: authenticate with SPF, DKIM, and DMARC; keep lists clean; warm up new domains and mailboxes gradually; generate genuine engagement. None of 2026's tooling or standards changes alter these basics - they change what you can measure and where additional reputation risk can now show up, not the underlying practices that keep deliverability healthy.

What to watch for as these changes settle in

Each of these changes is recent enough that best practice around them is still developing in places. Postmaster Tools v2's Deliverability analysis view, having only launched in June 2026, will likely get refined as Google gathers feedback on which cause categories senders find most useful. DMARCbis-aligned tooling from major ESPs and DNS providers is still rolling out unevenly, so check whether your specific sending platform and DNS host have updated their guidance and interfaces to reference the current RFCs rather than the retired one. And Heatwave, as a new blocklist, doesn't yet have the long track record that lets senders calibrate exactly how much weight different receiving systems give it compared to older, more established blocklists.

None of this uncertainty changes what to actually do day to day - authenticate correctly, keep lists clean, warm up gradually - but it's worth revisiting how you monitor for these specific changes every few months rather than treating this summary as a fixed, final reference. Set a recurring reminder to re-check each of these sources every few months rather than relying on this summary indefinitely, since deliverability tooling and standards continue to be updated at a pace that makes any single point-in-time summary a starting reference rather than a permanent one. Put this reminder on a recurring calendar entry tied to a specific person's responsibility, rather than leaving it as a general intention, since a check that depends on someone simply remembering to do it tends to lapse within a couple of quarters.

What not to do

Do not assume the retired Postmaster Tools v1 reputation chart is still the reference point - it's gone, and v2's spam-rate figure plus the Deliverability analysis view is the current source. Do not treat DMARCbis as requiring an urgent record change if your existing DMARC setup already passes alignment correctly. Do not check only IP-based blocklists and skip Heatwave on the assumption that one blocklist check covers all of them - the methodology and evaluation level genuinely differ.

MailPilot tracks per-mailbox reputation, bounce, and complaint signals continuously, and its seed-inbox placement checks reflect current provider behaviour rather than a static snapshot, so it stays aligned with changes like these as they roll out.