Opens in a new tab

mx.sendgrid.net: SendGrid’s MX record

mx.sendgrid.net, at 10, receives mail for Twilio SendGrid’s Inbound Parse, which posts it to your app. SendGrid asks for it on a hostname used for nothing else, such as parse.example.com — and as the only MX there.

What it isInbound mail for an app
MX records10 mx.sendgrid.net
SPFinclude:sendgrid.net

Does your domain use SendGrid Inbound Parse?

Enter a domain: we read its MX records as a sending server does, name whose each host is, and say whether SendGrid Inbound Parse’s are all there — and what else is.

The MX records

What SendGrid Inbound Parse asks for:

example.com.  MX  10 mx.sendgrid.net.

Worth knowing

The same host appears on an em<number> subdomain when SendGrid’s domain authentication has automated security turned off: there it serves the return path of sent mail, not an inbox.

Common mistakes

  • Other MX records on the parse hostname: mail goes to the lowest number, which may not be SendGrid.
  • Parsing the same domain you send from with automated security on — SendGrid warns messages bounce in a loop.

Sending mail through SendGrid Inbound Parse too? Its SPF, DKIM and DMARC records, and a check of all three.

Sources

Checked on 27 September 2026 against these official sources:

Know when your MX records change

Add your domain and we check its DNS on a schedule and email you when its records change — so a provider switch left half done, or an MX nobody meant to add, does not go unnoticed. Free for your first domain.

Create a free account