How to Verify Email Addresses From Jotform Submissions

To verify email addresses from Jotform submissions, export the submissions as a CSV, upload the file to an email verifier, and follow up with the addresses that come back valid. Jotform confirms an email field is shaped like an address; it cannot tell whether the mailbox exists. SimpleVerifier checks that on the verify page: upload the export, download valid, risky and invalid with a reason, and keep the status next to each lead. There is no native connection between the two, so the route is export, upload, download. Pro is $39 a month, and 100 checks are free.

A note on Jotform's screens. We tried to confirm the current export menu names on Jotform's help pages on 10 November 2026 and could not read the export instructions there, so this guide does not quote Jotform's menus. Use Jotform's own export option for submissions and choose a CSV or spreadsheet format; what matters is that the file has an email column.

Why verify form submissions

A public form is the easiest place for bad addresses to enter your list. They arrive in four ways:

• Typos. gmial.com is a format-valid domain. The field accepts it and the message never arrives.
• Fake addresses. Visitors invent addresses to get a download or a coupon.
• Disposable inboxes. They accept one message and vanish.
• Bots. Automated submissions fill forms with random addresses on real domains.

Replying to a handful of leads by hand is one thing. Sending an automated sequence, a newsletter or a confirmation mailing to hundreds of submissions is another; the bounces count against your sending domain, and a run of them can push your mail to spam. See why emails bounce.

Step 1: Export the submissions

Use Jotform's export option for your submissions and choose CSV or a spreadsheet. If you export a spreadsheet, save it as CSV before uploading. Keep the email column and an identifier such as a submission ID or date. You do not need to send every field to a verifier; trim columns you do not need, especially free-text answers and phone numbers.

Step 2: Tidy the file

• Remove repeat submissions with the duplicate email remover. People often submit a form twice.
• Fix common domain typos with the email typo corrector.
• To turn an export into a bare list of addresses, use the form responses to email list tool.
• If an answer contains line breaks and the file looks broken, try the CSV broken row fixer.

Step 3: Verify the file

1. Open the verify page and sign in with Google. The first 100 checks are free, no card.
2. Upload the CSV. If it has more than one candidate column, the page asks which holds the address.
3. Wait for the list to finish and download the results.

Each row returns a status, a reason and a send-advice column.

Status	Meaning	What to do
valid	The mail server confirmed the mailbox exists.	Safe to send.
risky	Delivery is not confirmed: a catch-all domain, a role address such as info@, or a provider that will not say.	Keep out of large sends. Test in a small batch.
invalid	Bad format, no mail server, disposable address or mailbox not found.	Do not send.

A risky result is not a rejection. On a catch-all domain the server accepts every address at the door, so a particular mailbox cannot be confirmed from outside. For form leads, that often means a small business that asked for something. Reply to them one to one rather than adding them to a bulk send. The catch-all send limit calculator helps size a cautious batch.

Step 4: Act on the results

Match results back to submissions on the email address, then:

• Valid. Follow up, add to your CRM or mailing list.
• Invalid. If the person genuinely wanted a reply, look for another channel in the same submission, such as a phone number. Do not email the address.
• Risky. One-to-one replies are fine. Hold back from newsletters until the address shows engagement.

Keep the date you checked each address. Lists decay, and re-verifying before a campaign is cheap.

Check live instead of afterwards

If the form runs all the time, an export is a repeating chore. Two ways to check each address as it arrives:

• An automation tool. Jotform can pass submissions to other tools; check Jotform's documentation for its current options. In the tool, add an HTTP request step to the SimpleVerifier API and branch on the result. See our pages for Zapier, Make and n8n.
• Your own code. If submissions go to your server through a webhook, call the API from there. The API docs list the fields and the language guides show working code.

The call is GET https://simpleverifier.com/api/v1/verify?email=... with a bearer key from the API keys page. Pro includes 10,000 API calls a month at 120 calls a minute per key.

Rules for a live check:

• Do not call the API from the browser. The key must stay on a server.
• Treat a timeout as unknown. Save the lead and verify later in a batch; never mark it valid.
• Flag, do not silently drop. If an address comes back invalid, ask the person to check the spelling when possible. If the check happens after submission, tag the lead and move on.

For the form itself, the sign-up form widget and signup protection recipes show how to catch bad addresses where they are typed.

A quick triage for an old backlog

If your Jotform has run for a year, you probably have thousands of submissions nobody has followed up. Do not mail them all in one go. Verify the whole export, then send in waves: the valid addresses from the last few months first, then older valid ones, with risky and old rows last or never. Watch the bounce count after each wave and stop if it climbs. A first message to a long-dormant list should also remind people how they came to be on it, since many will have forgotten the form.

Common mistakes with form leads

• Exporting every field. A verifier needs the address. Keep names, phone numbers and free-text answers out of the upload.
• Treating risky as a no. Many genuine small-business leads sit on catch-all domains. Keep them and reply one to one.
• Never re-checking. An address that was valid when someone filled the form can be closed months later.
• Losing the verdict. If the result lives only in a downloaded file, the next person will check the same addresses again. Save the status alongside the lead.

What it costs

SimpleVerifier Pro is $39 a month. The first 100,000 checks a month run at full speed, then they run slower, and you are never cut off. You can try 100 free checks first by signing in with Google, no card. See pricing for the other plans.

Bottom line

A form field makes sure an email looks like an email. Verification makes sure someone can receive it. Export the submissions, check the file, and follow up with valid addresses first. Try the 100 free checks on your latest submissions and see how many would have bounced.