Skip to content

// use case · SDRs, outbound agencies, growth teams and founders running cold email through sequencing tools.

Verify prospect lists so cold email bounces do not burn your domain

Before a list goes into your sequencer, verify each address with /v1/verify and remove anything invalid. Catch-all domains come back risky with reason accept_all, so you can send to them from a lower-volume inbox or skip them. Add a /v1/lookup call when you also want the company profile for personalization.

The problem

  • Our sending domain got flagged after one bad list.
  • The list vendor said the emails were verified, but bounces say otherwise.
  • Half the prospects are at catch-all domains and we have no idea which ones exist.
  • We keep emailing info@ and sales@ addresses that nobody reads.

How pingutil solves it

  1. 1

    Verify before import

    Run the list through POST /v1/verify/batch in chunks of 50 before it touches your sequencing tool.

  2. 2

    Drop invalid, segment risky

    Remove status invalid. Put accept_all and role_based addresses in a separate, slower campaign or skip them.

  3. 3

    Re-verify old lists

    Definitive results are cached for 30 days. For lists older than that, verify again before each new campaign.

  4. 4

    Personalize from the domain

    Call /v1/lookup for company.description, company.industry and company.tech_categories to write a relevant first line.

Fields you will use

Response fieldWhat to do with it
statusRemove invalid before sequencing
checks.catch_allRoute catch-all prospects to a lower-volume inbox
checks.role_basedSkip shared inboxes like info@
company.descriptionWrite a relevant opening line
import os, requests

def verify_chunk(emails):
    r = requests.post(
        "https://pingutil.com/v1/verify/batch",
        headers={"Authorization": f"Bearer {os.environ['PINGUTIL_KEY']}"},
        json={"emails": emails[:50]},
        timeout=120,
    )
    r.raise_for_status()
    return r.json()["results"]

keep, catch_all = [], []
for res in verify_chunk(prospects):
    if res["status"] == "valid":
        keep.append(res["email"])
    elif res["checks"]["catch_all"]:
        catch_all.append(res["email"])

Compared with the alternatives

Many outbound teams rely on the verification built into their prospecting database or sequencer, or use a dedicated verifier for big files. Built-in checks are convenient but often opaque about catch-all handling. pingutil gives you an explicit status, reason and score per address, and it never labels a catch-all address valid.

See provider comparisons →

Limits to plan for

  • Catch-all servers accept every address, so no SMTP check can tell you whether a specific mailbox exists there.
  • Some providers (for example Yahoo) accept everything at RCPT TO and come back risky or accept_all.
  • The Free plan verification budget (300 a day, 3,000 a month) suits steady prospecting; very large lists need Enterprise limits.

Common questions

Is it safe to send to catch-all addresses?
It is a gamble. Some will bounce later. Send to them in small volumes from a separate inbox and watch the bounce rate.
How often should I re-verify a prospect list?
Before each campaign if the list is more than about a month old. B2B addresses decay as people change jobs.
Can it find email addresses for me?
No. pingutil verifies and classifies addresses you already have. It is not an email finder.

Read next