Help for owners
Customers are getting fake emails that look like they came from my company
Short answer
Anyone can type your address in the From line of an email. Mail providers decide whether to trust it by checking SPF, DKIM and DMARC records on your domain. With a DMARC policy set to quarantine or reject, fake mail that fails the checks is sent to spam or refused. Set it up in steps, so your own mail is not blocked.
Does this sound like your situation?
- A customer forwarded me an invoice or payment request I never sent.
- I get bounce messages for emails I did not write.
- Staff received a message that looks like it is from me or from a colleague, asking for a transfer or a gift card.
- My own emails started landing in spam at the same time.
- I have no idea whether anything protects my domain from this.
Why does this happen?
Email does not check the From line by itself
The visible sender is just text the sender chooses. Protection comes from records on your domain that tell receiving servers who may send for it and what to do with the rest.
No DMARC record exists
DMARC tells receiving mail servers what to do with messages from your domain that fail SPF or DKIM checks: deliver, quarantine or reject. It also sends reports about who is sending as you. Without the record, the receiver decides alone.
Confirmed by knowledge.workspace.google.comTechnical detail: Mail from your own domain keeps landing in the spam folder
DMARC exists but is set to monitor only
A policy of none takes no action: the message is delivered and the result is only logged in the reports. That is the right first step, but it does not stop fake mail until it is moved on.
Confirmed by knowledge.workspace.google.com
A real sender of yours fails the checks
Your newsletter tool, shop or invoicing app may send as you without being listed in SPF or signing with DKIM. Tightening the policy before fixing these blocks your own mail, which is the main failure of a rushed rollout.
Confirmed by knowledge.workspace.google.com
A genuine mailbox may have been taken over
Not all fake mail is spoofing. If mail really leaves your mail system, an account has been compromised, and DMARC will not stop it.
What can I do about it today?
- Warn customers and staffSend a short note from a channel you trust: the real invoice comes from this address, and nobody is asked for payment details or gift cards by email.
- Keep two or three of the fake emailsForward them as attachments to a safe folder. The full message headers show where they really came from, and a developer needs them.
- Check whether it is spoofing or a hacked mailboxLook at the Sent folder of the mailbox being impersonated. If the fake messages are not there and the bounces are for mail you never sent, it is likely spoofing. If they are there, change the password from a clean computer.
- Turn on two-step sign-in for your mailboxesIt does not stop spoofing, but it removes the most common way real accounts are taken.
- Ask whoever manages your domain which records existAsk in writing whether SPF, DKIM and DMARC are set, and what the DMARC policy is. Do not edit DNS yourself without a copy of the current records.
- Do not jump straight to rejectGoogle recommends starting with a policy of none and reading the reports first. Then move to quarantine or reject and raise the percentage gradually.
When should I bring someone in?
- Customers have already paid a fake invoice, or staff were tricked.
- You use several tools that send mail as your domain and nobody knows the full list.
- Your own mail started to fail after someone changed the DNS records.
How do I handle it?
- Read the headersI use the saved fake messages to see where they came from and whether any of your own systems sent them.
- List every real senderMail system, website forms, shop, invoicing and newsletters are each checked for SPF and DKIM.
- Publish a monitoring policyA DMARC record with reporting goes first, to a mailbox set aside for reports, since their volume can be high.
- Fix what the reports showEach legitimate sender that fails is corrected before the policy gets stricter.
- Tighten in stepsI move to quarantine and then reject while raising the percentage, and keep a written copy of each DNS change and how to undo it.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I stop people typing my address in the From line?
No. What you can control is what receivers do with mail that fails your checks, through SPF, DKIM and a DMARC policy.
Will DMARC stop every fake email?
It covers mail that uses your exact domain. It does not stop look-alike domains with a different spelling, and it does not stop a hacked real mailbox.
How soon can I set it to reject?
Google advises waiting at least 48 hours after setting up SPF or DKIM before enabling DMARC, then reviewing reports before tightening. How long you need depends on how many senders you have.
Do I need a special mailbox for the reports?
Google suggests a dedicated mailbox or group, since the volume can be high.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.