Skip to content

// use case · Email marketers, newsletter operators, lifecycle teams and developers responsible for deliverability.

Clean your email list before the next send hurts your sender reputation

Run each address through /v1/verify, which checks syntax, disposable domains, DNS and MX, then asks the mail server about the mailbox without sending a message. Remove invalid, decide on risky (catch-all, role, full mailbox), and retry unknown later. Batches of up to 50 go through /v1/verify/batch, and small lists can be uploaded as a CSV in the dashboard.

The problem

  • Our last campaign bounced badly and the ESP sent us a warning.
  • The list is years old and nobody knows how many addresses still work.
  • We imported a list from an event and it is full of typos.
  • Open rates dropped and we suspect we are landing in spam.

How pingutil solves it

  1. 1

    Export and dedupe

    Export the audience from your ESP and remove exact duplicates so you do not verify the same address twice.

  2. 2

    Verify in batches

    Send up to 50 addresses per call to POST /v1/verify/batch, or upload a CSV of up to 50 rows in the dashboard.

  3. 3

    Act on status

    Suppress invalid. For risky, look at reason: accept_all and role_based may be fine for engaged subscribers. Retry unknown later.

  4. 4

    Fix typos

    did_you_mean suggests a likely intended address (gmial.com to gmail.com). Use it to reach out through another channel or correct imports.

Fields you will use

Response fieldWhat to do with it
statusKeep, suppress or review each address
reasonSeparate mailbox_not_found from accept_all and greylisted
scoreSort risky addresses by deliverability confidence
did_you_meanCorrect obvious domain typos
checks.catch_allFlag domains that accept every address
curl -X POST https://pingutil.com/v1/verify/batch \
  -H "Authorization: Bearer $PINGUTIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "emails": ["jane@stripe.com", "bob@gmial.com", "x7f3k@mailinator.com"] }' \
  | jq '.results[] | {email, status, reason, did_you_mean}'

Compared with the alternatives

Dedicated list-cleaning services handle very large files with asynchronous jobs, webhooks and native ESP integrations, and some are priced for bulk volume. That is the better fit for cleaning hundreds of thousands of addresses at once. pingutil suits smaller lists and ongoing hygiene through the API, with the same key also covering signup checks and company data.

See provider comparisons →

Limits to plan for

  • Catch-all domains and servers that refuse to answer cannot be confirmed; they come back risky or unknown, never valid.
  • Verification has a budget per account (300 addresses a day and 3,000 a month on the Free plan, API and CSV combined), so very large one-off cleans need Enterprise limits.
  • There are no asynchronous jobs or webhooks for the API; batch calls are synchronous with up to 50 addresses each.

Common questions

Should I delete risky addresses?
Not automatically. accept_all addresses on a catch-all domain often belong to real people. Keep engaged ones, and send unengaged risky addresses a re-permission email or suppress them.
Why are some results unknown?
The mail server greylisted, rate-limited or refused to answer. Those are cached briefly, so retrying later often gives a definitive answer.
Does verification send an email to the address?
No. The prober stops at the SMTP RCPT TO step and never sends a message.

Read next