{"id":80019,"date":"2024-12-25T09:00:00","date_gmt":"2024-12-25T09:00:00","guid":{"rendered":"https:\/\/wscms.walia-solutions.ch\/?p=80019"},"modified":"2026-08-05T11:28:32","modified_gmt":"2026-08-05T11:28:32","slug":"email-campaigns-are-successfully-secured-through-spf-dkim-and-dmarc","status":"publish","type":"post","link":"https:\/\/www.intecso.ch\/en\/email-kampagnen-erfolgreich-sicher-durch-spf-dkim-und-dmarc\/","title":{"rendered":"Email campaigns: successful and secure through SPF, DKIM and DMARC"},"content":{"rendered":"<p class=\"post__lead\">There was a time when we felt a little more secure when it came to the spam and email spoofing we were experiencing daily. Internet crime is on the rise and new malware helps scammers launch ever more sophisticated hacking attacks on email accounts. Moreover, all sectors and industries are now affected, from small SMEs to large corporations. Proven solutions such as the use of SPF, DKIM and DMARC are intended to help prevent cyber attacks via emails in the field of IT security.<\/p>\n<h3>Vulnerability in the email account<\/h3>\n<p>Before we get into the details of the three methods for combating spam, it is important to understand the vulnerability of emails. Email messages contain two sender addresses:<\/p>\n<ul>\n<li>Envelope From (also called return-path)<\/li>\n<li>Header From (also called friendly-from)<\/li>\n<\/ul>\n<p>The \u00abEnvelope From\u00bb address is the return address. This tells the email server where the message should be sent back to. This address is hidden in the email header, which also includes further technical details. The \u00abHeader From\u00bb address is the one that you see in the \u00abfrom\/from field\u00bb in your email client as an email user. Both addresses can be easily spoofed by spammers and cybercriminals.<\/p>\n<h3>Trustworthy emails thanks to SPF, DKIM and DMARC<\/h3>\n<p>SPF is an authentication protocol that allows the owner of a domain (e.g. @Intecso.ch) to define email servers that are allowed to send emails on behalf of the domain (e.g. @intecso.ch). Examples of these are email servers from Office 365 or cloud newsletter tools.<\/p>\n<p>The owners of the domain publish the email servers in the \u00abDNS SPF Record\u00bb. The receiving email server checks this DNS SPF Record to see whether the sender\u2019s email server is allowed to send the email from this domain. If this email server is not found there, authentication fails.<\/p>\n<ul>\n<li>Envelope From: Even if SPF authentication fails, the email will not always be blocked as spam.<\/li>\n<li>Email forwarding links can cause this validation to fail.<\/li>\n<li>Only the domain in the \u00abEnvelope From\u00bb address is checked, not the domain that the user sees in the email client (Header From).<\/li>\n<\/ul>\n<ul>\n<li>\u00abThe \u00bbEnvelope From\u00bb address is scanner@ich-bin-b\u00f6se.ch (the SPF record was correctly created by the attacking site for this domain).<\/li>\n<li>\u00abThe \u00bbFrom\u201d header address is scanner@ich-bin-gut.ch (the recipient has the feeling that the email was scanner@ich-bin-gut.ch sent).<\/li>\n<\/ul>\n<p>DKIM is a mechanism that enables your IT security to achieve higher trust in email accounts. Validation is ensured through cryptographic authentication.<\/p>\n<p>DKIM checks the email domain of the sender address. Unlike the SPF method, the IP addresses of the servers are not compared with DKIM. To ensure authenticity, the message and the mail header are digitally signed. To do this, a private key and a public key are generated on the own mail server, and the public key of the domain is attached via a DNS entry. This gives each email a signature calculated specifically using the private key, which is then compared by the receiving mail server. If the verification on the recipient mail server is positive, this proves that the incoming email was sent from a correct mail server.<\/p>\n<figure><img src=\"https:\/\/www.intecso.ch\/wp-content\/uploads\/2026\/08\/blog-1-img.webp\" alt=\"Scheme of the DKIM signature: The sending mail server signs the email with the private key, the receiving server checks it using the public key in the DNS.\" loading=\"lazy\" decoding=\"async\" \/><\/figure>\n<ul>\n<li>It can be ensured that the message was not manipulated on its way to the recipient.<\/li>\n<li>It works even if the email was forwarded.<\/li>\n<\/ul>\n<ul>\n<li>Not all email servers currently support DKIM<\/li>\n<li>As with the SPF method, the visible \u00abHeader From\u00bb address is not checked.<\/li>\n<\/ul>\n<p>\u00abEnvelope From\u00bb domain @ich-bin-b\u00f6se.ch (DKIM record was created for this domain by the attacking side) \u00abHeader From\u00bb address @ich-bin-gut.ch (the recipient feels that the email was sent from @ich-bin-gut.ch)<\/p>\n<p>Here, SPF and DKIM are combined. This ensures that the email has been validated using SPF and DKIM standards. The \u00abFrom\u00bb header and the \u00abEnvelope From\u00bb address are also compared. The two key values are Domain Alignment and Reporting.<\/p>\n<p>DMARC ensures that the \u00abFrom\u00bb header address (the visible address in the email client) has not been falsified.<\/p>\n<ul>\n<li>Here, not only the \u00abEnvelope\u00bb address is checked (through the SPF check), but also the \u00abHeader From\u00bb address. The two addresses must match.<\/li>\n<li>The domain of the \u00abHeader From\u00bb address must be the same as the domain in the DKIM signature.<\/li>\n<\/ul>\n<p>As with SPF and DKIM, a DMARC DNS record is created by the owner of the domain. Here, the owner can instruct the receiving email servers how to handle emails that do not pass the DMARC check.<\/p>\n<ul>\n<li>Only through monitoring (emails arrive)<\/li>\n<li>Quarantine (Emails end up in the Spam folder)<\/li>\n<li>Reject (Emails are not delivered at all)<\/li>\n<\/ul>\n<p>Email providers regularly send reports back to senders to provide insight into which messages have been properly authenticated, which have not, and why. DMARC is the first and only widely used technology that can make the \u00abFrom\u00bb header address (which users see in their email clients) trustworthy. This not only protects customers and the brand, but also deters cybercriminals from pursuing a brand with a DMARC record with less likelihood.<\/p>\n<ul>\n<li>The major advantage for a successful email campaign is the significant increase in deliverability rate. This is because fewer emails are marked as spam.<\/li>\n<li>Compliance with the DMARC standard signals a high level of security.<\/li>\n<li>You generally get a better overview and control over the messages sent and received by your domain.<\/li>\n<\/ul>\n<p>Despite all precautions, always be vigilant against cyber attacks of any kind. Even if you have taken all security measures and configured them, the sender of a message can still have been hacked. Therefore, if you are unsure, please have the sender\u2019s address professionally verified for its trustworthiness. Would you like to make your daily email communication and campaigns safer? We support you competently and transparently regarding DKIM, SPF, and DMARC, and look forward to your contact for a free consultation.<\/p>","protected":false},"excerpt":{"rendered":"<p>There was a time when we\u2026<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"intecso_author":"H\u00fcseyin S\u00f6nmez","intecso_author_role":"","intecso_author_photo":"","footnotes":""},"categories":[2],"tags":[],"class_list":["post-80019","post","type-post","status-publish","format-standard","hentry","category-best-practices"],"_links":{"self":[{"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/posts\/80019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/comments?post=80019"}],"version-history":[{"count":3,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/posts\/80019\/revisions"}],"predecessor-version":[{"id":90934,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/posts\/80019\/revisions\/90934"}],"wp:attachment":[{"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/media?parent=80019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/categories?post=80019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intecso.ch\/en\/wp-json\/wp\/v2\/tags?post=80019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}