Dashboard
A live overview of DMARC aggregate reports for example.com.
Messages
4,812
▲ 312 vs previous 14 d
DMARC pass
86%
4,140 messages
DMARC fail
14%
672 messages
Sources
7
unique sending IPs
Reports
98
processed
Over time
Stacked per day: messages that passed and failed over the last 14 days. Hover over or click a day for detail.
PassedFailed
Sending sources
Click a column heading to sort, or an IP for its detail page.
| Country | Source IP | Service / hostname | Header-from | Status | Messages | SPF | DKIM | DMARC |
|---|
One sender needs your attention
45.33.12.99 (Russia) is sending mail as example.com that fails SPF/DKIM, and therefore fails DMARC. Take a look at this source under Senders.
Senders
Per source: status, owner and note. The road to safe enforcement starts here.
| Country | Source IP | Service | Volume | Fails | Status | Owner | Vendor | Note |
|---|
Geography
Where mail sent as example.com comes from, worldwide.
Fully passing (≥95%) Mixed (50–95%) Mostly failing (<50%)
Sending organisations (ASN)
Who hosts the sending servers? Clusters usually point to a single service.
Vendors
Services that mail on behalf of your domain, recognised automatically.
| Service | Recognised through | Sources | Messages |
|---|
Alerts
An automatic notification when a new sender appears or volumes look suspicious.
New, unauthorised sender today
45.33.12.99 (Russia, Vultr) started sending mail as example.com 14 days ago and consistently fails SPF/DKIM/DMARC. Our advice: mark it as "abuse" and start an abuse case file.
Reporting gap detected 3 days ago
No new reports received from cdn-mail.io (Singapore) between 20 and 22 July. Back to normal from 23 July.
Domains
Add main domains and subdomains, and manage their DMARC monitoring.
For every domain, add a
TXT record on _dmarc with the following value:
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:rua+demo@reports.duzmarc.nl; ruf=mailto:rua+demo@reports.duzmarc.nl; fo=1
Add a domain
Add a main domain. Subdomains underneath it are unlimited and do not count towards your subscription.
Domains
| Domain | Type | Policy | Messages | Pass % | Sources | Last report |
|---|
Reports
The insights that matter, grouped by subject.
Not ready for p=reject yet 1 to review
One failing source is still open and needs reviewing before reject is safe (45.33.12.99, Russia). Have a look at the simulator under Reports.
The numbers
Messages4,812+312 vs previous
DMARC pass86%▲ 2 pt
Unique sources7
New sources10 failing
Alerts resolved2
Signals this period
2 alert(s) this period, no DNS changes and no blacklist hits.
New sources
Seen for the first time this period. Do review the ones you do not recognise.
| Country | Source IP | Service | Status | Messages | Fails |
|---|
Forensic reports
RUF reports about individual messages that failed DMARC. Note that not every provider sends RUF reports; it is optional in the DMARC standard.
| Time | Source IP | From (domain) | To (domain) | Fails on | Reported by |
|---|
TLS-RPT
TLS transport reports (RFC 8460): failures in secure email delivery to your domain.
Successful sessions
4,932
Failed sessions
9
Failure rate
0.2%
Reporters
3
Report overview
One line per TLS-RPT report received from a reporting organisation.
| Reporter | Domain | Period | Successful | Failed | Status |
|---|
Audit log
An overview of actions carried out by administrators. Log entries are kept for 30 days.
| Time | User | Action | Details | Domain |
|---|
Settings
Manage your account, subscription and team.
Organisation
Subscription
Main domains2 / 5
Team members2 / 10
History365 d
Security
Two-step verification (MFA)An extra layer of security for your account.
Team
| Name | Role | |
|---|---|---|
| Test administrator | admin@example.com | administrator |
| Colleague | colleague@example.com | member |
Sender
Abuse case file
· evidence and report, ready to send.