A customer in Eagle calls your office and asks why you emailed them a new bank account for their invoice.
You didn't. Somebody else did, using your company name and your domain.
That is email spoofing, and I see it hit small Treasure Valley businesses all the time: contractors, CPA offices, property managers, clinics. The scary part is that most of them never set up the three DNS records that tell the rest of the internet which mail is really theirs.
The flip side shows up too. Your real quotes and invoices start landing in spam at Gmail or Outlook, and you have no idea why. Same root cause.
This post walks through SPF, DKIM, and DMARC in plain English, what to check on your own domain today, and when it makes sense to have someone like me fix email spoofing for you.
Key Takeaways
- Spoofing works because email was never built to prove who sent it. SPF, DKIM, and DMARC are the fix.
- SPF lists who is allowed to send as your domain. DKIM signs your mail. DMARC tells receivers what to do when a message fails.
- Google, Yahoo, and Microsoft now expect these records from senders, so missing them hurts delivery, not just security.
- Start DMARC in monitor mode, read the reports, then tighten it. Jumping straight to reject can block your own invoices.
- Every tool that sends mail for you (QuickBooks, your CRM, your website form, your newsletter) has to be accounted for.
Why Spoofing Is So Easy
Email is old. When it was designed, nobody thought about someone pretending to be your business. By default, a scammer can put your address in the "From" line and send it from their own server.
Whether that message lands in your customer's inbox depends on whether your domain has told the world how to check it. If you never set that up, receivers have to guess. Guessing is how fake invoices get through and how real ones get flagged.
SPF: Who Is Allowed to Send as You
SPF (Sender Policy Framework) is a single TXT record in your DNS. It lists the services allowed to send mail for your domain.
A typical small business record looks something like this:
v=spf1 include:spf.protection.outlook.com include:_spf.google.com ~all
That says Microsoft 365 and Google can send for you, and anything else should be treated as suspicious.
Common problems I find on Boise business domains:
- No SPF record at all. Nothing to check against.
- Two SPF records. You only get one. Two means both can fail.
- Missing senders. Your website contact form, invoicing software, or email marketing tool sends mail, but it is not listed, so your own messages fail.
- Too many lookups. SPF has a limit of 10 DNS lookups. Stack enough "include" entries and the whole record breaks.
DKIM: A Signature on Every Message
DKIM (DomainKeys Identified Mail) adds a digital signature to your outgoing mail. Your email provider holds a private key and publishes the matching public key in your DNS. Receivers check the signature to confirm the message really came through your system and was not changed on the way.
In Microsoft 365 and Google Workspace, DKIM is a setting you turn on, then you add a couple of DNS records they give you. It takes a few minutes, but a lot of businesses never flip it on because nothing visibly breaks without it.
Each outside service that sends as your domain (newsletter, CRM, billing) usually has its own DKIM setup too. Do those as well.
DMARC: The Rule That Ties It Together
DMARC is the part that actually stops spoofing. It is another TXT record that says:
- A message has to pass SPF or DKIM, and match your domain, to count as yours.
- Here is what to do with mail that fails: nothing, quarantine it, or reject it.
- Send reports to this address so I can see who is sending as me.
It has three policy levels:
- p=none watches and reports but does not block anything. This is where you start.
- p=quarantine sends failing mail to spam.
- p=reject blocks failing mail outright. This is the goal.
The mistake I see is someone reading an article, setting p=reject on day one, and then wondering why invoices from their accounting software vanished. Start at none, read a few weeks of reports, fix your real senders, then move up.
Why This Matters for Delivery Now
This is not just a security nice to have anymore. Starting in 2024, Google and Yahoo began requiring bulk senders to have SPF, DKIM, and DMARC in place, and Microsoft followed with similar rules for Outlook.com addresses in 2025. Even if you are not a bulk sender, mail from domains without these records gets more suspicion from the big inbox providers.
So if your quotes keep going to spam, fixing these records is often the first real step.
A Quick Check You Can Do Today
You do not need to be technical to see where you stand:
- Send an email from your business account to a personal Gmail address.
- Open it in Gmail, click the three dots, and choose "Show original."
- Look for SPF, DKIM, and DMARC near the top. Each should say PASS.
If any say FAIL, or DMARC is missing, your domain is easier to spoof than it should be. Free lookup tools from MXToolbox or similar sites will also show what records you have published.
What to Fix First
Here is the order I work in for a small Treasure Valley office:
- List every sender. Microsoft 365 or Google, website forms, QuickBooks or other billing, CRM, booking software, newsletter tool.
- Clean up SPF so it is one record that covers all of them and stays under the lookup limit.
- Turn on DKIM in your main email platform and in each outside sender that supports it.
- Publish DMARC at p=none with a reporting address.
- Read the reports for a few weeks and fix anything legit that fails.
- Move to quarantine, then reject.
Pair this with the basics: MFA on every Microsoft 365 account , a habit of calling to confirm any payment change, and some phishing awareness for your team. DMARC stops people faking your domain. It does not stop a lookalike domain or a hacked mailbox, so you still want the other layers.
When to Get Help
If you have one email platform and nothing else sending mail, you can probably handle SPF and DKIM yourself in an afternoon. Where it gets messy is the DMARC reports and all the side systems nobody remembers are sending as your domain.
That is the kind of thing I set up for local businesses as part of cybersecurity and Microsoft 365 support . I check your current records, find every sender, get you to a reject policy without breaking your invoices, and keep an eye on it after.
If a customer already got a fake email from "you," or your mail keeps landing in spam, reach out here or call me at (208) 918-0636. I am in Garden City and work with businesses across Boise, Meridian, Nampa, Eagle, and the rest of the Treasure Valley.
Joey Garcia Idaho Proper IT