Rivalry2

HTML Diff

4 added 2 removed

Original 2026-01-01

Modified 2026-03-10

1 As inbox providers work to differentiate legitimate senders and spammers from the billions of messages they receive on a daily basis, marketers are often caught in the crossfire.

2 As the volume of malicious email grows, it’s essential to make every effort to help inbox providers easily recognise your business as a legitimate sender.

3 To do this, we rely on email authentication-a crucial factor in deliverability and fraud prevention.

4 The two most common methods for authenticating emails are Sender Policy Framework (SPF) and Domainkeys Identified Mail (DKIM). When authentication fails under one of these methods, a domain’s Domain-based Message Authentication, Reporting, and Conformance (DMARC) policy is checked to see what to do next with that message.

5 Since its release, DMARC has been considered a best practice, but not a necessity for bulk email senders. Now, that’s all changing. Because senders who don’t have DMARC policies are much more likely to be spammers,<a>Google and Yahoo’s sender requirements</a>are collectively shifting the industry standard from best practice to absolute necessity.

6 No DMARC policy, no entry into the inbox.

7 In other words, if your emails aren’t authenticated and they fail to pass a DMARC check, they won’t land in your audience’s inboxes. As of April 1, 2024, these messages were rejected and now bounce completely from Yahoo or Google email inboxes.

8 <h2>Why is DMARC important?</h2>

9 DMARC is considered an industry best practice when protecting:

10 <ul><li>Your brand and domain name</li>

11 <li>Your sending reputation, which is key for email deliverability</li>

12 </ul>Think of it this way: Most marketers spend significant time and money building a brand their customers can trust. Email is part of that process. If a customer receives spam or malicious email on behalf of a brand they have done business with, this may compromise their trust in that brand and even end that relationship.

13 Even worse, imagine a third party sends an email using your hard-earned reputation for a malicious purpose, like stealing someone’s identity or personal information. The consequences could extend beyond eroding trust and end up causing permanent damage to your brand’s image.

14 <h2>How does DMARC work?</h2>

15 DMARC is essentially your domain/brand’s email reputation guard dog. Its purpose is to prevent unauthorised sources from sending email on your behalf (a practice also known as spoofing) for malicious purposes, such as phishing scams.

16 Here’s how the DMARC authentication process works:

17 <ul><li>Alignment:DMARC passes or fails a message based on how close the message “from” header matches the sending domain specified by either SPF or DKIM.</li>

18 - <li>Policy enforcement:DMARC instructs mail servers on what to do with the message if it fails DMARC checks, defined by one of 3 possible settings:<ul><li>p=none:place the message in the inbox at your own risk</li>

18 + <li>Policy enforcement:DMARC instructs mail servers on what to do with the message if it fails DMARC checks, defined by one of 3 possible settings:p=none:place the message in the inbox at your own riskp=quarantine:do not place the message in the inbox; place it in spam/junkp=reject:do not accept the message; it is likely not from the owner of the domain the email originated from, and should be bounced<ul><li>p=none:place the message in the inbox at your own risk</li>

19 <li>p=quarantine:do not place the message in the inbox; place it in spam/junk</li>

20 <li>p=reject:do not accept the message; it is likely not from the owner of the domain the email originated from, and should be bounced</li>

21 </ul></li>

22 <li>Audit mail traffic:Your DMARC record can be configured to provide reporting on who or what is sending messages on your domain’s behalf. Third-party tools like<a>EasyDMARC</a>or<a>Dmarcian</a>can manage this process to secure your domains as needed. If someone is attempting to spoof your emails or is sending unauthorised emails (like a non-customer facing department), you can identify those sources and prevent them from sending further emails.</li>

23 </ul><h2>What led to the creation of DMARC?</h2>

24 Prior to the adoption of DMARC in 2013, the authentication methods the policy uses already existed.

25 SPF has been around, in some form, since 2000 or so. DKIM came on the scene a few years later, around 2004, for a number of major players-most notably, Yahoo and Cisco Systems.

26 Let’s take a closer look at SPF and DKIM to see how they work.

27 <h3>Sender Policy Framework (SPF)</h3>

28 SPF is used to authenticate the sender of an email. With an SPF record in place, inbox providers can verify that a mail server is authorised to send email for a specific domain. The SPF record resides in the DNS TXT record and contains a list of IP addresses that are allowed to send email on behalf of your domain.

29 An SPF record starts with “v=spf1”. For example, if you do a TXT lookup for “klaviyomail.com”, you will find an entry like this:

30 <h3>DomainKeys Identified Mail (DKIM)</h3>

31 DKIM is used to verify the authenticity of a message by using a cryptographic signature which is encrypted and added to the header of the message. When the message is received, a public key found in the DKIM record of the sending domain’s DNS is used to decrypt the DKIM signature and authenticate the message.

32 A DKIM record resides in a special location under the TXT records. In our example, you can find the DKIM record under the “kl._domainkey” subdomain:

33 <h2>How to authenticate with DMARC</h2>

34 A DMARC record shows up within the TXT records of the _dmarc subdomain and starts with “v=DMARC1;”.

35 For example, if you do a TXT lookup for “_dmarc.klaviyomail.com”, you will find an entry like this:

36 There are different steps for authenticating DMARC, though, depending on the DNS host. Find specific instructions based on<a>your DNS host here</a>.

37 <h2>Why DMARC is now table stakes for marketers</h2>

38 The world of email is quickly moving to a place where no authentication effectively guarantees your message will be rejected.

39 At Klaviyo, in line with industry best practices, all senders must implement SPF, DKIM, and DMARC records. This, in turn, equips senders with the technical set-up necessary for meeting the recent requirements outlined by Yahoo and Gmail-which means you can rest easy, and focus on other areas of deliverability and marketing best practices.

40 All Klaviyo customers, large and small, should have a DMARC policy for their brand’s domain. Even if you are not sending enough email to be classified as a “bulk sender” under Yahoo and Google’s new sender requirements, your business is growing-and it’s best to be prepared ahead of time.

41 Do your future business a favor and get started with DMARC now.

42 <h3>Related content</h3>

43 <ul><li><a>Understanding email authentication</a></li>

44 <li><a>Your complete guide to email deliverability: avoid the spam folder for maximum engagement</a></li>

45 <li><a>Google + Yahoo’s new sender requirements: how to optimise your strategy</a></li>

46 - </ul>

46 + </ul>Power smarter digital relationships with Klaviyo SMS.

47 + <a>Get started</a>

48 +