Your first 100,000 email verifications or 10,000 work emails found are on us.100K verifications or 10K finds, free.Sign up today

HomeWho it's forSaaS signups and product-led growth

Your signups aren't checked. Check them.

Email Finder Verifier checks an address when someone signs up, so you can ask them to retype a typo instead of saving a bad one. Your developer adds one API call to the signup form's backend (the server code behind it). You can also upload your old signups as a CSV and see how many we couldn't confirm.

Free while in beta. No card needed.

Key takeaways

  • Your job: grow signups without growing bounces.
  • The result: typos get fixed at the form, and welcome emails go to inboxes that exist.
  • Time: the audit is a CSV upload. The form check is one API call for your developer.

Last updated 16 Nov 2026

01The problem

Your problem, and what EFV does

Your problem What EFV does
Welcome and onboarding emails bounce. Check the address as the user submits, and ask them to retype if we can't confirm it.
Trial signups with a mistyped email. When we can't confirm the address, you can ask the user to retype it while they're still on the page.
Sales chases leads with bad addresses. Check inbound leads before they route to a rep, and write the result to the lead record.
Your sender reputation is slipping. Fewer bad addresses on your list means fewer bounces to hurt it.
You don't know how bad the old list is. Upload the whole signup table as a CSV and see the split.

02The workflow

Do the audit first

You don't need a developer for step one.

  1. Export your signups

    A CSV with the email column. Include the signup date if you have it.

  2. Verify the list

    Open Verify or find a list, upload the CSV, choose Verify, pick the email column and start. Up to 5,000 rows a run. Download the CSV when it ends.

  3. Read the split

    Count Verified, Verified on a catch-all domain, and Not confirmed. This is your baseline.

  4. Plan the form check

    Hand your developer the use-case page below. It's one request to verify, with your key stored on the server.

  5. Decide what the form does with each answer

    Verified: continue. Not confirmed: show "Did you mean to type that?" and let them fix it or continue. Don't hard-block, because a real address can come back Not confirmed.

03Dev notes

What your developer needs to know

  • Call from your backend (the server code behind the form), never from the browser. The key must stay secret.
  • Some checks take several seconds. Save the signup first, then check in the background and flag the record. For an inline check, use a short timeout, like 10 seconds, and let the user in if it runs out. Never let a slow or failed check stop a real signup.
  • New accounts can send one request a second and have five running at once. If you expect more signups than that, ask in Slack before launch.
  • Save the result next to the user record, so sales and lifecycle emails can use it.

04Example

Example: one signup, flagged

Made-up data. A signup comes in, you save it, and the background check writes its answer onto the record.

Field Value
user_id 1042
email sam@acme.example
signed_up_at 2026-11-16 09:14
email_check not_confirmed
checked_at 2026-11-16 09:14
next action Show "Is sam@acme.example right?" on the next page load. Leave the address out of lifecycle emails until it's fixed.

When email_check is verified, nothing else happens. When it's null, the check couldn't run, so a retry goes on your list.

Audit your old signups first. It's a CSV upload, free in beta.

Sign up for free

05FAQ

Questions, answered

01Will this block real users?

Not if you build it the way above. Treat Not confirmed as "ask to retype", not "reject". A real address can come back Not confirmed.

02Does it stop fake signups?

It tells you whether we could confirm the mailbox. It's not a fraud tool, so don't use it as one.

03How fast is the check?

Some checks take several seconds. Build the form so a slow check never stops a signup: save first, check in the background.

04Can I check signups I already have?

Yes. Export them as a CSV and use Verify or find a list. It runs up to 5,000 rows at a time.

05What do I do with the answer in my database?

Save verified next to the user record, with the date you checked. Then leave unconfirmed addresses out of lifecycle and sales emails until someone fixes them.

06Can I check leads before they reach sales?

Yes. Run the same verify request in your lead flow, then route on the answer. The help center has Zapier, Make and n8n steps.

07Start today

Start with an audit of your old signups

Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.