DMARC Dojo hosts your DMARC, SPF and DKIM records, reads every report mailbox providers send about your domain, and tells you exactly when it’s safe to move from monitoring to reject.
Free for one domain. No card required. Not sure where you stand? Check your domain free.

v=DMARC1; p=none; rua=mailto:k3f9x2qa@rua.dmarcdojo.aiChange the policy here and it’s live on your domain. No DNS ticket.
You don’t hand us your whole DNS zone. You delegate the few records email authentication needs, then change them whenever you like without filing another DNS ticket.
We give it a private report address and a starting policy of p=none, so nothing gets blocked while you learn.
On Cloudflare or Route 53, connect your account and we publish them for you. Anywhere else, copy them into your DNS provider. Either way, this is the last time you’ll need to.
k3f9x2qa.dmarc.dmarcdojo.aiv=spf1 redirect=k3f9x2qa._spf.dmarcdojo.aigoogle.k3f9x2qa._dkim.dmarcdojo.aiReports arrive within a day. Fix the senders that fail, then tighten the policy one belt at a time. Every change is live within a minute.
Aggregate reports are thousands of rows of XML. The DMARC Dojo AI analyst reads them for you, explains why each sender fails in plain language, and lays out a step-by-step path to p=reject that won’t block your own mail.
pct and when to holdAn unidentified sender, 185.234.72.19, started on the 12th and sends about 120 messages a day in bursts. All of them fail both SPF and DKIM and the IP has no reverse DNS. This is spoofing, not a misconfiguration.
Separately, SendGrid signs with d=sendgrid.net, so its mail only passes when SPF aligns. Fix the s1 selector and your legitimate pass rate reaches 99.6%.
Recommendation: fix SendGrid today, then raise pct to 100 next week.
DMARC Dojo runs a Model Context Protocol server. Connect Claude, or any MCP client, with an API key and ask about your domains in the same place you already work. It can read your stats, check your DNS and change your policy.
Example prompts
{
"mcpServers": {
"dmarc-dojo": {
"type": "http",
"url": "https://api.dmarcdojo.ai/mcp",
"headers": {
"Authorization": "Bearer dd_live_…"
}
}
}
}Tools: list_domains get_dmarc_stats get_top_sources list_reports update_dmarc_policy check_dns and more.
No email-volume limits and hosted SPF on every plan. You pay for domains, never for how much mail you send. Start with one domain for free.

$0
For one domain you want to protect properly.

$19 per month
For a business running several domains, with an AI analyst on call.

$99 per month
For agencies and MSPs managing email authentication for clients.
No account needed. Check a domain, build a record, read a report, or learn how it all fits together.
No. Your domain stays with your current DNS provider. You add a CNAME for _dmarc, one TXT record for SPF and a CNAME per DKIM selector. We only control what those records point to.
The DNS Setup tab always shows the exact values we publish. Paste them into your DNS as plain TXT records and remove the CNAMEs. Nothing breaks.
No. Aggregate reports contain counts, sending IPs and authentication results. They never include message content, subjects or recipients.
Yes. Add extra report addresses in the Policy tab and receivers will send reports to both.
Only the aggregate statistics, sources and settings for the domain you ask about. It runs when you ask a question, using Anthropic’s Claude API, which doesn’t train models on your data.
On Teams, yes. Group domains into client sub-accounts and invite each client’s people. They log in at your branded portal address and see only their domains, read-only. Client logins don’t use team seats.
No. There’s no per-message pricing and no email-volume limit on any plan: you pay for the number of domains, so a domain sending ten million emails a month costs the same as one sending ten. Hosted SPF is included on every plan, Free too. Paid plans can be billed monthly or yearly; yearly costs the same as ten months.
DMARC protects mail sent as your domain; MTA-STS protects mail sent to it. It tells Gmail, Outlook and other senders to deliver to your mail servers only over a verified, encrypted connection. Pro and Teams include it hosted: we serve the policy and its HTTPS certificate, start in testing mode, keep it in step with your MX records and turn the daily TLS reports into a list of what failed and why.
Yes. Every plan gets email alerts when a DNS record stops pointing at DMARC Dojo, a new sender starts failing DMARC or the pass rate drops sharply. On Pro and Teams, click Add to Slack and pick a channel, or add an HTTPS webhook for PagerDuty, Opsgenie, Microsoft Teams workflows or your own service. Webhooks are signed with HMAC-SHA256, and Settings shows an example payload and a verification snippet. Each problem alerts once, not on every check.
Turn on SPF flattening (Pro and Teams). We resolve every include to the IP ranges behind it and publish those instead, so the record needs one or two lookups however many services send for you. We re-check the ranges every hour and republish when a provider changes them; if a lookup fails we keep the last good record.
Yes, on Pro and Teams. Upload your logo as SVG and we check it against the SVG Tiny PS profile, host it (and your VMC or CMC certificate, which Gmail and Apple Mail require) and publish the BIMI record. Your domain needs DMARC at quarantine or reject first, which is what the belts get you to.
Most large providers send aggregate reports once a day, so expect your first reports within 24 to 48 hours.