What’s the difference between hosted DMARC and DIY setup?

Both approaches publish the same DMARC DNS record and receive the same reports. The difference is in what happens to those reports once they arrive.

DIY setup means you configure the DMARC record yourself, send aggregate reports to an email address you control, and handle the XML yourself. The raw reports are gzipped XML files, which aren't fun to read directly. You'd need to either write a parser, use a one-off tool, or use something like our free DMARC parser to extract the useful information. It's doable, but time-consuming if you have a lot of volume or multiple domains.

Hosted DMARC services take the raw reports off your hands. They provide an email address for your rua= tag, receive reports from all the major providers, process them, and display the results in a dashboard. You see graphs, source breakdowns, authentication pass rates, and trend data without ever looking at XML.

Some hosted services also alert you when new sending sources appear, help you interpret what needs fixing, and track your progress toward p=reject. Vendors include Dmarcian, Valimail, Postmark's DMARC service, and others. They typically charge based on volume, domains, or features.

And for For most small to medium senders with one or two domains and a manageable number of sending services, DIY is fine if you check the reports regularly. Once you're at p=reject and everything is stable, report volume drops and the maintenance burden is low.

Hosted services make more sense if you have many domains, complex sending infrastructure, or you need alerts and automation rather than periodic manual review. They're also useful during the active monitoring phase when you're trying to identify all your sending sources quickly.

Either way, the first step is the same: publish a p=none record with a working rua= address. See how to start implementing DMARC for the full walkthrough, or check what your aggregate reports actually contain before deciding which route to take.