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
My notifications
Your own choices for Example Ltd. Changing them changes nothing for anyone else.
Digest
Scorecard: the numbers, then every domain with its period, pass rate and stage.
Getting started emails
A welcome, reminders while a domain's records aren't in place, its first report, and when it reaches p=reject. Each is sent once.
On
Alerts
| DMARC record missingA DMARC record that was published is no longer there. | On | |
| DMARC record invalidThe DMARC record no longer parses, so receivers ignore it. | On | |
| Reports no longer sent to usThe DMARC record is present but no longer sends reports to us. | On | |
| Hosted DNS delegation brokenA CNAME or include that delegates a record to us no longer points at us. | On | |
| DNS record changedA record you manage yourself no longer matches what it should be. | On | |
| Ready to tighten policyThe adviser thinks a domain can safely move to a stricter policy. | On | |
| Policy step blockedA domain has enough evidence for its next step, but a sending source keeps failing. | On | |
| Mail being blockedAn enforcing domain has legitimate-looking mail failing DMARC. | On | |
| Policy loosenedThe published DMARC policy was loosened. | On | |
| Policy tightened in DNSThe DMARC policy was made stricter by a change at your DNS provider, not one published here. Usually seen within the hour. | On | |
| No reports in 7 daysA domain that was receiving DMARC reports has had none for seven days. The alert says whether its DMARC record still sends reports to us; if it does, the domain most likely sent little or no mail. | On | |
| New sending sourceA source not seen before sent meaningful volume as the domain. | On | |
| Compliance droppedThe share of mail passing DMARC fell by five points or more, week on week. | On | |
| Volume spikeA day's mail was more than three times the usual volume. | Off | |
| SPF lookup limit exceededThe SPF record needs more than ten DNS lookups, so receivers treat it as failing. | On | |
| SPF record invalidThe SPF record doesn't parse, or the domain publishes more than one. | On | |
| Hosted SPF not updatingThe flattened SPF record we serve couldn't be rebuilt three times in a row. | On | |
| DKIM key weakA DKIM selector publishes an RSA key under 1024 bits, which receivers reject. | On | |
| MTA-STS policy brokenThe MTA-STS policy can't be fetched, doesn't parse, or doesn't cover the MX hosts. | On | |
| BIMI brokenThe BIMI logo or its mark certificate fails a check, or the certificate expires within 30 days. | On | |
| TLS failuresMore than 5% of the TLS sessions senders reported for the domain failed over the last seven days (with at least 50 sessions). | On | |
| Alert channel failingA Slack, Teams, webhook or PSA channel has rejected five alerts in a row. | On |