This is what lands in your client's inbox on the 1st.

The real template, rendered server-side from the same React Email component the worker sends. Nothing on this page is a mockup: the numbers come from the example dataset shipped with the report package, and the branding is the sample agency's own logo, accent colour and Reply-To address.

Subject: November 2026 domain & security protection report: baxtercreek.com

Rendered from packages/report. Reply-To: hello@northwindstudio.com. No DomainCareHQ branding on client mail.

Why the format looks like this

Clients do not read dashboards, and a link is a hurdle. The report is the email body, so it survives on a phone, in a preview pane, and in a forwarded internal thread. The PDF version is attached for the client who files things.

Every number is computed from real checks. The checks-executed count is the actual number of DNS, TLS and RDAP queries run for that domain during the period, not a marketing constant.

Status badge
Computed from the worst finding in the period: protected, attention, or at risk.
Certificate line
Days remaining plus chain validity, with the issuer named when it is not obvious.
Email authentication
SPF lookup count against the RFC 7208 ceiling, and the DMARC policy spelled out.
Registration
Expiry countdown from RDAP, so a lapsed domain is visible months before it lapses.
Value summary
One paragraph in plain English: what was watched, what was caught, what it means.
Agency footer
Your Reply-To address, your footer text, your accent colour on the header rule.

Like this? Automate this monthly for all 50 clients for $39/mo.

Import a CSV, attach client emails, and the 1st takes care of itself. Your logo, your accent colour, your Reply-To, no vendor badge.