Set Up Custom Domain Authentication | DKIM

Internet Service Providers (ISPs), like Google, Yahoo, and Microsoft, use DKIM authentication as a way to scan inbound domains for spam or hoax addresses. Emails that fail verification are more likely to reach in a spam or junk folder.

Adding custom DKIM authentication for your domain makes sure that your campaign looks proficient, and ensures a successful campaign.

In this article you’ll learn how to set up DKIM authentication for your domain.


Custom Authentication

To authenticate your domain, you’ll need to complete tasks from our end and your domain provider’s control panel or zone editor. We will provide you with the necessary information from our platform to paste into your domain provider’s site.

Please note that you need to change some account settings with your DNS provider. If you don’t know who your DNS provider is, reach out to your hosting service.

Here’s a brief overview of the process.

From our platform, start by verifying your domain,

Copy the provided CNAME record


Authenticate Your Domain

To authenticate your domain, go to your domain provider’s site. Then, use the the DKIM info from from our end to update your DNS records.

Domain providers use different names for the page where you’ll update the DNS record, it’s best to refer to yours for detailed instructions.


Example CNAME Record for DKIM

Here’s an example of what your CNAME record will need to look like to configure DKIM authentication. Please note that each DNS provider has different settings, so the setup shown in this article may not work for all domains.

Record Type

Name Value/Data TTL
CNAME Record


Please note that DKIM requires underscores in the CNAME file, this wasn’t allowed before and some registrars still don’t allow any underscores in the CNAME file.

If you encounter this issue please contact your registrar to for assistance, or set up a secondary custom domain with a registrar that allows underscores, or switch DNS providers.


Leave a Reply

Your email address will not be published. Required fields are marked *