. = =:-
. : = + . ==:. .=:+-.- .. .
: =:-.+-: : - :+.::- :. - +
. -.:.:.-..: ==. :. ..:..: -
.:. - . +=..+::-. = .-::...==...-..+:. .
+ :+ =. : :+...+. .+. .:
. : + .
. . Bounceless vs Mailgun: an honest comparison
Mailgun is a sending platform first, and its validation lives inside that: the Validate product sits beside Send and Optimize, shares the same API key and bill, and leans on the cached send data of a mail firm that moves email at industrial scale. That convenience is real when Mailgun is already your system of record for mail. Bounceless approaches the same address from the other end, as a standalone engine that grades a list before it ever reaches a sending tool and prints a send, review, or suppress call on every row at export.
Bounceless is a standalone verification engine: every result carries a numeric confidence figure, reason codes, and a send, review, or suppress call, with Catch-All Evidence grading B2B catch-all domains, Doorman on the roadmap gating signup forms, blacklist and inbox-placement monitoring on the roadmap inside the product, and native MCP access for AI agents. Mailgun validates too, as a Validate add-on beside its sending platform, returning a per-address risk score and a free list-health preview, but priced as a per-hundred add-on to a paid sending plan and without the reason codes or the explicit pre-send call.
How we score: one point per round. Price rounds are computed from dated public figures; feature rounds show their verdict on the row, so every point is auditable.
Feature-by-feature, sourced
Every Mailgun row below links to the public source it came from, or says "Not publicly disclosed" instead of guessing. One point per round: a tie means both products cover it, rounds without public information score nothing, and any price rounds in the Pricing band below count toward the same score.
Facts last verified: 2026-07-08
| Feature | Bounceless | Mailgun | Round |
|---|---|---|---|
| Per-address score on every result | Every check returns a numeric confidence figure you can threshold and sort on | Assigns a unique risk score to each address, a scored output of its ownsource | [ TIE ] |
| Reason codes explaining each result | A set of reason codes rides with every score, so a low grade says which signal pulled it down | Not publicly disclosedsource | [ BOUNCELESS ] |
| Pre-send recommendation (send / review / suppress) | The Pre-Send Decision reads the score and codes and writes one send, review, or suppress call onto the export | Not publicly disclosedsource | [ BOUNCELESS ] |
| Catch-all address handling | Catch-All Evidence weighs premium deep catch-all domain detection billed at five credits fresh or three if already cached against the B2B domain behind the catch-all and hands back a graded confidence, not a bare label | Lists catch-all address verification as one of its checks, with no scoring method or B2B-specific handling documentedsource | [ BOUNCELESS ] |
| Dedicated validation API | A REST verification API that returns the confidence figure, the codes, and the decision in one response | A real-time Email Validation API with sub-second returns and an open-source client librarysource | [ TIE ] |
| Bulk list validation | Dashboard CSV uploads run through the exact result shape the API returns | Upload a CSV and verify a whole list, with results back in minutes for large filessource | [ TIE ] |
| Free pre-purchase list-health preview | Not offered as a distinct free preview: our free monthly credits let you sample real results instead | A free aggregate preview scores overall list health and risk level before you pay to clean anythingsource | [ MAILGUN ] |
| Real-time signup-form verification | Doorman signup-form gating is on the roadmap — a planned real-time form gate, not a shipped platform surface today | The validation API embeds directly in a signup page or form to check entries as they are typedsource | [ TIE ] |
| Blacklist monitoring and inbox placement | Blacklist watch on the roadmap and inbox-placement tracking on the roadmap are on the roadmap — not a shipped bundle today | Reputation monitoring and inbox placement are sold on the separate Optimize product, not bundled with Validatesource | [ TIE ] |
| Verification without a sending plan | Runs standalone, with a free monthly tier and pay-as-you-go packs, no sending relationship required | Validation is an add-on to a paid Mailgun sending plan, bundled only at the Scale tier and absent on the free plansource | [ BOUNCELESS ] |
| AI-native access (MCP and agent skills) | An MCP server and agent skills hand the full result contract to AI agents, the score, the codes, and the decision, with no wrapper to write | Not publicly disclosedsource | [ BOUNCELESS ] |
Choose Bounceless if
- ✦You want a decision, not just a score: every result carries reason codes and an explicit send, review, or suppress call, not a risk number to interpret yourself.
- ✦You verify lists before they reach any sending platform and would rather not tie verification spend to a mail vendor or a sending plan.
- ✦Your lists carry B2B catch-all domains: Catch-All Evidence grades the domain behind them with premium deep catch-all domain detection billed at five credits fresh or three if already cached instead of a single catch-all check.
- ✦Your stack is AI-native: an MCP server and agent skills let agents read the score, the codes, and the pre-send call without any wrapper code.
Choose Mailgun if
- ✦You already send through Mailgun and want validation in the same API surface, dashboard, and bill.
- ✦You want to gauge a list before paying: Mailgun runs a free aggregate list-health preview that scores overall risk before you clean anything.
- ✦You are a heavy Mailgun sender already on the Scale tier: that subscription runs $90/mo and bundles a fixed block of 5,000 validations, so checks cost nothing extra until you exceed the included allowance.
- ✦You want validation checks named up front: RFC grammar, mailbox and MX verification, provider detection, disposable and role-based flags are all documented.
What we won’t guess
Pricing, honestly
Mailgun's best published validation rate (its Scale tier floor) applied to this volume; Basic and Foundation list a higher per-hundred rate, and every tier still requires a paid sending plan on top. The rate is flat, so it does not fall at volume the way a Bounceless pack does.
Beyond the table
Almost every large sending platform eventually bolts a validation product onto the side, because bad addresses are the sender’s own problem before they are anyone else’s. Mailgun is a clean example of the pattern. Validate sits in the same console as Send and Optimize, draws on the cached send data of a firm that moves mail at enormous scale, and bills through the same account. For a team whose mail already leaves through Mailgun, that adjacency is the whole appeal: one login, one invoice, one API key covering both the sending and the checking.
The trade that comes with a side-feature is depth of intent. Mailgun assigns each address a risk score and names its checks plainly, from grammar and mailbox lookups to disposable and role-based flags, and it offers a free preview that grades a list’s overall health before you spend on cleaning it. Useful, all of it. What the validation pages stop short of is telling you what to do with a given address. The risk score arrives without the reason codes that would let you argue with it, and nothing on those pages describes a single send, review, or suppress verdict written onto the export.
Bounceless is built from that missing verdict outward. A check comes back with a confidence figure, the reason codes that produced it, and a Pre-Send Decision spelling out send, review, or suppress. Catch-all addresses, the ones most tools wave through, get graded rather than guessed: Catch-All Evidence runs premium deep catch-all domain detection billed at five credits fresh or three if already cached against the business domain behind the address and hands back a graded confidence. Signup forms are covered by Doorman on the roadmap, which would turn a bad address away at the point of entry the way Mailgun’s embedded call does. Blacklist watch on the roadmap and inbox-placement tracking on the roadmap sit in the same product, where Mailgun parks that work on its separate Optimize line. And since agents are first-class here, an MCP server and agent skills pass the entire result to them without a translation layer.
There is also the plain matter of independence. Mailgun’s validation is an add-on to a paid sending plan, priced by the hundred and at its lowest only near the top of the sending ladder. Bounceless stands alone, with a free monthly tier and pay-as-you-go packs, so checking a list is never chained to where the mail happens to leave from. The table above lines up the published rates volume by volume. What it comes down to is not really who can check an address but what you get handed back: a bare score to weigh yourself inside the tool that also ships your mail, or an explained, graded call ready to trust before anything sends, on whatever platform you use.
-
.
+ += - -:. : - = . ++. .
.= . = +: : :+=. .:+ -..
+= + :.: +..+::..- +::.- --.+
. :- .-..:- + :..= = =:+:..
::. . ..:= . ..- = . :
. := .- . -.. . . .. Frequently asked questions
How is this comparison different from the Mailgun integration guide on this site?
Two different questions. The integration guide at /integrations/mailgun walks a workflow: pull a mailing list out of Mailgun, verify it in Bounceless, and push the clean file back. This page instead weighs Mailgun's own Validate product against the Bounceless verification engine, capability by capability. Same vendor, different lens: one is about fit inside a Mailgun-centric workflow, the other about what each verification product actually returns.
Does Mailgun's risk score do what a Bounceless confidence score and Pre-Send Decision do?
Partly. Mailgun does assign a unique risk score to each address, so it is not a bare status label, and this page credits that as a scored output. What the checked pages do not show is the reason codes behind that score or an explicit send, review, or suppress call on the export. Bounceless returns the score, the codes that explain it, and the pre-send decision together, so the follow-on question of what to actually do with a borderline address is already answered rather than left to a threshold you tune.
How does Mailgun validation pricing compare to Bounceless?
Mailgun prices validation as a per-hundred add-on to a paid sending plan, quoted as a floor that reaches its lowest level only on the top sending tier. The comparison table applies Mailgun's best published rate at each matched volume and computes the difference; even at that best-case rate, the Bounceless pack comes in lower at every volume shown, and the gap widens as volume climbs because the Mailgun rate is flat while Bounceless packs discount with size. Remember the sending subscription sits on top of the validation line on Mailgun's side.
Is Bounceless a drop-in replacement for Mailgun validation?
For the verification step, yes, with a mapping note: Mailgun's risk score and status translate to a Bounceless confidence figure and reason codes, so logic built around a risk threshold needs a policy update rather than a rewrite. Signup-form checks move from the embedded Mailgun API to Doorman on the roadmap, and reputation work moves from the separate Optimize product to the blacklist and inbox-placement monitoring on the roadmap built into the platform. The one thing that does not move is your sending: Bounceless verifies, it does not send, so you keep Mailgun or any ESP for delivery.
Does Bounceless plan inbox placement and reputation monitoring on the roadmap like Mailgun Optimize?
Not as a shipped bundle today — those surfaces are on the roadmap. Mailgun packages reputation monitoring on the roadmap and inbox placement on Optimize, a separate product line with its own pricing page apart from Validate. Bounceless keeps blacklist monitoring on the roadmap and inbox placement on the roadmap inside the same platform as verification, with Doorman on the roadmap also on the roadmap, planned for a single bill. The practical difference today is procurement shape: one planned platform on our side, a validation add-on plus a deliverability product on Mailgun's side.
Can AI agent run Bounceless verification on its own?
Yes. Bounceless exposes an MCP server and agent skills, so an agent can submit an address and read back the confidence figure, the reason codes, and the send, review, or suppress call directly, with no wrapper code standing between the agent and the result. An agent triaging inbound leads or scrubbing a list acts on the pre-send call itself. Mailgun's public validation pages describe no comparable agent surface, which is why that row of the table is marked undisclosed rather than guessed at.
Are Mailgun's accuracy and bounce-reduction numbers independently verified?
No. Mailgun markets its validation on the scale of its cached send database and on self-reported gains in bounce rate and open rate. Those are the vendor's own figures, gathered on its own terms, not results measured against a shared benchmark that ran both engines on one list. This page deliberately keeps them out of the comparison scoring and records them only as Mailgun's own marketing claims rather than something this page independently checked.
Keep comparing
= .+ :
: : . =-+:: .=: : + . .. +
.. : ..--:.+++ = : : +:. .+=.=.=:: +
: -.=+ :-....=:= .- .. : .- -: =
. . +. = - . .:: -::. .:: :.==:.
- . : = : . . : ::-.:.: . +. +
-. == .= :=: . =. .-
: . - - ::. .+= . Spot risky contacts before your next send, not after
Test your list on 1,000 free credits: no card, no commitment, same engine as the playground above.