Skip to main content
BounceBan verifies every kind of email address and specialises in the ones other providers give up on: accept-all (catch-all) domains and mailboxes sitting behind a Secure Email Gateway. Instead of returning those as risky, BounceBan tries to establish whether they are actually deliverable.

​
How to set up BounceBan

​
Authentication

BounceBan uses API key authentication:
  1. Sign up at bounceban.com
  2. Go to your API settings
  3. Copy your API key
  4. Paste the API key in Cargo when connecting

​
BounceBan actions

​
Verify email

Check whether an email address is deliverable. Required fields:
  • Email: The email address to verify
Optional fields:
  • Mode: regular (default) or deepverify. DeepVerify assumes the email’s domain is the owner’s current company website — for example when the email and the company both come from the same LinkedIn profile — which raises the success rate on accept-all addresses.
Credits: 0.1 credits per verification Use case: Validate emails before adding them to a sequence, and recover the accept-all addresses a stricter verifier would have discarded.

​
Verification results

Every verified email gets a result and a score from 0 to 100.

​
Response data

​
How the result comes back

Most addresses are verified straight away and the node finishes on the spot. The hard ones — accept-all domains, gateways that greylist the first connection — take longer than BounceBan’s synchronous window, so BounceBan keeps working in the background and calls Cargo back once it has an answer. The node pauses in the meantime and resumes on the callback, without occupying a worker. Each email is submitted exactly once, so a verification is never billed twice. If no callback arrives within 30 minutes, the node stops waiting and fails.

​
Rate limits

BounceBan allows 100 verifications per second. Cargo handles rate limiting automatically.

​
Best practices

  • Use DeepVerify when you know the email’s domain is the person’s current employer — it is what makes accept-all addresses resolvable
  • Treat risky with the score rather than as a rejection: that band is where accept-all and gateway-protected addresses land
  • Verify emails before importing them into your sending platform
  • Re-verify older contacts periodically, since email addresses decay