Anyone Can Fake Your Business Email: SPF, DKIM & DMARC Explained

PC Net, Inc. technician reviewing business email security settings at an office desk in Miami
For illustration only.

Your bookkeeper gets an email from you — your name, your email address, your usual tone — asking her to update the bank details on a vendor payment and keep it quiet until Friday. She almost sends the money. The only problem: you never wrote it.

That scene is not hypothetical, and it is not rare. We recently evaluated the email security of a local business here in Miami, and its domain had none of the three basic email protections in place — no SPF, no DKIM, no DMARC. Its email worked fine — messages arrived, invoices went out, customers replied. But as far as the rest of the internet was concerned, anyone could send email pretending to be that business, and nothing would stop them.

If you have never checked your own domain, there is a real chance it is in the same shape. The good news: checking takes about five minutes, and fixing it is a staged, low-risk job that does not touch your email provider or take your mail down. Here is what the three protections actually do, what goes wrong without them, and how to check your domain today.


At a glance

  • SPF, DKIM and DMARC are free DNS records that prove an email really came from your business.
  • Without all three, anyone can spoof your domain — fake invoices and “we changed our bank” emails are the classic attack.
  • Missing authentication also sends your real email to spam, and Gmail, Yahoo and Microsoft now require these records from senders.
  • The fix is staged — monitor first, then tighten — with no downtime and no change of email provider.


Email and shield icons on a monitor, representing SPF, DKIM and DMARC email authentication
For illustration only.

The three protections: SPF, DKIM and DMARC in plain English

Email authentication sounds technical, but each of the three records does one simple job. Together, they answer the question every receiving mail server asks: “Is this message really from who it claims to be from?”

SPF — the approved sender list. SPF (Sender Policy Framework) is a public list, stored in your domain’s DNS, of the servers allowed to send email for your business — your Microsoft 365 or Google Workspace account, your invoicing software, your marketing tool. When a message arrives, the receiving server checks the list. If the sending server is not on it, the message fails the SPF check.

DKIM — the tamper-proof signature. DKIM (DomainKeys Identified Mail) attaches a digital signature to every outgoing message, created with a private key only your mail system holds. The receiving server verifies the signature against a public key in your DNS. If the message was forged or altered on the way, the signature does not match. Think of SPF as the guest list and DKIM as the wax seal on the envelope.

DMARC — the policy and the alarm system. DMARC (Domain-based Message Authentication, Reporting and Conformance) ties the two together. It tells receiving servers what to do with mail that fails SPF or DKIM — deliver it, send it to spam (quarantine), or reject it outright — and it sends you reports about who is sending email using your domain, legitimate or not. Without DMARC, the other two records have no enforcement and you get no visibility. With it, spoofed mail can be blocked before it ever reaches an inbox.


A bookkeeper pausing before paying a suspicious invoice, a common email spoofing scam
For illustration only.

What goes wrong when all three are missing

Anyone can impersonate you. With no authentication in place, a criminal can send email from your exact domain using free tools. The messages that follow are the ones that cost businesses money: a fake invoice to your customer with new payment instructions, a “we changed our bank account” note to your bookkeeper, a payroll change request that looks like it came from an employee. Your customer pays the fake invoice in good faith — and then comes to you asking where their product is.

Your real email starts failing. The flip side is quieter but constant: receiving servers cannot verify your legitimate messages either, so your quotes, invoices and proposals land in spam folders or get rejected outright. You usually never find out — the customer just never replies.

The big mailbox providers raised the bar. Since 2024, Google and Yahoo require SPF, DKIM and DMARC from bulk senders, and Microsoft has followed with similar requirements. Even if you are not a bulk sender, unauthenticated mail is treated with more suspicion every year — domains without these records reach fewer inboxes.

You get no warning. Without DMARC reports, you have no way to know someone is spoofing you until a victim calls. Businesses routinely discover a spoofing campaign from an angry customer — weeks after it started.


Not sure whether your domain is protected? Most owners we check have never looked — and the answer surprises them. Call PC Net, Inc. at (305) 513-8614 (Mon–Fri, 8:30 AM – 5:00 PM) and we will tell you what your domain shows today.


PC Net, Inc. technician configuring email authentication while the business owner looks on
For illustration only.

Check your own domain in five minutes

You do not need an IT department to check. The free lookup tools at MxToolbox (mxtoolbox.com) query the same public DNS records anyone can see:

  1. SPF: In the MxToolbox search box, type spf:yourdomain.com. You should see “SPF record found.” No record found means any server can claim to send for you.
  2. DMARC: Type dmarc:yourdomain.com. Look at the policy value: p=none means monitor-only (you get reports, but spoofed mail is still delivered), p=quarantine sends failures to spam, and p=reject — the goal — blocks them outright.
  3. DKIM: Type dkim:yourdomain.com:selector1 (Microsoft 365) or dkim:yourdomain.com:google (Google Workspace). “DKIM record found” with a long public key means your mail is being signed. No record means it is not.

If any of the three comes back empty, your domain is exposed — and if the tools confuse you, that is fine. This check is the first thing we run in an email security evaluation, and we are happy to read the results with you.


How the fix works: staged, safe, no downtime

Done properly, this is one of the safest changes in IT — nothing about how your people send or receive email changes, and there is no mail migration. The work happens in your domain’s DNS records, in stages:

Stage 1 — Inventory and monitor (week 1). We list every system that legitimately sends email as your domain: your mailboxes, invoicing and accounting software, your website’s contact forms, any marketing tool. Then DMARC goes on in monitor mode (p=none) with reports coming to us. For one to two weeks, those reports show exactly who is sending as you — including systems nobody remembered authorizing, and any spoofing already happening.

Stage 2 — Publish SPF and DKIM. With the full sender list known, the SPF record is written to cover every legitimate sender (and no one else), and DKIM signing is switched on for your mail platform. Your email looks and behaves exactly as before — it now carries proof.

Stage 3 — Tighten the policy. Once the reports show all legitimate mail passing, DMARC steps up to p=quarantine, then to p=reject. From that point, a forged email using your domain is blocked by receiving servers instead of landing in someone’s inbox next to your real messages.

The staging is the whole point. Switching straight to reject without the monitoring stage is how legitimate mail gets blocked — the careful order is what makes the fix safe. It is standard work in our Managed IT services, and it is the kind of invisible, unglamorous protection that quietly prevents the worst phone call a business owner can get. (This month, Managed IT agreements signed by November 30, 2026 get the first month free — see our November Specials for details.)


Frequently asked questions

Will setting up SPF, DKIM and DMARC break our email?

No — done in the staged order, it does not interrupt mail at all. The records are added alongside your existing setup, enforcement starts in monitor mode, and the policy only tightens after reports confirm every legitimate sender is covered. Your team keeps sending and receiving email exactly as before throughout.

Do we have to change our email provider?

No. SPF, DKIM and DMARC live in your domain’s DNS, not in your mailbox. They work with Microsoft 365, Google Workspace and most other business email platforms, and your addresses, mailboxes and history stay exactly where they are.

How long does the full fix take?

The initial records can be published in a day. The monitoring stage then runs one to two weeks so no legitimate sender is missed, and most businesses reach a full reject policy within about a month of starting.

What does it cost to do it ourselves?

The records themselves are free — they are text entries in your DNS. The real cost is the work around them: inventorying every system that sends as your domain, writing the records correctly, and reading the DMARC reports well enough to tighten the policy without blocking real mail. Most small businesses have it done once, properly, rather than learning it the hard way.

What happens if we just leave it?

Your domain stays open for anyone to impersonate, your real messages keep fighting spam filters that cannot verify them, and you will likely hear about a spoofing attempt from a customer or vendor first — after money has moved. The records take little effort to add now, and considerably more explaining later.


Email is how your business sends invoices, quotes and payment instructions — a message from your domain should be provably yours. If you checked your domain above and found gaps (or the check left you more confused than when you started), PC Net, Inc. can evaluate your email security and stage the fix safely, with no downtime. Call us at (305) 513-8614, Monday to Friday, 8:30 AM – 5:00 PM, or contact PC Net, Inc. through our website.

Scroll to Top