Blog · October 21, 2026
Can someone send email as you? SPF, DKIM, and DMARC in plain English
If your domain is missing three DNS records, anyone can send email that looks like it came from your business, and your real email is more likely to land in spam. What the records do, how to check yours in ten seconds, and the one setting most businesses get wrong.
By Orion Grimm
Here is a test. Put your business domain into our email spoofing check. It reads three public DNS records and tells you, in one line, whether an attacker can send email that appears to come from your company. Most Anchorage businesses we check get a warning on the first try.
That matters for two reasons. The obvious one: a fake invoice from “you” to your own customers, with new bank details. The less obvious one: mailbox providers now treat a domain with weak records as suspicious, so your real email lands in spam more often. Both problems have the same fix.
Three records, one job
Email has no built-in way to prove who sent a message. The “From” line is just text. Three DNS records were bolted on over the years to fix that, and they work together.
SPF is a list of the servers allowed to send mail for your domain. Microsoft 365, Google Workspace, your invoicing app, your newsletter tool. When a mailbox receives a message claiming to be from you, it checks whether the sending server is on your list.
DKIM is a signature. Your mail server signs each message with a private key, and publishes the matching public key in DNS. The receiver checks the signature. A message that was altered in transit, or sent by someone without your key, fails.
DMARC is the policy that says what to do when SPF or DKIM fails, and where to send the reports. Without DMARC, a failure is just a suggestion. With it, you can tell the world’s mailbox providers to quarantine or reject mail that pretends to be you.
The setting most businesses get wrong
DMARC has three policy levels: none, quarantine, and reject. Almost every domain that has DMARC at all is set to none, usually because a setup guide said to start there and nobody ever came back. none means “check it and tell me, but deliver it anyway.” It is monitoring, not protection.
The right end state is reject, and the path there is short: turn on DMARC at none, read the reports for a couple of weeks to catch any legitimate sender you forgot (the payroll provider, the scanner in the copy room), add them to SPF, then move to quarantine and finally reject. We do this for clients in the first month. It is not glamorous work and it is the highest-value hour in email security.
Things that break it
- A copier or a line-of-business app sends email through your domain and was never added to SPF. Its messages start bouncing the day you enforce DMARC. The reports tell you before you enforce.
- Too many includes. SPF allows ten DNS lookups. Businesses that have bolted on tool after tool exceed it, and SPF silently fails for everyone. The check flags this.
- A marketing tool sends “as you” from its own servers without DKIM configured on your side. Its mail passes today, fails the day you enforce, and the marketing manager calls.
- Nobody reads the reports. DMARC reports are XML files in an inbox nobody opens. Either route them to a service that summarizes them, or to the person who runs your IT.
And BIMI, since you will hear about it
Once DMARC is enforced, you become eligible for BIMI, which puts your verified logo next to your emails in Gmail and Apple Mail. It requires a trademark and a certificate, so it is a nice-to-have rather than a security control, but it is only possible for domains that did the work above. We have a check for that too.
Do this today
Run the ten-second check. If it comes back with “someone can spoof you,” send the result to whoever runs your email. If that is nobody, it is a thirty-minute conversation with us, and getting your domain to a real DMARC policy is part of the first month for every business we manage.