PowerDMARCStop attackers sending email that looks like it comes from your domain
PowerDMARC is a cloud platform for managing email authentication: DMARC, SPF, DKIM, MTA-STS, TLS-RPT and BIMI. It helps you see who is sending email in your name and move safely to a policy that blocks spoofed messages.
- Cloud platform
- Hosted service, set up through DNS records
- DMARC reporting
- Aggregate and failure reports turned into readable dashboards
- Hosted records
- DMARC, SPF, DKIM, MTA-STS and BIMI managed without repeated DNS edits
Problems PowerDMARC is designed to address
Email authentication problems are usually invisible until a customer or partner receives a fake invoice from your domain.
| Topic | What it can lead to | How PowerDMARC helps |
|---|---|---|
| No DMARC policy, or stuck at p=none | What it can lead to: Anyone can send email that appears to come from your exact domain, and receiving servers are told to deliver it. | How PowerDMARC helps: Reporting shows every source sending as your domain, so legitimate senders can be fixed and the policy moved towards quarantine or reject. |
| Unknown third-party senders | What it can lead to: Marketing, CRM or billing platforms send as your domain and fail authentication, so enforcing DMARC would break them. | How PowerDMARC helps: Aggregate (RUA) reports are parsed into dashboards that show which services send for you and whether they pass SPF and DKIM. |
| SPF record over the 10 DNS lookup limit | What it can lead to: SPF fails with a permanent error for all of your mail, as defined in RFC 7208. | How PowerDMARC helps: Hosted SPF can optimise the record, using flattening or SPF macros, to stay within the limit. |
| DKIM keys hard to manage across services | What it can lead to: Old or weak keys stay in use, and changing them means coordinating DNS edits. | How PowerDMARC helps: Hosted DKIM lets you manage keys and selectors through the platform after a one-time NS record delegation in your DNS. |
| Email between mail servers sent without enforced encryption | What it can lead to: Messages in transit can be downgraded to unencrypted connections. | How PowerDMARC helps: Hosted MTA-STS publishes and manages your policy, and TLS-RPT reports show delivery problems. |
What PowerDMARC does
PowerDMARC brings the email authentication protocols into one place, so you can monitor them, publish them and change them without repeated manual DNS work.
Hosted DMARC
Cloud-based management of your DMARC record and policy, so you can change policy settings without editing DNS each time.
DMARC reporting and analysis
Turns the XML aggregate (RUA) reports sent by mailbox providers into readable views of who sends as your domain, and supports failure (RUF) reports where providers send them.
Hosted SPF
Helps keep your Sender Policy Framework (SPF) record within the 10 DNS lookup limit, using automated flattening (PowerSPF) or SPF macros.
Hosted DKIM
Manage DomainKeys Identified Mail (DKIM) keys and selectors after a one-time NS record delegation, with support for 1024, 2048 and 4096-bit keys.
Hosted MTA-STS and TLS-RPT
Publishes and manages your MTA-STS policy, which asks sending servers to use encrypted connections, with TLS reporting on delivery problems.
Hosted BIMI
Manages the record that lets supporting mailboxes show your logo next to authenticated email. BIMI requires DMARC at quarantine or reject.
The email authentication protocols at a glance
Each protocol solves a different part of the problem. DMARC ties SPF and DKIM together and tells receivers what to do when they fail.
| Topic | What it checks or does | Why it matters |
|---|---|---|
| SPF (Sender Policy Framework) | What it checks or does: Lists the servers allowed to send email for your domain. | Why it matters: Lets receivers reject mail from servers you have not authorised. |
| DKIM (DomainKeys Identified Mail) | What it checks or does: Adds a cryptographic signature to each message. | Why it matters: Shows the message really came from your domain and was not altered. |
| DMARC | What it checks or does: Checks that SPF or DKIM pass and align with the visible From address, and sets a policy: none, quarantine or reject. | Why it matters: The only one of these that tells receivers to block spoofed mail, and it sends you reports. |
| MTA-STS and TLS-RPT | What it checks or does: Asks sending servers to use encrypted connections to your mail servers, and reports failures. | Why it matters: Protects email in transit between servers. |
| BIMI | What it checks or does: Displays your logo in supporting mailboxes. | Why it matters: A visible sign of authenticated mail; only works once DMARC is enforced. |
Email domain protection self-check
Most of these can be checked with free DNS lookup tools in a few minutes. Nothing you tick is saved or sent.
How VirtuThinko helps you adopt PowerDMARC
- 01
Requirements
We can help you map the problem you want PowerDMARC to solve, the systems and users in scope, and what success should look like.
- 02
Demo or proof of concept
We can show you the platform and help you add your domains in monitoring mode, so you see real reports from your own mail traffic.
- 03
Design and deployment
We can help identify legitimate senders, fix their SPF and DKIM set-up, and configure the hosted records you choose to use.
- 04
Tuning and handover
We can help plan the move from p=none to quarantine and reject in stages, watch the reports for problems, and hand over with clear ownership.
- 05
Ongoing support
Where needed, we can continue with policy changes, health checks and help with day-to-day questions, under an agreed scope.
It can, if legitimate services are not authenticated first. That is why PowerDMARC recommends starting at p=none and monitoring reports until known senders pass, then moving to quarantine and reject in stages.
It depends on how many services send email for you. PowerDMARC’s own guidance suggests monitoring for several weeks at p=none, and longer for organisations with many senders, before moving to enforcement.
With the hosted services, you point DNS to PowerDMARC once (CNAME records for most services, an NS record for Hosted DKIM), and then manage DMARC, DKIM, MTA-STS and other settings in the platform.
Aggregate (RUA) reports summarise authentication results by sending source. Failure (RUF) reports describe individual messages that failed, but PowerDMARC notes that fewer mailbox providers send them.
No. DMARC stops attackers sending from your exact domain. It does not stop lookalike domains or phishing sent from other domains, so it should sit alongside email security and user awareness.
Explore PowerDMARC for your organisation
Share the domains you use for email, the services that send on your behalf and your current DMARC policy if you have one. A member of our team will contact you to arrange an initial conversation.