List Bombing and Bot Signups: Protect Forms and Sender Reputation
Hundreds of overnight signups with odd names? That usually means list bombing. Bots push real people’s addresses into your form so those inboxes flood with your emails, and your brand ends up as the weapon. People also call it subscription bombing, and it has a knack for bad timing. Think of a small e-commerce newsletter a few weeks before a December giveaway, right when list quality and sender reputation matter most. The fix comes in three stages: spot the attack, contain it in the first hour, then layer protection onto the form.
What is list bombing and why does your form become part of the attack?
In list bombing (or subscription bombing, same thing), bots submit a victim’s real address, often lots of addresses, to lots of signup forms. The victim’s inbox fills up with confirmation and welcome emails. You’re not the target. But you’re in it anyway: your list collects fake or unwilling contacts, your messages pick up spam complaints, and your reputation pays for it.
The Spamhaus analysis of subscription bombing describes bots abusing open or poorly secured web forms. And here’s the part people miss: even lists running confirmed opt-in got hit, because the sheer volume of confirmation emails did the damage on its own. So if a web signup on your site triggers an email, that email is your responsibility.
This isn’t the same as ordinary fake email signups or someone deliberately poisoning your list. The point is to harass a third party, and you’re collateral damage (which can still feed problems like how spam traps get onto lists).
Signs of bot signups on your newsletter form
It looks like a sudden spike of signups that has nothing to do with your traffic or your campaigns. Patterns worth watching:
- a sharp jump after weeks of steady list growth;
- random strings or odd names in the name fields;
- many addresses on recently registered, disposable or short-lived domains;
- rising bounces and complaints right after welcome emails go out;
- repeated submissions in short bursts, often outside your usual hours.
The Spamhaus guidelines for large senders read a sharp increase after steady growth as a sign of one of three things: a purchased list, a compromised form, or a subscription bombing attack in progress. It also says to watch for clusters of subscribers on new or disposable domains. My quick sanity check? Put signups next to site analytics and order data from the same window. Real shoppers leave sessions and carts behind. Bots rarely bother.
The first hour: how to contain a list bombing attack
First, stop the form from sending more email. Cleaning the list comes after. In this order:
- Pause or hide the form, or swap it for a short “signups temporarily closed” message.
- Stop welcome automations for new signups.
- Do not mail unconfirmed contacts, including the giveaway announcement.
- Remove or suppress unconfirmed signups from the attack window.
- Track bounce and complaint figures over the following days.
In MailCraft, the subscriber activity log shows when the attack started and stopped, and tags and segments let you fence off those signups before any campaign goes out. Real-time bounce processing with hard bounce auto-cleanup drops dead addresses the moment they fail. Now, the temptation. You’ll want to keep the attack window in the December send “just to see who opens”. Don’t. Every unwanted message adds complaints exactly when you can least afford them.
Why the confirmation email can still hurt
Double opt-in keeps fake contacts off your active list, sure. But every confirmation message still lands in the victim’s inbox. Hundreds of those, sent to people who never asked, turn into spam complaints against your domain and your sending IP.
The Gmail email sender guidelines ask senders to confirm each recipient’s address before subscribing them, to send only to people who want the mail, and to keep the spam rate in Postmaster Tools below 0.3%. Gmail also warns against sudden volume spikes. Which is, well, exactly what an attack produces. On a shared IP the reputation damage spreads to every sender on it. So the defence has to stop bots before the confirmation goes out. Not after.
How to protect your signup form from bots: layers that work together
No single tool stops list bombing. You stack several layers, some on the website and some in the email platform:
- double opt-in as the base;
- a hidden honeypot field that humans never see or fill in;
- rate limiting per IP and per email address;
- a cap on confirmation resends to any single recipient;
- CAPTCHA as the last layer, since it adds friction for genuine subscribers.
Spamhaus recommends protecting forms with CAPTCHA and a honeypot, and throttling confirmation emails per recipient address. Honeypots, CAPTCHA and rate limits live in your website, CMS or form plugin, so that’s where you set them up. On the platform side, MailCraft adds double opt-in on embeddable forms plus hard bounce auto-cleanup. And keep the form lean. It’s worth thinking through which signup form fields to ask, and weighing double opt-in versus single for your particular list.
Keeping the list clean before the December campaign
Before the giveaway send, mail only confirmed contacts gained outside the attack window. Go through recent signups looking for disposable domains and the patterns you spotted earlier. Anything uncertain? Suppress it, don’t mail it. For the borderline cases, methods for verifying addresses without sending save you from yet another risky message.
Keep an eye on growth rate, bounces and complaints for the whole campaign, and only reopen the form once the protective layers are live. List bombing goes after someone else’s inbox. Securing your form is what keeps your own sender reputation in one piece.
FAQ
Does double opt-in stop subscription bombing?
Not by itself. It keeps fake contacts off the active list, but the confirmation emails still reach the victims and can trigger complaints. Add a honeypot, rate limits and a cap on confirmation resends.
Should I delete fake email signups or just suppress them?
Both work, as long as unconfirmed contacts from the attack window never get mail. Suppression has a slight edge, though: it keeps a record, so if the same address gets submitted again it’s recognised and blocked.
Is CAPTCHA enough to protect a newsletter form?
It helps as the last layer. But it adds friction for real subscribers and shouldn’t be your only line of defence. Pair it with honeypot fields, per IP and per address rate limits, and regular checks on list growth.


