This article provides you the DNS and the domain records to enable and authenticate your email accounts.
The information and examples listed at this page assume that your sending domain is a subdomain of your company or of an e-commerce domain. For example: email.mybrand.com or email.yourwebsite.com
Before applying the domain settings of the table below, ensure that you are aware of your from domain and link domain and that you use subdomains of your company or the e-commerce website. For pactical examples, see section Additional information.
Before you fill in the fields, take the following into consideration:
- The domains that you enter here must redirect/point/resolve to your brand or an e-commerce website.
- Please make sure that your domains are properly specified because the fields in the table will be populated based on the entered values.
Fill in the following fields:
If you completed the setup, you can test your configuration by clicking "Check DNS Records"
This can cause inbox placement issues
Return path domain, also known as bounce domain, SMTP FROM or Envelope FROM domain, is used as a destination for bounces.
This domain is shown only in the technical mail headers and is used for SPF checks by receiving mail servers.
The CNAME record on your bounce domain points to Emarsys, where we already have all other necessary records in place.
A sender domain is the domain to send emails from, which comes after the @ in your From address.
DKIM stands for DomainKeys
Identified Mail, which is a method of associating
a domain with an email message allowing the domain owner to take responsibility
for a message while in transit.
DKIM allows the domain name associated with a message to be validated through encrypted authentication.
It is a way to determine who is responsible for a particular message. This is achieved so by inserting a special signature header into the message itself.
We are asking for 2 DKIM entries to allow DKIM key rotation which ensures the security of the keys.
SPF stands for Sender Policy
Framework, which is a protocol used to verify the authenticity
of an email, which enables receiving mail servers to verify the sender before
allowing the message through.
Any domain which appears in the Return-Path header field (Bounce domain) must have an SPF record published.
This is covered by the Bounce domain setup.
However, we also require SPF for sender domains since some mailbox providers or ISPs check SPF for them as well.
DMARC stands for Domain-based Message
Authentication, Reporting &
Conformance, which is an email authentication method created
by a group of organizations, among them AOL, Google, Microsoft, and Yahoo!.
It allows senders to tell ISPs how to handle unsigned (non-authenticated), failed (broken authentication) or spoofed (with forged headers) emails which use the sender’s domain name.
For example, a DMARC record can indicate that such emails should be delivered, placed in a Spam folder, or be rejected.
An MX (mail exchange) record is an entry in your DNS zone file which specifies a mail server to handle a domain's email.
You must configure an MX record (Mail Exchanger) record to receive email to your domain.
Sender and Link Domain
Make sure that the link subdomain is in the same root domain as your sender
For example, if your sender domain is email.mybrand.com, your link domain should be link.mybrand.com.
Matching the subdomains on the root domain level helps with the brand awareness by exposing the brand, and the email deliverability by using the reputation of the root domain and making the links look trustworthy
Name - In the text boxes change the value according to your domain.
Important: If hosting your own replies: you must ensure you can receive all reply emails.
Reply mail management
If you host the reply emails on your end complete the following:
- Open the mailbox you use for sending in your mail server and make sure that it can receive emails.
- Ensure test reply emails are delivered successfully.
- Test all the relevant abuse emails.