Improved date filtering accuracy with reporting day

We have improved how DMARCwise assigns DMARC and TLS reports to calendar days when filtering by date.

Reports can cover any time interval and don’t include timezone information, making it non-trivial to determine which day a report actually belongs to. Previously, DMARCwise used a ±12-hour padding around the filter range to handle this ambiguity, which could produce imprecise results.

DMARCwise now attributes each report to its reporting day: the UTC date of the midpoint between the report’s start and end time. This timestamp is more reliably representative of the reporter’s intended reporting date, regardless of their report interval convention.

Since DMARC reports contain no ground truth about the reporter’s intent, we can only estimate accuracy based on timezone data, and by that measure, more than 99% of reports are attributed to the expected day.

You can learn more about how this works in the reporting day documentation.