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
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
| Check | Status | What it means for the business |
|---|---|---|
| MX records | Healthy | Incoming email is handled by Google Workspace. |
| SPF | Warning | Google is authorised, but the invoicing software and website contact form are not. Their emails fail SPF. |
| DKIM | Warning | Google Workspace signs mail. The invoicing software signs with its own domain, so it doesn't count for shop.example. |
| DMARC | Critical | No DMARC record. Fake invoices using shop.example would be delivered, and the business would never know. |
| Alignment | Critical | Invoices pass neither SPF nor DKIM for shop.example. This is why they land in spam. |
| Blocklists | Healthy | The 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
- Turn on custom domain authentication in the invoicing software. It provides two DKIM records to publish. This fixes the spam problem on its own.
- 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 - Move the contact form to SMTP through the Google Workspace mailbox, so it's signed with the company's DKIM key.
- Publish DMARC in monitoring mode:
v=DMARC1; p=none; rua=mailto:[email protected] - After 3 weeks of clean reports, move to
p=quarantine, thenp=reject.
5. Effort and risk
| Fix | Time | Risk | Rollback |
|---|---|---|---|
| Invoicing DKIM | 15 minutes | Low | Remove the two records |
| New SPF record | 10 minutes | Medium: a typo affects all mail | Restore the saved old record |
| Contact form SMTP | 30 minutes | Low | Turn the plugin off |
| DMARC p=none | 5 minutes | None: nothing is blocked | Delete 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