Opens in a new tab

include:sendgrid.net — SendGrid’s SPF include, and why it belongs on a subdomain

include:sendgrid.net lists the servers SendGrid sends from. Once you authenticate your domain in SendGrid, its mail carries a return-path on a subdomain SendGrid creates — em1234.yourdomain.com — and SPF is checked there, not on your root domain. So the include on your root record does nothing for SendGrid mail; the record that counts is on that subdomain, which SendGrid sets up itself by default.

v=spf1 include:sendgrid.net ~all
Belongs toTwilio SendGrid — Email API and Marketing Campaigns
Needed on your domain?Only in some set-ups — by default SPF checks a different domain for its mail

What it costs, and is it in your record?

We measure include:sendgrid.net as the page opens. Enter a domain: we read its SPF record, follow every include and say whether SendGrid’s is there and what it costs.

What it covers

Mail sent through Twilio SendGrid’s Email API and its Marketing Campaigns.

Do you need it?

Domain authentication gives your mail a return-path on a subdomain such as em1234.yourdomain.com, “to handle bounce and unsubscribe notices”. SendGrid explains that it creates “a unique SPF record linked only to your new subdomain … incoming emails will be checked against this specific SPF record, not the original one tied to your primary domain”.

With Automated Security on — the default — that subdomain is a CNAME to SendGrid, which publishes its SPF record for you. With it off, you publish a TXT record on the subdomain yourself: v=spf1 include:sendgrid.net ~all. Either way, SPF passes and aligns with your From domain, because the subdomain is part of it.

The include matters on your root record only if SendGrid support has turned on “Preserve Sender”, which keeps your own address as the return-path — something SendGrid does “only … in extreme circumstances”, and which stops it capturing bounces.

Common mistakes

  • A DMARC record with aspf=s: the return-path em1234.yourdomain.com does not strictly match yourdomain.com, so SPF alignment fails. SendGrid advises avoiding it.
  • With Automated Security off, forgetting to add a new dedicated IP to the SPF record on the subdomain.
  • A custom return-path label that matches an existing CNAME, which then gets overwritten.

Setting up SendGrid: SPF, DKIM and DMARC together →

Questions

Can I remove include:sendgrid.net from my root SPF record?

If you have authenticated your domain in SendGrid, SPF for its mail is checked at the em subdomain it created, so the include on your root is not what makes SendGrid’s mail pass. Check first that nothing else relies on it.

Sources

Checked on 26 September 2026 against these official sources:

Stay under 10 lookups without dropping a sender

Let us host your SPF record: you publish one include line, we flatten every service in it to their addresses and refresh it hourly, so however many there are they fit in a few lookups — and we tell you when a service changes its addresses. On the Personal plan and up.

Create a free account