IsThisAScam
AccueilBlogTarifsÀ ProposHistoryAPIExtension
Upgrade
FR
Sign in
Sign in
IsThisAScam

Independent scam & phishing analysis. Free for individuals. APIs for developers.

Operated by Zeplik, Inc.
Produit
  • Home
  • Blog
  • Pricing
  • À Propos
  • History
  • Chrome Extension
Resources
  • Developers
  • Documentation API
  • Phishing brief
  • Romance scams
  • Tech support
  • Crypto scams
  • Apple scams
  • PayPal scams
Mentions Légales
  • Politique de Confidentialité
  • Conditions d'Utilisation
  • product@zeplik.com

© 2026 Zeplik, Inc. Tous droits réservés.

Built for the calm, the cautious, and the careful.

Home/Glossary/DMARC
Glossary · Defense & Authentication

What Is DMARC?

Domain-based Message Authentication, Reporting, and Conformance — an email authentication protocol that builds on SPF and DKIM to give domain owners control over what happens to emails that fail authentication checks.

Quick Definition

Domain-based Message Authentication, Reporting, and Conformance — an email authentication protocol that builds on SPF and DKIM to give domain owners control over what happens to emails that fail authentication checks.

Think you've been targeted?

Paste the suspicious content here for an instant analysis.

No signup · 6 detection layers · Results in seconds · Cmd+Enter

01DMARC explained.

DMARC is the policy layer that ties SPF and DKIM together. While SPF and DKIM can verify email origins, DMARC tells the receiving server what to do with messages that fail those checks: accept them, quarantine them (send to spam), or reject them outright.

DMARC also solves the "alignment" problem — it checks that the domain in the header "From" address (what the user sees) matches the domain verified by SPF and DKIM. This closes the gap that allowed attackers to pass SPF checks while still spoofing the visible sender.

The reporting feature of DMARC sends feedback to domain owners about who is sending email using their domain, legitimate or otherwise. This visibility helps organizations identify and stop unauthorized use of their brand in phishing campaigns.

02How it works.

01The domain owner publishes a DMARC policy in DNS specifying how to handle authentication failures
02When an email arrives, the receiving server performs SPF and DKIM checks
03DMARC verifies that the domain in the visible "From" header aligns with SPF/DKIM results
04Based on the DMARC policy, failed messages are accepted, quarantined, or rejected
05Aggregate reports are sent to the domain owner showing authentication results for their domain

03Real-world example.

After the US government mandated DMARC with a "reject" policy for all .gov domains in 2018, the volume of spoofed emails impersonating government agencies dropped dramatically. This made it significantly harder for scammers to send convincing IRS, Social Security, and Medicare phishing emails.

04How to protect yourself.

01Organizations should implement DMARC with a "reject" policy after testing with "none" and "quarantine"
02Check email headers for DMARC results ("dmarc=pass" means the email is authenticated)
03Use IsThisAScam to analyze email authentication including SPF, DKIM, and DMARC status
04Individual users should prefer email providers that enforce DMARC (Gmail, Outlook)
05Report emails that spoof legitimate organizations so their DMARC reports can flag the abuse
Related Terms
SPFDKIMPhishingSpoofing
Explore Scam Types
phishingromancecryptoinvestmenttech supportdelivery
Suspect Something?

Run a scan on the message you received.

Run a scan →