DMARC (Domain-based Message Authentication, Reporting & Conformance) is a critical email authentication protocol that safeguards your domain from spoofing attacks. These attacks involve forging your email address to trick recipients into believing the message is legitimate. DMARC helps prevent this by verifying the sender's identity through existing protocols like SPF and DKIM.
By implementing DMARC, you gain greater control over your email security. You can instruct receiving mail servers on how to handle emails that fail authentication checks. This empowers you to quarantine or even reject suspicious emails, protecting your reputation and preventing sensitive information breaches.
DMARC's true power lies in its reporting capabilities. Beyond just verification, DMARC provides valuable insights into email activity associated with your domain. These reports reveal any unauthorized attempts to send emails under your name, even if they manage to bypass initial authentication checks. This advanced visibility allows you to identify potential security weaknesses and take proactive steps to address them before they evolve into costly cyberattacks.
TAG | MEANING |
---|---|
v | Required: Specifies the version of the DMARC protocol being used. Always set to v=DMARC1 for the current DMARC protocol version. |
p |
Required: Specifies the policy to be enacted by the receiving mail server when DMARC authentication fails.This tag determines what action should be taken if an email fails DMARC checks.
Possible Values:
|
sp | Specifies the policy for handling messages from subdomains of the DMARC-aligned domain. Subdomains inherit policies from their parent domain unless explicitly overridden. |
rua | Specifies the URI(s) to which aggregate DMARC reports should be sent, for example: rua=mailto:your@email.com. Aggregate reports provide statistics about DMARC usage and authentication results. |
ruf | Specifies the URI(s) to which forensic DMARC reports should be sent (reports about individual failed messages), for example: ruf=mailto:your@email.com. Forensic reports contain detailed information about specific messages that failed DMARC checks. |
adkim |
Specifies how DKIM (DomainKeys Identified Mail) alignment should be handled. DKIM alignment verifies that the DKIM signature on an email matches the sender's domain.
Possible Values:
|
aspf |
Specifies how SPF (Sender Policy Framework) alignment should be handled. SPF alignment verifies that the SMTP MAIL FROM domain matches the domain used in the RFC5322.From header field.
Possible Values:
|
fo |
Determines the level of detail in forensic reports (message-level reports) generated when DMARC authentication fails.
Possible Values:
|
rf |
This tag specifies the format for forensic (message-level) DMARC reports that are sent to the specified reporting addresses (ruf).
Possible Values:
|
pct | Specifies the percentage of messages subjected to DMARC policy filtering.Allows gradual enforcement of DMARC policies to monitor impact before full enforcement. Any integer value from 0 to 100. |
ri | This tag specifies the interval at which aggregate DMARC (Domain-based Message Authentication, Reporting & Conformance) reports should be generated and sent by receivers to the specified reporting addresses (rua). For example: ri=86400 indicates that aggregate reports should be sent daily (every 86400 seconds). |
Become a part of the Campaign Cleaner community today, and join countless satisfied customers who have witnessed significant improvements in their email deliverability and campaign success. Don't let HTML issues hold you back; let Campaign Cleaner optimize your campaigns and boost your inbox rates