Step by step
- In SendGrid, go to Settings, Sender Authentication, and click Get Started under Domain Authentication.
- Pick your DNS host, and enter your root domain (
example.com, withoutwww). Leave automated security on unless you have a reason not to. - Add the records it shows at your DNS provider.
- Come back and click Verify. DNS changes can take up to 48 hours; if only some records verify, wait and try again before changing anything.
Do I add include:sendgrid.net to my SPF record?
Not with automated security on. SendGrid sends with a return address on the em subdomain, and receivers check SPF there, which SendGrid manages through that CNAME. Adding include:sendgrid.net to your main record only uses up one of your ten SPF lookups. With automated security off, SendGrid shows TXT and MX records instead, and you maintain them yourself.
The mistakes I see most
- The domain added twice. GoDaddy, Route 53, Namecheap and others add your domain to the host automatically. Typing
em1234.example.comgivesem1234.example.com.example.com, and verification fails. Enter onlyem1234ands1._domainkey. - A CNAME proxied through Cloudflare. DNS records for email must be "DNS only" (grey cloud).
- No DMARC. SendGrid's setup suggests
v=DMARC1; p=none;. Gmail and Yahoo require a DMARC record from bulk senders. See setting up DMARC. - Sending from a different domain. Authentication covers the domain you set up. Mail from another domain, or a subdomain you didn't authenticate, is still signed by SendGrid's own domain.