Sample email health audit report

This is what you receive with the Email health audit and Spam folder rescue. The business and domain are fictional.

Sample report. Fictional business and domain.

The example uses shop.example, a domain name reserved for documentation, so it can't belong to a real business. A real report covers your actual domain, every service that sends email for you, and a real message's headers.

1. Summary

Spice Garden Traders (fictional), shop.example. Audit date: 18 November 2026.
Customers report that invoices from [email protected] go to spam in Gmail. The main cause is that the invoicing software sends as shop.example without being authorised, so those emails fail DMARC. A second, separate risk: anyone can currently send fake invoices in the company's name.

2. Findings

CheckStatusWhat it means for the business
MX recordsHealthyIncoming email is handled by Google Workspace.
SPFWarningGoogle is authorised, but the invoicing software and website contact form are not. Their emails fail SPF.
DKIMWarningGoogle Workspace signs mail. The invoicing software signs with its own domain, so it doesn't count for shop.example.
DMARCCriticalNo DMARC record. Fake invoices using shop.example would be delivered, and the business would never know.
AlignmentCriticalInvoices pass neither SPF nor DKIM for shop.example. This is why they land in spam.
BlocklistsHealthyThe sending servers are not on the major blocklists checked.

3. Evidence from a real message

From the headers of an invoice email sent to a Gmail test account:

Authentication-Results: mx.google.com;
  dkim=pass [email protected];
  spf=pass smtp.mailfrom=bounce.invoicing-app.example;
  dmarc=fail (p=NONE) header.from=shop.example

SPF and DKIM both pass, but for the invoicing app's own domain, not shop.example. DMARC therefore fails, and Gmail treats the message as suspicious.

4. Fixes, in order

  1. Turn on custom domain authentication in the invoicing software. It provides two DKIM records to publish. This fixes the spam problem on its own.
  2. Replace the SPF record with one that also covers the website's mail server:
    v=spf1 include:_spf.google.com include:spf.invoicing-app.example ~all
  3. Move the contact form to SMTP through the Google Workspace mailbox, so it's signed with the company's DKIM key.
  4. Publish DMARC in monitoring mode:
    v=DMARC1; p=none; rua=mailto:[email protected]
  5. After 3 weeks of clean reports, move to p=quarantine, then p=reject.

5. Effort and risk

FixTimeRiskRollback
Invoicing DKIM15 minutesLowRemove the two records
New SPF record10 minutesMedium: a typo affects all mailRestore the saved old record
Contact form SMTP30 minutesLowTurn the plugin off
DMARC p=none5 minutesNone: nothing is blockedDelete the record

6. Next steps

With the Email health audit, you receive this report and apply the fixes yourself. With Authentication setup or Spam folder rescue, I apply them, test with Gmail and Outlook, and add a section showing the passing results.

Get a report for your domain

Start with the free check. If it's worth going further, the full audit costs LKR 5,000 / $20.

Ask for a free check
Check domain WhatsApp