If your business emails regularly end up in the spam folder, it’s almost always due to missing or incorrectly configured SPF, DKIM and DMARC records. These three DNS settings prove to receiving mail servers that your email genuinely comes from your domain and hasn’t been forged. In this article, you’ll learn what each record does and how to set them up correctly step by step.
SPF, DKIM and DMARC are checked before your mail reaches the inbox
Why does email end up in spam?
Receiving mail servers (such as Gmail and Outlook) check with every incoming email whether the sending domain has actually given permission to send mail on its behalf. Without these checks, it cannot be proven that your email hasn’t been forged β and that’s exactly what spammers often do. If SPF, DKIM, or DMARC are missing, there’s a good chance your email will end up in the spam folder or even be rejected entirely.
These settings are entered as DNS records for your domain name. If you manage your domain with Tandata, you do this through your domain names management in Plesk.
Setting up SPF
SPF (Sender Policy Framework) is a TXT record that indicates which mail servers are allowed to send on behalf of your domain. If this is missing, or contains the wrong IP address, the recipient will see this as a warning sign.
Check your current SPF record
Check whether a TXT record already exists that starts with “v=spf1”. You can find this in your domain’s DNS management.
Determine which servers are allowed to send mail
Note which services send email on behalf of your domain: your hosting package, a newsletter service, a CRM system, and so on.
Add the TXT record
Create a TXT record containing all permitted senders, and end it with “-all” to reject all other senders.
Use one SPF record per domain
If you have multiple services, combine them into a single record. Two separate SPF records don’t work and will actually cause problems.
Setting up DKIM
DKIM (DomainKeys Identified Mail) adds a digital signature to outgoing email. The receiving server verifies this signature using a public key stored in your DNS, proving that the email wasn’t altered in transit.
Generate a DKIM key
Many hosting environments, including Plesk, let you generate this automatically through your domain’s mail settings.
Add the record to your DNS
The public key is added as a TXT record under a selector, for example “default._domainkey”.
Check the activation
Send a test email and check the headers for successful DKIM verification, or use an online testing tool.
If you use multiple mail services at the same time (for example, a webshop and a newsletter service), each service usually needs its own DKIM selector. Ask the relevant provider about this.
Setting up DMARC
DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. It tells receiving servers what to do if an email fails the SPF or DKIM check, and provides you with reports on misuse of your domain.
Make sure SPF and DKIM already work
DMARC is of little use without correctly functioning SPF and DKIM, since it builds on them.
Create a DMARC record
Add a TXT record at “_dmarc.yourdomain.com” containing your policy: for example, monitoring (“p=none”), quarantine (“p=quarantine”), or reject (“p=reject”).
Start cautiously
Start with “p=none” so you first receive reports without legitimate mail being rejected. Then gradually build up to a stricter policy.
Set up a reporting address
Add “rua=mailto:youraddress” to the record to receive daily reports about who is sending mail on behalf of your domain.
Frequently Asked Questions
How long does it take for SPF, DKIM, and DMARC to become active?
DNS changes are usually active within a few hours, but in some cases can take up to 24 hours to be visible everywhere.
Can I use SPF, DKIM, and DMARC independently of each other?
SPF and DKIM can be used separately, but DMARC needs both to function properly. Without SPF and DKIM, a DMARC record has little effect.
Why does my email still end up in spam after setting up these records?
Besides technical authentication, the content of your email, your sending frequency, and your IP address’s reputation also play a role. Also check that there are no typos in your DNS records.
Do I need to set this up again if I switch hosting providers?
Yes, when switching to another host, you need to check whether SPF, DKIM, and DMARC are correctly carried over or need to be reconfigured in the new DNS environment.
Conclusion
SPF, DKIM, and DMARC together provide reliable email verification and reduce the chance that your messages end up in the spam folder. Set them up in the right order, start cautiously with DMARC, and regularly check that everything still works correctly, especially after changes to your mail environment. If you can’t figure it out, check the settings in our knowledge base or get in touch.