Changelog

Your domains’ DMARC records are now analyzed to identify syntax issues that could prevent parsers from using DMARC correctly.

When a syntax error or potential issue is detected, you’ll find the details in the DMARC overview page. A check warning or error will also be triggered.

We currently validate the record to make sure that:

• No leading whitespace is present.

• Policy tag (p) is present.

• Policy tag (p) is the second tag in the record.

• All tag names are valid.

• All tag values are correctly formatted.

• No duplicate tags are present.

• No misplaced mailto: destinations are detected.

We currently don’t detect the following issues:

• Strict fo value compliance.
• Missing ruf when fo is present.
• rua and ruf URIs correctness.
• A record not starting with v=DMARC1 (leading whitespace is ignored) will be discarded and not shown at all.

The validation will be improved in future updates.

Learn more in the documentation.

The DMARC record summary table now shows default values when a tag is not set.

For example, if you don’t specify the sp tag (subdomain policy) in your DMARC record, the UI will show that the value of p is being used as per RFC 7489.

You can now group domains by domains group, DMARC setup status or DMARC policy, making it easier to identify which domains require action.

You can now bulk import and export domains from/to a CSV file to ease the management of a large number of domains.

Learn more in the documentation about importing domains and exporting domains.

We’ve just improved the design of several tables and pages in the web app.

Take a look at the before and after in the video above.