PlainDMARC.Get started
Sample client report

The report your name goes on

This is a sample — exactly what a client of the fictional agency Harbor & Vine Digital receives every Monday, shown from both sides. Real structure, sample data.

Scenario for both views: a sample domain still at p=none, working toward p=quarantine. (A domain already at p=quarantine would be coached toward p=reject — same progression, later stage.)

What your client sees

The white-label report — verdict, pass rate, what changed, and a reassurance line. No raw fix instructions, so your client never reads an unactioned to-do list.

What you see

Your own copy adds the technical action items — exact SPF includes, DKIM fixes and policy next steps — in your weekly email and dashboard.

How to read this report

Every weekly report opens with one verdict — PASS, WARN or FAIL — so a client knows at a glance whether their email is safe. Underneath sits the pass rate: the share of mail claiming to be from the domain that authenticated correctly this week. A healthy domain trends toward 100%; a sudden dip is the first sign a new sending tool was added without authentication, or that someone is spoofing the domain.

Below that comes what changed since last week — a new sender appearing, a pass rate moving, a policy step suggested — and a plain-English next step. The client version stops there, on a reassurance line, so nobody outside the agency is handed a technical to-do list they cannot action. The agency version continues with the exact fixes: which SPF include is missing, which DKIM selector needs a key, and when the domain is ready to move from p=none to p=quarantine and then p=reject.

What the sender list tells you

Further down, each report names the senders seen that week — the mail platform, the marketing tool, the helpdesk — with whether each one passed. This is where portfolio problems surface: a client signs up for a new newsletter service, it starts sending as their domain without a DKIM key, and the pass rate dips. Because the report names the sender in plain English rather than by raw IP address, you can act on it the same afternoon instead of decoding an address block first.

The trend, not just the week

Each report also carries a short history — the last several weeks of pass rates side by side — so a client sees direction, not just a single number. A line ticking up toward 100% is the story you want to tell at a renewal; a dip that recovers shows you caught and fixed something. It turns a weekly check into a running record of the work you are doing on their behalf.

Why two views of the same week

The same underlying data is framed for two different readers. Your client wants proof the retainer bought something and reassurance that their email is protected — a branded page they can forward to their own boss. You want the action items. Splitting the two means the client never sees a scary raw failure they will email you about at 9pm, and you never have to hand-translate an XML report into something presentable.

Why plain English instead of raw XML

DMARC aggregate reports arrive as dense XML — source IPs, message counts, disposition codes, SPF and DKIM results, one row per sending source. It is precise and completely unreadable to a non-specialist. Handing a client that file, or a screenshot of a technical dashboard, does not demonstrate value; a one-line verdict with a short explanation does. That translation, done every week and branded as yours, is the entire product.

How the report reaches your client

On the Agency plans the report goes out every Monday by email from reports@plaindmarc.com carrying your display name and reply-to, plus a hosted link and a printable PDF — your logo, your sender name, no mention of PlainDMARC. Auto-send is opt-in per account, and the report emails are delivery-tracked, so a bouncing client address is caught rather than silently lost. Free and Solo plans get the same weekly verdict for their own domains; the white-label branding is what the Agency plans add.

Common questions

What is a white-label DMARC report?

A weekly DMARC summary rebranded as your agency's — your logo, sender name and reply-to — so you can forward it to a client as proof of work without exposing the tool behind it.

How often is it sent?

Once a week, the same day each week, with daily alert checks in between for anything urgent: a record disappearing, a new sender failing, or a pass rate collapsing.

Do clients see the technical fixes?

No — by design. The client view ends on a plain-English verdict and reassurance; the exact SPF, DKIM and policy fixes are in your agency view only.

Can I see a real report before signing up?

This page is one — the structure and layout are exactly what ships; only the domain and numbers are sample data. Create a free account and add a domain to get your own, populated from real reports within 1–3 days.

Clients get this by email and as a hosted link, with a printable PDF — the agency's logo, sender name and reply-to. PlainDMARC stays invisible.

Create your free accountHow it works →