Today, anyone can send email that appears to come from clientdomain.com.
Your customers cannot tell a forgery from the real thing, because nothing in your DNS instructs their mail provider to refuse one.
Read from public DNS and the reports providers already generate. No system access required.
The forgery targets your customers, not you — nothing on your network is touched, so the fraud can run for months in someone else’s inbox using your name.
Google, Yahoo and Microsoft now expect authentication — unauthenticated bulk mail is filtered harder, which means this also affects whether your real invoices and notices arrive.
Insurers and card standards ask about it directly — PCI DSS 4.0 requires anti-phishing controls, and cyber-insurance questionnaires now ask whether your domain enforces DMARC.
You will have your first list of the services seen sending as clientdomain.com within a week, and a monthly report showing what changed.
- What we need from you:
- DNS access to your domain, or an introduction to whoever holds it
Prepared by Your company for Client name using data and findings from DDMARC. DDMARC is not a party to this document and makes no representation to Client name about its content.