Back to Blog

Should you block disposable email addresses at signup?

What a disposable email blocklist stops, what it misses, who it turns away and what it costs to keep current, with a break-even you can run yourself.

It's Tuesday, 8:15 a.m., six days after the best pull request you've merged all quarter.

Last Wednesday at 4:40 p.m. you finally got to it. You'd looked up how to block disposable email signup attempts, found a public list of about 4,000 throwaway domains and wired it into your form in under 40 lines. On Thursday at 9:05 a.m. the throwaway-domain row in your dashboard read zero. You sent your co-founder a screenshot.

Now the weekly usage report is open, and it doesn't match the screenshot.

This is a scenario, with sums you can redo using your own numbers. Your free plan gives 500 credits, and an account that uses them all costs you $1.20. The week before the list went in, 378 new accounts on throwaway domains drained their credits and never came back. This week you count accounts that did the same thing, whatever address they used.

Before the list:  378 accounts x $1.20 = $453.60 a week
After the list:   290 accounts x $1.20 = $348.00 a week
Saved:             88 accounts x $1.20 = $105.60 a week

Your list earned those 88. The other 290 still used everything and left, some on domains your list has never heard of and most on ordinary mailboxes it was never going to touch. That's $18,096 a year ($348 × 52), and the row that told you the problem was solved still says zero.

So that's the first way to lose. The second one only shows up if you go looking, so you open the log of rejected signups. There are 140 this week, and most are gibberish. Then you reach Saturday, 10:52 p.m.: a first name and a last name, on a domain the list calls throwaway. They'd come from your pricing page. They submitted the form once, read "Please use a valid email address" and closed the tab. It's a forwarding address, the kind careful people use so they don't have to hand their real one to every new app. They didn't open a ticket or try again.

You can't know how many there were, because a rejected row has nobody behind it to ask. Say 12 of the 140 were real people, and 1 in 10 of them would have paid for your $29 plan for a year.

12 people x 1 in 10           = 1.2 customers a week
1.2 customers x $29 x 12      = $417.60 of revenue a week
$417.60 lost / $105.60 saved  = nearly 4 times what the list saved

Over a year that's $21,715.20 that never came in ($417.60 × 52), on top of the $18,096 still going out. Together they're $39,811.20, more than two and a half months of runway for a company spending $15,000 a month. Your conversion rate dips by an amount you'd put down to the season.

And now you have to choose. Loosen the list and keep paying for those accounts, or tighten it and turn away more people you'll never hear from. Neither choice comes with a number you can trust.

Why blocking disposable email at signup doesn't hold

A blocklist answers one narrow question: is this a domain someone has already reported as throwaway? The answer starts going stale the day you copy the list, because a new domain costs a few dollars and takes minutes to register.

Email verification can't rescue it. A throwaway inbox is a real inbox for as long as it lasts, so the code arrives and the verification passes. A domain set up to accept mail at any address passes too, and no public list will call it disposable.

The bigger gap is where the money goes. You pay when one person takes your free credits more than once, and an email domain says nothing about that. A unique-email rule has the same blind spot, because Gmail ignores dots and delivers jane+notes@gmail.com to Jane, so one mailbox can look like several people.

Here's what happens to the list once it's live.

NoYesYou add a public listabout 4,000 domainsThose domainsstop getting throughNew throwaway domainsgo liveNew accounts passyour signup formAnyone updatingthe list this week?The list fallsfurther behindSomeone adds domainsby handA real customer's domaingets listed by mistake
NoYesYou add a public listabout 4,000 domainsThose domainsstop getting throughNew throwaway domainsgo liveNew accounts passyour signup formAnyone updatingthe list this week?The list fallsfurther behindSomeone adds domainsby handA real customer's domaingets listed by mistake

Block disposable email, or hold back the benefit?

You have more options than yes or no. Doing nothing blocks nobody and pays for every throwaway account. The rest fail in different ways.

OptionWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Public list, added onceWell-known throwaway servicesEvery domain added since you copied itAnyone on a forwarding service it includesNothing at first, while it quietly ages
List you keep updatedMost known services, for nowNew domains until your next update, and all ordinary mailboxesThe same people, plus any domain added by mistakeSomeone's time, every week
Paid list, updated for youThe same, with less lagOrdinary mailboxesWhoever that provider gets wrong, and you can't see whyA fee per lookup, and a plan for when it's down
Hold back the free benefit, keep the accountWhatever your list catchesWhatever your list missesFewer people, since they can still payA no-credits state in your product

The last row changes the worst outcome. The person on Saturday night still gets an account and a reason.

You can price the rest. Say someone spends 30 minutes a week reading rejections and adding domains. That's 26 hours a year, or $2,080 at $80 an hour. Your list saved $105.60 a week, which is $5,491.20 a year, so it's $3,411.20 ahead. Each real customer it turns away costs you $348 ($29 × 12).

Break-even customers=(yearly savings−yearly upkeep)÷revenue per customer\text{Break-even customers} = (\text{yearly savings} - \text{yearly upkeep}) \div \text{revenue per customer}

$3,411.20 ÷ $348 is 9.8, so the tenth real customer you lose in a year puts the list in the red. The scenario above loses 62 (1.2 × 52). Run it with your real cost per free account.

So should you block? If free accounts cost you real money, yes, as a small filter on the free benefit with a way for people to reach you. If they cost next to nothing, skip it. Either way, it won't answer repeat accounts.

If you block disposable email at signup, do it this way

Log before you block. Run the list for two weeks and only record what it would have rejected. If that's a handful of accounts, stop there.

Take forwarding services off it. Apple's Hide My Email, for one, creates random addresses that forward to a person's own inbox. Read the list before you use it. A forwarding address usually means someone cares about their privacy.

Hold back the free benefit, and keep the account. Someone ready to pay you shouldn't be stopped by a list of domains.

Say why, and leave a door open. If they can reply, you get a chance to fix it. There's more on what to say when you deny someone.

Give the list an owner and a date. Name who updates it and when, and keep a short allow list for mistakes.

A message you can use

We can't add free credits with this email address. Try a different one, or reply here and we'll take a look.

The other basic fixes, and how they break

Most teams try these next, and each one does catch something.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny working inboxPeople whose code lands in spamDeliverability work
Unique emailsThe same address twiceEvery different addressAlmost nobodyVery little
Treating Gmail dots and plus addresses as oneOne Gmail inbox written several waysA second real mailboxPeople who sort their mail with plus addressesUpkeep as mail services change
CAPTCHASimple scriptsPeople signing up by handPeople using screen readers or privacy toolsFees and lost signups
Phone requirementCasual second accountsAnyone with another numberPeople without a reliable mobile numberA charge for every text
Card requirementCasual second accountsAnyone with another cardStudents and people who want to try firstFewer signups
One per IP addressRepeats on one connectionAny other networkOffices, campuses and householdsExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listStaff on company VPNsAnother list to maintain
Rate limitsBursts from one sourceA slow, steady trickleReal users in a busy hourTuning per route
Usage capsOne account overrunningEach new account's fresh capAnyone at the capDeciding when your product stops
Shorter trialsSome value per accountMore accounts make up the differenceEvery honest userFewer people reach paying
Manual reviewWhat a person can spotAnything spread out over weeksWhoever looks odd to a tired reviewerHours every week

Manual review sounds safe until you do the sum: 378 accounts a week at one minute each is more than six hours a week, spent guessing from the same rows you were. Stacking the others moves the cost onto honest visitors, who meet every step on their way in.

In this chart, upkeep means maintenance plus the signups a fix costs you.

Illustrative protection vs upkeepHelps at a priceWhere you want to beCheap and thinCostly and thinLow upkeepHigh upkeepLess protectionMore protectionUnique emailsEmail verificationStatic blocklistCAPTCHAUpdated blocklistCard requiredPhone requiredManual review
Illustrative protection vs upkeepHelps at a priceWhere you wantto beCheap and thinCostly and thinLow upkeepHigh upkeepLess protectionMore protectionUnique emailsEmail verificationStatic blocklistCAPTCHAUpdated blocklistCard requiredPhone requiredManual review

Nothing lands in the top left. Everything stronger than a cheap fix charges you in hours or in real signups.

Evaluate the claim instead of the domain

Every row above runs out in the same spot. A domain can't tell you whether this claim should go through, and that's the question AbuseZero was built to answer. You don't have to build your own abuse prevention system to get it answered, or spend 26 hours a year reading rejected signups.

Start with what you just built. AbuseZero checks disposable domains, mailbox aliases and mail routing, and there's no list for you to keep current. That's the small part. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and a domain list is about as single as a check gets. Those signals are read together, never one at a time. You also get a proprietary algorithm, with AI that checks the claim again. When the email address is the thing that keeps changing, AbuseZero recognizes repeat devices across new accounts, and creating a fresh account isn't enough to erase previous activity.

Your server makes one API call before the free benefit goes out and gets a clear allow or deny, under rules you control. For the second way to lose, Observe mode shows you what would be denied before anyone is blocked. The quickstart walks you through your first benefit.

Frequently asked questions

Will blocking disposable email stop repeat free trials?

It stops people using the services on your list. Anyone with a second ordinary mailbox gets through, which is why unique emails don't stop repeat trials either.

Are email forwarding services the same as disposable email?

No. A forwarding address leads to someone's real inbox and can last for years. A throwaway inbox is made to be abandoned.

How often does a disposable domain list need updating?

Weekly is a sensible place to start, and it never finishes. If nobody will own that job, keep the list in logging mode.

What can I use instead of a disposable email blocklist?

Decide at the moment the benefit goes out. AbuseZero evaluates each claim and returns allow or deny, and you can start with how to write a one account per person policy.

Stop guessing who gets your free credits

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.