Illustrative report · no real account data ← Dashboard tour
Checkup for

example.org

Published configuration looks healthy. · 0 critical, 0 warnings

A
92/100

Findings & recommended next steps

✓
DMARC enforcement published
Receivers are asked to reject mail that fails DMARC alignment. Keep reviewing new senders and actual mail reports.
✓
SPF record published
Confirm every legitimate sender and review the DNS lookup limit.
✓
DKIM DNS keys found
Verify a real message to confirm signing and alignment.
Inbound mail provider hint
Example mail provider
Checked
2026-09-22 12:00 UTC · public DNS + HTTPS
DNS configuration does not prove message signing, alignment or delivery. DKIM uses common selectors; SPF includes and MTA-STS policy content need separate review.

← check another domain

Your next step

Review the aggregate reports arriving at your report mailbox. Check messages from your newsletter, invoicing and other sending services.

Ensign does not automatically change your enforcement policy.

Check your own domain