Mailchimp
Test a draft campaign as Mailchimp sends it, and keep a permanent address in an audience that checks every campaign it receives.
Open MailchimpHome › Integrations
Start the spam test from the tool that already sends your mail. Some tools below work through your account or a plugin, and for six more sending platforms there is a guide to mailing one real email to a test address.
Connect the account once and test a campaign from inside the tool that sends it.
Test a draft campaign as Mailchimp sends it, and keep a permanent address in an audience that checks every campaign it receives.
Open MailchimpTest a marketing email from inside HubSpot and keep the results in one history.
Open HubSpotPlugins for the people who run the server. The customer tests a mailbox from the panel they already use.
A plugin for hosting providers; customers test a mailbox from the Email section and fix DNS from the findings.
Open cPanel & WHMThe same for Plesk, opened from the Mail tab of a domain, with buttons that fix DKIM, SPF and DMARC.
Open PleskA plugin that tests the emails your site sends through wp_mail and whatever SMTP plugin is behind it.
Open WordPressCreate a test address in a Zap, send to it from any app and pass the score on.
Open ZapierOne community node that gets an address, waits for the report and hands on what to fix.
Open n8nFail a build when a template change breaks authentication or the score drops.
Open GitHub ActionsThe same check as a catalog component, with each result in the merge request.
Open GitLab CI/CDA REST API for anything else.
Open the API docsAll of these talk to one hosted MCP server, so the test and the report are the same in each.
A connector in the Claude directory; Claude gets an address, reads the report and writes the DNS records.
Open ClaudeThe test in a conversation, with the report in a card and a permanent address for a whole series.
Open ChatGPTOne command, or a plugin that adds a skill for reading the report.
Open Claude CodeThe agent tests what your code sends and opens the file to change.
Open CursorA spam test from the Gemini prompt, set up in settings.json.
Open Gemini CLIAgent mode in VS Code, with the config in the repo for the whole team.
Open GitHub CopilotA context server for the agent panel.
Open ZedFor testing a relay from the terminal it runs on.
Open WarpA remote entry in opencode.json, for whichever model you run.
Open OpenCodeThe server address and the usual config.
Open Any MCP clientAn extension that gives you an address from the toolbar and tells you when the report is ready.
Open ChromeThere is no connection to these platforms yet. You do not need one: every one of them can send an email to any address, and a real email from your account is exactly what the test wants to see. Each guide shows where the test send is in the platform, why a test send and a real campaign can get different results, and which DNS records that platform asks you to publish.
An integration sends the test for you. A guide shows you where to press send yourself. The report is the same.
Run a real Brevo campaign through a spam test and see SPF, DKIM, DMARC, blocklists and spam scores, and why your sender may become brevosend.com.
Read the Brevo guideHow to point a SendGrid Single Send or a v3 API call at a disposable address, and how to read the SPF, DKIM, DMARC and unsubscribe results.
Read the SendGrid guideUse aws sesv2 send-email to mail a throwaway test address, then check DKIM, custom MAIL FROM, DMARC alignment and unsubscribe headers.
Read the Amazon SES guideRun a Klaviyo campaign or flow email through a spam test, avoid the Smart Sending trap, and see why the shared sending domain fails DMARC for your brand.
Read the Klaviyo guideSend an ActiveCampaign campaign or automation email to a one-off test address, then read DKIM, Mailserver Domain, DMARC and blocklist results line by line.
Read the ActiveCampaign guideMailerLite test emails carry a [TEST] label and no unsubscribe header. Send the real campaign to a one-hour test address instead and see what to fix.
Read the MailerLite guideYes. Anything that can send email to an address works: copy a test address from the home page, send your email to it and open the report. If you would like a proper connection to your platform, write to us and say which one.
None of these exist yet. Tell me which one you would use and it moves up the list.
test a broadcast before it goes out.
a module for scenarios, like the Zapier one.
the panel plugin for a third control panel.
a piece for flows, like the n8n node.
a check from the admin page of a self-hosted server.
a component for workflows.
test the emails a store sends from its admin.
test the message you have open.
reports posted to a channel.
the same as the Gmail add-on, in Outlook.
a bot that hands you an address.
the score of a domain on a dashboard.
If your platform is in the first list, use that: it sends the test from your account with your settings and keeps the history. Otherwise follow the guide for your platform, or send any email to an address from the home page. The report is the same 42 checks and the same optional inbox test either way.
No. The integrations, the plugins and the API use the same free tests as the site.
Yes. Anything that can send email to an address works: copy a test address from the home page, send your email to it and open the report. If you would like a proper connection to your platform, write to us and say which one.
Test an email now
One address, one email, valid for an hour. No account. The report builds itself as the checks finish.