Getting Bounces for Emails You Never Sent? Backscatter Explained
If you are getting bounce messages for emails you never sent, someone is most likely forging your address as the sender of their spam. When those messages fail, the bounces come back to you. This is called backscatter. It does not necessarily mean your account was hacked, but you should rule that out, then use SPF, DKIM and DMARC to make your domain much harder to forge.
How backscatter happens
Email lets any sender put any address in the From and return-path fields. Authentication exists to catch forgeries, but not every domain has it set up and not every receiving server enforces it. So:
- A spammer sends thousands of messages with your address as the sender.
- Some go to addresses that do not exist or servers that reject them after accepting.
- Those servers send delivery failure notices to the forged sender: you.
You see a stream of "Undeliverable" or "Delivery Status Notification" messages about emails in languages or topics you have never written.
Step 1: Rule out a compromised account
Before assuming spoofing, check whether someone actually has access:
- Sent folder: are the bounced messages there? If yes, they were sent from your account.
- Sign-in activity: Google Workspace and Microsoft 365 show recent sign-ins and locations.
- App passwords and connected apps: remove anything you do not recognise.
- Forwarding rules and filters: attackers sometimes add hidden rules.
- SMTP credentials: if your website or app sends mail with stored credentials, those may have leaked.
If you find signs of compromise, change the password, enable multi-factor authentication, revoke sessions and app passwords, and tell your IT contact. Then continue below.
Step 2: Look at the bounced messages
Open a few bounces and look at the original message attached or quoted inside.
- Which server sent the original? If it is not one of your known senders, it is forged.
- What was the From address? Often a random username at your domain, such as
xk29@yourdomain.com. - What does it contain? Usually generic spam or phishing.
The email header analyzer helps read the original headers.
Step 3: Publish SPF and DKIM
If your domain has no SPF record, or one that ends in +all, receivers have no way to tell your mail from forgeries.
- SPF lists the servers allowed to send for your domain. Check it with the SPF checker.
- DKIM signs your genuine mail cryptographically. Check with the DKIM checker.
On their own, these help receivers judge mail, but they do not tell receivers what to do with failures. That is DMARC's job.
Step 4: Enforce DMARC
DMARC tells receivers what to do when a message claiming to be from your domain fails authentication:
| Policy | Effect on forged mail |
|---|---|
p=none |
Monitor only; forgeries may still be delivered or bounced to you |
p=quarantine |
Forgeries go to spam |
p=reject |
Forgeries are rejected during delivery |
With p=reject, many receivers refuse forged mail at the connection stage, which means fewer messages are accepted and later bounced back to you. Move gradually: start at p=none, read the reports to confirm all your legitimate senders align, then tighten. Moving DMARC from none to reject explains the steps, and the DMARC generator builds the record.
The email spoofing test shows how easy your domain is to forge right now.
Step 5: Filter what still arrives
Even with DMARC enforcement, some backscatter will arrive from servers that accept first and bounce later. To reduce the noise:
- Most mailbox providers already filter much backscatter as spam.
- Create a filter for bounce notices that do not reference messages from your real sending systems.
- If you run your own mail server, it can check whether a bounce refers to a message you actually sent.
Be careful not to filter real bounces from your own campaigns. Those tell you which addresses are invalid.
If the forged mail uses your domain, not just your address
Spoofing that uses random addresses at your domain, rather than your personal address, affects everyone at the company. It is a sign that DMARC enforcement is overdue. Phishing using your domain can reach your customers and partners, and enforcement protects them as much as it protects you.
Backscatter vs real bounces
| Backscatter | Real bounces | |
|---|---|---|
| Original message | Not sent by you | Sent by you |
| Sending server | Unknown | Your platform or mailbox |
| Content | Spam you did not write | Your campaign or email |
| Fix | SPF, DKIM, DMARC enforcement | Verify and clean your list |
Worked example (illustrative)
A small design studio starts receiving hundreds of "Undeliverable" messages a day, about emails selling pharmaceuticals.
- The owner checks the sent folder and sign-in history: nothing unusual. The account is not compromised.
- The bounced originals show random addresses at the studio's domain, sent from servers the studio does not use.
- The domain has an SPF record but no DKIM and no DMARC.
- The studio enables DKIM in its email provider, publishes DMARC at
p=none, and reads reports for two weeks to confirm its own tools align. - It moves to
p=quarantine, thenp=reject.
The backscatter drops to a handful of messages a week, and receivers now have a clear instruction to refuse mail forged in the studio's name.
Keep your own bounces low
Once forged mail is under control, the bounces that remain are yours, and each one matters for your sender reputation. Verifying lists before you send removes invalid addresses before they bounce. Upload a list on the verify page; you get 100 free email checks when you sign in with Google, no card.
Common questions
Why am I getting bounce messages for emails I didn't send?
Most often because a spammer used your email address or domain as the forged sender. When their messages fail, the receiving servers send the bounces to the forged address, which is yours. This is called backscatter.
Does backscatter mean my email account was hacked?
Not necessarily. Forging a sender address does not require access to your account. But check: if the bounced messages appear in your sent folder, or your account shows unfamiliar sign-ins, the account may be compromised and you should change your password and review access.
How do I stop backscatter?
Publish SPF and DKIM for your domain, then move your DMARC policy to quarantine or reject once your legitimate mail is aligned. Receiving servers then reject or filter forged messages instead of accepting and bouncing them. Spam filters can also hide obvious backscatter.
Can backscatter hurt my domain's reputation?
Spoofed spam using your domain can confuse recipients and, without DMARC enforcement, may be associated with your domain. An enforcing DMARC policy is the strongest protection.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.