Email Validation on Signup Forms: What to Check and When
Which checks to run on a signup form, in which order, and how to keep validation from blocking real users.

Email validation on signup forms decides whether the people who sign up can ever hear from you. A mistyped address means a lost user, a bounced welcome email, and a small dent in your sender reputation. This guide shows which checks to run, in which order, and how to keep them from getting in the way of real users.
TL;DR#
- Check the format in the browser, and suggest a fix for likely typos instead of rewriting the address.
- Run a real check on your server: does the domain accept mail, and is the address disposable?
- Use double opt-in when you need proof that the person owns the address.
- Never let a slow or failed validation call block the form.
Why does email validation on signup forms matter?#
Every address you collect feeds something later: a welcome email, a password reset, a trial nurture. If the address is wrong, none of that arrives. The user may blame your product, and you may never know why they went quiet.
Bad addresses also hurt you. Mail sent to addresses that do not exist produces bounces, and a high bounce rate is a signal mailbox providers watch. Catching the error when the person is still on the page costs one second. Catching it after the bounce costs a user.
What checks can you run on a signup form?#
There are four layers. Each one catches things the previous one misses.
| Layer | Where it runs | What it catches | What it misses |
|---|---|---|---|
| Format check | Browser | Missing @, spaces, empty fields | Typos in the domain |
| Typo suggestion | Browser | gmial.com, hotmial.com |
Typos that look like real domains |
| Server-side check | Your server or API | Domains with no mail server, disposable addresses | Mailboxes that do not exist on a catch-all domain |
| Confirmation email | Inbox | Wrong owner, fake sign-ups | Users who never open the email |
A regular expression alone is not enough. Both typo@gmial.com and fake@tempmail.com look valid to a format check, as Suped's guide to signup validation points out.
How should you handle typos?#
Show a suggestion and let the user decide. If someone types name@gmial.com, display "Did you mean gmail.com?" with a button to accept it. Do not change the field for them. The address may be right, and a silent rewrite sends the welcome email to the wrong person.
Bird's guide to preventing email typos covers the same idea, along with other form patterns. A "confirm your email" second field helps less than it seems, because people tend to repeat the same mistake in both fields.
What should the server-side check do in email validation on signup forms?#
The server check is where you learn whether the address can receive mail. A good one looks at:
- The domain. Does it have a mail server (an MX record)?
- The mailbox. Does the receiving server accept this address?
- Disposable domains. Is it a throwaway service?
- Role addresses. Is it something like
info@orsales@?
You can build the first check yourself. The mailbox check is harder, because it needs an SMTP conversation with the other server and careful handling of servers that accept everything. That is why most teams call a verification API. The Tomba Email Verifier is one option, and the Tomba API lets you call it from your own backend. Each verification uses one verification credit.
For servers that accept all addresses, read our guide to catch-all email verification.
Should you block or warn?#
It depends on the result.
- Invalid domain or clearly undeliverable: block, with a clear message.
- Disposable address: block or warn, depending on how much a fake account costs you.
- Risky or unknown (for example a catch-all domain): accept the address, and flag it in your database.
- Validation service down or slow: accept the address and check it later.
The last rule matters most. Real-time checks must not become a point of failure. SendGrid's documentation on real-time validation describes the feature in detail, and the same advice applies to any provider: set a short timeout and fail open.
When do you need double opt-in?#
Validation tells you the address can receive mail. It does not tell you that the person who typed it owns it. Double opt-in does. You send a confirmation link, and the account stays inactive until it is clicked.
Use both when it matters, for example for newsletters, or where a stranger could sign someone else up. Use validation alone when friction is costly, such as a free trial that must start in seconds. The two answer different questions: validation checks technical correctness, and opt-in checks consent.
A simple flow for email validation on signup forms#
- The user types an address. The browser checks the format and shows a typo suggestion if needed.
- On submit, your server calls the verification API with a short timeout.
- If the result is invalid, return an error that names the problem.
- If the result is valid or risky, create the account and send the welcome email.
- If the call times out, create the account and queue a recheck.
- Store the verification result next to the address, so marketing and sales can use it later.
How do you keep the form accessible?#
Put the error message next to the field and tie it to the input, so screen readers announce it. Do not rely on color alone. Keep the message specific: "This domain cannot receive email" is more useful than "Invalid email". Do not clear what the user typed.
Frequently asked questions#
Is a regex enough to validate an email address?#
No. It confirms the shape of the address, not whether it can receive mail. Use it as the first layer, then run a server-side check.
Does real-time validation slow the form down?#
It adds a network call. Keep the timeout short, run it on submit or when the field loses focus, and accept the address if the call fails.
Should I block disposable email addresses?#
It depends on your product. If fake accounts cost you money or abuse your free tier, block them. If not, a warning is often enough.
Can I validate emails I already collected?#
Yes. Run your existing list through a bulk check. The Tomba bulk tools accept a CSV file.
Next step#
Add email validation on signup forms this week: a typo hint in the browser and a server-side check behind it. To try the check on a few addresses first, use the Tomba Email Verifier.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA