The information on this page applies to Free Trial and Essentials customers who received access on or after April 6, 2020. If you received access before April 6, 2020, you can disregard the information below.
To ensure our customers maintain the best possible sender reputations and to uphold legitimate sending behavior, we require customers to verify their Sender Identities. A Sender Identity represents your “From” email address—the address your recipients will see as the sender of your emails.
You can verify one or more Sender Identities using either Domain Authentication or Single Sender Verification. There are advantages to both verification methods, and we provide detailed guides to configure whichever option you choose.
This page offers a high-level overview of Single Sender Verification and Domain Authentication to help you decide which option best fits your needs.
Single Sender Verification is a fast way to verify your Sender Identity when you don’t have access to the DNS settings for your domain. Though you will want to complete Domain Authentication for your production mail send, Single Sender Verification is a great way to start quickly while building a proof of concept or test.
To verify a Single Sender, see our Single Sender Verification page.
Please note, you must have the ability to edit the DNS records on the domain you want to authenticate.
Domain Authentication is the preferred method of verification. Though Single Sender Verification provides a quick start, Domain Authentication should be completed before you launch your mail send into production. If access to DNS records is a barrier for you, you can always start with Single Sender Verification and return to Domain Authentication once you obtain DNS access.
To authenticate your domain, see How to set up domain authentication.
Let us know how we’re doing! Please rate this page:
Please note, we cannot resolve account and login issues reported on GitHub. Contact support for account assistance.
Thanks for helping us improve our docs!