( WEBSITE BASICS ) Nov 15, 2026

Business Email Not Arriving? SPF, DKIM and DMARC in Plain English

01Two Problems That Look Like One

A bookkeeper in Venice emails an engagement letter and hears nothing for a week. When she finally calls, the client says it never came, and later finds it in a spam folder under a pile of coupons. Across town, a contractor notices that his website’s contact form has gone quiet since the new site launched, although the phone still rings.

Both owners end up typing the same thing into a search box: why is my domain not receiving emails? They have different problems, though. In one case mail sent to the business is not reaching it. In the other, mail the business sends is not reaching other people. The causes and the fixes are separate.

Both usually come down to a few short text entries called DNS records, which are kept wherever your domain is managed. This post explains four of them in plain terms: MX, SPF, DKIM and DMARC. You do not have to write them yourself. Knowing what each one is for lets you ask the right person the right question.

02When Mail Is Not Reaching You: The MX Record

Incoming mail depends on one kind of record. Cloudflare’s learning center defines it this way: “A DNS ‘mail exchange’ (MX) record directs email to a mail server.” Think of it as the delivery address on file for your domain. Each MX record carries a priority number, and Cloudflare explains that the lower value is preferred, with a higher-numbered record acting as a backup.

MX records rarely break by themselves. They break when something nearby changes: a new website goes live and the domain’s records are moved to a different company, or the business switches email providers and the old entries are left in place.

Google’s help page on setting up MX records for Google Workspace, last updated on November 10, 2026, gives a single value, smtp.google.com, with a priority of 1. It tells administrators to remove any other MX records and warns, “Your email might not work correctly if you keep old or incorrect MX records.” The same page says it can take up to 72 hours for new MX records to be recognized.

So if incoming mail stopped right after a launch or a provider change, start here. Ask whoever made the change to compare the MX records with your email provider’s current setup page. This is also the moment you find out whether anyone knows the login for the domain, which is the subject of our post on where to buy and keep your business domain. If mail arrives from some people and not from others, the MX record is probably fine, and your own spam folder is the next place to look.

03When Your Mail Is Not Reaching Them: Three Records

Email was built so that anyone can type any address into the From line. Three records exist to let the receiving mail server check whether a message that claims to be from your domain really is.

SPF is a list of who may send.

It names the mail services allowed to send on behalf of your domain, a little like the list of people authorized to sign for a company at the bank. RFC 7208, the technical standard for SPF published in April 2014, says the record is a DNS TXT record that begins with “v=spf1.” For a domain that sends only through Google Workspace, Google’s help page gives the value “v=spf1 include:_spf.google.com ~all.” For a domain that sends only through Microsoft 365, Microsoft’s documentation gives “v=spf1 include:spf.protection.outlook.com -all.”

DKIM is a signature.

Google’s help page on DKIM says a private key “generates and adds a DKIM signature to each outgoing message.” The matching public key sits in your DNS, where the receiving server can look it up and confirm the signature, much as a tamper-evident seal shows that a package was not opened on the way. Google has administrators generate the key in the Admin console and publish it as a TXT record. Microsoft’s documentation says DKIM signing for a custom domain in Microsoft 365 “requires two CNAME records in the domain.”

DMARC is the instruction.

Google’s help page on setting up DMARC says it “tells receiving email servers what action to take on messages” that do not pass the checks. The policy has three settings. Under the original DMARC specification, published in March 2015 and since replaced by newer versions, “none” asks for no specific action, “quarantine” asks receivers to treat failing mail as suspicious, and “reject” asks them to refuse it. The record lives at a subdomain named “_dmarc” and can list an address where receivers send summary reports.

DMARC also adds a condition that is easy to miss. The domain in the From address has to match a domain that SPF or DKIM validated. The specification calls this identifier alignment, and it is the reason a message can pass a check and still fail DMARC.

04Why This Matters More Than It Used To

For years these records were optional good practice. The large mailbox providers have since written them into their rules.

Google’s email sender guidelines say that starting February 1, 2024, all senders who send email to Gmail accounts must set up SPF or DKIM for their sending domains. Senders of 5,000 or more messages a day must set up SPF, DKIM and DMARC, and the guidelines note that the DMARC policy can be set to none. On the consequence, the page says that messages that are not authenticated “might be marked as spam or rejected with a 5.7.26 error.”

Yahoo’s Sender Hub asks the same of everyone: “Implement SPF or DKIM at a minimum.” For bulk senders it requires both, plus a valid DMARC policy of at least p=none. Microsoft followed. According to a summary by dmarcian, a company that provides DMARC tools, Microsoft’s rules for its consumer services outlook.com, hotmail.com and live.com apply to domains sending over 5,000 emails per day, and messages that do not comply have been rejected since May 5, 2025.

A landscaping company in Lakewood Ranch is not sending 5,000 messages a day. The first rule has no volume threshold, though. It covers a single estimate sent to one customer with a Gmail address. That matters most each fall, when a note to returning winter residents goes out to a long list of personal Gmail and Yahoo addresses.

05The Mistakes That Break It

In a small business, the records are usually set up correctly once and then undone by something added later. These are the common ways it happens.

  • Two SPF records. A newsletter tool’s instructions say to add an SPF record, and someone adds a second one instead of merging it into the first. RFC 7208 states that “multiple SPF records are not permitted for the same owner name,” and that a check which finds more than one returns a permanent error. Microsoft’s documentation says the same thing more simply: “only one SPF record is allowed per domain or subdomain.”
  • Too many services in one SPF record. RFC 7208 limits to 10 the number of terms in a record that make the receiving server look something up, and says the result is a permanent error if the limit is exceeded. Remove entries for tools you no longer use.
  • The website contact form. Many forms send their notification from the web server, with your own domain in the From line. If that server is not covered by your SPF record and does not sign with DKIM, the notice of a new inquiry can land in your own spam folder. The usual fix is to have the form send through your real email provider or a mail service that has been set up for your domain. Our contact page guide covers the rest of the form.
  • A tool that sends as you. Email marketing, booking and invoicing services all send messages with your address on them. Each one publishes a setup page with records to add. Until those are in place, its messages are not aligned with your domain. Google’s guidelines say that for direct email the domain in the From header “must be aligned with either the SPF domain or the DKIM domain.”
  • A strict DMARC policy on day one. Google’s DMARC page recommends setting the policy to none when you start and changing it to quarantine or reject over time. It also says SPF or DKIM must be turned on first, and to allow 48 hours after setting them up before adding DMARC. Going straight to reject can block your own invoices.

06A Short Check, and What These Records Will Not Do

You can run a first test yourself. Send a message from your business address to a personal Gmail account and open it there. Gmail’s help page on checking authentication says, “If you see a question mark next to the sender’s name, the message isn’t authenticated.” Repeat the test with a message from your contact form and one from your newsletter tool, because each travels a different route.

The fix belongs to whoever manages your DNS. That may be your web designer, an IT person, or the support desk at your email provider. Four questions will tell you where things stand:

  • Where are our DNS records managed, and who has the login?
  • Is there exactly one SPF record, and does it include every service that sends mail as us?
  • Is DKIM turned on for our email provider and for our newsletter or booking tool?
  • Is there a DMARC record, what is its policy, and who reads the reports?

Keep expectations modest. These records prove that a message came from you. They do not make it welcome. Google’s guidelines also ask senders to keep the spam rate reported in its Postmaster Tools below 0.3 percent, and that number is set by how recipients react to your mail. Gmail’s help page notes that “messages that aren’t authenticated aren’t necessarily spam,” and the reverse is also true: an authenticated message can still be filtered. No one can guarantee that every email reaches the inbox.

If you have not yet moved to an address on your own domain, our comparison of Google Workspace and Microsoft 365 is the place to begin. If you are planning a new website and want to be sure your email keeps working through the move, you can tell us about your project.

When you are ready to talk about your own site, the Sarasota web design page covers what is included at each level and what drives the cost.

Ready for a website that reflects your business?

Start a project ↗