You look after many client domains. Tightening DMARC on one of them is safe on the day you find the last system that sends mail as that client, and a support call on every day before it. DMARCdesk tells you which of your domains are safe to enforce now, which sender is still missing on each of the others, and what breaks if you turn it on today.
Get early access$4 per client domain per month. No minimum number of domains, and no contract.
The gain is invisible and the loss is loud. A blocked spoof is a line in a report that nobody reads. A blocked invoice is your telephone ringing. So the safe move is to leave every client at monitor only, and the risk quietly grows instead.
A report gives you an address and a number. It does not tell you whose system that is. An engineer who moved one large company to a stricter policy found 25 separate teams sending as it, and it took him two years.
The billing system that nobody has touched in years. The help desk. Calendar invitations. Scripts and monitoring mail. Each one is somebody's real mail, and each one is a telephone call.
A single user reports a missing message, the policy goes back to monitor only, and the work starts again. Doing this once is hard. Doing it for forty client domains is why it does not get done.
You paste the domain and DMARCdesk gives you one DNS record to publish. The client's mail providers start sending their reports to us the next day.
Every report is read for you. For each domain you get the list of systems that still send as your client and would be blocked today, in plain language, with what each one looks like: a billing system, a help desk, a calendar, a script.
Every domain you hold is sorted into three groups: safe to enforce now, waiting on a named sender, and not started. You work the middle group, and you turn on the top one.
Forty client domains costs $160 per month. The price is published so that you can read it without talking to anyone. It is not the argument for this product: cheaper tools than this one exist, and they give you the same reports and leave the same hunt to you.
Leave your email and four answers. You will hear directly from the person building it, and telling us it is wrong for you is a useful answer.
No, not yet. It is being built, and this page is how the first providers are being found. If you sign up you will hear from the person building it before it opens.
Because price is not the problem. Every tool in this category, including the cheap ones, hands you the same report and leaves you to find out whose system each failing sender belongs to. That hunt is the work, and it is what stops you enforcing. DMARCdesk is built for that hunt.
No. You hold the account and the domains sit under it. You can export a report to send to a client.
Not for the price. Switch only if your present tool leaves you unable to answer one question: which of your client domains is safe to enforce today.
For one domain, use the free tool. It is a good tool and this product does not try to beat it.
The free tools are built around one domain at a time. Cloudflare shows DMARC inside the dashboard of a domain that already uses Cloudflare DNS. Postmark sends a weekly email for each domain you register. Both are free because the company earns from something else: DNS in one case, sending email in the other.
That is the part which does not grow. Forty client domains means forty places to look, on whichever platform each client happens to use, and no single view of which client is failing this week. DMARCdesk is one screen for all of them, wherever their DNS is. If your domains all sit on one platform and you are happy opening them one at a time, the free tool is the right answer and you should keep it.