Written by
20 February, 2025
Email authentication is now a requirement for businesses and mass email senders. As of February 2024, Google and Yahoo mandate protocols like DMARC, while Microsoft joined the movement shortly after.
We hosted a webinar on email authentication to help familiarize email senders with the topic. Watch the video below as ZeroBounce COO Brian Minick explains how to authenticate emails.
Email authentication is a set of protocols verifying that an email sent from your domain is legitimate. Email authentication tools protect your domain from spoofing and fraud and also tell email service providers – like and – whether you sent an email or if someone is a fraudulent sender.
If you want to know how to authenticate email, you need to familiarize yourself with the various email authentication protocols.
SPF is a DNS record that lists all authorized mail servers for a given domain. Whenever someone sends an email from your domain, the recipient service provider will check your SPF record and attempt to match the sender’s IP address to confirm its legitimacy.
When you sign up for a service like Mailchimp or Constant Contact, it provides you with SPF records during the initial setup. However, this setup can be tricky if you use multiple platforms.
For example, a company may use Constant Contact for their main newsletter and Klaviyo for automation. Instead of creating different SPF records, you need to implement a combined one to account for all sending services.
This is how an SPF email authentication check takes place in real time:
Here’s an example of an SPF record:
v=spf1 include:_spf.google.com ~all
And here’s a breakdown of SPF syntax:
Other possible mechanisms include:
There are additional ways to configure your SPF record, including:
If you run into issues with your SPF record, check it for these common errors:
To help you configure your SPF record or check for errors, check out these free tools:
DKIM is a cryptographic method of authenticating emails sent by bulk senders. The DKIM protocol adds a unique encrypted key to every sent email, and that key must match the public key found in the DKIM DNS record.
Here’s how it works:
Here’s an example of a DKIM record:
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A…
In addition to the public record, the header of the sent email will contain a similar notation, including the DKIM version and method of cryptography. It will also include a unique DKIM key signified by ‘b=’.
While DKIM is necessary to secure your emails, the encryption method is not foolproof. Therefore, it’s recommended to follow these rules when using the protocol:
Here are some free tools to help you check and configure your DKIM record:
DMARC is a protocol that instructs recipient mail servers on how to behave if an SPF or DKIM check fails. It allows the bulk sender to work with ISPs in an effort to minimize spam, spoofing, and phishing attempts created by unauthorized senders.
Here’s an example of a DMARC record:
v=DMARC1; p=reject; rua=mailto:reports@yourdomain.com; ruf=mailto:alerts@yourdomain.com; pct=100;
A critical component of a DMARC record is the policy type. Here’s an explanation of the three and when to use them:
Here are some free tools to help you start and check DMARC records:

However, we strongly recommend all users to use a DMARC Monitor tool for the following reasons:
Here’s an easy-to-follow overview of how to setup DMARC on a domain using the DMARC Monitor:
Once your domain is set up, you’ll see the domain in the DMARC Monitor dashboard.
Clicking on the domain will allow you to see insights including:
Additionally, you’ll be able to view every source sending emails from that domain, how many, from what countries, and which IP addresses are being used.

Reverse DNS records, also called pointer (PTR) records, are an additional method for securing emails from attackers. When you provide a PTR record, the recipient email server can perform a reverse DNS lookup by attempting to match your device’s IP address with the associated email domain.
Though not a requirement, BIMI is an email authentication specification that allows a company to customize and display its logo next to their emails. However, you can’t just upload any image file. You need to provide an SVG file with the following parameters:
In addition to providing a valid SVG, you also need to have an active DMARC policy set to either quarantine or reject.
After meeting the requirements, you can submit your BIMI logo along with proof of company ownership to a third party. In exchange, you’ll receive a Verified Mark Certificate (VMC) to include with your BIMI record. Trusted popular third party verifiers include companies like DigiCert and Entrust.
Here’s an example of a BIMI record:
v=BIMI1; l=URL(path to logo here); a=URL(path to VMC here)
If you need help creating a BIMI record, you can use our by providing an appropriate SVG URL.
| Protocol | How does it work? | Purpose |
|---|---|---|
| SPF | Provides servers with a list of trusted senders/IP addresses | Prevents spoofing and phishing attempts using your domain |
| DKIM | Adds a unique encryption key to every email sent from your domain | Prevents spoofing and phishing attempts using your domain |
| DMARC | Provides instructions on how to handle emails that fail SPF and DKIM checks | Aligns SPF and DKIM and prevents fraudulent emails by pushing them to spam or rejecting them outright |
| rDNS & PTR | Validates the IP address by cross-referencing it with the associated domain | Stops fraudulent use of your domain and impostors |
| BIMI | Displays your verified brand logo next to emails that pass DMARC checks and are trusted | Builds trust with audiences and an easy way to identify if an email is legitimate |
Here’s a rundown of the next steps you can take to ensure your emails are authenticated and compliant:
If you don’t use email authentication, here’s what will happen:
On February 1st, 2024, Google and Yahoo made changes that impacted every single company that sends emails worldwide.
Here’s a quick overview of those changes from the webinar:

Let’s break those details down. Here’s a closer look at what’s changing:
These three rules apple to any person or organization sending 5,000 emails or more daily.
Failing to comply with these new rules and email authentication requirements will result in the following:

Zach is the manager and coordinator of (nearly) all things content-related at ZeroBounce. He works closely with all teams, from marketing to design to web development, to quickly deploy written and visual content that communicates how ZeroBounce brings value to your business. Zach has seven years of experience in digital marketing, crafting content for a wide variety of small-to-medium-sized businesses, including healthcare, finance, tech, SaaS, and real estate. When he's not writing, you can find him at the gym, playing or listening to music, or seeking out his next compelling TV show to binge-watch.
Test our ZeroBounce's free email verifier tool by entering an email below.
or