Exporting your data to CSV
Your DMARC data shouldn't be locked in our dashboard. The Export button in the top bar downloads whatever you're currently looking at as a CSV file — ready for a spreadsheet, a client report or an audit trail. There are two exports, one per view, and this page documents their exact columns so you can build on them.
Overview export — one row per domain
From the all-domains overview, Export downloads dmarcmetric-domains.csv: a per-domain summary of the domains on screen (the workspace you picked, or all you can see) for the selected reporting window.
| Column | Contents |
|---|---|
domain | The domain name. |
status | verified once a DMARC report for the domain has reached us, awaiting data when its DMARC record is confirmed correct but no report has arrived yet, otherwise pending. |
messages | Total messages reported for the domain in the window. |
compliance | DMARC pass rate to one decimal, e.g. 98.4% — or — when the domain has no messages. |
threats | Count of threat sources (mail failing both SPF and DKIM). |
sources | Count of distinct sending sources. |
last_report | Timestamp of the most recent report received, blank if none yet. |
This is the export to schedule your own reporting around: one file, one row per domain, the same KPIs the overview cards show.
Domain export — one row per source
From a domain's detail view, Export downloads a per-source file named after the domain — dmarcmetric-example.com-sources.csv — covering every sending source in the window.
| Column | Contents |
|---|---|
source | The detected provider name (Microsoft 365, Postmark, …) or Unknown. |
ip | The sending IP address. |
country | Two-letter country code from GeoIP, blank when the IP couldn't be placed. |
messages | Message count for this source. |
spf | The DMARC-evaluated SPF result for the source (pass / fail). |
dkim | The DMARC-evaluated DKIM result for the source (pass / fail). |
status | threat when the source fails both SPF and DKIM, otherwise ok. |
Note that spf and dkim are the alignment-aware results DMARC actually evaluated — the same verdicts the grouped sources table displays as tags, not raw authentication outcomes. A row is one source, not one group: the provider grouping is flattened so the file works in pivot tables.
How the export behaves
Three properties define what you get:
- It's generated in your browser. The file is built client-side from the data the dashboard has already loaded — no server round-trip, no export queue, no email-me-a-link. Click, and the file is in your downloads.
- It's scoped to the current view and window. Export gives you exactly what's on screen: the overview export while you're on the overview, the source export while you're in a domain, always for the reporting window currently selected. Want a year of data? Switch to Last 12 months first, then export. 90-day and 12-month windows are available on Starter and above; Free includes 30 days — see pricing.
- It's spreadsheet-friendly. Files are UTF-8 with a byte-order mark (so Excel opens domain names and country data correctly rather than mangling them), values containing commas or quotes are properly quoted, and headers are lowercase machine-readable names.
What people build with it
The CSVs are deliberately plain so they compose with whatever you already use:
- Client reporting — agencies export the domain summary monthly and paste it into their own report template.
- Audits and compliance evidence — a dated per-source export is a clean record of who was sending as your domain and how it authenticated, at a point in time.
- Trend tracking outside the app — exporting on a schedule and diffing
sourcesandcomplianceper domain catches drift with nothing but a spreadsheet. - Investigation notes — the per-source export pins down IPs and countries for a spoofing incident before the window rolls past it.
The export reflects what the dashboard shows, no more and no less — if a number looks unexpected in the file, the place to interrogate it is the corresponding dashboard view, with the same window selected.