Authwright vs Palisade in 2026

Five registrars against a wider catalogue

Custody and reach are the same decision seen twice. Because Authwright writes through registrar adapters it has built, it works where an adapter exists: GoDaddy, Namecheap, Cloudflare, Porkbun and Route 53. Its own FAQ says those five "map to the overwhelming majority of agency books" and invites you to email if yours is not covered. Palisade's automatic configuration reaches 64 DNS providers, because it connects through the provider's own authorisation rather than through a credential Palisade had to build a home for.

For a book of client domains, that gap decides how much of the book the tooling covers. Five adapters handle a portfolio consolidated at a big registrar. A mixed inheritance, which is what most agencies actually have, spreads past them.

A setup run against an operating loop

Authwright's flagship is Email EasyPass, its email_auth_wizard tool. Its homepage sets out the sequence: read the current state, diagnose against the Gmail and Yahoo rules, write corrected records at the registrar, host the MTA-STS policy, wait for propagation, verify, then ingest DMARC reports on an ongoing basis and summarise them in plain language. The homepage transcript clocks the run at 47 seconds and moves a score from 32 to 94.

Getting a domain to a good configuration quickly is genuinely useful, and that sequence does it. The part that decides whether a domain stays there is what happens over the following weeks, when a marketing team adds a sender nobody told you about, or an upstream provider changes its SPF include and the lookup count creeps back over ten.

Palisade is built around that second phase. Aggregate reports feed a work queue: the agent investigates each sending source, works out whether it is legitimate, drafts the fix, and files it as a prioritised ticket with instructions specific to the provider involved. Webhooks push those events into your own systems. The agent investigates every sender, drafts every fix, and proposes each policy step, and you approve before anything ships. The output is a task with an owner rather than a report to read.

Where Authwright is the better tool

Authwright is not really a DMARC product with extras. Of its 42 published tools, 8 are email authentication; the other 34 handle DNS records, domain portfolio lifecycle, SSL/TLS, bulk operations and health checks. Its registrar pages make the actual pitch plainly: renewals you keep forgetting, certificates expiring on inconvenient days, WHOIS privacy that flips off after a billing failure, defensive registrations that each cost a trip through a checkout flow.

If that is the job in front of you, Authwright covers ground Palisade does not and is not trying to. Palisade does not renew certificates, buy domains, manage WHOIS privacy, or audit DNSSEC. An agency whose real problem is a sprawling registrar portfolio should weigh that breadth seriously, and can run both: the two overlap only on the email-authentication tools.

Two smaller things worth knowing before you commit. Authwright is not listed in the official MCP registry, checked on 20 August 2026, so an assistant that discovers servers through the registry will not find it. And its /docs and /pricing URLs both returned 404 that day, which for a product sold on its MCP surface is worth a question before you connect it.