See what p=reject would do. Before you turn it on.
We replay the last 30 days of your DMARC reports under the stricter policy, so you see which messages receivers would be asked to quarantine or reject before you change anything. After the change, we watch your reports for 14 days.
Included: Every plan. Compare plans
Enforcement preview
What a stricter policy would have asked receivers to do with the last 30 days of mail sent as kanbello.xyz, replayed from their own reports.
Next step
Reject
p=quarantine, 41 days at this policy
Unidentified sources
212messages
From sources we can't match to a sender
Identified senders
0
Every identified sender aligns
Forwarded
38messages
Receivers reported forwarding or a mailing list
Start here
Check 212 messages from sources we can't name
Every identified sender aligned. Reject would also ask receivers to reject 212 messages from sources that match no sender we know. If one of them is a tool you use, identify it on the Senders page before you tighten.
Why first: reports can't tell a forgotten tool from a forgery.
What the replay found
- Unidentified sourcesMatch no sender we know212 messages
- Forwarded or mailing listAs receivers reported it38 messages
- Identified sendersFailing alignmentNone
Messages reject would have asked receivers to act on, last 30 days.
Messages reject would have asked receivers to act on, by dayHover a day for its numbers
- Unidentified sources
- Identified senders
- Forwarded or mailing list
How it works. Nothing to set up.
It reads the reports you already have. Open it from a domain's DMARC page.
- Read the replayIdentified senders, unidentified sources and forwarded mail, each counted on its own.
- Make the changeOne click on Cloudflare or AWS Route 53. On any other DNS host, copy the new record.
- We watch for 14 daysIf receivers report quarantining or rejecting mail from your identified senders, you get an alert with a rollback.
What it will not do. You make every change.
- Change your DNS without a click. The rollback is offered in the alert. It never runs on its own.
- Predict what receivers will do. A policy is a request, and each receiver decides. The replay counts what it would have asked for.
- Treat forwarded mail as a sender problem. Forwarding and mailing lists get their own count, because receivers handle them case by case.
At a glance
- Included
- Every plan
- Replays
- The last 30 days of your DMARC reports
- One click on
Cloudflare
AWS Route 53
- Other DNS hosts
- The new record, ready to copy
- Watches
- The 14 days after the change
Start with one domain. See it with your own data.
Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.