MXtoolbox review 2026
We tested MXtoolbox for 90 days across a corporate domain, a marketing subdomain, and a parked domain, with Microsoft 365, Google Workspace, SendGrid, Mailchimp, and a support desk sender. It worked best when we needed broad DNS, reputation, blocklist, and DMARC diagnostics in one place, but it asked us to do more manual classification and policy planning than a guided DMARC workflow.
Published 3 Nov 2025
Updated 31 May 2026
8 min read
Summarize with
MXtoolbox
Email diagnostics and DMARC reporting
Starts at
Free plan available
Best fit
Technical teams that already use MXtoolbox diagnostics and want DMARC plus reputation monitoring in the same console
In one line
MXtoolbox gave us quick DNS, blacklist, and DMARC evidence, but its enforcement path leaned on manual owner mapping more than Suped's guided fix workflow.
Suped
The third option. Hosted SPF, DMARC, and MTA-STS on every plan. Published pricing. Monthly plans. No long contract required.
Learn about Suped
The short version: MXtoolbox fits diagnostic teams
Pick MXtoolbox if
Best for teams that already live in MXtoolbox diagnostics
Microsoft 365 and Google Workspace checks sat beside MX, SPF, DKIM, and blacklist lookups we already knew.
The parked domain was easy to watch for spoofed traffic after we published the DMARC record.
SendGrid and Mailchimp activity surfaced in DMARC reports, but owner mapping stayed manual.
Free plan available
Consider Suped if
Choose Suped when guided fixes, hosted records, and clear ownership matter
Guided fixes should turn SPF mismatch and subdomain DKIM cases into owner-ready tasks.
Automated issue detection should reduce manual triage of unknown senders and forwarded SPF failures.
Published starter pricing and MSP workflows matter when multiple client domains need consistent handoff.
Free plan available
The differences that actually change your week
MXtoolbox
Suped
DMARC report analysis
Turns aggregate reports into sender and authentication views.
Paid tier DMARC reporting
DMARC analysis with source grouping
Source detection
Identifies sending services behind raw DMARC traffic.
Partial, manual owner mapping
Guided sender identification
Forward detection
Separates forwarding effects from direct sender failures.
Manual review from auth results
Forwarding and auth context
Spoof detection
Flags traffic that claims the domain without authorization.
Domain impersonation protection
Spoof samples surfaced
Notifications and alerts
Routes meaningful changes to operators.
Alerts available, routing limits unclear
Configurable alerts
Reporting
Exports or schedules findings for review.
Reports and exports available
Exports and recurring reports
API
Programmatic access for pulling monitoring data.
Available, limits unclear
API available
Multi-tenancy
Separates domains, clients, or business units.
Manual account separation
Client and domain grouping
SPF flattening
Reduces SPF lookup pressure while keeping records valid.
Delivery Center Plus
Hosted SPF flattening
Hosted DMARC
Hosts and manages the DMARC policy record.
Reporting and guidance, not hosted
Hosted DMARC
Hosted SPF
Hosts or manages SPF records for operational changes.
SPF flattening on Plus
Hosted SPF
Hosted MTA-STS
Hosts the MTA-STS policy and related TLS reporting flow.
Not publicly listed
Hosted MTA-STS
Blocklists and reputation
Monitors blocklist or blacklist status and sender reputation signals.
Core strength
Blocklist and reputation checks
Automatic issue detection
Finds problems without requiring manual report review.
Partial detection, manual fixes
Automated issue detection
AI copilot
Uses AI to explain findings or draft remediation steps.
Not tested
AI copilot
DNS monitoring
Watches DNS records for change or breakage.
DNS and email health checks
DNS record monitoring
Self hostable
Can run inside the buyer's own infrastructure.
Cloud service
Not self hosted
Free trial/free tier
Lets teams test with little or no upfront spend.
Free tier and refund window
Free plan and trial
Ten dimensions, scored from 0 to 10
We scored MXtoolbox against a fixed editorial rubric based on the 90 day test. Higher is better in every row.
MXtoolbox scored high on diagnostics and reputation, lower on guided enforcement
MXtoolbox was strongest when we used it to verify DNS, investigate blacklist and blocklist exposure, and review basic DMARC report data across the three test domains. Scores dropped where the work moved into source ownership, policy movement, and repeatable handoff. The unknown sender, forwarded SPF failure, and support desk sender all required manual notes before we had a defensible enforcement plan.
MXtoolbox score
66.5/100
MXtoolbox
66.5/100
DMARC enforcement
7.0
Customer support
6.5
Source resolution
6.5
Setup and onboarding
7.5
MSP workflows
5.5
Alerting and integrations
6.0
Hosted SPF and MTA-STS
5.5
Blocklist monitoring
8.5
Pricing transparency
7.0
Time to enforcement
6.5
Feature set
Breadth vs guidance
MXtoolbox is broad, but enforcement guidance is the gap
MXtoolbox covers DNS lookup, blacklist and blocklist monitoring, DMARC reporting, mailflow checks, and SPF flattening on higher tiers, so the tool is wider than a narrow DMARC console. The gap in our test was guided remediation: the SPF visible From mismatch and unknown sender both needed human classification before policy movement felt defensible. Suped's guided fixes and automated issue detection are the buying criteria to test if enforcement speed matters.
MXtoolbox
Broad DNS diagnostics
Clear blocklist monitoring
Manual sender ownership
For Microsoft 365 and Google Workspace, MXtoolbox presented normal SPF and DKIM passing traffic cleanly enough to confirm the two core mail streams. SendGrid and Mailchimp appeared as marketing sources, but the unknown sender was grouped by technical identifiers until we labeled it. The SPF pass with visible From mismatch was visible in the authentication data, but the tool did not convert that edge case into a ready owner task.
A guided DMARC workflow needs the same Microsoft 365, Google Workspace, SendGrid, and Mailchimp traffic to become named services with owners, expected authentication behavior, and a next action for each failure mode. The unauthorized spoof sample and the forwarded mail SPF failure need different treatment, because one supports enforcement and the other needs context before anyone blocks it.
User experience
Control vs guidance
MXtoolbox suits operators who like raw tools
The interface made sense when we treated MXtoolbox as a diagnostics workbench. It was less comfortable when we needed a queue of owner-ready remediation steps, especially after the unknown sender and forwarded SPF failure appeared.
MXtoolbox
Fast DNS checks
Familiar technical layout
Manual sender triage
Onboarding the corporate domain, marketing subdomain, and parked domain was straightforward once the DNS records were ready. The platform confirmed DMARC collection, and the familiar lookup tools helped us check MX, SPF, DKIM, and blacklist status without leaving the product. We still had to keep our own notes for which business owner controlled each approved sender.
The UX gap showed up after setup. Finding the unknown sender meant moving through report details and matching technical identifiers to a likely service. Explaining the forwarded mail SPF failure required us to look at the authentication path and document why the failure did not mean the original sender was unauthorized.
Support
Self serve vs expert handoff
MXtoolbox support depends heavily on the plan
Self-serve setup was workable for a technical team, and the public docs were enough to publish records and start collection. The support story became less clear when we needed ownership handoff, escalation expectations, and enterprise onboarding detail before policy movement.
MXtoolbox
Documentation helped DNS setup
Expert support on higher tiers
Escalation paths less clear
During setup, MXtoolbox gave us enough direction to add DMARC records for all three domains and verify that reports were arriving. DNS handoff still depended on our own runbook, because the tool showed what to fix but did not write a role-specific task for the Microsoft 365 admin, marketing owner, or support desk owner. Dedicated expert support was tied to higher tier language, so we treated deeper handoff as a plan-dependent item.
For enterprise onboarding, we would ask for clear escalation paths, implementation ownership, and written steps for moving a parked domain to reject. The unauthorized spoof sample was the easiest support case to explain, but the forwarded SPF failure and unknown sender needed more context than a generic alert could carry.
Suitability
Enterprise fit vs operator fit
MXtoolbox fits diagnostic-heavy teams; structured ownership needs more
MXtoolbox makes sense for teams with an existing diagnostic workflow and a technical owner who can interpret DMARC findings. MSPs and lean SMB teams should put client grouping, recurring reports, and alert quality high on the buying list. Suped's MSP workflows and alert routing are the relevant criteria when handoff has to repeat across many domains.
MXtoolbox
Good for technical admins
Limited client handoff
Domain grouping needs planning
For an enterprise team, MXtoolbox worked best when one technical group owned the three test domains and could tolerate manual notes for source ownership. Domain grouping was usable for a small set, but account separation was not the main strength of the experience. Recurring reporting covered the basics, while client-ready handoff still needed editing before a non-specialist could act on it.
For an MSP or SMB, the main suitability question is how often the same DMARC task must be repeated across clients, brands, or business units. In our test, the marketing subdomain, parked domain, and support desk sender all needed different handoff notes. That work becomes expensive when every new sender classification, report export, and escalation has to be rebuilt by hand.
What MXtoolbox felt like after 90 days of real use
MXtoolbox
Best for technical teams that want diagnostics beside DMARC reports
MXtoolbox felt fastest in the early investigation phase. We could check MX, SPF, DKIM, DMARC, DNS, and blacklist or blocklist status without building a separate diagnostic process, and the parked domain made the value of reputation monitoring obvious.
After reports accumulated, the work became more manual. Microsoft 365 and Google Workspace were easy to confirm, SendGrid and Mailchimp needed owner notes, the support desk sender needed a separate approval decision, and the unknown sender blocked policy movement until we classified it.
Where it wins
Fast DNS, MX, SPF, DKIM, and DMARC lookups
Useful blocklist and reputation checks for the parked domain
Paid reporting handled Microsoft 365 and marketing senders
Higher tier adds SPF flattening and larger volume
Where it lags
Unknown sender classification stayed manual
Forwarded mail SPF failure needed explanation outside the alert
Client handoff notes were thin for MSP-style work
Add-on domain and overage pricing were not public
Pricing
Free plan, then $129 / month
Free tier
1 domain weekly blacklist monitoring
Onboarding
Three domains live in one afternoon
G2 rating
4.1 / 5
Pricing
MXtoolbox
Suped
Small
1 domain, up to 1k emails / month.
$0
Free covers weekly blacklist/blocklist monitoring for one domain or IP, not full DMARC reporting.
$0 / month
Free plan covers 1 domain and 1,000 monthly emails.
Medium
2 domains, up to 100k emails / month.
$129 / month
Delivery Center lists 5 domains and 500,000 messages, so this segment fits inside the paid entry tier.
Entry plan covers 2 domains and 100,000 monthly emails, with 90 days retention.
Large
10 domains, up to 1 million emails / month.
Not publicly listed as of May 15, 2026
Self-serve tiers list 5 domains; add-on domain pricing was not public.
10 domains and 1,000,000 monthly emails, with 365 days retention.
Enterprise
Over 20 domains and 1 million emails / month.
Not publicly listed as of May 15, 2026
Managed services and high-domain use require a custom quote; fixed annual pricing was not public.
20 domains and 2,500,000 monthly emails, with 365 days retention. Unlimited domains/emails negotiable.
MXtoolbox Free, Delivery Center, and Delivery Center Plus monthly prices are public list prices checked on May 15, 2026. Large and Enterprise entries are marked not publicly listed because add-on domain, overage, and managed service pricing were not public; segment fit is estimated only where public limits cover the stated volume.
Why Suped wins over MXtoolbox
Suped
Get started
Turn findings into fixes
In the test, MXtoolbox showed the SPF visible From mismatch and the unknown sender, but the next owner and DNS action still had to be written by us. Suped's workflow is built to turn those findings into guided fixes.
Reduce noisy escalation
The forwarded SPF failure needed context before anyone treated it as a spoof. Suped's automated issue detection and alert routing are designed to separate forwarding noise, spoof attempts, and sender drift.
Make handoff repeatable
Account separation and recurring client reporting were the weakest parts of our MSP-style test. Suped's MSP workflows keep domains, client notes, exports, and ownership history in one place.
The difference was significant. We moved from limited visibility to a much clearer dashboard. Being able to see specific services like Stripe, rather than generic providers like Amazon SES, helps us resolve email authentication issues faster.
Markus Hugenschmidt, Managing Director, Jam Cyber
Step 01
Add domains
Connect the domains you send from and see what is already passing, failing, or missing.
Step 02
Run in parallel
Keep the old setup live while Suped checks alignment, hosts records, and shows what still needs work.
Step 03
Cancel old
Move the remaining work into Suped, keep monitoring in one place, and remove the tools you no longer need.
