This article covers the SPF and DKIM authentication processes for Email Blaster and how they are managed in Valimail. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.

Email Blaster uses the new 2048-bit key length for added security and is recommended by service providers such as Google.

The DKIM record sits behind the scenes on your company domain name, it is placed on your DNS server (like an SPF record).

On your organization DNS server, create a CNAME record with the following values:

NAME: eb._domainkey.yoursite.co.uk

VALUE: dkim.ebsnd.com

Remember to replace yoursite.co.uk with your actual domain name!

This CNAME record forwards the verification check onto the email blaster network, which your subscribers email server will then be automatically provided with a secure key to verify the authenticity of your email.

NOTE: If you manage you domain in Valimail, you will need to add the CNAME DKIM key on your domain's configuration page in the Valimail platform.

You can also find the instructions on how to set up DKIM and SPF for Email Blaster, here.

You can find more detailed information on how to add a DKIM key in Valimail, here:

Once you establish that Email Blaster is an authorized sender for your domain, you will need to add the service in your Enabled Senders.

You will find more detailed information on how to add a service for your domain in Valimail, here:

Note: We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.