PowerDMARC MCP Server: Connect Your AI to Your DMARC Data
Your DMARC data, just a question away.
dmarc_aggregate_per_sending_source Live data 0sources
sending mail as powerdmarc.com
Same prompt. Different intelligence.
General guidance on DMARC posture
Honest take, without access to your actual DMARC reports I can only walk you through the standard playbook. The typical recommendation is to start at p=none, monitor for a few weeks, then move toward p=quarantine and eventually p=reject.
For SPF, you'll want to stay under the 10 DNS lookup limit, and your DKIM keys should be at least 1024-bit (ideally 2048). BIMI requires a VMC and prior DMARC enforcement.
I don't have visibility into powerdmarc.com's actual sending sources, current policy, alignment failures, or any spoofing attempts targeting your subdomains, so I can't tell you which domains are spoofable.
powerdmarc:get_domains() Live data Domain portfolio
12 domains, 30-day window
| Domain | Score | Spoofing (30d) | Policy | Status |
|---|---|---|---|---|
| powerdmarc.com | 62 | 1,284 | p=none | Monitor |
| mail.powerdmarc.com | 38 | 8,917 | no record | Spoofable |
| powerdmarc-billing.com | 29 | 14,602 | no record | Spoofable |
| support.powerdmarc.com | 71 | 312 | p=quarantine | Partial |
| marketing.powerdmarc.com | 44 | 2,108 | p=none | Spoofable |
| powerdmarc.io | 94 | 0 | p=reject | Enforced |
Three domains are actively spoofable right now, mail.powerdmarc.com, powerdmarc-billing.com, and marketing.powerdmarc.com. Combined, they absorbed ~25,600 spoofing attempts in the last 30 days...