This built-in DMARC record generator tool empowers you to strengthen your email security with ease. Forget complex manual configuration – this intuitive feature guides you through the process step-by-step, ensuring a smooth and efficient setup.
Simply enter your domain name and select your preferred policy. The tool offers clear explanations for each option, allowing you to choose whether to monitor (p=none) email activity for informational purposes, quarantine (p=quarantine) suspicious emails for further review, or reject (p=reject) unauthenticated emails outright. Additionally, you can specify email addresses to receive reports detailing email activity. These reports provide valuable insights into how your domain is being used for email and can help identify potential security threats like email spoofing.
No technical expertise is necessary! The generator handles the intricacies of crafting an accurate DMARC record, saving you time and ensuring you have the essential reporting features in place. This simplifies the initial setup and grants you control over your email security by providing valuable insights from DMARC reports. With this knowledge, you can make informed decisions to further protect your organization from email-based attacks.
Once you have it set up, it's time to test it with our very own eMail Tester.
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