Features
DMARC monitoring that does the heavy lifting.
DMARC is a fiddly protocol with an even fiddlier set of reports coming back at you. DMARCHub turns the reports into a clear picture, explains why mail is failing, and tells you when something needs attention.
Capabilities
Nine things DMARCHub handles for you.
A DMARC report analyser that turns XML into something you can read
DMARC aggregate (RUA) reports arrive every day from Google, Microsoft, Yahoo, and dozens of smaller mail receivers. We parse them, normalise the data, and give you a clean view of who's sending mail as your domain, what's passing alignment, and what isn't, with each sending source labelled by the email service it belongs to where we recognise it. When a source we have not seen before starts sending as your domain, we email you the details, at most once a day per domain, leaving out your own mail provider and the services you already use.
How to read a DMARC report →Forensic reports, privacy-scrubbed automatically
When a receiver sends us a DMARC failure report about a single message, we keep the technical headers and source IP and throw away the body, subject, and recipient details. You get the information you need to investigate without taking on a pile of customer email content.
Why mail is failing, explained
Each domain shows why mail is failing DMARC and what to do about it. Failing mail is grouped by likely cause, such as a service that signs with its own domain, a sender missing from SPF, or forwarding, and each explanation says how sure we are, with the evidence behind it. We only suggest approving a sending service when receivers we have confirmed as genuine back it up. Where it could be someone else using your domain, we say so.
How DMARC failure explanations work →Plain-English summaries, if you want them
On eligible plans, one click asks for a short plain-English summary of those findings, written by AI from the cause categories and counts alone. It is optional, it runs only when you ask, it never sees IP addresses or message content, and it is processed within the EU. Microsoft, which runs the model for us, does not use it to train models.
What the AI summary sees →Domain assistant (optional, eligible plans)
Ask questions about one domain in plain English, such as why some mail is failing or which services send as it. The assistant reads your domain's data in DMARCHub, cannot change anything, and is processed by Microsoft Azure OpenAI in the EU. The data it reads about your domain never includes IP addresses or message content, and Microsoft does not use what it sends to train models.
How the AI features handle your data →Managed SPF - one record, and we keep it under ten lookups
SPF gives a receiving server ten DNS lookups and no more, and four or five email services is often enough to blow past it. Point your domain at us with a single TXT record and we flatten your senders down to plain addresses, keep them current as your providers change theirs, and never shrink your record on the strength of a lookup we could not confirm.
How SPF, DKIM and DMARC fit together →Hosted DMARC, MTA-STS and TLS reporting
We host your DMARC policy, so changing it is a setting rather than a DNS edit. MTA-STS lets receivers encrypt mail to you over verified TLS: the portal checks your mail servers, you pick a mode, you publish two CNAMEs and we serve the policy, usually live within the hour. The cache duration starts at a day and steps up to 7 then 28 days as the policy proves itself, so an early mistake clears quickly. TLS reports (TLS-RPT) then show you when other servers could not deliver to you securely.
Choosing a DMARC policy: none, quarantine or reject →DNS drift alerts
If the DNS behind your email changes externally - someone in your team edits a record, a new vendor adds one, an attacker plants one - we notice, usually within ten minutes, and email you. That covers your DMARC record, your nameservers, your mail servers, your SPF and DKIM records and whether DNSSEC is switched on. You see what changed and decide whether it was intentional.
DMARC monitoring built for UK businesses
Your data is stored in the UK (Azure UK South), encrypted at rest and in transit. Sign-in is through Microsoft Entra or Google Workspace, so we never see your password. Our infrastructure follows Cyber Essentials Plus aligned controls.
How we look after your data →FAQ
Common questions about DMARCHub.
Why is my DMARC failing?
Most DMARC failures come from a legitimate service sending as your domain without SPF or DKIM that lines up with your From address, from mail being forwarded, or from someone else using your domain. DMARCHub groups failing mail on each domain by likely cause, says how sure it is, and lists the steps to fix it.
What are SPF alignment and DKIM alignment?
DMARC only passes when SPF or DKIM passes for a domain that matches the address people see in the From line. A message can pass SPF or DKIM for the domain of the service that sent it and still fail DMARC, because that domain is not aligned with yours.
Does DMARCHub use AI?
The explanations of why mail is failing are produced by fixed rules applied to your DMARC reports, not by AI. On eligible plans you can also ask for a short plain-English summary of those findings, which is written by Microsoft Azure OpenAI. It is optional and only runs when you ask for it.
Is there an AI assistant?
On eligible plans there is an optional domain assistant. You open it from a domain's page and ask questions about that one domain in plain English. It can only read that domain's data in DMARCHub, it cannot change anything, and it is processed by Microsoft Azure OpenAI within the EU. The data it reads about your domain never includes IP addresses or message content, we do not keep the conversation, and answers can be wrong, so check anything important.
Is my data used to train AI?
No. For an AI summary we send only the findings for that domain: cause categories, message counts, the names of well-known email services and your domain name. We send no IP addresses, server names, report contents or personal details. It is processed within the EU, and Microsoft does not use it to train models.
Where is my data stored?
Your data is stored in Microsoft Azure UK South. Forensic report content is privacy-scrubbed when it arrives, so message bodies and recipients are never stored. Optional AI summaries are processed within the EU.
Beta
Want a closer look?
DMARCHub beta testing is running. Sign up with your work Microsoft or Google account to join it.