Skip to content →
Verifier
  • Integrations
  • Security
  • Pricing
Log inGet started

From a raw listto a safe send.

Get started free

No email is sent during a check. The free plan includes 100 checks a month.

Verifier

Product

Email verificationWeb workspacePricingIntegrationsChangelog

Features

Single checksFind emailList cleaningScores and reasonsDelivery feedbackSuppression listOngoing re-checksAPI and SDKsTeam workspace

Use cases

Email marketingMarketing operationsSignup formsPlatforms and agencies

Resources

Resource hubGuidesBlogSecurity

Company

ContactPrivacyTermsResponsible disclosure
Verifier

© 2026 Oppulence Engineering · Verifier

Use cases/01 of 04/Email marketing

Protect your sender reputation

Check lists before each campaign and keep your bounce rate low, so your mail reaches the inbox.

Get started freeList cleaning
Fig. 1List quality

7.1 Quality score

Threshold 70
88 · Ready to send
41 · Held for review
0255075100

7.2 What each list holds

October newsletter4,511 rows
acme-launch.csv2,180 rows
  • valid
  • risky
  • invalid
  • unknown
Sample lists · fictional domains
When
Before each campaign
Input
A CSV from your platform
Output
A clean file to import back
After the send
Bounces come back as suppressions

§ 1

Why it matters

Bounces send your next campaign to spam

Mailbox providers watch bounce and complaint rates. When they rise, your mail goes to spam, and your email platform may pause your account.

For lifecycle and newsletter teams that send to lists they already have.

Fig. 2Without and with Verifier
WithoutWith Verifier
  1. ×Without: An old list goes out, and the bounce rate goes up.→✓With Verifier: The list is checked the day before the send.
  2. ×Without: Mailbox providers move the next campaign to spam.→✓With Verifier: Only rows marked safe or fixed go to the platform.
  3. ×Without: Bounced addresses come back with the next import.→✓With Verifier: Bounces after the send become suppressions.

§ 2

How it works

Clean before, learn after

Clean the list before you send. Connect your email platform, so bounces and complaints are suppressed after the send.

  1. 2.1Upload the campaign list.
  2. 2.2Send only to addresses that are safe to send.
  3. 2.3Let delivery feedback suppress what bounced.
Fig. 3Rows in, actions out

newsletter.csv

email,first_name[email protected],Ada[email protected],Sam[email protected],[email protected],Lee

Export · all rows

original_email,effective_email,remediation_classification[email protected],[email protected],safe[email protected],[email protected],fixed[email protected],[email protected],review[email protected],[email protected],drop
Export columns trimmed · your own columns stay in the file

§ 3

What you get

What you get.

  1. 3.1Safe-to-send in one columnExport a file with one clear yes or no for each address.
  2. 3.2Fewer repeat bouncesBounced addresses are suppressed before they come back in the next import.
  3. 3.3Domain reputationCheck a domain against 8 blocklists, such as Spamhaus ZEN, and read its SPF and DMARC records.

Table 3 · Export files

FileRows in it
safeRows to keep as they are.
fixedRows with a corrected address, such as a fixed domain typo.
reviewRows to look at before you send.
dropRows to suppress.
allEvery row, with its result and its action.

§ 4

In practice

Typical uses.

  • Case 4.1

    Re-engagement campaigns

    Check old subscribers before you try to win them back. These lists bounce the most.

Works with the tools you send from.

All integrations
  • SendGrid
  • Mailgun
  • Postmark
  • Amazon SES
  • CSV files
  • REST API

Questions

Before you start.

Do I still need my email platform's bounce handling?

Yes. We add a check before the send and one shared suppression list across tools.

Continue reading

  1. 01List cleaning
  2. 02Delivery feedback
  3. 03Start free