Glossary
DMARC
DMARC Explained: Stop Email Spoofing and Brand Impersonation
DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email security standard that lets a domain owner tell receiving mail servers how to treat messages that claim to come from the domain but fail authentication. It builds on SPF and DKIM and adds reporting. For brands, DMARC is one of the most effective controls against email spoofing and phishing in their name.
What Is DMARC?
Email was designed without a built-in check of who the sender really is. Anyone can type any address into the "From" line, which is why scammers can send messages that look like they come from a bank, a retailer or a CEO. DMARC closes part of that gap.
DMARC works in combination with two older protocols:
- SPF (Sender Policy Framework) lists which servers may send mail for a domain.
- DKIM adds a digital signature to a message so the receiver can verify it was not altered and comes from the claimed domain.
DMARC adds two things. First, it requires alignment: the domain that passes SPF or DKIM must match the domain the reader sees in the "From" address. Second, it lets the domain owner publish a policy and request reports. DMARC is published as a TXT record in the DNS of the domain, at the name _dmarc followed by the domain. It is specified in the standard RFC 7489.
How DMARC Works
When a receiving server gets a message, it checks SPF and DKIM and looks up the DMARC policy of the "From" domain. The message passes DMARC if at least one of the two checks passes and is aligned. If it fails, the receiver follows the policy:
- p=none: Monitoring mode. No action is requested, but reports are sent to the domain owner.
- p=quarantine: Failing messages should be treated as suspicious, for example delivered to the spam folder.
- p=reject: Failing messages should be rejected and not delivered.
The record can also contain addresses for aggregate reports (rua) and, optionally, failure reports (ruf). Aggregate reports show who is sending mail using your domain, which lets you find legitimate services you forgot and abusers you did not know about.
Receivers decide how strictly they act on the policy, but major mailbox providers take DMARC into account. Several large providers have also introduced requirements for bulk senders, so having DMARC in place helps deliverability as well as security.
Example
A cosmetics brand has no DMARC policy. A scammer sends an email that appears to come from the brand's customer service address, announcing a prize and linking to a fake page. Many receivers cannot tell it is fake and the message lands in inboxes.
Now the brand publishes DMARC with p=reject, properly aligned with its own sending services. Receivers that honor the policy reject the forged message, and the brand receives reports showing the attempt.
DMARC only protects the exact domain it is set on. The scammer can still register a lookalike such as brand-support.example, which carries no policy of its own. That is why it works together with domain monitoring.
Why It Matters for Brands
- Customer protection: Fewer forged emails reach customers, partners and staff, which limits phishing and business email compromise.
- Reputation: Legitimate email arrives more reliably, and customers see fewer scam messages in your name.
- Visibility: Reports reveal unauthorized senders and forgotten systems.
- Compliance and trust: Many security frameworks and partners expect DMARC on corporate domains.
How to Implement DMARC Safely
- Inventory every service that sends mail for your domain: marketing tools, support desks, billing and internal systems.
- Set up SPF and DKIM for each of them.
- Publish DMARC with p=none and a reporting address, and read the reports for a few weeks.
- Fix gaps by authenticating the legitimate senders that fail.
- Move to quarantine, then reject, gradually, once legitimate mail passes consistently.
- Protect parked domains. Set a reject policy on domains that never send email (see domain parking).
- Keep monitoring. New tools and campaigns can break alignment.
A move to reject without checking all senders can block real mail, so go step by step.
Related Terms
- SPF (Sender Policy Framework): a DNS record that lists servers allowed to send mail for a domain.
- DKIM: a signature that proves a message came from the domain and was not altered.
- Email Spoofing: forging the sender address of an email.
- BIMI: a standard that can display a verified brand logo next to authenticated emails.
- DNS (Domain Name System): the system where DMARC records are published.
How Remove.tech Helps
DMARC protects your own domain, but attackers often turn to lookalike domains and fake sites that DMARC cannot cover. Remove.tech finds those lookalike domains, phishing pages and impersonation sites, and prepares the takedown notices. Together the two measures close both the front door and the side door. To see what is running under your brand name, get started.

