HomeGuidesBlock fake and temporary signups
How to block fake and temporary email signups
Use three layers: a typo check in the form, a block list of known temporary domains, and a background verify with Email Finder Verifier. Save the signup first and never hard-block on one failed check. A temporary inbox can still be real, so a blocklist does that part.
Free while in beta. No card needed.
Key takeaways
- The problem: signup forms accept whatever people type, so bad addresses get saved.
- The fix: three layers, with a soft check instead of a hard block.
- The catch: a temporary inbox can be a real, working address, so verify alone won't spot it.
Last updated 16 Nov 2026
What you're dealing with
A disposable email is a temporary address people use to sign up without giving their real inbox. Then there are plain typos and made-up addresses. All three end up in your list, and the first email you send, the welcome message, bounces. Do that often enough and mailbox providers start to distrust your domain.
Email verification at the form moves the fix to the moment the person is still on the page and can retype.
Three layers
| Layer | What it catches | What it misses |
|---|---|---|
| 1. A typo check in the form | gmial.com, missing dots, spaces |
Fake addresses that look right |
| 2. A block list of known temporary domains | Temporary inboxes from known services | New services not on the list yet |
| 3. A verify check with the email verifier | Addresses we can't confirm | Temporary inboxes that are real and working |
Verify tells you if the mailbox is confirmed. It doesn't tell you if the inbox is a temporary one, so layer 2 does that job. For a public block list, many teams use the community-kept disposable-email-domains list on GitHub.
Set it up
Make a key for the form
In the dashboard, open API keys and create one named "Signup form". Keep it on your server. Never put it in a web page or app.
Check the typo and block list first
These are quick and run in the browser or your backend. Show a friendly line like "Did you mean gmail.com?" for typos.
Save the signup, then verify in the background
Send a GET request to the verify address from your server, with your key in the
X-API-Keyheader. Flag the record with the result. If you must check inline, use a short timeout and let the person through if it runs out.Decide per answer
Verified: carry on. Not confirmed: ask the person to check the spelling, and let them continue if they say it's right. Timeout or error: keep the signup and check it later.
Audit what's already there
Export your signups as a CSV, choose Verify in Verify or find a list and download the results. Up to 5,000 rows a run.
See the full backend example in Verify website signups.
Don't turn away real people
- Don't hard-block on one failed check. A real address can sometimes come back Not confirmed.
- Say why, in plain words. "Please use your work email" beats "Invalid email".
- Offer a way forward. Let people retype, or continue if they say it's right.
- Keep the key on your server. Never call the verify address from the browser.
If you have no tool
Without a verify check, you can still add a typo check and a block list. They're free to set up and stop the most obvious fakes. Add a "confirm your email" link in your welcome message as a backstop: the real owner clicks it, the others don't.
Check the emails already in your signup list. Free while in beta.
Sign up for free01FAQ
Questions, answered
01What is a disposable email address?
It's a short-lived address made to sign up without giving a real inbox. Several services hand them out for free.
02Can Email Finder Verifier tell if an address is disposable?
It tells you if we could confirm the mailbox. It doesn't label temporary inboxes, so use a block list alongside it.
03Should I block every signup that fails a check?
No. A real address can come back Not confirmed. Ask the person to check it, then let them continue.
04Does the check slow down my form?
Some checks take several seconds. Save the signup first and check in the background, or use a short timeout inline.
05What about the signups I already have?
Export them as a CSV and verify them. It's a good first step, because it shows the size of the problem.
06Is a typo check enough?
It's a good start, but it can't tell a made-up address from a real one. Add the other layers.
08Keep going
Where to next
- SaaS signups and product-led growthCheck the email on every trial signup, and audit the ones already in your database.
- RevOps and sales opsCheck CRM contacts, re-find the ones that went bad, and re-import a cleaner list.
- GTM engineers and Clay buildersTwo HTTP columns in Clay or n8n: find the work email, then verify it. One key.
08Start today
Audit 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.