Since v0.6.0, this release has mostly been about trust: fixing things that were quietly not working, and giving you ways to see for yourself that they do.

A small release after v0.7.0, mostly about how things look and one warning that shouldn't have been there.

Since v0.5.0, the Dashboard and Manage Domains tables have picked up the two things people ask for first once they're managing more than a handful of domains: sorting and filtering.

Since v0.4.0, dotMARC picked up a third DNS push provider, a genuinely new kind of insight into why mail gets rejected or quarantined instead of just that it did, and a self-hosting story that no longer assumes you already know how to wire up a reverse proxy.

Since v0.3.0, dotMARC picked up four things worth calling out: tickets that open and close themselves in HaloPSA, DNS pushes that can now fix a record instead of just refusing to touch it, one more Azure-only gap closed in MTA-STS, and a real breakdown of everything dotMARC actually knows about a domain's health.

Since v0.2.0, dotMARC picked up four things worth calling out: alerts when a domain goes quiet, a second report type alongside DMARC, a much faster way to make the DNS changes dotMARC asks for, and a way to tell us what you want next.

Since v0.1.0, dotMARC has picked up three things worth calling out: you can now see who actually owns a source IP, host MTA-STS policies without standing up your own infrastructure, and try the whole thing without installing anything.

dotMARC v0.1.0 is tagged and published. This is the first release: a self-hosted DMARC aggregate report analyzer that lets you monitor every domain you're responsible for from a single shared mailbox, instead of digging through raw XML attachments or standing up a separate tool per client.

This is where dotMARC release notes and announcements will show up. Nothing to report yet check back after the next release.