Email & Domain Protection
Email & Domain Protection shows who sends mail as your domains and stops others from doing it. It moves each domain step by step to the strictest DMARC policy, and makes sure mail sent to you only travels over encrypted connections (MTA-STS). Innovarro manages it for you. You can follow every step on the Protection page of your organisation in the portal at https://signatures.innovarro.cloud.
What you get
| What it does | |
|---|---|
| DMARC reports | Every day Google, Microsoft, Yahoo and other providers report every server that sent mail as your domains, and whether it passed SPF and DKIM. The Protection page groups these by sender (for example Microsoft 365, Mailchimp, or Unknown). |
| Staged DMARC rollout | Each domain moves from p=none (monitor only) to p=quarantine (spoofed mail goes to Junk) and then p=reject (spoofed mail is refused). It only moves up once the reports show that all your real senders pass. |
| MTA-STS | Tells other mail servers to deliver to you only over encrypted connections, to your real Microsoft 365 servers. It starts in testing mode, where senders only report problems, and moves to enforce when the reports are clean. |
| TLS reports (TLS-RPT) | Daily reports from sending servers about encrypted delivery to your domains. These show whether MTA-STS can be enforced safely. |
Connect and give people access
Email & Domain Protection does not need access to your mailboxes or your user directory. It only needs sign-in, so the people you choose can open the Protection page.
- A Global Administrator of your Microsoft 365 tenant opens https://signatures.innovarro.cloud/connect/protection,
enters your organisation's name and the domains to protect, and approves sign-in for the Innovarro Signatures
application. This grants sign-in only (
openid,profile,email), nothing else. - Innovarro checks the domains, sets them up and activates your organisation, usually within one working day.
- Give people access with the Protection.Admin role: Microsoft Entra admin centre → Enterprise applications →
Innovarro Signatures → Users and groups → Add user/group. Or run
.\Grant-InnovarroSignaturesAdmin.ps1 -User it@contoso.com -Role Protection.Admin(download). - They sign in at https://signatures.innovarro.cloud and see only the Protection page of your organisation.
Already using Innovarro Signatures? You don't need to connect again. Innovarro adds Email & Domain Protection to your organisation, and people with the Signatures.Admin role see both. Give Protection.Admin to people who should see only the reports.
DNS records
Innovarro first sets up each of your domains on its side. The Protection page then lists the records still to add,
with the exact values for your domains. You add them once, for every domain you send mail from. After that, Innovarro
changes the policies without needing any more DNS changes from you. In the examples, replace contoso.com with your
domain.
| Type | Name | Value |
|---|---|---|
| CNAME | _dmarc.contoso.com |
contoso.com._dmarc.policy.innovarro.cloud |
| CNAME | _mta-sts.contoso.com |
contoso.com._mta-sts.policy.innovarro.cloud |
| CNAME | mta-sts.contoso.com |
mta-sts.innovarro.cloud |
| TXT | _smtp._tls.contoso.com |
v=TLSRPTv1; rua=mailto:dmarc@innovarro.cloud |
Rules to keep in mind:
- Delete your existing
_dmarcTXT record when you add the CNAME. A name with a CNAME cannot have any other record. Innovarro starts the hosted record at the policy you already have, so nothing changes for delivery. - Keep your SPF record and DKIM as described in Update SPF and turn on DKIM. DMARC depends on them.
- Some DNS providers want only the first part of the name (
_dmarc,_mta-sts,mta-sts,_smtp._tls) and add the domain themselves. mta-sts.contoso.comserves your MTA-STS policy over HTTPS. Innovarro gets the certificate for it automatically.
Check the records from PowerShell or a terminal:
Resolve-DnsName _dmarc.contoso.com -Type TXT
Resolve-DnsName _mta-sts.contoso.com -Type TXT
dig +short TXT _dmarc.contoso.com
dig +short TXT _mta-sts.contoso.com
Both should return the record through the CNAME, for example v=DMARC1; p=none; rua=mailto:dmarc@innovarro.cloud and
v=STSv1; id=….
Reports only, without hosted policies
If you want to manage your own DMARC record, you can still get reports. Add
rua=mailto:dmarc@innovarro.cloud to your _dmarc TXT record, for example:
v=DMARC1; p=none; rua=mailto:dmarc@innovarro.cloud
The Protection page then shows the reports, but you move the policy up yourself.
How a domain moves to the next step
Every 6 hours the portal checks each hosted domain. A domain is ready for its next DMARC step when all of these are true:
- It has been at its current policy for at least 14 days.
- Reports came in on at least 7 of those days. A domain that sends no mail at all is ready without reports, because a stricter policy then only stops spoofing.
- Every sender with more than 1% of the domain's mail passes DMARC at least 98% of the time. Senders that almost never pass (below 5%) are treated as spoofing or forwarding. They are listed so you can see what the next step would block.
MTA-STS moves from testing to enforce after 14 days in testing, when fewer than 0.5% of encrypted sessions fail and none fail because of your own certificate or policy.
When a domain is ready, Innovarro gets an e-mail with the evidence and approves the step with one click. Nothing becomes stricter without that approval. The step takes effect within 5 minutes, because the records are published with a short lifetime.
Automatic rollback
For 30 days after each step, the portal watches the reports. A step is undone automatically, and Innovarro is told, when:
- DMARC: a sender that normally passes has at least 5 messages, and at least 5% of its mail, sent to Junk or rejected in the last 3 days.
- MTA-STS: at least 5 encrypted sessions, and at least 1%, failed in the last 3 days. The policy goes back to testing, so senders deliver as before.
Every change is listed under Policy changes on the Protection page, with the date, the reason and who made it.
The Protection page
| Section | What it shows |
|---|---|
| Totals | Messages reported, how many passed DMARC, how many were sent to Junk or blocked, and the number of senders with failures. Choose 7, 30 or 90 days. |
| Domains | Each domain's DMARC policy, whether it reports to Innovarro, and its pass rate. |
| Who sends as these domains | Every sender seen in the reports, with how much of its mail passed and why the rest failed. |
| Encrypted delivery (MTA-STS) | Each domain's MTA-STS mode, whether its DNS records are right, and the TLS reports. |
| Policy rollout | Each domain's current step, what the next step is waiting for, records still to add, and the history of changes. |
Receivers send one report a day, so the first numbers appear within about 24 hours of adding the records.
A sender fails DMARC
If a legitimate service (a newsletter tool, CRM, ticket system or invoicing platform) shows up with failures, the domain stays at its current step until that service is fixed. Usually one of these fixes it:
- DKIM: turn on DKIM signing in the service with your own domain. Most services give you one to three CNAME records to publish.
- SPF: add the service's
include:to your SPF record. This only helps if the service uses your domain as the envelope sender. Check its documentation. - Not yours: if you don't recognise a sender, it is probably spoofing. You don't need to do anything: the next step will stop it.
Tell Innovarro when you have fixed a sender. The next proposal comes as soon as the reports show it passing.
Privacy
DMARC aggregate reports contain sending IP addresses, message counts and SPF and DKIM results. They contain no subjects,
no recipients and no message content. Innovarro does not ask for DMARC failure reports (ruf), which can contain message
content. Reports are kept for 13 months. TLS reports contain only connection counts and error types.