|DomainKey Identified Mail (DKIM) and Sender Policy Framework (SPF) work in tandem to authenticate SharpSpring’s emails.
That way, even though emails are being sent from a SharpSpring-owned server, the receiving server knows that email is coming from you. This is an incredibly important step you must take before sending emails out of SharpSpring.
This article will detail how to set up DKIM and SPF if you are using GoDaddy.
Verifying Your Domain
You will need to have verify the domain that you want to send from before setting up DKIM.
To verify domains, do the following:
Note: SharpSpring offers Professional Services to assist with configuring CNAME and DKIM.
Note: Once your domain is verified, you will see a Get My CNAME Settings link next to that domain.
Adding CNAME Records in GoDaddy
Once you have verified the domain that you want to send from, you can begin adding CNAME records to GoDaddy.
To add CNAME records in GoDaddy’s DNS Settings, do the following:
Note: When adding the host or domain value, GoDaddy automatically will append the domain to your host. As such, you will only need to add the first portion. The first half of the Name field will appear in a similar fashion to the following example:
Note: The TTL field can remain as the default value.
Important: The host and domain information regarding the Name field also applies to other web hosting services, such as Network Solutions.
Frequently Asked Questions
Q: Do I need to add SPF TXT records?
A: No. The em.makeyourmarketing.us CNAME record is the SPF record for SharpSpring.
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.