Product updates
What's new in DMARCHub v0.58: why mail fails, and AI tools in beta
By DMARCHub Team5 min read
On this page
Over the last few releases we have concentrated on one question that every DMARCHub customer asks sooner or later: why is some of my mail failing DMARC, and what should I do about it? This post covers the new Why mail is failing section on each domain, two optional AI tools that are now in beta, and a handful of smaller improvements to alerts and notifications.
Nothing here changes your DNS records or your DMARC policy, and none of it asks anything of you unless you choose to use it.
Why mail is failing, explained on each domain
Aggregate reports tell you which messages failed, but not why. DMARCHub now does that first pass for you.
Open any domain and go to its Messages tab. At the top you will find Why mail is failing. It is folded away by default, with a one-line summary of how many likely causes we found and how many failing messages they cover over the last 30 days, or over the period your plan shows if that is shorter. Open it and the failing mail is grouped by likely cause, busiest first. The causes include:
- Mail forwarded or sent through a mailing list
- Sender is not listed in your SPF record
- Sending service authenticates with its own domain
- DKIM signature for your domain failed
Each explanation opens on its own and gives you the steps to take, a Show evidence table listing the busiest sources behind it, and a line saying how many receivers reported it and how many of those we could confirm as genuine.
Where a sender looks like someone else using your domain name, the explanation says so plainly and tells you that no change is needed, because a stricter DMARC policy will block that mail. We only suggest adding a sender to your records when the receivers reporting it are confirmed as genuine.
For more background, our guide to why DMARC fails walks through each cause in detail, and the failure explanations feature page shows how the section works. If you are newer to the subject, DMARC vs DKIM vs SPF and how to read a DMARC report are good places to start.
AI tools in beta, with limited functionality for now
We are also trying two optional tools that use AI to make the same information easier to act on. Both are in beta and have limited functionality for now. They are available on selected plans as we switch them on, so you may not see them yet.
Explain in plain English
Inside the expanded Why mail is failing section there is an Explain in plain English button. It writes a short summary of the findings for that domain in everyday language. The summary is labelled as written by AI, and the explanations and steps below it are unchanged.
Summaries are kept for up to 7 days, so asking again while the findings are unchanged shows the same summary, and there are limits on how often they can be requested.
Ask about this domain
We are also starting to roll out a domain assistant, Ask about this domain. Click the button at the top right of a domain's page and it opens in a panel on the right-hand side, which you can minimise or close and which stays with you as you move between that domain's tabs. Ask in plain English about things like which services send email as the domain, whether your DMARC policy looks ready to move to quarantine, or how your pass rate has changed over the last 90 days. Where an answer draws on the domain's data, it lists what it used.
The assistant has a deliberately narrow scope:
- It answers only about the domain you opened it on, about email authentication (DMARC, SPF, DKIM, BIMI, MTA-STS and TLS reporting) and about using DMARCHub. For another domain, open that domain and use the assistant there.
- It can only read. It cannot change records, settings or anything else. Where a change is needed, it tells you where in DMARCHub you can make it yourself.
- Your conversation is not stored by us. It lives only in your browser tab, and Clear conversation removes it.
What these tools send, and what they never send
Both tools are processed by the Microsoft Azure OpenAI Service within the European Union. What we send is not shared with OpenAI and is not used by Microsoft to train models or improve its products. Microsoft may keep content flagged by its automated abuse checks, within the European Union, for review by authorised Microsoft staff in the European Economic Area.
A summary is only written when someone clicks the button. We send your domain name, the categories of likely cause, message counts, the names of well-known email services from our own list, and our own explanatory text. For the assistant we also send your question, a few earlier messages from the same conversation, and read-only data about that one domain, such as volumes, pass rates, the status of your DNS records as we last checked them and your settings in DMARCHub.
From your domain's data we never send IP addresses, the names of sending servers, the raw contents of your reports, message content or reporter details. Please do not type personal information into the assistant. Our privacy notice sets out the full detail.
Answers can be wrong
Summaries and answers can be wrong. Treat them as a starting point and check them against the explanations and evidence on the domain before you change any DNS records. If an answer looks wrong or unhelpful, please tell us through Feedback in the left-hand menu. That shapes what we switch on next.
Smaller improvements
- DNS change alerts no longer raise false alarms for websites behind Cloudflare. A genuine change, such as switching Cloudflare on or off or moving to a different host, is still reported.
- Opening a notification now marks it as read. The Mark read button is still there.
- Failure reports are now matched to the right sending domain even when the sender address is written in an unusual but valid way.
These build on the previous release, which brought new sending IP alerts, a steadier MTA-STS and a two-step domain setup.
Where to start
| Change | Where it lives | What it asks of you |
|---|---|---|
| Why mail is failing | Each domain's Messages tab | Nothing. Open it when you want to understand failing mail. |
| Explain in plain English (beta) | Inside Why mail is failing, on selected plans | Nothing. Click it if you want a plain-language summary. |
| Ask about this domain (beta) | A button at the top right of each domain's page, on selected plans | Nothing. Check answers before acting on them. |
| Fewer false DNS change alerts | Your inbox and notifications | Nothing. |
Sign in to DMARCHub to try them. If anything does not behave the way this post describes, email hello@dmarchub.io or use Feedback and we will look at it.