Email Authentication for Small Businesses: A Simple Guide to Reaching More Inboxes

  • Understand email authentication: SPF verifies authorized sending servers, DKIM checks digital signatures, and DMARC helps protect your domain from spoofing.
  • Meet mailbox provider requirements: Gmail and Yahoo require SPF or DKIM from all senders, while bulk senders face additional authentication and unsubscribe requirements.
  • Authenticate your own domain: Set up the required DNS records, start with a p=none DMARC policy to monitor results, and verify that everything works before sending.
  • Know what Constant Contact handles: Constant Contact provides default email authentication and manages SPF, while self-authentication lets you sign emails using your own business domain.

Mailbox providers (MBPs) like Gmail, Yahoo, and Microsoft are getting stricter about which emails they trust. Their email security checks and spam filters help keep phishing attempts out of users’ inboxes while making sure legitimate messages still get delivered.

Say your bakery sends an email announcing its holiday hours and taking preorders. Your customers want that information, but if mailbox providers can’t verify that the message really came from your business, it could end up in spam instead.

And these checks matter for a good reason. According to the FBI’s 2025 Internet Crime Report, phishing and spoofing accounted for 191,561 complaints, more than any other reported crime type. With scammers regularly impersonating legitimate senders, mailbox providers are paying closer attention to how businesses authenticate their emails.

So, what does this mean for your business? Let’s dig deeper into how email authentication works, what’s changed, and how to set it up to help your messages reach the inbox.

What is email authentication and why does it matter?

Email authentication verifies that an email comes from who it claims to be and isn’t someone trying to impersonate your business (also known as spoofing).

Over the years, several approaches to email authentication have emerged. Today, mailbox providers like Gmail, Yahoo, and Microsoft check information added to your email headers by your mail server against information published in your domain’s Domain Name System (DNS) records to check whether your messages are legitimate.

These checks have become increasingly important as mailbox providers work to keep spam and phishing emails out of their users’ inboxes. According to Google’s sender guidelines, all senders to personal Gmail accounts need SPF or DKIM authentication, while bulk senders must meet additional requirements.

So, what does this mean for your business? Proper email authentication can help you:

  • Meet mailbox provider requirements: Gmail, Yahoo, and Microsoft have authentication rules, and emails that don’t meet them are more likely to be filtered to spam or rejected.
  • Protect your domain from spoofing: Authentication helps mailbox providers identify unauthorized senders pretending to send emails from your business.
  • Build your sender reputation: Signing emails with your own domain helps establish a sending history tied to your business. You can also check your email reputation as it grows.
  • Improve email deliverability: When combined with good sending practices, authentication helps legitimate emails avoid unnecessary filtering and improves their chances of reaching subscribers’ inboxes.

As mailbox providers continue tightening their requirements, authenticating your emails is one of the most important steps you can take to protect your sender reputation and help your messages reach your subscribers’ inboxes.

The building blocks of email authentication

The three main email authentication standards are SPF, DKIM, and DMARC. Each has a different job, from checking which servers can send on behalf of a domain to verifying digital signatures and protecting against spoofing.

Here’s how they work.

SPF (Sender Policy Framework)

SPF helps mailbox providers check whether an email was sent from an authorized mail server — the system responsible for sending or receiving emails. Domain owners publish a list of approved sending servers in their DNS records, which receiving providers can check when a message arrives.

For example, if your business uses an email service provider (ESP) to send newsletters, SPF can help confirm that the service’s servers are authorized to send on behalf of the domain used for delivery.

However, SPF doesn’t necessarily check the domain in your visible From address. That address can be different from the one used behind the scenes to send your message. This is why SPF works best alongside other authentication methods.

When you send through Constant Contact, receiving mail servers check the SPF record for the bounce domain we manage. You don’t need to add Constant Contact’s sending servers to your domain’s SPF record. If you send from your own domain, set up DKIM in Constant Contact to align your visible From domain with DMARC.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature, also known as a digital signature, to outgoing emails. The sending service creates this signature using a private key that it keeps secure.

When an email arrives, the receiving provider checks the signature against a matching public key published in the signing domain’s DNS records. The private key stays with the sending service, while the public key allows mailbox providers to verify that an authorized domain signed the message and that it hasn’t been altered along the way.

The public key is usually stored in a TXT record, but some email services use CNAME records that point to keys they manage on your behalf.

According to Google’s sender guidelines, DKIM keys must be at least 1024 bits long, although 2048 bits is recommended for stronger security. Signing emails with your own domain also helps build a sender reputation tied to your business, which can support better email deliverability over time.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)

DMARC works alongside SPF and DKIM to help protect your business from email spoofing. It checks whether an email passes at least one of these authentication methods and whether the verified domain matches the domain in your visible From address (or an allowed subdomain). This is called domain alignment.

DMARC also lets domain owners publish authentication policies that tell mailbox providers how they’d prefer emails that fail these checks to be handled. These policies can help you monitor authentication failures and decide how to treat suspicious messages.

There are three main DMARC policies:

  • p=none: Monitor authentication results without requesting that providers block or quarantine failing messages.
  • p=quarantine: Ask providers to treat failing messages as suspicious, typically by sending them to spam.
  • p=reject: Ask providers to reject messages that fail DMARC alignment authentication.

According to the IETF’s DMARC standard, starting with a p=none policy is a good way to identify authentication problems before applying stricter rules.

You can also configure DMARC reports to see which services are sending emails using your domain and spot potential spoofing attempts. When you do, you’ll be inundated with messages from major mailbox providers showing how many messages passed/failed and where they came from. It’s best to partner with a DMARC reporting provider to help manage these. Many providers offer a basic free service that works well for small business domains. Keep in mind that DMARC doesn’t prevent scammers from registering lookalike domains that resemble your business name.

BIMI (Brand Indicators for Message Identification)

BIMI is an optional email branding standard that allows supporting mailbox providers to display your logo alongside authenticated messages. It doesn’t authenticate your emails itself. Instead, it builds on the protection you’ve already established with SPF, DKIM, and DMARC.

To qualify for BIMI, your domain generally needs a DMARC policy set to p=quarantine or p=reject. Gmail also requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC), while Yahoo doesn’t currently require a certificate.

Gmail displays UNIQLO's brand logo and a verified sender checkmark next to this promotional email.
Gmail displays UNIQLO’s brand logo and a verified sender checkmark next to this promotional email. Source: Author’s inbox

BIMI doesn’t directly improve email deliverability, and publishing a BIMI record doesn’t guarantee your logo will appear. It’s an additional way to help customers recognize your brand once you’ve properly configured authentication.

What mailbox providers require from senders

Gmail, Yahoo, Microsoft, and Apple have similar email authentication requirements, but they differ depending on how many emails you send. Here’s a breakdown of what each provider expects.

Who it applies to Authentication required DMARC policy Other requirements
Gmail, all senders: Anyone emailing personal Gmail accounts SPF or DKIM Not required for all senders Use TLS, valid DNS records, and proper email formatting. Aim for spam rates below 0.1% and avoid reaching 0.3%.
Gmail, bulk senders: Around 5,000 or more messages a day to personal Gmail accounts Both SPF and DKIM DMARC required, with a policy of at least p=none. The From domain must align with SPF or DKIM. Same general requirements, plus one-click header unsubscribe and a visible standard unsubscribe link for marketing emails.
Yahoo, bulk senders: No specific daily volume threshold published Both SPF and DKIM DMARC must pass, with at least p=none. Keep spam complaints below 0.3%, support one-click header unsubscribe, and provide a visible unsubscribe link.
Microsoft, high-volume senders: 5,000 or more emails a day to Outlook.com, Hotmail, Live, and MSN accounts Both SPF and DKIM must pass DMARC must pass, with p=none accepted. Provide a clear, working way to unsubscribe.
Apple iCloud Mail, bulk senders: No specific daily volume threshold published SPF and DKIM A DMARC policy must be published. Provide an unsubscribe link that works immediately and follow Apple’s sending and formatting requirements.

Yahoo and Apple don’t publish specific daily sending thresholds for bulk email, so follow their full authentication requirements regardless of list size.

These are the main requirements, not an exhaustive list. Authentication alone won’t guarantee inbox placement. Mailbox providers also consider factors like sender reputation and spam complaints when deciding whether to deliver your messages.

How to set up email authentication with your own domain

Ready to authenticate your emails? You’ll need access to your business domain’s DNS settings and the email service you use to send messages. Most providers give you the records you need, so you won’t have to create them from scratch.

Here’s how to get started.

Step 1. Make sure you own your sending domain

Start by checking the From address you use to send emails. Say you own a bakery called Sweet Corner and send newsletters from hello@sweetcorner.com. If you own sweetcorner.com, you can set up email authentication using that domain.

But what if you send from sweetcorner@gmail.com instead? Since you don’t own gmail.com, you can’t change its authentication settings. You’ll need a business email address using a domain you own before you can set up self-authentication.

Step 2. Find where your DNS records are hosted

Next, find out which company manages your domain’s DNS records. This is where you’ll add the authentication information provided by your email service.

Your DNS host is often the company where you purchased your domain, but that’s not always the case. For example, you might have bought sweetcorner.com through GoDaddy, but your web developer later set up Cloudflare to manage its DNS records. In that case, you’d need to log in to Cloudflare, not GoDaddy, to make changes.

Not sure who manages your DNS? Ask whoever set up your website or use the MxToolbox DNS lookup tool to check your domain’s nameservers, which can help identify your DNS provider.

Once you’ve found the right company, log in and look for the DNS management section. That’s where you’ll add the records needed to authenticate your emails.

Step 3. Check your SPF configuration

Next, look at the services you use to send emails. For example, Sweet Corner might use one provider for everyday business emails and Constant Contact to send newsletters. Each service may handle SPF authentication differently.

Some providers require you to add or update an SPF record in your DNS settings, while others manage SPF through their own sending domains. Check your provider’s instructions to see what’s required.

If you use Constant Contact, we handle SPF authentication through our own sending domain. You don’t need to add our sending servers to your SPF record. Instead, self-authentication uses DKIM to connect your emails to your business domain, which we’ll cover next.

If another service requires SPF changes, follow its instructions carefully. Remember that each domain should have only one SPF record, so update an existing record rather than creating a duplicate.

Step 4. Set up DKIM authentication

Now set up DKIM for your domain. Your email service should provide the information you need, usually as TXT or CNAME records.

Copy these records into the DNS settings you found in Step 2. For example, if Sweet Corner uses GoDaddy to manage sweetcorner.com, that’s where its DKIM records should go.

If you’re using Constant Contact, go to Settings > Advanced settings > Add self-authentication. You’ll see two options:

  • DKIM CNAME records: The recommended option for most customers. Constant Contact manages the DKIM private key, so you don’t have to generate or maintain it yourself. You can also continue sending emails while your DNS records update.
  • DKIM TXT record: Best if you use the same domain across multiple Constant Contact accounts. You won’t be able to send emails through Constant Contact until the new records take effect, which can take up to 48 hours.
Constant Contact offers two DKIM self-authentication methods, with CNAME records recommended for most customers.
Constant Contact offers two DKIM self-authentication methods, with CNAME records recommended for most customers. Image source: Constant Contact

Select your preferred method and the domain you want to authenticate, then follow the prompts to generate your records. Copy the record names and values exactly as provided and add them to your DNS settings.

Step 5. Publish your DMARC policy

Next, check whether your domain already has a DMARC record. If it doesn’t, add one through your DNS host.

For businesses just getting started, a p=none policy is a good place to begin. It tells mailbox providers to take no action based on a failed DMARC check alone.

To monitor authentication results, add the RUA tag to your DMARC record. It tells mailbox providers where to send summary reports. For Sweet Corner, adding rua=mailto:dmarc@sweetcorner.com would request reports at that email address. These reports show which services send emails using your domain and whether those messages pass DMARC checks.

These reports can be technical, so you may want help from your IT specialist or a DMARC reporting tool to review them.

If you use Constant Contact, we’ll provide the DMARC record information alongside your DKIM records. You’ll need to publish both in your DNS settings before activating self-authentication. If you already have a DMARC record, review it rather than creating a second one.

Step 6. Verify your authentication records

Most email providers offer a way to check whether your authentication records are working. You can also send an email to yourself and examine its message header, which contains technical information about how the email was sent and authenticated.

For example, Sweet Corner could send a newsletter to a small test list containing the owner’s personal email address. This helps confirm that messages sent from hello@sweetcorner.com are properly authenticated before sending to customers.

If you use Constant Contact, return to Settings > Advanced settings and select Check status or Activate when your records are ready. Once Constant Contact confirms they’re correctly published, click Activate to complete self-authentication.

Make sure your From address is verified in your Constant Contact account and uses the domain you’ve authenticated. Then, send a campaign to a small test list with your own email addresses to confirm it goes through successfully.

If you need a hand, our step-by-step self-authentication guide walks you through both the CNAME and TXT methods, including how to publish your DNS records, activate authentication, and test your setup.

What has recently changed in email authentication 

Mailbox providers continue to tighten their email authentication rules to protect users from spam and phishing attacks. If you set up authentication a few years ago, here are three developments worth knowing about.

  • Microsoft introduced stricter requirements: Starting May 5, 2025, Microsoft began requiring domains sending more than 5,000 emails a day to Outlook.com, Hotmail, and other Microsoft consumer accounts to pass SPF and DKIM checks and have a valid DMARC policy. Emails that don’t meet these requirements may be rejected with error 550 5.7.515. If you send large campaigns to Microsoft addresses, make sure your email service meets all three requirements.
  • Gmail increased enforcement: Google introduced stricter sender requirements in 2024, but began increasing enforcement in November 2025. This means emails that don’t meet its rules are more likely to face temporary delivery failures, land in spam, or be rejected. If you send to personal Gmail accounts, check your authentication status in Google Postmaster Tools to catch potential problems.
  • The IETF updated the DMARC standard (May 2026): The Internet Engineering Task Force published an updated DMARC standard (RFC 9989), replacing the older specification. It also separated the technical rules for aggregate reports and failure reports into their own documents. This doesn’t mean you need to redo your authentication setup. However, it’s a good reminder to confirm your domain’s authentication is working and review any DMARC reports for issues.

If you’ve already set up SPF, DKIM, and DMARC correctly, you may not need to make any changes. The important thing is to make sure your configuration still meets the requirements of the mailbox providers your customers use.

Send authenticated emails with Constant Contact

Constant Contact has been authenticating emails on behalf of our customers for years. By default, emails sent through our platform are signed using our own domain (auth.ccsend.com). We also handle SPF authentication, so you don’t need to add our servers to your SPF record.

If you have your own business domain, you can set up self-authentication to add your domain’s DKIM signature alongside ours. We provide the necessary DKIM and DMARC records, making it easier to complete the setup through your DNS host. And if you’re still using a free email address, Constant Contact uses a shared ccsend.com From address to meet authentication requirements.

Once you’re set up, you can focus on creating emails your customers want to receive. Constant Contact offers customizable email templates, a drag-and-drop editor, and automation tools for welcome emails and follow-ups. You can also segment your contacts to send more relevant messages and use campaign reporting to see how people respond.

Ready to get started? Start your free trial and create your next email campaign with Constant Contact.

FAQs

Is DKIM a TXT record or a CNAME record?

DKIM can use either type of record, depending on who manages your signing keys. Microsoft’s DKIM setup documentation notes that Microsoft 365 stores DKIM public keys in CNAME records, while other systems might use TXT records. Constant Contact’s self-authentication gives you CNAME records to add at your DNS host.

What is MTA-STS in email security?

MTA-STS (Mail Transfer Agent Strict Transport Security) is an email security standard that helps protect messages as they travel between mail servers. It allows domains receiving email to require secure, encrypted connections from sending servers that support MTA-STS, helping prevent messages from being intercepted or redirected. Unlike SPF, DKIM, and DMARC, MTA-STS doesn’t verify the sender’s identity. Instead, it focuses on securing email transmission.

What is ccsend.com in my email headers?

The ccsend.com domain is the one Constant Contact uses to sign your emails by default, through auth.ccsend.com. Seeing it in your headers means your emails are authenticated with Constant Contact’s domain. Once you turn on self-authentication, your own domain’s signature is added alongside it.

Do I need email authentication if I send fewer than 5,000 emails a day?

You still need it, because Google requires SPF or DKIM from everyone who sends to personal Gmail accounts. Yahoo sets the same SPF or DKIM minimum for all senders. A small salon sending 300 appointment reminders falls under the same rule.

Should my DMARC policy be set to reject?

For most small businesses and nonprofits, a p=none policy is the right setting because it already meets the DMARC minimum Gmail, Yahoo, and Microsoft set for bulk senders. Keep in mind, however, that p=none doesn’t protect your domain against spoofing and phishing because it does not instruct mailbox providers to treat failed mail as suspicious.

How long do DNS changes take to work?

Most DNS changes take effect within an hour, according to GoDaddy, though they could take up to 48 hours to update globally. A short delay is normal, so wait a day or two before checking again in Constant Contact.

Does BIMI help my emails reach the inbox?

No, BIMI doesn’t change whether your email reaches the inbox. According to the BIMI Group’s FAQ for senders, it’s a display signal that sits on top of strong authentication.

Share with your network
Avatar photo

Marilia Dimitriou is a senior content writer and editor with 7+ years of experience in SEO content writing, editing, and digital marketing. She specializes in creating educational and product-led content for small businesses and marketing technology brands, with a focus on email marketing and automation.

Avatar photo
Tara's Website

Manager of ISP Relations at Constant Contact. I focus on increasing email deliverability and making sure our customers have the tools they need. With more than 25 years of email industry experience, I am a member of the Messaging Anti-Abuse Working Group (MAAWG) where I co-chair the Senders Sub Committee, and collaborate with other email service providers and ISPs to reduce network abuse and refine email best practices as the email ecosystem continuously changes. I work hard to make sure the email industry continues to hold a place for small businesses to succeed.