Back to Blog

How to stop repeat signups on a free email API tier

Repeat free accounts eat shared sending capacity and drag down paying senders' deliverability. What it costs, which basic fixes break and what to do first.

You made the call in one afternoon, and it was a reasonable one: free accounts would send from the same IP pool as everyone else. A second pool meant extra cost for a few hundred hobby projects, so you wrote "2,500 emails a month, free forever, no card" on the pricing page and went back to the SDK.

Eleven months later, a customer on your $40 plan writes in: "Our password resets have been landing in spam since Tuesday. 40 of our users are locked out and they're emailing me. What changed on your end?"

You didn't change anything. Then you open the pool's numbers and find that the IP carrying those resets also carried mail from free accounts you've never heard of.

That's email API free tier abuse, and it rarely looks like an attack. This is a scenario, so swap in your own numbers: 400 paying senders at $40 a month ($16,000 in revenue), each sending about 1,000 emails a day, an assumed sending cost of $0.40 per 1,000 emails, and 15 people each running 120 free accounts. Honest free accounts are left out to keep the sums short.

  • 15 people × 120 accounts = 1,800 free accounts
  • 1,800 accounts × 2,500 emails = 4,500,000 emails a month
  • 4,500 batches of 1,000 × $0.40 = $1,800 a month

That's $21,600 a year. If you burn $9,000 a month, it's 2.4 months of runway spent on 15 people, who pay $0.

The invoice is the part you can at least read. Those emails leave from the same IPs as your customers' password resets, at 150,000 a day (4,500,000 ÷ 30). Assume the stacked accounts draw complaints at 1.2% and your paying senders at 0.02%.

  • Paying senders: 400,000 emails × 0.02% = 80 complaints a day
  • Repeat accounts: 150,000 emails × 1.2% = 1,800 complaints a day
  • The pool: 1,880 ÷ 550,000 = 0.34%, up from 0.02%

Yahoo's sender requirements, enforced since February 2024, tell every sender to keep their spam rate below 0.3%. Yahoo measures against mail delivered to the inbox, so this sum is a rough guide. In the chart, the flat line is that 0.3%, and your pool crosses it at about 1,500 accounts.

Pool complaint rate, illustrative00.050.10.150.20.250.30.350.40300600900120015001800Complaints, %Repeat free accounts
Pool complaint rate, illustrative00.10.20.30.4060012001800Complaints, %Repeat free accounts

Say your workers clear 100 emails a second from one shared queue. One person's 300,000 emails (120 × 2,500) take 3,000 seconds, or 50 minutes, and a password reset stuck behind them can arrive after a 30-minute link has expired.

So 31 customers ask for a month's credit (31 × $40 = $1,240). You rent a clean pool of 8 IPs at $35 each ($280 a month), and new IPs take weeks of warming. With the $1,800 in sending, that's $3,320, just over a fifth of your revenue. 12 customers leave, and nobody moves email providers for fun: $480 a month gone, or $5,760 a year.

Then you delete all 1,800 accounts, and the costs keep running. Complaints don't disappear with the accounts that caused them, so assume six weeks of recovery with your customers' mail paying for it. And 1,800 complaints a day is 54,000 addresses a month on your suppression list. If that list is shared across accounts, someone who complained about a free account's mail can stop getting a paying customer's receipts.

Now you've got a decision to make this week. You can close the free tier, which is how most of those 400 customers found you, or add a card requirement and go back on what you promised. The line you wrote eleven months ago is still on the pricing page.

Why email API free tier abuse gets past your signup form

A free tier on an email API is sending capacity, handed out per account. Each new account gets a fresh 2,500 emails and a key, so 120 accounts add up to 300,000 emails with every account under its limit. Your metering counts usage inside an account, and this usage is spread across accounts. Getting a key in under a minute is the point of a developer product, and that speed serves repeat signups just as well.

The obvious fix in this business is a verified sending domain: no DNS records, no sending. Keep it, because it stops people who can't show control of any domain. It doesn't limit free accounts, though. One person can control many domains.

New account, new key2,500 free emailsSends the whole allowanceSent from shared IPsComplaints pile upPassword resetSame shared IPsSpam folder or delayRepeat accountYour email APIMailbox providerPaying senderRepeat accountYour email APIMailbox providerPaying sender
Newaccount,newkey2,500freeemailsSendsthewholeallowanceSentfromsharedIPsComplaintspile upPassword resetSamesharedIPsSpamfolder ordelayRepeataccountYouremailAPIMailboxproviderPayingsenderRepeataccountYouremailAPIMailboxproviderPayingsender

What this post covers

One thing: the same sender collecting your free tier more than once. Complaint limits, bounce handling and rules about what people may send are a separate job.

Basic fixes for email API free tier abuse, and how each breaks

Each of these does catch something. Start with unique emails, which compare text. Gmail ignores dots, and plus-tagged mail reaches the same inbox, so one mailbox can look like many addresses.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny second real inboxDevelopers whose company mail filters your codeYour own sending
Unique emailsThe same address twiceEvery different addressAlmost nobodyVery little
Disposable-domain blocksKnown throwaway servicesNew domains, ordinary mailboxesDevelopers using privacy forwardingA list someone updates forever
Gmail dots and plus addressingOne Gmail inbox written several waysA second real mailboxDevelopers who keep projects on tagged addressesUpkeep as mail services change
CAPTCHASimple signup scriptsAccounts opened by handPeople using screen readersFees and lost signups
Phone requirementCasual second accountsAnyone with another numberDevelopers without a reliable mobile numberA charge for every text
Card requirementCasual second accountsAnyone with another cardThe hobbyists "no card" was forFewer signups
One per IP addressRepeat signups on one connectionAny other networkCoworking spaces and hackathon Wi-FiExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listDevelopers on company VPNsAnother list to maintain
Rate limits per keyOne key sending too fast120 keys under the limitA customer's launch-day receiptsTuning per plan
Daily sending capsOne account overrunningEach new account's fresh capA developer testing a real flowChoosing when your product stops
Smaller free tierSome volume per accountMore accounts make it upEvery honest free developerFewer reach a paid plan
Manual reviewWhat a person can spotAnything spread out slowlyWhoever looks odd to a tired reviewer1,800 accounts × 1 minute = 30 hours

Cut 2,500 emails to 500 and the same 300,000 a month needs 600 accounts instead of 120, while every honest developer loses 80% of their allowance. A disposable-domain list goes stale, and the accounts you already have keep their allowance on the 1st, because a signup rule only runs at signup. Email verification tells you someone can open an inbox, and developers can open plenty.

Stack all of it and getting a key takes a verified inbox, a puzzle, a phone number and a card. A developer comparing three APIs late at night closes the tab, and your signup chart never tells you why.

What to do about it this week

None of this stops repeat signups on its own. It limits what each one can reach.

Give free mail its own IP pool and queue. Paid mail goes first. The catch is that honest free developers now share a pool with the repeat accounts, and their first test may land in spam.

Grant the allowance at the first API key, not at signup, through one server function that writes a record. Accounts that never ask for a key cost nothing.

Hold new free accounts to a small daily cap, and let them send only to addresses they've verified until their sending domain is set up. Set the cap above what a normal test needs.

Write down the limit, then go through your past signups against it. Agencies and side projects are real reasons for a second account, so decide what you mean first.

Decide what a no looks like. Offer the paid plan and a way to reach you, because some people you turn away will be real.

A new account arrives with nothing on file tying it to an earlier claim, so the question at the moment the key goes out stays open: should this claim go through?

Before the next free allowance goes out

You don't have to build your own abuse prevention system. AbuseZero is built for the exact spot where every row in that table gave out, which is a new account that passes. Its multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. Your list of throwaway domains needs someone to keep it current, while AbuseZero checks mailbox aliases, disposable domains and mail routing. Your one-per-IP rule lands on a coworking space. AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. It recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity. And there's a proprietary algorithm, with AI that checks the claim again.

Your server makes one API call before it issues the free allowance and gets a clear allow or deny, under rules you control. Your free tier becomes a benefit with its own eligibility: one claim ever, one per calendar month or one every set number of days. Observe mode shows you what would be denied before anyone is blocked, and the quickstart takes you through your first one.

Your pools, complaint limits and sending rules stay yours. What changes is the moment someone claims the free tier.

Frequently asked questions

What is email API free tier abuse?

It's one sender opening several free accounts to get more sending than you meant to give them, on capacity and IPs your paying senders share.

Does stopping repeat signups fix my deliverability?

It removes one source of volume. Your reputation also depends on what every account sends, so complaint limits and bounce handling stay on your list.

Should I shut down the free tier?

Treat that as a last resort, and read should you remove your free tier first. AbuseZero evaluates each claim before the allowance goes out, so the free tier can stay while you fix the rest.

Protect your free tier

Keep reading

Copying your prompt…

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