DNS Records for Domain Authentication (SendGrid)

DNS Records for Domain Authentication (SendGrid)




Introduction

This article explains how to locate, view, and extract the DNS Records generated by SendGrid for Domain Authentication.

Why Domain Authentication is Required

Domain Authentication helps:
  1. Verify ownership of the sending domain
  2. Improve email deliverability
  3. Reduce spoofing and phishing risks
  4. Authenticate messages using SPF and DKIM standards

Prerequisites

  1. Access to SendGrid with Admin permissions
  2. Target Domain
  3. DNS Provider access


Step-By-Step Process

  1. Log in to SendGrid.

  2. Select Settings > Sender Authentication.

  3. Click Authenticate Your Domain.


  4. Select a DNS Provider or Other Host.



  5. Enter domain details and continue.


  6. Review and copy the generated DNS records.


  7. Add them to your DNS provider.

  8. Return to SendGrid and click Verify.


Expected Outcome

The Domain's Status shows Verified and SPF/DKIM authentication is enabled.


Troubleshooting

Ensure the records are an exact match, then wait for DNS propagation and verify no conflicts exist.

Host Name
Type
Value
em123.example.com
CNAME
u123.wl.sendgrid.net
s1._domainkey
CNAME
s1.domainkey.u123.wl.sendgrid.net


 

Verification Failed

Verify the following:
  1. DNS records match the values provided by SendGrid.
  2. No typographical errors exist.
  3. DNS propagation has completed.
  4. Existing DNS records do not conflict with the new records.

Partial Verification Success

If only some records are verified:
  1. Wait for DNS propagation to complete.

  2. Retry the verification process.

  3. Check with your DNS provider for propagation status
 

Additional Information

Disclaimer

This document is intended for informational and guidance purposes only. The procedures described in this document are based on standard Twilio SendGrid Domain Authentication functionality available at the time of publication. User interfaces, menu options, DNS requirements, and platform features may change without prior notice.

    • Related Articles

    • Two-Factor Login Authentication

      What’s Changing: Two-Factor Authentication (2FA) is being implemented to log in to the Admin page. Admin Login Page When a Username and Password is entered on the Admin page, the app will require Two-Factor Authentication to login The app sends the ...

    • 26.06.001 Release Notes

      Cloud POS 26.06.001 Release Notes Versions POS (Android and iOS) | CDS | Go (Android) | Swift Go – 26.06.001 Retail – 26.06.001 Driver – 1.3.0 KDS – 3.6.9 Custom App – 3.0.3 Release Date: 6/9/2026 Expires: 9/21/2026 This update includes performance ...

    • Uber Eats Integration

      Subscribe and Configure in Back Office Requirement To get started with this integration, an OLO add-on license is required. Please ensure that the OLO web order license is purchased and enabled under the account license settings. Page Navigation: Log ...

    • November 17th, 2025 - Release Notes

      Versions: Custom App – 3.0.1 Cloud POS – 6.1.45 Go – 6.1.4 iPad Cloud (Native) – 5.4 (1.2) CDS – 4.1.8 Release Date: 11/17/2025 Expires: 9/21/2026 This update includes performance improvements, new features, and bug fixes to enhance the efficiency ...

    • December 15th, 2025 - Release Notes

      Versions: iPad Cloud (Native) – 5.4 (1.3) Release Date: 12/15/2025 Expires: 9/21/2026 This update includes bug fixes to enhance the efficiency and reliability of your Point of Sale (POS) and Restaurant Operating System. Bug Fixes Fixed a bug where ...