You're looking at a demo with sample data. Look around: nothing here can be changed.Start free with your own domain

Example Ltd

example.net

DMARC pass0%0 of 125 messages
Messages125last 30 days
Published policyrejectp=reject
Quarantined or rejected125by receivers applying your policy

Next step: Fully enforcing

45 days of reports in the last 90; 125 messages in the last 30, 0% passing DMARC.

Maintain, 44 days
  1. Discover
  2. Fix sources
  3. Quarantine
  4. Reject
  5. Maintain
Assessed 2026-11-11 05:09 UTC. The help centre explains each check.

Volume and compliance

Daily messages, passing and failing DMARC, with policy changes marked.

01020Oct 13: 2 messages, 0 passing, 2 failingOct 13Oct 14: 2 messages, 0 passing, 2 failingOct 15: 9 messages, 0 passing, 9 failingOct 16: 2 messages, 0 passing, 2 failingOct 17: 2 messages, 0 passing, 2 failingOct 18: 9 messages, 0 passing, 9 failingOct 19: 2 messages, 0 passing, 2 failingOct 20: 2 messages, 0 passing, 2 failingOct 21: 9 messages, 0 passing, 9 failingOct 22: 2 messages, 0 passing, 2 failingOct 23: 2 messages, 0 passing, 2 failingOct 24: 9 messages, 0 passing, 9 failingOct 25: 2 messages, 0 passing, 2 failingOct 26: 2 messages, 0 passing, 2 failingOct 27: 11 messages, 0 passing, 11 failingOct 27Oct 28: 2 messages, 0 passing, 2 failingOct 29: 2 messages, 0 passing, 2 failingOct 30: 9 messages, 0 passing, 9 failingOct 31: 2 messages, 0 passing, 2 failingNov 1: 2 messages, 0 passing, 2 failingNov 2: 10 messages, 0 passing, 10 failingNov 3: 2 messages, 0 passing, 2 failingNov 4: 2 messages, 0 passing, 2 failingNov 5: 9 messages, 0 passing, 9 failingNov 6: 2 messages, 0 passing, 2 failingNov 7: 2 messages, 0 passing, 2 failingNov 8: 10 messages, 0 passing, 10 failingNov 9: 2 messages, 0 passing, 2 failingNov 10: 2 messages, 0 passing, 2 failingNov 11: 0 messages, 0 passing, 0 failingNov 11 Nov 11: SPF: SPF record published. DMARC: DMARC record published.
Table
Day (UTC)MessagesPassingFailing
2026-10-13202
2026-10-14202
2026-10-15909
2026-10-16202
2026-10-17202
2026-10-18909
2026-10-19202
2026-10-20202
2026-10-21909
2026-10-22202
2026-10-23202
2026-10-24909
2026-10-25202
2026-10-26202
2026-10-2711011
2026-10-28202
2026-10-29202
2026-10-30909
2026-10-31202
2026-11-01202
2026-11-0210010
2026-11-03202
2026-11-04202
2026-11-05909
2026-11-06202
2026-11-07202
2026-11-0810010
2026-11-09202
2026-11-10202
2026-11-11000
DNS change (UTC)RecordWhat
2026-11-11 05:09SPFSPF record published.
2026-11-11 05:09DMARCDMARC record published.

Sources

Who sends as this domain, by how they authenticate.

All 2 sources
GroupSourcesMessagesShare
CompliantPasses DMARC: SPF or DKIM aligned with your domain.000%
Known sender, failingA service the library recognises that isn't aligned yet. Each has a fix guide.000%
ForwardedYour mail relayed by a forwarder, mailing list or filtering gateway. Expected to fail SPF; DKIM survives when untouched.000%
Unknown or threatNot recognised and failing. Either a sender you haven't set up, or someone spoofing your domain.2125100%

Who's reporting

The receivers sending reports on this domain: where your mail arrives, not who sends it. Senders are under Sources.

ReceiverStatusReportsMessagesShareLast report
GoogleReported on 29 daysReporting296148.8%Nov 10
MicrosoftReported on 29 daysReporting295140.8%Nov 10
YahooReported on 9 daysReporting91310.4%Nov 8