Email verification

Verify every email before you hit send

One bounced campaign can poison your domain for months. Verify deliverability in bulk, inside the same sheet where you found the addresses — and send only to emails that are real.

Bring your own keys · Pay providers at cost · No credit card

Sender reputation is the asset. Bounces spend it.

Mailbox providers score your domain on every send. A clean list keeps you in the inbox; a dirty one — dead mailboxes, catch-all domains, disposable addresses — trains Gmail and Outlook to route you to spam. By the time open rates crater, the damage is done.

Verification is cheap insurance. In Liquid Rows it’s a column: every address gets checked, every row gets a status, and your sequences only ever see the good ones.

Every address, classified

✓ ok — mailbox exists ◐ catch_all — domain accepts everything ✕ disposable — throwaway provider ⓘ role — team inbox (info@, sales@) – invalid / unknown

Beyond the verdict, map quality scores, free-provider flags, role-address flags, and did-you-mean typo fixes into their own columns — then filter and route on any of them.

Verification that lives inside your pipeline

  1. Load the starter. Pick “Verify email” from the HTTP column templates and add your provider key as a workspace secret — one click, no request-building.
  2. Point it at your email column. Works on imported addresses or ones your enrichment columns just found.
  3. Run and filter. Verify the sheet, then save a view filtered to deliverable rows — your “safe to send” segment, always current.
  4. Sync the clean list. Push verified rows to your CRM or sequencer via webhook, or export the filtered CSV.
Why in-sheet verification beats standalone checkers: no exporting CSVs between tools, no stale results by the time you send, and verification composes with everything else — enrich → verify → filter → sync is one flow, not four apps.

Frequently asked questions

Why verify emails before sending?

Bounces destroy sender reputation. Once mailbox providers see your domain bouncing, even good emails land in spam. Verifying before a sequence sends keeps bounce rates low and open rates honest.

What do the verification statuses mean?

“ok” — mailbox exists and accepts mail. “catch_all” — domain accepts everything, so the address can’t be confirmed. “disposable” — throwaway provider. “invalid” — mailbox doesn’t exist. “unknown” — couldn’t be checked. Quality scores, free/role flags, and did-you-mean fixes can map to their own columns.

How does it work inside Liquid Rows?

It’s a one-click starter on an HTTP column: add your provider key as a workspace secret, point it at your email column, and run. Because it’s a column, it composes with your whole flow.

Can I verify emails I just enriched?

Yes — find the address with an enrichment column, verify it with the next column, filter to deliverable rows, and sync those to your outreach tool. One pipeline, no CSV shuffling.

Related

Send to real inboxes, not bounce logs

Verify your whole list in one run — inside the sheet that built it.

Start verifying →