[ Regional requirements ]

US federal email authentication: determine applicability of government directives

US federal agencies have been directed to use SPF, DKIM and DMARC with an enforcing policy, and contractors and partners who email them are increasingly expected to meet the same bar. Whether a directive applies to you depends on who you are and who you send to, but the technical goal is the same: aligned SPF or DKIM on every sending service and a DMARC (RFC 9989) policy of quarantine or reject.

Before you change anything, it helps to see exactly where your domain stands today. The EmailAuth AI Agent reads your live DNS, explains which requirements your records already meet, and gives you the ready-to-paste changes to reach enforcement safely. Start with your domain below, or book a free call with an EmailAuth engineer.

To get specific help for US federal email authentication, engage with our EmailAuth AI Agent. It reads your domain's live DNS, checks what is already in place, and gives you ready-to-paste records or walks you through each step.

Open the EmailAuth AI Agent

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

Regional requirements and research