Verify Icypeas Results Before You Send

What Icypeas says

From Icypeas's pricing page, read 9 November 2026. Its documentation site was not readable from here, so export columns and status names are not described below.

• The pricing headline reads "Pay For Verified Emails Only", and every plan includes "Catch-All verification".
• Email Finder: 1 credit per found email. Email Verifier: 0.1 credit per email verification.
• Credits are non-expiring: "They never expire, even if you downgrade or cancel your subscription."
• Monthly plans start at $19 for 1,000 credits (Basic), $39 for 4,000 (Premium) and $89 for 10,000 (Advanced), plus VAT, with larger tiers above.

For how it compares with other finders see Icypeas alternatives. The page says nothing about how long a result stays valid.

Why a Icypeas row can still bounce

• Time since the search. Results you ran last month are older than they look (email valid but person left the company).
• Catch-all outcomes. Even with catch-all verification, an accept-everything server leaves some mailboxes unprovable (catch-all emails: what to do).
• Verifier credits spent early. Mixed files hold rows checked at different times.
• Merged files. Icypeas results combined with other finders. The oldest rows set your bounce rate.

The send-day routine

1. Export and note the date

Add an export-date column so you can re-verify by age later. Keep the original file untouched and work on a copy.

2. Clean

• Remove duplicate emails across every file you are loading.
• Limit contacts per company so one account does not get a burst.
• Tag catch-alls with the bulk catch-all checker.

3. Verify

Upload the CSV at /verify, pick the email column and run it. Each address gets a live SMTP check.

Result	Action
Valid	Main sequence
Risky (catch-all)	Second wave, best grades first
Risky (role, disposable, full)	Drop for outreach
Invalid	Suppress
Unknown	Re-check tomorrow

Catch-alls come back as risky with a grade and a reason (catch-all scoring).

4. Re-import and send in waves

Download the results, keep valid rows for your main sequence and load them into your sender. Catch-alls go a day later in a small batch. Pause when hard bounces pass your platform's line (bounce rate thresholds by platform).

5. Compare against your own numbers

Note the bounce rate by source. If Icypeas rows bounce less than other sources after your own check, that is evidence worth more than any pricing page. Bounce rate by source helps compare.

What to do with each group

Valid rows go into the main sequence, with the verification date kept in a column.

Risky catch-all rows are the judgment call. The server accepts anything during the check, so the best you get is a grade and a reason. Send the best-graded ones first, a day after the valid wave, and stop if bounces rise.

Risky role, disposable and full-mailbox rows are poor outreach targets.

Invalid rows go to a permanent suppression list so they never return in a later import (cold email suppression lists).

Unknown rows mean the server did not answer in time. Retry the next day.

A second opinion is cheap

Two different checks disagree sometimes, and the disagreement is useful: a row one tool calls fine and another calls risky is the row to hold back. Run your own check on send day and treat any mismatch as a reason to mail that row in the small second wave. Enrich then verify explains the order.

More on timing: how often to verify an email list. Compare approaches on the bulk email verifier page.

Try it on your own export

Upload a slice at /verify. The first 100 checks are free with a Google sign-in, no card.

Pro, $39 a month: Unlimited email verification.* Never metered, never cut off. See pricing.

*Fair use: the first 100,000 checks a month at full speed, then slower, never cut off.