Should you block VPN users from signing up?
Before you block VPN signups, see what it stops, who it turns away without a word, what it costs to maintain and which options treat real people better.
You've read the cancellation email three times now, and it still doesn't say why. It's from a team on your $149 plan, 14 months in, the kind of customer who replies to your product emails. You open their exit survey. Reason: "Other." Comment: blank.
You write to the person who signed up. "Sorry to see you go. Was there anything we got wrong?" Nobody answers on Tuesday, or on Wednesday. By Thursday you've stopped refreshing your inbox and started reading logs, because $149 × 12 is $1,788 a year and you'd like to know why it left.
You find it at 11 a.m. The previous Friday at 4:17 p.m., someone with an email at that company tried to sign up three times in under two minutes. All three attempts ended on a page you wrote nine days before that: "Signups aren't available from this network." A new hire on the company VPN, you'd guess. You'll never be able to prove that's why the team left, and there's nobody left to ask.
That team is made up, and so are the numbers below.
You turned that block on for a good reason. Your free plan costs about $1.50 an account in model usage, and last month you counted 500 accounts that looked like the same handful of people coming back. That's 500 × $1.50 = $750 a month, or $9,000 a year, which is 18 days of runway if your company spends $15,000 a month. So when you ask whether to block VPN signups, start from the fact that both answers cost money. Here's one month with the block on:
2,000 signups attempted
240 on a VPN (12%), all refused
150 of those were repeat accounts
90 were real people
Saved: 150 x $1.50 = $225
Never earned: 90 x 4% conversion = 3.6 customers
3.6 x $39 a month x 14 months = $1,966
Still paying: (500 - 150) x $1.50 = $525The $225 is the best case, since someone refused at the form can come back on another connection that evening. The $1,966 is revenue, before what it costs to serve those customers, and it goes missing again next month. You won't see it go. Those 90 people never got an account, so they aren't in your churn report or your support queue. Your signup chart dips a little and you put it down to fewer fake accounts.
So on Thursday afternoon you've got a choice to make. Take the block off and go back to paying $750 a month for people who were never going to buy. Or leave it on, keep paying $525 anyway, and keep turning away strangers who'll never tell you they were there. Meanwhile the free plan that brought you most of your customers has become the thing you argue with yourself about.
Why blocking VPN signups catches the wrong people
A VPN tells you how someone connected. You wanted to know who they are and whether they've had your free plan before, and a VPN answers neither.
One VPN address is shared by many strangers at once, so blocking it is a decision about a crowd. That crowd includes staff on a company VPN who aren't allowed to switch it off, consultants connecting through a client's network and developers who run one all day out of habit. It includes people on hotel Wi-Fi, and people in countries where a VPN is how they reach foreign software at all. If you sell to developers or remote teams, these are your buyers.
The block also misses most of what you built it for, because a repeat account doesn't need a VPN. In the scenario above, 350 of the 500 came from ordinary home and mobile connections and the block never touched them. The list behind it starts going stale the day you buy it, too. Providers add addresses, ranges change hands, and an office gateway hosted in a data center can look just like a commercial VPN.
Then there's fairness. Someone refused for how they connect hasn't done anything wrong, and the page they land on rarely tells them what happened. The cost of blocking real people never appears on an invoice, which makes it easy to keep paying.
Block VPN signups or try something else: four options compared
Block every VPN at signup
This does stop repeat accounts and scripts coming through the VPN addresses on your list, that same day, with very little code. It misses everything on a normal connection and every range your list hasn't picked up. It wrongly blocks the whole crowd above, usually in silence. Keeping it working means a list you pay for or update by hand, plus tickets from the few people who bother to write.
Ask people to turn the VPN off
A page that says "Turn off your VPN and try again" is kinder, because most people have a way through. It stops very little for the same reason. And it's still a wall for someone whose employer won't let them disconnect, so it needs a way to reach you.
Let them sign up and hold the free benefit
Anyone can create an account and anyone can pay. Someone on a VPN can look around, but the free credits or trial wait until they connect without it or ask you. You avoid the cost of those 150 accounts, and the 90 real people can still buy or write to you. It takes more work than a block, because you now have two paths through signup and you still need the list.
No VPN rule, and a hard cap on free spend
You block nobody. You set a monthly budget for free usage, so your worst month costs what you decided it could cost. A cap does nothing to reduce repeat accounts, and once it's reached, honest new users wait with everyone else. Keep paid usage on a separate budget with its own cap and your paying customers never get caught in it.
The other basics and how they break
Each of these catches something real, and each has people it catches by mistake.
| Basic fix | Good at stopping | Gets past it | Hits by mistake | Upkeep |
|---|---|---|---|---|
| One signup per IP | Repeat signups on one connection | Any other network | Offices, campuses, households | Exceptions and tickets |
| Email verification | Dead addresses and typos | A second real inbox | People whose code goes to spam | Deliverability work |
| Unique emails | The same address twice | One mailbox written several ways | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | Newer domains | People using privacy forwarding | A list with no end date |
| CAPTCHA | Simple scripts | People signing up by hand | Screen reader users | Fees and lost signups |
| Phone or card required | Casual second accounts | Another number or card | Students, anyone without a reliable mobile number | Fees per text, fewer signups |
| Usage caps, shorter trials | Some cost per account | More accounts make it up | Every honest user | Fewer people reach paying |
| Manual review | What a person can spot | Anything after hours | Whoever looks odd that day | Hours every month |
Reviewing just those 240 VPN signups by hand, at 90 seconds each, is 6 hours a month. And when you pile these up, honest people drop out first, because someone after free credits will put up with more steps than someone who's just curious about your product.
Those positions are our judgment, and yours will differ. Nothing on that list reaches the bottom right, though.
So should you block VPN users from signing up?
For most SaaS products, no. Let VPN users sign up and let them pay. If each free account costs you real money, make the free part wait and cap your total free spend. A hard block earns its place when you've got a legal or licensing reason to control where your product is used, and then the page should say so.
Before you change anything, find out what a block would cost you. For two weeks, log whether each signup came through a VPN, block nobody, and then count how many of those accounts went on to pay. Every paying customer on that list is someone a block would have turned away. You can't run this test once the block is on, because refused people never get the chance to pay.
Whatever you choose, never refuse someone silently, and choose the words with care.
A message you can use
We can't start a free trial on this connection. If you're on a VPN, turn it off and try again. If you can't, email us and we'll sort it out.
Even done well, you still own a list, and those 350 accounts on ordinary connections keep collecting your free plan at $525 a month. No VPN rule can tell you whether this person has already had the benefit.
Getting an answer a VPN list can't give you
A VPN list stops at the address, a per-IP limit stops at the connection and a verified email stops at the inbox. AbuseZero evaluates what all three leave open: whether this claim looks like a repeat. It sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. With multi-layer AI risk analysis, AbuseZero examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and those signals are read together, never one at a time. It recognizes repeat devices across new accounts, even when email addresses keep changing, so creating a fresh account isn't enough to erase previous activity. AbuseZero uses a proprietary algorithm, with AI that checks the claim again. You don't have to build your own abuse prevention system, or keep another list up to date.
For you, it's one API call before a free benefit goes out and a clear allow or deny, under rules you control. Your signup form stays open. Observe mode shows you what would be denied before anyone is blocked, and the quickstart walks you through your first benefit.
Frequently asked questions
Do VPN blocks stop multiple accounts?
Some of them. A block stops repeat accounts arriving through VPN addresses on your list. Anyone on an ordinary home or mobile connection gets straight through.
Should I block data center addresses and Tor as well?
Run the same test first. Office gateways and cloud desktops sit in data center ranges too, and many Tor users are there for privacy.
Can I stop repeat accounts without blocking VPNs?
Yes. Leave signup open and decide when someone claims the free benefit. AbuseZero's evaluation returns allow or deny at that moment, and your app does the rest.
Protect your free benefit without turning customers away
Start with Builder
Pay as you go. Evaluate your first claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.