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
TLS reporting
10.3K TLS sessions reported, 70 failed (99.3% succeeded).
| Policy | Reporter | Reports | Succeeded | Failed | Last |
|---|---|---|---|---|---|
| sts | 30 | 6,120 | 40 | Nov 10 | |
| sts | Microsoft | 30 | 4,080 | 30 | Nov 10 |
Failures
| Result | Your MX | Sessions | Sending servers | Last |
|---|---|---|---|---|
| certificate-host-mismatch | mx-backup.example.com | 70 | 2 | Nov 9 |
Failures on 5 days, most recently Nov 9.
MTA-STS
Checked 2026-11-11 05:09 UTC.
Mode testing, max_age 604800, MX aspmx.l.google.com, *.aspmx.l.google.com.
The policy doesn't cover mx-backup.example.com: mail to them fails under enforce.
BIMI
Checked 2026-11-11 05:09 UTC.
No BIMI record at default._bimi. Set one up under DNS records once the domain is at p=quarantine or p=reject.
DKIM keys
Selectors from your reports, the ones hosted here and common ones found in your DNS, looked up daily. Keys under 1024 bits are rejected by receivers; use 2048, and rotate a key after 365 days.
| Selector | Key | Age | Found | Notes |
|---|---|---|---|---|
| fm1 | Revoked | – | Found by lookup | – |
| fm2 | Revoked | – | Found by lookup | – |
| RSA 2048 | 0 d | Hosted here | – | |
| pm | RSA 2048 | 0 d | Seen in reports | – |
| s1 | RSA 2048 | 0 d | Hosted here | – |
| selector1 | Revoked | – | Found by lookup | – |
| selector2 | Revoked | – | Found by lookup | – |
| xero | RSA 1024 | 0 d | Seen in reports | A 1024-bit RSA key: use 2048 bits when you next rotate it. |
| zoho | Revoked | – | Found by lookup | – |
Failure reports
Individual messages that failed DMARC, as receivers reported them. They can hold personal data, so we keep only the sending details (no subjects, recipients or content), delete them after a short retention, and record every view in the audit log.