SPF, DKIM and DMARC for SendGrid
Set up SendGrid domain authentication so app mail passes DMARC: Automated Security's CNAME records for the return path and the s1 and s2 DKIM selectors, and the DMARC record.
SendGrid
app and transactional mail
SPF
aligns after setup: on the em<number> return-path subdomain SendGrid creates, which aligns with the domain
DKIM
aligns after setup: selectors s1 and s2, as CNAME records SendGrid points at its keys
DMARC pass
one aligned pass is enough
- CNAME
em<number>u<number>.wl<number>.sendgrid.netThe return path. SendGrid shows the exact names and values. - CNAME
s1._domainkeys1.domainkey.u<number>.wl<number>.sendgrid.net - CNAME
s2._domainkeys2.domainkey.u<number>.wl<number>.sendgrid.net
1Start domain authentication
In SendGrid open Settings › Sender Authentication and, under Domain Authentication, Get Started. Choose the DNS host and enter the domain the From address uses.
2Keep Automated Security on
Under Advanced Settings leave Use automated security checked, unless the DNS host refuses underscores in CNAME names. Change the DKIM selector only if another service already uses s1 or s2.
3Publish the records
Add the CNAME records SendGrid shows. If the DNS host adds the domain itself, enter only the host part, such as em123.
4Verify
Back in SendGrid press Verify. DNS can take up to 48 hours.
5Publish a DMARC record
At _dmarc.<your domain>, a TXT record starting at p=none with a report address, so you can see this service's mail pass before you enforce. The DMARC generator writes one.
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.