← Back to reports

Sample reports

Report anatomy examples.

Two sample reports showing what a recipient actually sees: the summary, findings, evidence and next actions.

Sample free report

Free Domain Health Report

A one-domain report showing platform-led threat exposure, DNS defense gaps and first remediation priorities.

Domain

example-business.co.uk

Report type

Free single-domain health report

Primary exposure

Microsoft 365 and payment-platform lures relevant to visible platform footprint

DNS defense

DMARC present but not enforcing; SPF and DKIM require alignment review

First action

Harden email authentication and review stale DNS records

Executive summary

The domain shows a visible Microsoft 365 mail footprint, public helpdesk and payment-related platform signals. External suspicious infrastructure is appearing around several of those platform lures. DNS defenses are partially configured but not yet strong enough to give a high-confidence anti-spoofing posture.

Threat exposure is mainly platform-led, not direct brand impersonation
DMARC policy is not enforcing
Several subdomains expose third-party platform usage
First remediation should focus on email authentication and stale DNS review

Platform-led threat exposure

Detected platform footprint makes Microsoft 365, Stripe and Zendesk-themed lures relevant to this organization. The report highlights suspicious infrastructure using login, verify, billing and support language around those platforms.

Detected platform: Microsoft 365
Detected platform: payment workflow
Detected platform: support/helpdesk
Recommended action: move high-confidence platform lures into alerts

DNS and email defense analysis

The public DNS records show basic mail authentication is present but not hardened. The domain should move gradually from monitoring to enforcement after SPF and DKIM alignment is verified.

DMARC: p=none, not enforcing
SPF: present, review includes and lookup depth
DKIM: provider keys visible, alignment check required
MTA-STS and BIMI not detected

Remediation priorities

The first fixes are practical: verify mail authentication alignment, move DMARC towards enforcement, review stale CNAMEs and monitor platform-led impersonation around visible vendors.

Priority 1: verify SPF/DKIM alignment
Priority 2: move DMARC towards quarantine/reject
Priority 3: review stale CNAMEs and unused subdomains
Priority 4: enable alerts for detected platform lures

Sample paid report

Cross-Estate Domain Risk Report

A paid report showing individual domain findings, repeated weaknesses and systemic risk across the estate an organization owns.

Open the full sample report (the Acme Group render) →

Estate

42 domains across brands, subsidiaries and legacy properties

Report type

Cross-Estate Domain Risk Report

Systemic issue

DMARC non-enforcement repeated across 61% of active domains

Operational risk

Inconsistent mail and DNS ownership across business units

Program priority

Standardize email authentication and review exposed platform dependencies

Portfolio summary

The organization owns multiple active, parked and legacy domains. Individual findings matter, but the bigger issue is inconsistency: the same DNS and email weaknesses appear repeatedly across brands and subsidiaries.

42 domains reviewed
18 active business domains
11 parked or defensive domains
13 legacy or unclear ownership domains

Systemic risk patterns

Paid reporting groups repeated issues so leadership can see which weaknesses are isolated and which require a program-level fix.

DMARC monitoring-only policy appears across 61% of active domains
SPF records vary by business unit
Several domains expose old marketing or helpdesk CNAMEs
Supplier and platform footprints are inconsistent across subsidiaries

Domain ranking

The report ranks domains by exposure, importance and remediation urgency so teams can avoid treating every domain as equal.

High: customer-facing login and payment domains
Medium: active brand and campaign domains
Low: parked defensive registrations
Review: legacy domains with unclear ownership

Remediation program

The output is designed to support an organized remediation program: standardize controls, assign owners, remove stale records and move high-risk domains into monitoring.

Create a domain ownership register
Set a standard DMARC progression plan
Review CNAMEs and third-party service ownership
Monitor priority brands, platforms and suppliers