[ Protocols & standards ]

Standards and transitions

DMARCbis, RFC changes and protocol transitions: what changes, when, and how to move without breaking mail.

26 guides

[ All guides ]

Article

The Evolution of Email: Its Journey to Becoming Indispensable

Explore the remarkable journey of email and its transformation into a vital communication tool in our lives.

Article

The Evolution of SPF: A Historical Journey to Its Critical Importance in Email Security

Learn about its evolution, challenges, and impact on protecting email communications from phishing and spoofing attacks.

Guide

A change register for evolving email-authentication standards

Maintain an auditable standards change register that connects an authoritative event to affected routes, evidence and a reviewed operational decision.

Guide

Assess the DRPF proposal and its unresolved trust questions

Assess DRPF’s dated proposal, reciprocal validation and conceptual revocation while keeping current status and implementation evidence explicitly open.

Guide

Assessing provider guidance that still cites RFC 7489

Review provider guidance that cites RFC 7489 by separating still-valid product steps, changed standards language and unverified implementation behavior.

Guide

Build a post-quantum DKIM standards watchlist

Compare published DKIM algorithm guidance with current PQ proposals, and record the verifier, DNS, message-size and approval evidence still missing.

Guide

Building a DMARCbis acceptance-test pack for a domain portfolio

Design a versioned DMARC acceptance pack that separates policy discovery, alignment, reporting and portfolio-specific release decisions.

Guide

Choose np only after establishing domain nonexistence

Distinguish existing names, NODATA, NXDOMAIN and resolution failure before selecting np, sp or an Author Domain policy.

Guide

Compare classic DKIM replay with DKIM2’s proposed detection context

Compare unchanged signed-message reuse with spec-09 envelope binding, intermediary attribution, repeated observations and original-time evidence.

Guide

Design a DKIM2 lab with reproducible, bounded conclusions

Define versioned DKIM2 cases, evidence fields and cleanup before execution, while preserving the boundary between a lab and production support.

Guide

DKIM2 proposals: separate current drafts from implementation claims

Review DKIM2 spec-09, its revision history and related drafts without treating a proposal or reported implementation as deployed conformance.

Guide

DMARC specifications, errata and IANA registrations: which source to trust

Use published DMARC specifications, registry entries and verified correction status for different evidence questions without treating any one page as universal implementation proof.

Guide

DMARCbis readiness: what to review before changing DNS

Review DMARCbis changes across DNS, policy, reporting and sender ownership. Build a scoped readiness register before changing production settings.

Guide

How to verify whether a new email requirement actually applies to your organisation

Determine whether an announced email requirement applies by mapping its authoritative scope to actual organizational roles and sending streams.

Guide

Move beyond percentage based DMARC rollout assumptions

Review legacy DMARC pct rollout plans against RFC 9989 testing semantics, mixed receiver behavior and evidence-led acceptance and recovery criteria.

Guide

Read ARC retirement proposals without overstating their status

Read the dated ARC and reclassification records, separate proposal language from approval, and keep provider support and migration evidence explicit.

Guide

Review deprecated DMARC tags without guessing

Review legacy DMARC pct, rf and ri tags against the current registry, protect active reporting controls and prepare an evidence-led minimal record change.

Guide

Revise aggregate report parsers for RFC 9990

Plan an RFC 9990 aggregate parser migration with namespace recognition, legacy profiles, field preservation, extension handling and defensive test gates.

Guide

Revise failure report handling for RFC 9991

Plan RFC 9991 failure-report intake with conditional field requirements, external destination verification, privacy minimization and unexecuted acceptance gates.

Guide

Test DMARC t semantics without promising receiver support

Build the six expected t-policy combinations, separate assessment from disposition and identify the receiver evidence still needed.

Guide

Test legacy and updated DMARC interoperability

Prepare a legacy versus updated DMARC test matrix with fixed inputs, staged protocol outcomes, reporting coverage and explicit unrun evidence cells.

Guide

Trace DMARC policy discovery through a bounded DNS tree

Follow a fictional DNS tree to distinguish the Author Domain, selected policy and organizational boundary under RFC 9989.

Guide

Trace message changes through DKIM2’s proposed trust model

Follow an invented original and modified message through spec-09 recipes, chain checks and verification limits without claiming a real verified result.

Guide

Track DKIM2 DNS proposals through an isolated experiment plan

Pin DNS-03 syntax, distinguish key and policy names, preserve draft inconsistencies and require compatible software before any experiment.

Guide

Use psd to explain DMARC boundaries and suffix fallback

Compare psd=y, psd=n and default discovery with fictional suffix and tenant records, including policy precedence and reporting boundaries.

Guide

Which DMARC RFC governs each implementation component?

Map core evaluation, aggregate reporting and failure reporting to the current RFCs while keeping errata and actual deployment evidence separate.

Related free tools

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

[ More in Protocols & standards ]

All topics