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.org
DMARC pass90.7%5,602 of 6,176 messages
Messages6,176last 30 days
Published policynonep=none
Quarantined or rejected0by receivers applying your policy
Next step: Resolve these sending sources
60 days of reports in the last 90; 6,176 messages in the last 30, 90.7% passing DMARC.
Fix sources, 41 days
- Discover
- Fix sources
- Quarantine
- Reject
- Maintain
The policy was tightened at your DNS provider on 2026-11-11: no policy to p=none. See the DNS history.
What's in the way
- 90.7% aligned (needs 95%)
- HubSpot keeps failing (29 days, 549 messages)
Today
- HubSpot: Connect the email sending domain in HubSpot (Settings > Domains & URLs) and publish the hs1/hs2._domainkey CNAMEs. For SPF, add include:_spf.hubspotemail.net. HubSpot guide
If you enforced today: 574 messages in the last 30 days would have failed, 549 of them from senders that look legitimate.
Under quarantine they go to the junk folder; under reject they are refused.
| Source | Group | Failing messages |
|---|---|---|
| HubSpot | noncompliant known | 549 |
| 203.0.113.20 | unknown | 25 |
Volume and compliance
Daily messages, passing and failing DMARC, with policy changes marked.
Table
| Day (UTC) | Messages | Passing | Failing |
|---|---|---|---|
| 2026-10-13 | 617 | 591 | 26 |
| 2026-10-14 | 180 | 155 | 25 |
| 2026-10-15 | 185 | 162 | 23 |
| 2026-10-16 | 191 | 168 | 23 |
| 2026-10-17 | 27 | 23 | 4 |
| 2026-10-18 | 27 | 22 | 5 |
| 2026-10-19 | 174 | 149 | 25 |
| 2026-10-20 | 567 | 539 | 28 |
| 2026-10-21 | 183 | 158 | 25 |
| 2026-10-22 | 179 | 156 | 23 |
| 2026-10-23 | 184 | 157 | 27 |
| 2026-10-24 | 26 | 21 | 5 |
| 2026-10-25 | 42 | 24 | 18 |
| 2026-10-26 | 186 | 165 | 21 |
| 2026-10-27 | 651 | 625 | 26 |
| 2026-10-28 | 187 | 162 | 25 |
| 2026-10-29 | 178 | 154 | 24 |
| 2026-10-30 | 200 | 173 | 27 |
| 2026-10-31 | 30 | 25 | 5 |
| 2026-11-01 | 30 | 25 | 5 |
| 2026-11-02 | 168 | 145 | 23 |
| 2026-11-03 | 627 | 602 | 25 |
| 2026-11-04 | 173 | 150 | 23 |
| 2026-11-05 | 151 | 130 | 21 |
| 2026-11-06 | 173 | 139 | 34 |
| 2026-11-07 | 27 | 23 | 4 |
| 2026-11-08 | 27 | 23 | 4 |
| 2026-11-09 | 178 | 154 | 24 |
| 2026-11-10 | 608 | 582 | 26 |
| 2026-11-11 | 0 | 0 | 0 |
| DNS change (UTC) | Record | What |
|---|---|---|
| 2026-11-11 05:09 | DMARC | DMARC record published. |
| 2026-11-11 05:09 | SPF | SPF record published. |
Sources
Who sends as this domain, by how they authenticate.
| Group | Sources | Messages | Share |
|---|---|---|---|
| CompliantPasses DMARC: SPF or DKIM aligned with your domain. | 4 | 5,602 | 90.7% |
| Known sender, failingA service the library recognises that isn't aligned yet. Each has a fix guide. | 1 | 549 | 8.9% |
| ForwardedYour mail relayed by a forwarder, mailing list or filtering gateway. Expected to fail SPF; DKIM survives when untouched. | 0 | 0 | 0% |
| Unknown or threatNot recognised and failing. Either a sender you haven't set up, or someone spoofing your domain. | 1 | 25 | 0.4% |
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,120 | 50.5% | Nov 10 |
| MicrosoftReported on 29 days | Reporting | 29 | 2,161 | 35% | Nov 10 |
| YahooReported on 29 days | Reporting | 29 | 895 | 14.5% | Nov 10 |
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 |
|---|---|---|---|
| news.example.org | 2,183 | 100% | 1 |
| promo.example.org | 317 | 100% | 1 |