// how to fix
Someone sends fake emails with your domain (spoofing)
Scammers can send emails that look like they come from your domain. A DMARC policy at reject tells receivers to refuse them. Monitor first, then enforce.
What it means
Email was designed without proof of who the sender is. Anyone can write your address in the From line, just like anyone can write any return address on a paper letter. This is called spoofing.
Signs that it is happening to you:
- You receive bounces for emails you never sent.
- Customers or partners tell you they received strange invoices, payment requests or links "from you".
- DMARC reports show servers you do not know sending with your domain.
Why it matters
Spoofed emails are used for phishing and invoice fraud. They hurt your customers and your brand, and they can damage your domain's reputation with mailbox providers.
Note: if your own mailbox was hacked, the emails really come from you. Change the password, turn on two-factor login and check forwarding rules first.
How to check
- Use the Domain scanner at
/domain-scanner: check that SPF, DKIM and DMARC exist, and look at your DMARC policy. - Read DMARC reports: they list every IP that sent email with your domain and whether it passed. Delivmail DMARC monitoring, in the paid dashboard, receives and summarizes them for you.
- If you have a suspicious email, look at its headers: an email that fails SPF and DKIM for your domain is not yours.
How to fix it
- Set up SPF and DKIM for every service that legitimately sends for you.
- Publish DMARC in monitoring mode if you do not have it yet:
_dmarc.yourdomain.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"
- Read the reports for two to four weeks. Sort sources into "mine" (fix their SPF or DKIM) and "not mine" (spoofing).
- Move to quarantine once all your real senders pass:
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com
- Then move to reject, which tells receivers to refuse spoofed emails:
v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com
- Protect your other domains: domains that never send email should have
v=spf1 -alland a DMARC record withp=reject. - Keep monitoring. New tools you add later must be authenticated, or
p=rejectwill block them.
What DMARC cannot do
DMARC protects your exact domain. It does not stop lookalike domains such as yourdomaín.com or yourdomain-billing.com. Warn your customers, and report fake domains to their registrar.
Check that it is fixed
DNS changes are not instant. Most are visible within a few minutes, but some providers take up to 24 to 48 hours.
Run the Domain scanner again: the DMARC policy should show reject. Send a test email from the home page to confirm your own emails still pass. Over the following weeks, DMARC reports should show spoofed emails as rejected.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- No SPF record on your domainYour domain does not say which servers may send email for it. Add one TXT record and receivers can tell your real emails from fakes.
- SPF error: too many DNS lookups (permerror)SPF allows at most 10 DNS lookups. Above that, the whole record breaks and receivers treat it as invalid. Here is how to slim it down.
- Several SPF records on one domainA domain must have only one SPF record. With two or more, SPF breaks for every email. Merge them into a single line.
- SPF fails: the sending server is not authorizedYour domain has an SPF record, but the server that sent your email is not in it. Find which service sent the email and add it.
- No DKIM signature on your emailsDKIM adds a digital signature that proves an email really comes from your domain. Turn it on in your email provider and publish its key in DNS.