See what a plain-English report can look like.
Illustrative example — not a real customer, live scan or completed project.
Get your free domain review →This fictional example uses example.com, a reserved example domain. All statuses and actions below are illustrative. Your report will reflect your actual scope and available evidence.
Example summary
Overall status: rollout in progress. The main mail service is configured in this example, but an invoicing sender still needs testing. Stronger enforcement has not yet been recommended.
| Check | Illustrative finding | Next step |
|---|---|---|
| SPF | Main provider included; invoicing service awaiting confirmation. | Confirm its documented sending requirements. |
| DKIM | Main provider test message passes and aligns. | Obtain an invoicing test message and verify its signing domain. |
| DMARC | Monitoring policy, with an agreed aggregate-report destination. | Review sending evidence before enforcement. |
| Unexpected source | One unfamiliar source appears in sample reports. | Ask whether this belongs to an authorised service; do not label it an attacker without evidence. |
Example action record
- Completed: recorded baseline settings and verified a main-provider test message.
- Customer action: confirm the invoicing platform and arrange a test message.
- SenderShield action: review the additional sender and document the next policy recommendation.
- Decision pending: whether the evidence supports stronger enforcement.
What your actual report should make clear
The reporting period, domain, sources checked, evidence limitations, changes made, outstanding issues, action owner and agreed next review. Findings should distinguish observed facts from assumptions and recommendations.
What this report does not prove
Passing authentication is not a guarantee against phishing, compromise or fraud. Aggregate-report coverage is incomplete and receiver-dependent. No invented protection percentage, customer results or financial savings are used in this example.
Discuss your domain
Start with your domain and the services you use. We confirm the scope before making changes.
Ask SenderShield for advice →