Skip to content
StrikeOps

DMARC Not Enforced (Email Spoofing Possible)

MediumTypical severity Email securityCWE-290ATT&CK T1566

01Description

The domain's DMARC record was missing or set to a monitoring-only policy (p=none), so receiving mail servers are not instructed to reject email that fails authentication.

02Impact

Attackers can send email that appears to come from the organization's exact domain, supporting phishing of staff, customers and suppliers and business email compromise fraud.

03Severity

Typically

Medium

Typically Medium. Medium by default. High for organizations whose customers or suppliers routinely act on emailed payment or account instructions.

04How to verify

  1. 1Query the domain's DMARC, SPF and DKIM DNS records.
  2. 2Assess the DMARC policy, alignment settings and reporting configuration.
  3. 3Where authorized, send a test spoofed message to a controlled mailbox to confirm delivery.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Publish SPF and DKIM for all legitimate sending services.
  2. 2Collect DMARC aggregate reports and fix legitimate senders that fail.
  3. 3Move the DMARC policy to quarantine, then reject.
  4. 4Apply DMARC reject to parked domains that never send email.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo