SPF, DKIM and DMARC, provider by provider.
The records each service needs and where to find them, checked against the provider’s own pages. Each guide starts with how that service’s mail passes DMARC, because that decides which records matter.
Mailbox hosts where staff mail comes from
Microsoft 365 staff mail
Microsoft 365 passes DMARC by SPF and by DKIM once both are set up. SPF is one include; DKIM is two CNAME records and a switch in the Defender portal, and it is off for custom domains until you turn it on.
Google Workspace staff mail
Google Workspace passes DMARC by SPF and by DKIM once both are set up. SPF is one include; DKIM is a key you generate in the Admin console, publish as a TXT record, then switch on.
Zoho Mail staff mail
Zoho Mail passes DMARC by SPF and by DKIM once both are set up. SPF is one include; DKIM is a selector you add in the Admin Console, publish, verify and enable.
Sending services newsletters, marketing and app mail
Mailchimp newsletters
Mailchimp passes DMARC by DKIM. Its campaigns use Mailchimp's own bounce address, so SPF passes for Mailchimp's domain, not the client's, and does not count. Two CNAME records make DKIM sign as the client's domain.
SendGrid app and transactional mail
SendGrid passes DMARC by DKIM and by SPF once domain authentication is done. With Automated Security on (the default) you publish CNAME records and SendGrid maintains the SPF and DKIM behind them, on a subdomain of the client's domain.
HubSpot marketing mail
HubSpot passes DMARC by DKIM: two CNAME records let it sign as the client's domain. It also asks for an SPF include, but on HubSpot's shared sending the bounce address is HubSpot's, so DKIM is what aligns.
Amazon SES app and transactional mail
Amazon SES passes DMARC by DKIM once Easy DKIM's three CNAMEs are published. SPF passes for amazonses.com by default, which does not align; a custom MAIL FROM subdomain makes SPF align too.
Mailgun app and transactional mail
Mailgun passes DMARC by DKIM and by SPF once the sending domain is verified. Use a subdomain such as mg.<domain>: its records then sit apart from the domain's own mail and still align.
The free tools
Set up once. Watched every day.
DNS says what a domain asks receivers to do. Only the reports receivers send say what happened to its mail. DMARC Harbor reads those reports for every client domain, every day, names each service sending as it, and says when it is safe to move to p=reject.