The SMTP protocol does not validate who sends an email. An attacker can forge your domain in the 'From:' and deceive clients and staff. DMARC, SPF and DKIM shut that door, and WebMon watches that it stays shut.
Home · Email Security · Email spoofing
In short
It is the forgery of an email's sender address to pass it off as a legitimate origin. Because SMTP was designed without authentication, anyone can put your domain in the 'From:' field without permission, unless controls are in place to prevent it.
SPF declares which servers may send for your domain; DKIM signs the message cryptographically; and DMARC tells the receiver what to do if SPF or DKIM do not align with the 'From:' domain — quarantine or reject — and sends you reports of every attempt.
Companies whose name or brand can be used to deceive: banking, retail, insurers, government and any organization that communicates by email with clients, suppliers or staff across Latin America.
It prevents your domain from being used for phishing and fraud in your name. With DMARC set to reject, spoofed emails never reach the victim's inbox, protecting your brand and those who trust it.
Capabilities
Why it matters
FAQ
SMTP was designed in the 1980s without sender authentication, so the 'From:' field can be written freely. SPF, DKIM and DMARC are the layers added later to validate the origin.
DMARC needs SPF or DKIM to work: it defines what to do when authentication does not align with the 'From:' domain. In a reject policy, spoofed emails are discarded before reaching the recipient.
Yes. A frequently spoofed domain builds up negative reputation, and without proper authentication your legitimate mail may land in spam. A well-configured DMARC protects both brand and deliverability.
WebMon continuously monitors your SPF, DKIM and DMARC records, processes aggregate reports and alerts you to spoofing attempts or any change that weakens your authentication.
Diagnose your DMARC, SPF and DKIM with WebMon and shut the door on spoofing.
Diagnose your domain with WebMon