Troubleshooting Sender Authentication

After you add your CNAME, TXT or MX records to your DNS host, you need to validate them in the SendGrid UI. If your DNS records aren't validating, try the following steps.

Some DNS providers take longer than others to update your DNS records with the CNAME files or TXT and MX files that we ask you to add. Give it up to 48 hours to validate.

Some DNS hosts will automatically add your top-level domain to the end of DNS records you create, which can turn a CNAME for "email.domain.com" into "email.domain.com.domain.com".

Be sure to follow the convention on existing records in your DNS panel when adding new ones, as sometimes you will only need to add what is to the left of the top-level domain.

For example, a CNAME for "email." becomes "email.domain.com"

If you get an error like this, the problem is that the TXT record has been split up. The solution is to combine the key back together into one set of quotes, which looks something like this:

Sender Authentication confirms the validity of SPF, DKIM, and DMARC records. However, a DMARC pass is not mandatory for successful Sender Authentication. You will be routed to the successful authentication page, and be able to send mail. The 'Install DNS Records' UI will indicate a DMARC failure, alerting you to address the issue with your DNS provider.

Some DNS providers don't automatically prevent you from duplicating a DNS file. For example, there might be an MX and TXT record where you are trying to set up a CNAME file. If your DNS files aren't validating, check to make sure there are no other DNS records that could be a duplication.

SendGrid requires underscores for sender authentication, but some DNS providers do not support underscores in zone file entries.

If your provider does not allow you to use underscores in zone files, consider changing your DNS hosting provider.

Though you can disable automated security — this allows you to set TXT and MX records rather than CNAME records — a DKIM record will always contain an underscore.

DKIM record using a CNAME record

DKIM record using a TXT record

For more information about setting up automated security, see Using automated security.

Sometimes there is no other option but to manually validate your DNS records. This can be caused by certain DNS providers or by customizations you add to your records.

To validate a DNS record manually, use the Unix command DIG. The following examples use Terminal on a Mac platform. The tables show specific validations. If the ANSWER section of the dig return is empty, that usually means that either the record does not exist or has yet to propagate.

You can also use the DNSLookup tool provided by MxToolbox.

If you can successfully verify your DNS changes manually, but it won't validate in the tool, contact Support, and we can help you investigate.

If you aren't sure what DNS provider hosts your domain use this command to find out:

Yes, it's possible to authenticate multiple domains. When multiple authenticated domains exist on your account, SendGrid will use the from address for each email you send through SendGrid and match it to a domain and branded link. If the from address does not match an existing authenticated domain, SendGrid will fall back to the domain you have chosen as the default.

Run through your application logic to understand why your sent emails may be using sendgrid.net instead of the domain you authenticated.

For any account, SendGrid attaches authenticated domain information in the following order, starting at the top of the list and applying the domain when the criteria are matched:

1. Valid authenticated domain that matches the domain in the FROM address.
2. Valid default authenticated domain.

If no valid authenticated domains can be found, your mail domain defaults to sendgrid.net.

For subusers, SendGrid attaches authenticated domain information in the following order, starting at the top of the list and applying the domain when the criteria are matched:

1. Authenticated domain for this subuser that matches the domain in the FROM address.
2. Default authenticated domain for this subuser .
3. Authenticated domain assigned by the parent account to this subuser.

If no valid authenticated domains can be found, the sending domain defaults to sendgrid.net.

• How to set up domain authentication
• How to set up link branding
• How to set up reverse DNS