A cookie for product analytics
May we set a cookie to see which pages of DMARCLoop are used? It records the pages, never what's on them. Without it, visits are counted anonymously.
Example Ltd
example.com
DMARC pass98.7%8,170 of 8,275 messages
Messages8,275last 30 days
Published policyquarantinep=quarantine
Quarantined or rejected47by receivers applying your policy
Next step: Ready to test p=reject
89 days of reports in the last 90; 8,275 messages in the last 30, 98.7% passing DMARC.
Quarantine, 46 days
- Discover
- Fix sources
- Quarantine
- Reject
- Maintain
Today
- Publish the record for the next step (test p=reject).
v=DMARC1; p=reject; t=y; rua=mailto:rua-irwimbfn3egllmvy@dmarcloop.net
If you enforced today: 105 messages in the last 30 days would have failed, 58 of them from senders that look legitimate.
Under quarantine they go to the junk folder; under reject they are refused.
| Source | Group | Failing messages |
|---|---|---|
| 2001:db8:4::25 | forwarded | 58 |
| 203.0.113.55 | unknown | 40 |
| 203.0.113.77 | unknown | 7 |
Volume and compliance
Daily messages, passing and failing DMARC, with policy changes marked.
Table
| Day (UTC) | Messages | Passing | Failing |
|---|---|---|---|
| 2026-10-13 | 306 | 304 | 2 |
| 2026-10-14 | 305 | 303 | 2 |
| 2026-10-15 | 328 | 326 | 2 |
| 2026-10-16 | 341 | 339 | 2 |
| 2026-10-17 | 155 | 153 | 2 |
| 2026-10-18 | 155 | 153 | 2 |
| 2026-10-19 | 360 | 338 | 22 |
| 2026-10-20 | 326 | 324 | 2 |
| 2026-10-21 | 324 | 322 | 2 |
| 2026-10-22 | 294 | 292 | 2 |
| 2026-10-23 | 321 | 319 | 2 |
| 2026-10-24 | 159 | 157 | 2 |
| 2026-10-25 | 164 | 162 | 2 |
| 2026-10-26 | 375 | 373 | 2 |
| 2026-10-27 | 310 | 308 | 2 |
| 2026-10-28 | 301 | 299 | 2 |
| 2026-10-29 | 336 | 334 | 2 |
| 2026-10-30 | 330 | 328 | 2 |
| 2026-10-31 | 163 | 161 | 2 |
| 2026-11-01 | 161 | 159 | 2 |
| 2026-11-02 | 354 | 332 | 22 |
| 2026-11-03 | 325 | 323 | 2 |
| 2026-11-04 | 338 | 336 | 2 |
| 2026-11-05 | 325 | 323 | 2 |
| 2026-11-06 | 307 | 305 | 2 |
| 2026-11-07 | 157 | 148 | 9 |
| 2026-11-08 | 149 | 147 | 2 |
| 2026-11-09 | 423 | 421 | 2 |
| 2026-11-10 | 383 | 381 | 2 |
| 2026-11-11 | 0 | 0 | 0 |
| DNS change (UTC) | Record | What |
|---|---|---|
| 2026-10-30 05:09 | SPF | SPF record changed. |
| 2026-11-11 05:09 | SPF | SPF record published. |
| 2026-11-11 05:09 | DMARC | DMARC record published. |
| 2026-11-11 05:09 | DMARC | DMARC record changed. |
| 2026-11-11 05:09 | DMARC | DMARC record changed. |
Sources
Who sends as this domain, by how they authenticate.
| Group | Sources | Messages | Share |
|---|---|---|---|
| CompliantPasses DMARC: SPF or DKIM aligned with your domain. | 7 | 8,170 | 98.7% |
| Known sender, failingA service the library recognises that isn't aligned yet. Each has a fix guide. | 0 | 0 | 0% |
| ForwardedYour mail relayed by a forwarder, mailing list or filtering gateway. Expected to fail SPF; DKIM survives when untouched. | 1 | 58 | 0.7% |
| Unknown or threatNot recognised and failing. Either a sender you haven't set up, or someone spoofing your domain. | 2 | 47 | 0.6% |
Who's reporting
The receivers sending reports on this domain: where your mail arrives, not who sends it. Senders are under Sources.
| Receiver | Status | Reports | Messages | Share | Last report |
|---|---|---|---|---|---|
| GoogleReported on 29 days | Reporting | 29 | 3,966 | 47.9% | Nov 10 |
| MicrosoftReported on 29 days | Reporting | 29 | 2,826 | 34.2% | Nov 10 |
| YahooReported on 29 days | Reporting | 29 | 1,204 | 14.5% | Nov 10 |
| FastmailReported on 25 days | Gone quiet | 25 | 279 | 3.4% | Nov 6 |
Subdomains seen
Mail with these names in its From header, covered by this domain's policy (or its sp=).
| Header From | Messages | DMARC pass | Sources |
|---|---|---|---|
| updates.example.com | 1,498 | 100% | 1 |