Google, Microsoft, and other Internet service providers (ISPs) check your emails to see if the domain you are sending from (such as email@example.com) is authenticated. This is the information they need to recognize you and your clients as trusted senders. This article will detail how to authenticate emails through DKIM and SPF by adding CNAME records.
The following user roles can set up DKIM:
- Getting Started
- Setting Up DKIM and SPF in SharpSpring
- Adding CNAME Records Externally
- Frequently Asked Questions
- Ready to Learn More?
If your emails are authenticated, then more of your emails will get into the inbox instead of the spam folder. Setting up DKIM and SPF is how you authenticate your emails. Doing so means that these ISPs will trust the content that you send. In order to do so, you must add CNAME records for your domain via your hosting provider (such as GoDaddy, HostGator, or NameCheap).
Below is a breakdown of what each of these terms mean:
|DKIM:||DomainKeys Identified Mail.
An important email authentication mechanism for protecting senders and receivers from forged email.
|SPF:||Sender Policy Framework.
A type of DNS (Domain Name System) record used to identify which mail servers are permitted to send email on behalf of a domain.
A type of DNS record added to hosting providers that is used to specify that a domain name is an alias for another domain, which is considered the canonical domain.
SharpSpring provides an in-application configuration tool which creates CNAME records. When configuring CNAME records, in order to set up DKIM and SPF, you will need to add CNAME records to your DNS settings. The DNS settings must be for the domain you are looking to authenticate. The configuration tool will generate these CNAME records, which will point to your unique DKIM keys.
Then, wholly outside of SharpSpring, these CNAME records must be added to your domain’s DNS settings. These settings are often handled by your Domain Name Registrar (such as GoDaddy, HostGator, or NameCheap), or managed by a dedicated DNS service provider (such as DNSimple or EasyDNS).
Setting Up DKIM and SPF in SharpSpring
Authentication with DKIM and SPF is required to send from a domain in SharpSpring.
To set up DKIM and SPF, do the following:
Note: If you are still seeing Waiting on CNAME Records, be aware that it could take as long as 24 hours for the DNS settings to update.
Adding CNAME Records Externally
Configuring CNAME records in SharpSpring is only part of the overall DKIM setup process. To complete configuring CNAME records, you will need to do so outside of SharpSpring. While SharpSpring can verify if you have correctly configured the CNAME with a registrar or hosting provider, SharpSpring cannot provide CNAME configuration procedures for individual hosting providers.
As the CNAME configuration process varies for each hosting provider, you will need to refer to the help documentation provided by the individual providers. You will need to do so for each hosting provider of the website you are adding a CNAME record for. As such, website owners must log in to their hosting provider accounts and configure CNAME records there.
The following external documentation links will redirect to CNAME configuration articles for more popular registrars and hosting providers. However, this is by no means a complete list. If your provider is not listed, refer to their help documentation on CNAME configuration.
For more information on registrar or hosting provider CNAME configuration, contact your registrar or hosting provider.
Frequently Asked Questions
Q: What are CNAME records?
|Q: How can I check to see if I correctly set up the CNAME records?
A: MxToolBox is a tool that can help. With it, insert the full key name from SharpSpring, change the search to CNAME Lookup, and search. If successful, you should see the data from SharpSpring under the Canonical Name column in MxToolBox.
|Q: How does this impact what my email looks like in the inbox?
A: The email will show the sending domain as the domain you have configured with DKIM (signed-by), and a return path (mailed-by), including that same domain.