Input
Paste once
Drop in HTML or text without wiring a sending workflow just to get a QA verdict.
Free campaign QA
Free campaign probe for pre-send email QA
Paste campaign HTML or plain text and run a one-shot campaign probe before you send. This free checker surfaces broken links, missing images, compatibility warnings, HTML quality issues, and content-risk signals so teams can catch problems before launch.
Run a free campaign probe
Paste one campaign and get a pre-send QA verdict
Provide HTML, plain text, or both. HTML will produce the most complete result because link, image, compatibility, and HTML checks can all run together.
Best fit
Use this as the fast pre-send gate
The public probe is strongest when a team wants a quick answer before a launch, template handoff, or last-minute campaign change.
- Validate a campaign before the send window opens
- Catch CTA, tracking, and image regressions after template edits
- Give marketing ops and engineering one shared QA summary
Upgrade path
Persistent probes are built for repeat sends
When you need trend history, dedicated probe addresses, or operational ownership, move into the authenticated workflow instead of pasting content manually each time.
- Keep a probe per lifecycle stream or campaign program
- Compare run history before and after template changes
- Route regressions to owners instead of hunting issues manually
Key details
Checks
Links + images
Catch broken CTA paths and missing assets before they reach customers.
Coverage
Compatibility
See whether the HTML relies on email client features that deserve extra review.
Output
Ship / fix
Get one summary status and a set of insights that make the next action obvious.
What gets checked
One campaign QA run should cover the defects that matter most
Instead of treating HTML validation, compatibility review, links, and images as separate tasks, this tool frames them as one launch-readiness workflow.
Links
CTA safety
Check the URLs customers will click before they drive traffic into broken or misrouted paths.
Images
Asset hygiene
Catch missing or broken images that reduce trust and hurt campaign performance.
Compatibility
Client risk
Identify HTML features that deserve extra review across mailbox clients.
HTML
Markup quality
Surface structural issues that can degrade rendering and QA confidence even before delivery testing starts.
Operational use
Pre-send QA is strongest when it maps to a real send decision
This page is designed for teams that want one answer before they launch, not a vague dump of analyzer output.
Marketing ops
Use the probe as part of the launch checklist to reduce broken links, missing assets, and last-minute surprises.
Lifecycle teams
Re-run after template edits to keep recurring email programs stable over time instead of degrading quietly.
Agencies
Standardize one QA workflow across brands and clients so handoffs are cleaner and reporting is consistent.
Related tools
Email audit tool
Run a broader email audit when you want HTML, link, image, spelling, and compatibility review together.
Open toolEmail compatibility checker
Inspect detected HTML feature support in more detail when client compatibility is your main risk.
Open toolEmail spam checker
Pair content QA with sender and spam-risk diagnostics before important sends.
Open toolDomain monitor
Use sender-domain health checks alongside campaign QA so delivery posture and template quality stay aligned.
Open toolFAQ
What is a campaign probe?
A campaign probe is a fast pre-send QA workflow for pasted email content. Instead of waiting until after a launch to catch defects, it checks links, images, compatibility signals, and HTML quality before the send goes out.
Should I paste HTML or plain text?
HTML gives the richest result because link, image, compatibility, and HTML checks can all run together. Plain text still works when you are validating content early or do not have final HTML yet.
Does this save run history?
No. This public page is intentionally one-shot. Persistent run history, comparison over time, and operational workflows live in the authenticated campaign probe and email QA product surfaces.
When should a team use this instead of a manual checklist?
Use it whenever a broken link, missing image, or compatibility regression would be expensive after launch. That is usually lifecycle email, promotional campaigns, onboarding series, and conversion-critical transactional content.