Which email authentication procedure you need depends on the change in front of you: finding out which services send as your domain, keeping SPF, DKIM or DMARC in working order, or authenticating a domain in one particular service. The materials in this section are written for mail and DNS administrators and for the application owners who work with them. Every procedure states the conditions you should meet before you start, the evidence to collect along the way and how to judge whether the result is good. Pick the task in front of you.
Start with the sending services
If you cannot name a person responsible for every platform sending from your domain, map those streams before touching policy.
Work through who sends email from your domain, and who owns each sender. That procedure records each service instance with its business purpose, its approver, the person who operates its configuration and the message evidence you can get hold of. What you end up with is an inventory in which every unresolved ownership or authentication gap has become a specific request to the person who can close it.
When you need those owners, evidence references and pending decisions in a reusable table, open the email sender register template. It logs who approved each account and who manages its technical settings.
Routine maintenance and DMARC enforcement
Once your sending services are mapped out, pick the authentication change you need to make:
- To move DMARC past monitoring, open When to move DMARC from p=none to quarantine and reject. It covers the evidence that justifies quarantine, the separate decision about reject, the conditions under which you stop, how to roll the policy back and how to recover mail that enforcement affected.
- For a planned key replacement and its recovery path, use DKIM key rotation: when it’s safe to retire the old key. It takes you through the routine change, verifying the new signature and deciding when the old public key can be retired. It also separates routine rotation from a suspected compromise.
- When adding a tool or retiring a vendor, consult How to add a sender to an SPF record (and retire an old one). You will inspect the envelope sender domain, assess what the policy depends on, and verify that existing streams keep passing uninterrupted.
Before moving DMARC to quarantine or reject in production, put the written enforcement decision in the DMARC readiness checklist, which records the evidence before a policy change. For any DNS update, use the email DNS change checklist. It is the place for before-and-after DNS values, what you observed, who approved what and the next action; it treats publication and activation as two separate results.
Setting up authentication in a specific mail service
Pick the service that sends the messages you want to check:
- For Google Workspace organizations, follow Setting up SPF, DKIM and DMARC for a Google Workspace domain. It assumes an established Workspace organization with a working sending account and walks through SPF, DKIM, a check on a message received outside the organization and DMARC monitoring.
- If your team runs Microsoft 365, use How to set up SPF, DKIM and DMARC for a Microsoft 365 domain. It assumes an existing sending tenant with a custom domain and covers SPF, enabling DKIM, an external message check and DMARC monitoring; migrating mailboxes is outside its scope.
- For an application that already sends transactional mail, follow Postmark domain verification: DKIM, Return-Path and DMARC. It covers verifying the domain, the DKIM settings specific to your account, the optional custom Return-Path and a message check through the application’s own sending route.
If you need to troubleshoot an active delivery incident or explore another area, return to the knowledge base.


